Bookkeeping firm SOPs should start with the steps every client goes through each month: statement intake, conversion and review, export, and client questions, in that order. Write each one as a numbered list that fits on a page, test it on someone who has never done the task, and update it the day a tool or a step changes.
Which bookkeeping firm SOPs come first?
Write first the procedures that every client passes through every month, because they repeat most and break most quietly. Intake comes first, then conversion and review, then export, then client questions. Procedures for rare events, such as offboarding or year end, can wait until the monthly ones are written and in use.
The order follows the flow of work. A missing intake step means statements arrive late or in the wrong folder, and everything after it slips. A missing review step lets errors through. Export and client questions matter just as much but fail more visibly, so they are easier to notice without a written procedure.
A priority table
The table is an example order for a small firm. The lengths are targets, not limits.
| Order | SOP | When it runs | Target length |
|---|---|---|---|
| 1 | Statement intake | Every client, every month | 8 to 12 steps |
| 2 | Conversion and balance check | Every statement | 6 to 10 steps |
| 3 | Categorization review | Every client month | 8 to 12 steps |
| 4 | Export to the accounting system | Every client month, per system | 5 to 8 steps |
| 5 | Client questions | Every month with open items | 5 to 8 steps |
After these five, add onboarding. If you take on clients in groups, the guide to onboarding multiple clients at once shows how an onboarding procedure handles several new clients in the same weeks.
Why not write everything at once
A firm that tries to write twenty procedures in a month usually finishes none of them well. Write one, use it for a full month, fix what the month revealed, then write the next. Five procedures that people follow beat twenty that sit in a folder.
Intake SOP for client statements
The intake procedure covers how statements reach the firm and where they go: the request, the reminder, the folder, the file name, and the check that every expected account arrived. It ends when each client's statements for the month are filed and counted. Nothing in it should depend on remembering which client sends what.
Steps an intake SOP usually includes
- On a fixed day, open the list of expected statements per client and account.
- Send the monthly request to clients who do not send statements on their own.
- File each statement that arrives in the client's folder for that month.
- Rename the file to the firm's pattern, for example client, account last four digits, and period.
- Tick the account off the expected list.
- On a fixed later day, send one reminder listing only the missing accounts.
- Escalate anything still missing to the client lead.
Record the client-specific facts elsewhere
An SOP should not say "Client A sends statements by email on the 5th." Facts like that belong in the client's own notes and the expected-statements list. The SOP says "check the expected list", and the list carries the detail. That keeps one procedure valid for every client.
Conversion and review SOPs for each client month
The conversion and review procedures cover the core of the close: turning statements into transactions, proving each statement balanced, categorizing, and checking the result before release. Split them in two. Conversion is mechanical and can be handed to anyone. Review needs judgment and a named reviewer.
The conversion SOP
The conversion procedure says how statements are converted, what to check afterwards and what to do when a check fails. A useful version has these steps:
- Upload the month's statements for the client.
- Confirm every statement passed its balance check.
- If one failed, find the gap before going further.
- Confirm the opening balance matches last month's closing balance.
- Mark the client ready for categorization.
In AutoBankConvert, a statement is not marked done until its opening balance plus transactions equals its closing balance, so step two becomes a matter of reading the result rather than doing the arithmetic.
The review SOP
The review procedure lists what the reviewer checks, in order. Start with lines the rules were unsure about, then large or unusual amounts, transfers between the client's accounts, and the holding account. Deposits nobody can explain are the most common holding item; the guide to unidentified deposits on bank statements gives the steps to resolve them, and the review SOP can link to it instead of repeating them.
Where the two meet
Write down how a client moves from one to the other, such as a status in your task list. The handoff is where work stalls if nobody owns it.
Export SOP per accounting system
The export procedure covers how a finished month leaves your tools and lands in the client's books. Write one per accounting system you support, not one per client, because the steps depend on the system. Each version should name the file format, where to import it, and how to confirm the import matched.
What every export SOP should cover
- Which file to produce, and from which batch or client.
- Where in the accounting system the import happens.
- How to check that the imported count and total match the export.
- What to do if the import rejects lines.
- Where to file a copy of what was exported.
AutoBankConvert exports per client or per batch in the format each client's books already use, for QuickBooks and Xero. Write the export SOP around those two paths if those are the systems your clients use, and keep a separate short version for any other.
Check the import, every time
The step most often skipped is confirming that what arrived in the books matches what left. A rejected line during import is easy to miss on a busy day. The SOP should make the comparison a required step with a tick box.
Client question SOP: who asks, when and how
The client question procedure sets one way of asking clients about unclear lines: who sends the questions, how often, in what format, and what happens to a line while the answer is outstanding. Without it, clients receive questions from several people at random times and answer few of them.
Rules worth writing into the procedure
- One sender per client. The client lead sends all questions, whoever found them.
- One message per month. Questions are gathered and sent together on a fixed day.
- One line per question. Date, amount, description as printed, and a plain question.
- Offer choices where possible. "Was this a loan, or a payment from a customer?" gets faster answers than "What is this?"
- A holding rule. Unanswered lines stay in the holding account, with the date asked.
- A follow-up date. One reminder, then the item goes on next month's list and into the client report.
Track what questions cost
Questions take time on both sides. If you track time per client, log question handling separately; the guide to time tracking for bookkeepers explains how to set up categories that show it. Clients who generate many questions every month may need a scope or fee conversation.
How long should a bookkeeping SOP be?
A bookkeeping SOP should fit on one page: a title, the trigger that starts it, a numbered list of steps, and the result that shows it is done. Most good procedures run between five and twelve steps. If a procedure needs more, it is usually two procedures, or it is carrying client facts that belong elsewhere.
A template that keeps it short
- Name. What the procedure is for, in a few words.
- Trigger. What starts it, such as "a client's statements are all filed".
- Owner. The role that runs it, not a person's name.
- Steps. Numbered, each starting with a verb.
- Done when. The check that shows it finished.
- Last checked. The date someone last ran the procedure exactly as written.
Test on someone new
Ask a person who has never done the task to follow the procedure exactly while you watch. Every place they hesitate is a missing step or an unclear word. The guide on how to scale a bookkeeping practice treats this kind of test as the point at which a procedure becomes ready to hand to a hire.
Mistakes that make procedures long
Long procedures usually explain why each step exists, include screenshots of every menu, or list exceptions inline. Put the reasoning in a separate training note, use one screenshot only where a step is hard to find, and move exceptions to the client notes.
Keeping firm SOPs current after a tool or staff change
Procedures go stale when a tool changes, a step moves or a person leaves, and a stale procedure is worse than none because people trust it. Update the procedure the same day the change happens, give each one an owner, and run every procedure exactly as written at least once a year.
Triggers for an update
- A tool is added, replaced or redesigned.
- A step is added or removed after a review or a quality check.
- A new hire hesitates at the same step as the last one did.
- A client type appears that the procedure does not cover.
Who owns each procedure
Give every procedure one owner, usually the person who runs it most often. The owner updates it and records the date. When the owner leaves, assigning a new owner is part of their handover.
Keep old versions
When you change a procedure, keep the previous version with its date. If a client asks how something was done two years ago, the old version answers the question.
Written procedures get shorter when tools do more of each step. To see how intake, conversion and export work for a full client list, get started with AutoBankConvert.