A payroll process that lives only in one person’s head tends to break at the worst time: when a manager submits hours late, a new employee misses the first paycheck, a tax filing deadline overlaps with a holiday, or someone has to step in unexpectedly. This article gives you a practical payroll SOP for small businesses that you can reuse each pay period and each month. It is designed as a working checklist rather than a theory piece, so you can adapt it to manual payroll, spreadsheets, or payroll software while keeping approvals, timing, recordkeeping, and exception handling clear.
Overview
This payroll standard operating procedure is a simple operations blueprint for running payroll consistently. It works best if you assign an owner for each step, document deadlines in one place, and review the process whenever your team, tools, or compliance requirements change.
A useful payroll SOP should answer five questions:
- What happens: the sequence from time collection to payment, filing, and recordkeeping.
- Who does it: payroll admin, owner, bookkeeper, manager, HR, or backup approver.
- When it happens: cutoff dates, review windows, pay dates, funding deadlines, and month-end tasks.
- What gets checked: hours, pay rates, PTO, deductions, tax setup, approvals, and final reports.
- What happens if something goes wrong: missed hours, reversals, off-cycle payroll, final pay, and corrections.
For most small businesses, the cleanest way to document payroll is to split the SOP into two layers:
- Per-pay-run workflow: the repeatable checklist used every weekly, biweekly, semimonthly, or monthly payroll.
- Monthly control workflow: the review steps that confirm payroll posted correctly, liabilities are tracked, and records are complete.
Before using the checklist below, define these core SOP settings in your own version:
- Pay frequency and pay dates
- Payroll cutoff date and time
- Timecard approval deadline
- Who can edit time, pay rates, and employee profiles
- Who gives final payroll approval
- How new hires, terminations, bonuses, reimbursements, and deductions are entered
- Where payroll reports and supporting documents are stored
- Who acts as backup if the main payroll owner is unavailable
If your deadlines are still informal, it helps to standardize them before documenting the procedure. A separate cutoff policy can support this workflow, especially for timecards and corrections. See Payroll Cutoff Dates Explained: How to Set Deadlines for Timecards, Approvals, and Corrections.
Checklist by scenario
This section gives you the reusable checklist itself. You can convert it into a payroll operations checklist, a spreadsheet tab, or a task list in your project management tool.
1) Standard per-pay-run payroll workflow
- Confirm the payroll calendar.
Verify the pay period start and end dates, the payroll processing date, the funding date if using direct deposit, and the pay date. - Collect time and attendance data.
Pull approved hours from your timesheet, scheduling, or attendance system. Include regular hours, overtime, shift differentials if used, paid leave, unpaid leave, and any manual adjustments. - Review hours for obvious errors.
Look for missing punches, duplicate entries, unusual overtime, negative balances, and employees with zero hours who should be paid. - Confirm manager approvals.
Make sure each supervisor has approved time for their team by the stated cutoff. If approvals are missing, escalate before payroll is finalized. - Add employee changes effective in the period.
Enter new hires, terminations, rate changes, bonuses, commissions, reimbursements, garnishments, benefit deductions, or one-time adjustments. Document who approved each non-routine item. - Check onboarding completion for anyone being paid for the first time.
Confirm tax forms, pay method setup, pay rate, start date, and classification are complete. Use a separate onboarding process if needed: New Employee Payroll Checklist: Forms, Tax Setup, Direct Deposit, and First Pay Run. - Review worker classification before processing payments.
Confirm employees are in payroll and contractors are handled through the correct payment workflow. Misclassification creates avoidable confusion and downstream corrections. See 1099 vs W-2 Payroll Rules: Worker Classification, Taxes, and Payment Differences. - Calculate gross pay.
Verify salaried pay, hourly pay, overtime, PTO, and any variable earnings are calculated according to your internal rules and applicable requirements. If hour calculation is a recurring issue, review How to Calculate Payroll Hours Correctly: Breaks, Rounding, Travel Time, and Training Time. - Review deductions and withholdings.
Check pre-tax and post-tax deductions, benefit amounts, repayment schedules, and tax setup for any changed employee profile. - Run a pre-processing audit report.
Compare current gross wages, net pay, taxes, and employee count against the prior pay run. Investigate anything unusual before approval. - Approve payroll internally.
Require signoff from the designated approver, ideally someone other than the person who entered all adjustments. - Process payroll.
Submit payroll by the required deadline and confirm funding requirements for direct deposit. If direct deposit setup is new or changing, review Direct Deposit Setup Guide for Employers: Requirements, Timelines, and Common Problems. - Distribute pay information.
Provide pay stubs or payroll summaries through your standard employee access method. - Store payroll reports and support files.
Save payroll register, tax summary, deduction reports, time approvals, adjustment approvals, and any exception notes in a consistent folder structure. - Log issues for follow-up.
If there were manual workarounds, missing approvals, or pending corrections, record them in an issue log instead of relying on memory.
2) Monthly payroll control workflow
- Reconcile payroll totals to your books.
Match payroll expense, employer taxes, benefit deductions, reimbursements, and cash outflows to your accounting records. - Review payroll tax liabilities and filing status.
Confirm liabilities have been recorded, scheduled, or remitted through your normal process. - Check PTO and leave balances.
Review accruals, carryovers, and manual adjustments for reasonableness. If your policy depends on accrual calculations, see PTO Accrual Calculator Guide: Vacation and Sick Leave Accrual Methods for Small Employers. - Audit employee master data changes.
Review any updates to names, addresses, withholding settings, bank details, pay rates, and job status. Verify there is support for each change. - Review exception trends.
Identify repeated late timecards, frequent manual edits, recurring overtime surprises, or the same location or manager causing delays. - Confirm document retention.
Make sure payroll reports, approvals, and supporting records for the month are stored in the correct location with clear naming conventions. - Update the payroll issue log and SOP notes.
If the same problem appears more than once, revise the SOP rather than accepting it as normal.
3) Exception workflow: payroll changes outside the normal run
Most payroll stress comes from exceptions, not routine runs. Your SOP should include mini-checklists for the situations below.
New hire before first payroll
- Confirm start date and worker classification
- Enter pay rate or salary and department coding
- Complete tax setup and direct deposit or check setup
- Confirm eligibility dates for deductions or benefits
- Make sure the employee appears on the pre-processing register
Termination or final pay
- Confirm termination date and whether unused PTO must be addressed under your policy and applicable rules
- Calculate final wages, approved expenses, and any authorized deductions
- Check whether final pay timing differs from normal payroll timing in the relevant jurisdiction
- Disable future recurring earnings or deductions after the final run
- Document equipment return or other non-payroll offboarding items separately from wages
For a closer review of timing issues, see Final Paycheck Laws by State: Termination Pay Deadlines and What Employers Must Include.
Missed hours, underpayment, or overpayment
- Identify the root cause: late approval, setup error, duplicate entry, wrong rate, or tax issue
- Decide whether the fix belongs in the next payroll or requires an off-cycle correction
- Document employee communication, approval, and accounting impact
- Retain the correction record with the original payroll support
A dedicated correction process helps here: Payroll Error Correction Guide: Missed Hours, Overpayments, Underpayments, and Tax Fixes.
Compliance or policy change
- Update pay rates, deduction logic, or local rules before the effective date
- Test payroll setup in advance if software changes are involved
- Communicate changes to managers and employees when needed
- Update the SOP, not just the current pay run
Minimum wage updates are a common example: Minimum Wage by State and City for Payroll: What Employers Need to Update Each Year.
4) If you are still using manual payroll or spreadsheets
A spreadsheet-based payroll SOP needs stronger controls because manual steps create more room for error. Add these steps:
- Lock formula cells and maintain a change log
- Version-control each payroll file
- Require second-person review of rates, formulas, and tax tabs
- Keep a master employee data sheet separate from pay-period input sheets
- Archive a PDF or static copy of each final payroll calculation
If your manual system is becoming hard to maintain, review Manual Payroll vs Payroll Service: When Small Businesses Should Switch.
What to double-check
These are the control points worth reviewing every cycle, even when payroll feels routine. They catch a high share of avoidable problems.
- Employee list changes: Anyone newly added, terminated, or returning from leave.
- Pay rate changes: Effective dates, retroactive updates, and manager approvals.
- Time anomalies: Unapproved overtime, incomplete breaks, unusually high hours, or missing PTO coding.
- Net pay outliers: Sharp increases or decreases compared with the previous run.
- Deductions: New benefit elections, ending deductions, garnishments, or one-time repayments.
- Tax setup: Employee profile changes that affect withholding or location-based setup.
- Payment method: New direct deposit instructions, rejected deposits, or employees who need a paper check.
- Approvals: Evidence that managers approved time and authorized non-routine pay items.
- Journal entry mapping: Correct departments, classes, locations, or general ledger accounts.
- Retention: Supporting reports saved where someone else can find them later.
A practical habit is to compare each payroll against the previous similar payroll, not just the immediately prior one. For example, compare biweekly payroll to the prior biweekly cycle with a similar staffing pattern. This makes outliers easier to spot than reviewing one payroll in isolation.
Common mistakes
The goal of a payroll SOP is not just to document the happy path. It is to reduce recurring mistakes that come from rushed approvals, unclear ownership, and missing controls.
- Cutoff dates exist on paper but are not enforced.
If managers can submit time late without consequence, payroll becomes a rolling correction exercise. - One person controls everything with no backup.
A workable SOP names both an owner and a backup, with access instructions and calendar reminders documented. - Employee changes are made without support.
Rate changes, bonus payments, and deduction edits should have a clear source and approver. - Hours are accepted without review.
Time systems reduce effort, but they do not eliminate the need to review overtime, rounding, travel time, and exceptions. - Corrections are handled informally.
A Slack message or hallway conversation is not a correction record. Use a standard issue log. - Payroll records are saved inconsistently.
When support is scattered across email, desktop folders, and screenshots, month-end review becomes slower and riskier. - The SOP is too generic.
A document that says “process payroll and review for accuracy” is not an SOP. It needs named steps, owners, deadlines, and outputs. - The SOP is never updated.
Payroll procedures drift when software changes, responsibilities move, or the business adds locations, pay types, or leave policies.
If you want your SOP to stay useful, make it easy to follow under real conditions. That usually means shorter steps, clear deadlines, linked forms, and a visible exceptions process.
When to revisit
This payroll SOP should be treated as a living business operations template. Revisit it before seasonal planning cycles and whenever workflows or tools change. Small updates made on time are easier than rewriting the process after a major payroll problem.
Review and refresh your payroll process workflow when any of the following happens:
- You change payroll software, time tracking tools, or accounting integrations
- You move from manual payroll to a more automated process
- You add a new location, state, city, pay schedule, or employee group
- You introduce new earnings types, bonuses, commissions, or reimbursement rules
- You assign payroll duties to a new admin, manager, or finance lead
- You see repeated errors, late approvals, or off-cycle corrections
- You update PTO, attendance, overtime, or onboarding procedures
- You prepare for year-end cleanup, staffing changes, or a busy seasonal period
A practical update routine looks like this:
- Run one payroll using the current SOP. Mark every step that caused confusion, delay, or rework.
- Meet with the people involved. Include payroll, a manager approver, and whoever handles accounting or HR inputs.
- Revise the checklist. Tighten deadlines, clarify ownership, and remove steps that no longer match reality.
- Test the revised workflow on the next cycle. Watch for bottlenecks, especially around time approvals and last-minute changes.
- Publish the new version in one place. Retire outdated copies so people do not follow conflicting instructions.
If you need one final rule for maintaining a small business payroll procedure, use this: every recurring payroll problem should lead to either a checklist step, a control point, or a clearer owner. That is how a payroll SOP becomes a reliable operating system instead of a document no one opens.