The Monthly Close SOP

Purpose

To close each accounting month as a two-party handoff with defined gates: the bookkeeper assembles and certifies, the owner reviews and adjudicates variances, and the period is then locked. This SOP governs the handoff and the acceptance criteria, not the task list. It assumes a task-level close checklist already exists and is being worked; what it adds is who certifies what, what has to be true before the packet moves, and which variances stop the close until someone explains them.

The failure it exists to prevent is the close that completes on time with every account reconciled and no one having decided what the month meant.

Scope

In scope: the assembly, certification, review, adjudication, sign-off, and locking of a single accounting month, plus the escalation of variances found during review.

Out of scope, routed elsewhere: tax positions, filing decisions, entity or owner-compensation structure, and year-end adjusting entries. Those go to the accountant who signs the return. Nothing in this SOP is tax advice, and a bookkeeper following it must not be asked to make a tax determination.

Applies to any month in which the business transacted, including a month with no revenue. A dead month still gets closed and locked, because a gap in the sequence destroys every trailing comparison downstream of it.

Roles and responsibilities

If one person holds two of these roles, the roles do not merge. The certificate is still produced, the adjudication is still written down, and the sign-off is still a separate act with a date on it. A close where the same person assembles and accepts without recording either step has no control in it at all.

Timing

Close runs on the first five working days after month end. Phase 1 occupies working days 1 to 3, Phase 2 lands on working day 4 or 5, and the lock happens the same day as sign-off. The date matters less than holding it. A close date that moves is a close date that eventually stops arriving.

Procedure

Phase 1: assembly and certification (bookkeeper, working days 1 to 3)

1. Reconcile every bank, credit card, and merchant-processing account through the last calendar day of the month. Reconciled means every item on the statement exists in the books at the same date and amount, and nothing in the books is absent from the statement. An unexplained difference is never plugged to a holding account to make the close move; it goes on the exceptions list as an open item and blocks certification.
2. Confirm job-to-invoice completeness. Every job marked complete in the month has an invoice, a documented reason it was not billed, or an entry on the exceptions list. Unbilled completed work is the highest-cost item this SOP is designed to catch, because it never appears as a loss on any statement.
3. Code every transaction against the written coding rule. Anything the rule does not clearly place goes on the exceptions list without being coded provisionally. A provisional code becomes a permanent one roughly every time.
4. Post recurring entries the shop has agreed to run monthly, on the same basis as prior months.
5. Produce the packet and issue the completeness certificate (below). The certificate is a statement of fact, not an opinion on the numbers.

Gate 1: the packet does not move to the owner until the certificate is complete. An incomplete packet reviewed anyway trains everyone that the gate is decorative.

Phase 2: review and adjudication (owner, working day 4 or 5)

1. Confirm the certificate, item by item, before reading a single number. A statement built on an unreconciled account is not evidence.
2. Clear the exceptions list. Each item gets a decision. Where the same category appears three or more times in one month, amend the coding rule rather than deciding it a fourth time.
3. Run the variance gates (below) against every expense category. Each triggered category gets a written explanation of one or two sentences, and a classification: structural (the cost has changed and will persist) or episodic (a one-month event that will not repeat).
4. Act on structural causes within this cycle. Episodic causes get recorded and re-checked next month; a cause classified episodic twice in a row is structural and must be reclassified.

Gate 2: sign-off is blocked while any triggered category lacks a written explanation and a classification. "I know what that was" spoken aloud does not clear the gate. The point of writing it down is that next quarter you will compare against it.

Phase 3: sign-off, lock, archive

1. Sign off with a date. One line, recorded in the file: month, date signed, and the one action carried out of the review.
2. Lock the period. After the lock, nothing new is dated into the month. A late document lands in the current month with a note pointing back.
3. Archive the packet as a fixed copy, not a live report that will re-render differently later. A live report re-run in six months reflects every entry made since, which means you can no longer see what you actually signed.

The close packet

Seven items, every month, in the same order:

1. Completeness certificate
2. Profit and loss statement for the month, with the trailing three months alongside, stated in percentages of revenue
3. Balance sheet as of the last day of the month
4. Receivables aging
5. Payables aging and committed cash for the next four weeks
6. Exceptions list, with each item's proposed treatment
7. Variance sheet: every expense category, its trailing three-month average, its current value, and the gate result

Variance gates

Both gates are evaluated per expense category, per closed month, against a trailing three-month average that excludes the month being closed. They are joined by OR: a category escalates if either fires.

• Gate A (share of revenue): the category's share of revenue moves more than 3.0 percentage points from its trailing three-month average. Ties do not escalate; a category landing exactly at 3.0 points is noted on the variance sheet and watched, not explained.
• Gate B (absolute size): the category's absolute value moves more than 25% from its trailing three-month average.

Two gates rather than one, because each catches what the other misses. Gate A finds a category eating a larger slice at flat revenue. Gate B finds a category holding its slice while revenue jumps, which is a real change in what you are spending that a percentage view hides completely.

Correction step size, when a structural cause requires a price or estimate change: for a documented input-cost change, such as a supplier price increase you have in writing, pass through the full measured change once. For a variance inferred from a single month of job data, adjust by half the measured gap per cycle and re-measure the following month. Applying full gain to an inferred variance is how a price book oscillates for a year without settling, because you are correcting for noise as though it were signal.

Worked example: the variance sheet, filled in

Revenue for the closed month came in at 1.12 times the trailing three-month average. All figures are percentages of revenue in that month or that trailing period.

Read direct labor carefully, because it is the row that justifies having two gates. Its share of revenue moved exactly 3.0 points, which under a strictly-greater-than rule does not trigger Gate A, and a reviewer running one gate would have passed it. But revenue itself was 12% higher, so the absolute labor spend moved 27% of 1.12 against 24%, which is up about 26%, and Gate B fires. Materials fires on both: 4.0 points on share, and 26% of 1.12 against 22% is up about 32%.

Vehicle and fuel is the mirror case worth noticing on the same sheet. Its share of revenue did not move at all, and its absolute value rose about 12%, which is exactly what you expect when volume rises and no gate should fire. That row is what a normal response to a busy month looks like, and it is the comparison that makes the other two rows meaningful.

The bottom line the sheet implies: the five categories consumed 92% of revenue this month against 88% in the trailing period, so net margin fell from 12% to 8% of revenue. Because the revenue base was 1.12 times larger, absolute profit still fell about 25% despite a 12% better revenue month. That is the sentence the owner should be able to say out loud after review, and it is not visible on any single line of the packet.

Adjudication recorded at Gate 2: materials, structural - a supplier price change effective mid-month, confirmed in writing, so the price book takes the full documented pass-through in this cycle. Direct labor, episodic - overtime absorbed on the higher volume with no added headcount, re-check next month. The owner's note adds the condition that makes the classification honest: if labor fires again next month at similar volume, it is not overtime absorbing a spike, it is a capacity constraint, and it gets reclassified structural under step 9.

References

• Generally Accepted Accounting Principles (GAAP), accounting period, cutoff, and consistency concepts
• U.S. Small Business Administration (SBA), small business financial recordkeeping and internal control practices
• See related: Month-End Close Checklist for a Service Business; How to Run a Monthly Close That Takes an Hour; What the Owner Must Own and What the Bookkeeper Owns