Payroll SOP Examples: 5 Procedures That Get Everyone Paid Right

Payroll SOP examples are only worth copying if they match how the money actually moves in your business, where hours arrive as text messages and commissions get assembled out of chat threads. Below are 5 payroll SOP examples covering the full run: field time capture, the commission and bonus run, deductions and chargebacks, contractor and offshore payments, and the payroll close with its audit. Every one of them was built alongside operators, including a weekly commission run that ate 3 full days and took 85 minutes to describe out loud.

Key takeaway: Every number on a pay stub is a claim, and the procedure exists to hold the proof behind it. When that proof lives in one person's memory instead, the errors stay invisible until they are expensive. One owner who took over a money process after a key employee left found $500 to $800 leaking every week.

What Is a Payroll SOP?

A payroll SOP is a written procedure for one recurring step in paying people: the owner, the schedule, the steps, and what counts as proof that a number is right. That last part separates payroll from most documentation. Hours, commissions, and deductions are assertions about the past, and each one rests on evidence or on somebody's recollection.

When we document a pay process, we capture the purpose, the decision points, and the step-by-step, recorded from the person who runs it rather than the person who manages it. The anatomy matches what real standard operating procedures look like in any department, except that a broken step here lands in somebody's paycheck on Friday.

Here are the 5 procedures, with the failure each one prevents.

Notice how little of that is arithmetic: 4 of the 5 exist to produce or protect evidence.

Payroll SOP Example 1: Time Capture from the Field

In one field service company we documented, office staff clock in by geofence: they arrive, the system knows, nobody types anything. The field crews had nothing. Helpers clocked in by texting a selfie in front of the house number, and somebody in the office read timestamps off the photos into a spreadsheet.

That gap is not about technology. The geofence had run upstairs for years; nobody had decided the rule for a helper standing in a driveway at 7:12am. Reading timestamps off photos by hand is a process running on spreadsheets past the point where they hold.

Settle the judgment calls before you write steps: drive time, waiting on a customer who is not home, a job that rolls into next week. One client asked it best: how do we stop people having to remember the process?

1. Name one clock. Hours enter in one place, because a second channel is a second system to reconcile.
2. Make the capture passive. A tap or a geofence, anything that removes the typing and the remembering.
3. Write the payable-hour rules. Drive time, wait time, rollovers: decided once, in writing.
4. Set the correction path. Missed punches are normal, so name who fixes them, by when, with what proof.
5. Freeze on a named day. Hours lock at the cutoff and late items land in the next run.

An hour is payable when the written rule says it is, not when the person rebuilding the week decides it is. Write the crew-facing half in the language the crew actually speaks: on teams working in Spanish, an English-only procedure is decoration.

Payroll SOP Example 2: The Commission and Bonus Run

A bookkeeper walked us through her weekly commission run on a screen share, and describing it took 85 minutes: 2 reports merged with a VLOOKUP because the export strips the job IDs, chat threads searched to find who the helper on each job was, receipts hunted through a hardware store login she did not have. The company runs on more than 20 group chat threads, and two people rebuild the same picture out of hundreds of messages every week. Watching his own process, the owner said quietly that this is a 3-day job every week.

The system of record for who gets paid was a group chat, and nobody in the building had ever called it that.

Bonus rules drift faster than commission rates. In one field service business a per-van revenue target moved from 4,000 to 6,000 dollars mid-conversation, and the small incentives (10 dollars for a customer review, 15 with a photo) lived in whoever remembered them. In a retail group, salespeople did their quarterly bonus math at home on a calculator, because the number was buried in a report nobody surfaced.

Write the procedure so none of that has to be reconstructed:

1. Write the plan first. Rates, thresholds, splits, and effective dates in one dated document before the period starts, because a target that changes verbally mid-sentence is a future argument.
2. Name the record that decides. If the helper's name exists only in a chat thread, that thread is your payroll system.
3. Document the repair. When an export destroys job IDs and someone restores them with a lookup, write it as a named step with the file and the match key.
4. Show people their own math. Publish each person's number, or they will rebuild it at night and dispute it Monday.
5. Split assembly from approval. Whoever builds the numbers is not whoever releases them.

Every commission should trace to a job somebody closed and a payment somebody recorded, which is why jobs never flipped to done leave techs unpaid through no fault of their own, and why the invoicing and collections procedures upstream decide whether this one can run.

Payroll SOP Example 3: Deductions, Chargebacks, and Money Owed Both Ways

Money moves in both directions between a company and its people, and the second direction rarely gets documented. In one company, field workers charge 50-dollar embroidered uniforms against future pay, and a debt-tracking spreadsheet carries a tab for a tech who wrecked a van and left owing $7,400. That tab exists because nobody decided in advance what happens to an open balance when a person walks.

The other direction leaks just as quietly: new hires there waited up to 3 weeks for a company card, bought parts and gas on personal cards, and got reimbursed by chasing receipts. One procedure covers both.

1. Sign at the event. The uniform charge, the advance, the damage: agreed and dated when it happens, not litigated on payday.
2. Keep one visible ledger. A balance somebody carries in their head is a dispute waiting for a bad week.
3. Answer the limit question once. Ask your payroll provider what a single check may carry, then write the answer in.
4. Reimburse on the payroll rail. Same cutoff, same run, coded to a job or a category.
5. Write the exit rule. Decide what happens to an open balance at termination before you need to know.

No deduction reaches a paycheck without a dated agreement behind it. Reimbursements are the mirror image; the accounting SOP examples cover the expense and payables side that feeds this one.

Payroll SOP Example 4: Contractor and Offshore Payments

Contractors, agencies, and offshore staff get paid on a different rail from employees, which is why they get forgotten: no pay cycle protects them automatically. In one business we documented, the books are run by an offshore bookkeeper, and that 85-minute walkthrough happened at 1am her time.

Keep this procedure short and separate.

1. Keep the rails separate. One list, one cadence, one approver, never a tab on the payroll workbook.
2. Set both clocks. Write the cutoff in each time zone, because an ambiguous deadline across a border is a missed deadline.
3. Require a scoped invoice. Approval means matched to a scope, a job, or a rate sheet.
4. Grant access early. Receipts, portals, and logins bite hardest when the person blocked cannot walk to anyone's desk.

Whether a person belongs on this rail at all is a question for your accountant, not for whoever assembles the run.

Payroll SOP Example 5: The Payroll Close and Its Audit

An owner took over a money process himself for a few weeks after a key person left, assuming it was fine. He found $500 to $800 vanishing every week through skipped audit steps, missed part deductions, and small overpayments. His math on the call: up to $10,000 a month, not from theft, but from a process nobody followed.

A payroll nobody audits pays out its errors on schedule, every single week.

The close catches all of it, and it stays short when the other 4 procedures work:

1. Run the variance check. Compare this run to the last by person, and explain every outlier before money moves.
2. Audit the deductions. Parts, advances, chargebacks, uniforms: a missed deduction is invisible, because nobody calls to report being overpaid.
3. Reconcile pay to closed jobs. Every payment traces to a closed job, and every closed job produced the pay it should have.
4. Log every exception. One list is your leak report; a monthly read shows the same steps getting skipped.
5. File the evidence. Register, source reports, and approvals in one dated place a stranger could open.

Nobody releases a payroll they cannot explain, line by line, against the run before it. One company already owned a feature that tracked unsettled jobs and nobody used it. The tool exists; the step is not in anybody's written week.

How Do You Write a Payroll SOP?

You write a payroll SOP by recording one real run, then structuring what you captured. Do not ask the person who runs payroll to write down how they do it. Memory produces a tidy version of the work, wrong in the places that cost money: the second export, the workaround, the file only they know about.

The method runs in 5 steps, and each fills a section of a basic SOP template:

1. Record one full run. Screen share, practitioner narrating, first report pulled to last approval.
2. Write the purpose first. One sentence on what the procedure protects and who it affects.
3. Mark every decision point. When is an hour payable, when is a commission earned, who approves a chargeback.
4. Write steps as action headers. Each opens with a verb and passes the glance test.
5. Test it on the backup. If someone who has never run payroll cannot finish a run from the document alone, it is not done.

One honesty rule while you write: if the recording never answered a question, the SOP does not get to pretend it did. Efficiency and completeness pull against each other on every page, and the tiebreaker is the backup, meaning enough detail that a stand-in finishes the run and not one word more.

Keep the rate table out of the procedure. Percentages, thresholds, and tax parameters change on a schedule the process does not, so one rate change makes a combined document suspect. Put them in a dated appendix with an owner and a review date, the discipline behind keeping one current copy of every document.

---

What an Undocumented Payroll Process Actually Costs

Start with time, because time is the argument that wins budget. A 3-day weekly run is roughly 12 days a month spent reassembling a week that already happened. Assign minutes to every step, multiply by frequency and headcount, and the case for fixing it writes itself.

The second cost is the leak itself: $500 to $800 a week, up to $10,000 a month, all of it recovered the moment somebody ran the audit steps again.

The third cost arrives without warning. The bookkeeper who assembled every commission run at one field service business was leaving in 3 weeks, and her replacement's whole training was watching her narrate screen shares. When we studied 16 small businesses across 68 roles and 461 process areas, an average of 27% of the work was documented, and half the role areas had nothing at all.

Getting that knowledge out of one head and into a procedure the next person can follow is the work The Systems Effect does. Start it yourself, and start small: record one real run of the pay process that would hurt most if its owner quit on Friday, usually the commission run.

Frequently Asked Questions

What should a payroll SOP include?

A payroll SOP should include the purpose, a named owner and schedule, the decision points where judgment is required, the step-by-step captured from the person who runs it, a cutoff, and what counts as proof that each number is right. If it does not say what done looks like, it is a description, not a procedure.

How do you document a commission process?

Record one full run instead of asking for a written summary. In one company, describing the weekly commission run out loud took 85 minutes and surfaced 2 merged reports, a lookup written to repair an export that strips job IDs, and chat threads used to identify who worked each job. Then write the plan (rates, thresholds, splits, dates) as its own document and name the one system that decides who worked what.

How do you capture hours for field employees who never touch an office computer?

Give the field the same passive capture the office already has: a geofence or a single tap on a phone, so a timestamp exists that nobody typed. One company we documented had geofenced office staff while helpers clocked in by texting selfies in front of house numbers, and someone read the timestamps into a spreadsheet. Pair the tool with a written rule for what counts as a payable hour.

What happens when the person who runs payroll leaves?

Whatever is not written down leaves with them. In one business, the exiting bookkeeper trained her replacement entirely through screen shares because the process had never been documented, and she was gone in 3 weeks. Record a real cycle before the notice period ends: a narrated screen share is enough raw material to build the procedure from.