Writing the month-end close SOP that lives in your head
Your close process exists — in your head, in muscle memory, in a sticky note from 2023. The moment you hire, subcontract, or take a real vacation, that becomes a problem. Turning rough process notes into numbered SOPs and checklists is one of the most-cited practical AI uses for bookkeepers, because the AI supplies structure while you supply every actual step.
You are helping a bookkeeper turn tribal knowledge into a written procedure someone else could follow. I will describe my month-end close in rough notes; your job is to structure it cleanly — not to add steps I didn't mention. My rough notes: {{close_notes}} Software involved: {{software_stack}} Who will use this SOP: {{audience}} Produce: 1. A numbered SOP with one action per step, in the order I described, each tagged with the software it happens in and roughly when in the close it occurs. 2. A checklist version (task / owner / done) I can paste into a doc. 3. A section titled "Gaps I noticed" — places where my notes skip something a new person would ask about (for example, "you didn't say where the loan statements come from"). Phrase each gap as a question back to me. Hard rule: the SOP must contain only what I told you. Do NOT fill gaps with invented steps or generic best practices — that's what the questions section is for. Keep the language exact and boring: "Reports > Reconciliation reports > select month" beats "review the reconciliation module."
Fill in your details and the prompt updates live — then copy.
Month-End Close SOP — excerpt 4. Reconcile business checking (QuickBooks Online, day 2). Accounting > Reconcile > select checking account. Enter ending balance and date from the bank statement PDF in Google Drive > [Client] > Statements. 5. Book the payroll journal (QuickBooks Online, day 2). Pull the monthly journal report from Gusto and enter it as a journal entry, matching the template from last month. Gaps I noticed: - You mention chasing missing docs — where do you track which docs are outstanding per client? - Who reviews the close before the summary email goes out, or does it ship unreviewed?
The full workflow
- Voice-memo or type your close process for one client, stream-of-consciousness.
- Run the prompt and answer the "Gaps I noticed" questions.
- Re-run with your answers folded in until the gaps list is empty.
- Test the SOP on the next close yourself before handing it to anyone.
- Store it where the team works and date it — SOPs rot quietly.
Watch out for
The failure mode is subtle: AI-invented steps sound plausible ('verify accruals') and a new hire will follow them off a cliff. The no-invented-steps rule in the prompt matters — check the output against it.
Keep client names generic in the notes ("Client A, restaurant") — a process document doesn't need real names to be useful, and a consumer AI chat shouldn't have them.
Where this comes from
Every use case on this site is grounded in real reports from working bookkeepers — not invented by us.