Accounting SOP Examples: 5 Procedures Every Small Business Needs

A useful accounting SOP example shows 3 things: who owns each step, what counts as proof the money moved, and what the right call is when the numbers do not tie out. Below are 5 accounting SOP examples every small business needs: the weekly payables run, payroll and commission assembly, cash and check reconciliation, expense and reimbursement handling, and month-end close. Each skeleton comes from real documentation work, including one owner whose unfollowed payables process was quietly costing up to $10,000 a month.

Key takeaway: An accounting SOP is a written procedure for one recurring money process, captured from the person who runs it: purpose, decision points, and step-by-step. The 5 procedures below are where small businesses leak the most, and the failure pattern is always the same: the process lives in one person's head, and the leak starts the day that person is out.

What Is an Accounting SOP?

An accounting SOP is a standard operating procedure for one recurring money process: it names who runs the process, when it runs, the exact steps, and what counts as proof that the money moved. That last part separates accounting SOPs from every other kind. Each step either has evidence behind it or a leak behind it.

When we document a money process for a client, we capture 3 things: the purpose (what this process protects), the decision points (where someone has to make a judgment call), and the step-by-step, taken from the person doing the work, not the person managing it. The anatomy matches what real standard operating procedures look like in any department. The difference in accounting: every skipped step has a dollar value, whether anyone measures it or not.

Each example below names the failure it prevents and hands you a skeleton to copy. Here is the set at a glance:

Accounting SOP Example 1: The Weekly Payables Run

One owner we worked with took over the payables process himself for a few weeks after a key employee left. He found $500 to $800 vanishing every single week through skipped audit steps, missed part deductions, and small overpayments, which adds up to as much as $10,000 a month.

The money was never stolen: it leaked through a process nobody followed.

A payables SOP makes that leak impossible to miss. Here is the skeleton:

1. Pull the open bills. Same day every week, one list, from one place. Payables runs on a schedule, not on whoever asks loudest.
2. Audit before you approve. Check each bill against what was actually delivered, received, or worked. This is the step busy weeks skip, and where the leak starts.
3. Apply the deductions. Parts charged to jobs, advances, chargebacks. A missed deduction is invisible, because no vendor calls to report an overpayment.
4. Pay in one sitting. One approver, one cutoff, every week.
5. Log paid against expected. The difference is your leak report; review it monthly.

Notice that 3 of the 5 steps are checks, not payments. That is deliberate. Paying bills is easy; the SOP exists for the auditing a tired week wants to skip.

Example 2: Payroll and Commission Assembly

The most expensive undocumented process we see in small businesses is payroll assembly. One bookkeeper we interviewed spends 3 full days every week building commissions: merging 2 reports with VLOOKUP because the export strips the job IDs, scrolling group chats to find each job's helper, then cross-referencing a payment app, receipts, and 5 spreadsheets before anyone gets paid. Describing the process on a screen share took 85 minutes. The owner watched parts of his own process for the first time in years and finally understood the 3 days.

Payroll should be arithmetic, but in most small businesses it is archaeology.

She was also leaving in 3 weeks, and her replacement's only training was watching those same screen shares, because none of it was written down. A payroll SOP prevents both problems at once:

1. Freeze the inputs. Hours, closed jobs, and adjustments land by the same cutoff each week. Late items move to next week; they do not reopen this one.
2. Pull every report once. If an export corrupts something, write the repair into the SOP as a named step instead of leaving it in one person's head.
3. Assemble in one workbook. One tab per input, one summary tab, saved to the same place every week.
4. Reconcile pay to jobs. Every commission traces to a closed job, and every closed job traces to a recorded payment.
5. Split assembly from approval. The person who builds the numbers is not the person who releases them.

Write this SOP while the person who runs payroll still works for you, and make the outputs visible. In another business, salespeople recalculated their own commissions at home on a phone calculator because the number they were owed was buried in a report nobody surfaced. When people cannot see how their pay is assembled, they rebuild the process themselves, badly, on their own time.

Example 3: Cash and Check Reconciliation

Card payments record themselves: the money and the data arrive in the same second. Cash and checks do not. In one field service company we documented, anyone could mark a job paid cash with nothing in the bank yet, so the office lived in a permanent chase: chasing deposits, chasing check photos, chasing techs to ask what happened on Tuesday.

A payment is real when the money is in the bank, not when someone marks it paid. Every step in this SOP exists to close the gap between those 2 moments:

1. Record the promise at close. Method, amount, and who took it, logged the moment the job closes.
2. Capture proof same day. Checks photographed, cash counted against the day's jobs before anyone goes home.
3. Deposit on a fixed schedule. Daily, or a named day. The older cash gets, the less anyone can prove about it.
4. Match deposits to jobs. Line by line, weekly, by someone who did not take the payments.
5. Flag the stale. Any job marked paid with no matching deposit after 7 days goes on one list, owned by one person.

This procedure covers money already promised at the job. Invoicing, payment recording by method, and the collections ladder sit upstream with procedures of their own: the accounts receivable SOP examples cover that side of the ledger.

Example 4: Expense and Reimbursement Handling

Expense handling is where small leaks hide in plain sight. In one company, new field hires waited up to 3 weeks for a company card, so they bought parts and gas on personal cards while the office reimbursed them by chasing receipts. The same business tracked chargebacks in a spreadsheet with a tab for a tech who wrecked a van and left owing $7,400.

An expense SOP has one goal: every dollar that leaves gets coded to something, the same week it leaves.

1. Issue cards before day one. A company card on day 1 costs less than 3 weeks of chasing personal-card receipts.
2. Capture the receipt at purchase. Photo to one place, coded to a job or a category, the same day.
3. Reimburse on a fixed day. Weekly, through payroll, never on demand.
4. Track chargebacks on one ledger. Uniforms, advances, damage: one sheet, visible to the employee it applies to.

The card step is really a provisioning problem wearing an accounting costume, and it pairs with the day-one setup procedures in these HR SOP examples. The deeper rule is the single ledger. Once reimbursements live in text threads and chargebacks live in someone's memory, you are back to chasing, the tax an undocumented process collects every week.

Example 5: Month-End Close

The close is the monthly stop where you prove the numbers tie out. Skip it and errors do not disappear; they compound quietly until something forces a dig. One ops leader we interviewed rebuilds his company's reporting pipeline roughly every 6 weeks, and each break means re-auditing 6 weeks of numbers he can no longer trust. The longer you run without closing, the deeper the dig.

A month-end close SOP for a small business fits on one page:

1. Close on a fixed day. Pick the day and keep it, even when the month was ugly. Especially then.
2. Reconcile every account. Bank, cards, payment apps, payroll. No account is boring enough to skip.
3. Chase the unmatched. Anything that does not tie out gets a named owner and a deadline, not a shrug.
4. Lock the period. No backdated edits after close. Corrections happen in the current month, visibly.
5. Report the same numbers. Same format every month, so drift shows up as drift.

The close is also where the other 4 SOPs get graded. The payables leak report, the stale cash list, and the reimbursement backlog all surface here. A skipped close does not just hide accounting errors; it hides every process failure upstream of it.

How Do You Write an Accounting SOP from Scratch?

You write an accounting SOP by recording the person who actually runs the process doing it once, then structuring what you captured. Do not ask anyone to write down how they do their job. Memory produces a cleaner, shorter version of the work, wrong in exactly the places that cost money. Recording produces the truth, workarounds included.

The method we use with clients runs in 5 steps, and each one fills a section of a basic SOP template:

1. Record one real run. A screen share of the real weekly run, the practitioner narrating what they check and why.
2. Write the purpose first. One sentence on what the process protects and what leaks when it is skipped. People do not follow procedures they do not understand the point of.
3. Mark the decision points. When is a payment real, what does approved mean, what gets escalated to whom. In accounting, this is where money is won or lost.
4. Write steps as action headers. Each step opens with a verb and passes the glance test: a reader glances at any single step and knows what to do.
5. Test it on the backup. Hand the draft to someone who has never run the process. If they cannot complete a run from the document alone, the document 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. Flag the gap and go ask. The full method is in our guide on how to write an SOP.

Be honest about the cost too. Recording one real run is cheap; turning that narration into steps a stranger can follow takes longer than the run itself, and it is the half that gets postponed. Do not start with month-end close either: if payables and payroll still live in one person's memory, a fixed close day only surfaces the mess faster. Document the weekly processes that feed the close first.

---

The Cost of an Unfollowed Accounting Process

The owner who took over his own payables found $500 to $800 leaking every week, up to $10,000 a month, and every dollar of it came back the week someone ran the audit steps again. An unfollowed accounting process never announces itself. It shows up later, as a bank balance lower than the work you did.

This is not rare. 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. The pattern behind the number is always the same: the process lives with one careful person, and it works right up until they leave.

That is the work The Systems Effect exists to do: interview the people who run a business's money processes and turn what they say into procedures the next person can follow. You do not need a consultant to start, though. Pick the one accounting process that would hurt most if its owner quit on Friday, usually payroll, and record a single real run of it this week. The leak does not wait, and neither should the document.

Frequently Asked Questions

What should an accounting SOP include?

An accounting SOP should include the purpose (what the process protects), a named owner and schedule, the decision points where judgment is required, the step-by-step captured from the person who runs the process, and what counts as proof: bank deposits, matched reports, filed receipts. If the document does not define what done looks like, it is a description, not a procedure.

How detailed should a bookkeeping SOP be?

Detailed enough that a competent backup can complete the process from the document alone, with the author out of the building. Spend the detail where money moves or judgment is required: approvals, deductions, reconciliation. Skip narrating every button in the software. Each step should pass the glance test: readable at a glance, executable without re-reading the page.

What accounting processes should a small business document first?

Start with the process that would hurt most if the one person who runs it disappeared, which is usually payroll or payables. Payroll errors touch every employee and compound weekly, and payables is where quiet leaks live: one owner found $500 to $800 a week disappearing through skipped audit steps alone. Document one procedure, prove a backup can run it, then move to the next one.

How do you keep accounting SOPs current when software changes?

Keep the process and the software instructions in separate documents. One company we worked with had fused them into a single giant document, so every time the vendor changed a screen, the whole SOP went stale at once. Write the SOP at the level of steps, owners, and decisions, link out to short software how-tos, and review it on triggers: the tool changes, the process fails, or the person running it changes.