A bookkeeping SOP is a written document that spells out exactly who records which transactions, on what schedule, and with what supporting evidence attached. It turns bookkeeping from something only the owner understands into a repeatable process anyone trained on it can follow correctly — including a version of the business without you in the room.
Most small businesses never learn how to build a bookkeeping SOP until they need one — a busy week, a new hire, an owner on leave — and discover the "process" only ever existed as habits in one person's head.
Key takeaways
- A bookkeeping SOP names each recurring task, who owns it, how often it happens, and what evidence proves it was done.
- Without a written SOP, quality depends entirely on one person remembering the right steps — which breaks the moment that person is unavailable.
- A good SOP is detailed enough that someone with basic training could follow it without asking clarifying questions.
- For a small business, an SOP can be a one-page table — it doesn't need to be a long formal document to do its job.
- Review and update it whenever software, staff, or your chart of accounts change, and at least once a year regardless.
- A checklist is usually a subset of an SOP: the steps alone, without the ownership, evidence, and review rules that make it enforceable.
What a bookkeeping SOP actually does
A bookkeeping SOP is a written procedure stating who records each transaction type, on what schedule, using what steps, and with what evidence attached before it counts as complete. Build one by listing recurring tasks, assigning an owner to each, and defining the evidence and review step that closes the loop.
The word "procedure" makes it sound heavier than it needs to be. For a small business, an SOP is really just an answer, written down, to a question that usually only lives in the owner's head: if I disappeared for two weeks, would the books still get kept correctly? If the honest answer is no, that's the gap an SOP closes.
The four elements every task needs
Every recurring bookkeeping task — recording a sale, logging an expense, reconciling a bank account, closing the month — needs the same four pieces of information written down. Missing any one of them is usually where an SOP quietly stops working.
- The task, defined precisely. Not "handle sales" but "enter each day's POS sales total into the ledger before closing out."
- The owner. One named person or role responsible, even if others can technically do it. Shared ownership with no single name attached tends to mean nobody does it.
- The frequency. Daily, weekly, monthly — stated explicitly, not implied. "Regularly" is not a frequency.
- The evidence required. What has to be attached — a receipt, an invoice, a bank statement — before the task counts as actually done, not just started.
A checklist is the list of steps to tick off — useful, but it's usually a subset of a full SOP. A complete SOP also names who owns each task, what evidence is required, how exceptions get handled, and who reviews the result. The ownership and evidence rules are what make a process survive a staffing change; the checklist alone doesn't.
Building your SOP, task by task
Start by listing every recurring bookkeeping task your business actually has — not an idealized list, the real one. Most small businesses find it's shorter than expected: daily transaction entry, receipt attachment, weekly or monthly reconciliation, month-end reporting, and maybe payroll if there are employees.
| Task | Owner | Frequency | Evidence required | Reviewed by |
|---|---|---|---|---|
| Enter daily sales | Shift lead | Daily, end of day | POS summary attached | Owner, weekly |
| Log and attach expenses | Whoever makes the purchase | Same day | Receipt or invoice attached | Owner, weekly |
| Reconcile bank account | Owner or bookkeeper | Monthly | Bank statement matched, zero difference | Owner |
| Run month-end reports | Bookkeeper | Monthly, within 5 business days of close | Income statement, balance sheet filed | Owner |
That table, filled in for your actual tasks, is a working SOP. It doesn't need narrative paragraphs to be complete — it needs to be specific enough that someone unfamiliar with the business could follow each row correctly.
How detailed should it be?
Detailed enough that someone with basic training could complete the task correctly on their first attempt, using only the SOP and the software — but not so long it goes unused. A good test: hand it to a new hire and watch whether they can do the task without asking a clarifying question that a well-written SOP should have already answered. If they get stuck, that's a gap to fill, not a sign to abandon the document for something less specific.
Over-specifying is its own failure mode. An SOP that documents which browser tab to click in exhausting detail becomes something people stop reading. Aim for the level of detail a competent, newly trained employee actually needs — not the level a first-time computer user would need.
A five-person hair salon doesn't have a written manual — it has a single printed page taped near the front desk: who enters the day's bookings and product sales (the closing stylist), by when (before locking up), and what has to be attached (the POS Z-report, photographed and linked to that day's entry). That page has survived two staff turnovers without a gap in the daily record, because it named an owner, a deadline, and required evidence — the three things a task list alone doesn't guarantee.
Keeping the SOP current
Review it whenever software, staff roles, or your chart of accounts change, and at minimum once a year even without an obvious trigger. An SOP that no longer matches how the software or team actually works is worse than no SOP at all — it trains new staff to follow steps that don't apply anymore, which is often harder to unlearn than starting from nothing. Tie the review to a fixed point, like your annual pre-filing tax season checklist, so it doesn't get forgotten between busy periods.
Reyuko gives an SOP's rules something to actually enforce, rather than staying words on a page. Role-based access — seven preset roles including Owner, Accountant, Sales, and Cashier, each with a Full/Read/None matrix across every module — means an SOP that says "the cashier enters daily sales but doesn't edit posted journal entries" can be set up to match, not just requested. Every transaction can carry up to eight attached files, so the "evidence required" column of your SOP maps directly to something reviewable inside the transaction itself, and a Trial Balance or Income Statement report gives the owner a fast way to check the "reviewed by" step actually happened.
None of this requires a paid plan — roles, attachments, the ledger, and core reports are all in Reyuko's free edition.
Write your own SOP
Show the steps
- List every recurring bookkeeping task your business actually performs — no more than a dozen for most small businesses.
- For each task, write down the owner, the frequency, and the exact evidence required before it's "done."
- Add who reviews the completed task, and on what schedule.
- Put it somewhere it will actually be seen — printed near a register, pinned in shared software, not buried in a folder nobody opens.
- Test it: hand it to someone else and watch where they get stuck. Fix that gap.
- Put a review date on it — a year from now, or sooner if anything about your software, staff, or accounts changes first.
For two worked examples built from this exact framework, see a sample SOP for daily transaction recording and a sample SOP for month-end close. Once the SOP exists, it's also what makes delegating bookkeeping to staff safe rather than risky — and skipping this step is one of the more common mistakes businesses make going digital.
Reyuko