The Month-End Document Handoff SOP

Purpose

To define exactly what the shop sends its bookkeeper each month, in what form, by when, and what comes back in return, so that the close runs on a fixed calendar instead of a chase.

The problem this solves is not laziness on either side. It is that a bookkeeper cannot close a month with 80% of the documents, and a partial packet feels like progress while producing none. Every missing statement stalls a reconciliation; every unexplained charge becomes a question; every question that waits a week for an answer pushes the close past the point where the numbers are still useful for a decision. Shops that close on day 10 and shops that close on day 40 usually run the same software and the same complexity. What differs is whether the handoff is a defined artifact with a due date or a series of emailed attachments.

Scope

Applies to every month, including months with no unusual activity, at any shop that uses an outside or part-time bookkeeper. Covers document collection, transmission, the question-and-answer loop, and the return deliverable.

Does not cover the mechanics of the close itself (see the month-end close checklist), the design of the accounts the documents land in, or anything tax-determinative. Where a document raises a question about how something must be treated - whether a large purchase is a repair or an asset, how a new revenue stream should be characterized - the question routes to the accountant and is answered before the close, not during it.

Roles and responsibilities

The division that matters: the owner supplies information nobody else has, and nothing else. If the owner is chasing a credit card statement, the SOP has failed. If the bookkeeper is guessing at what a charge was for, the SOP has also failed, in the more expensive direction.

The packet manifest

The packet is one folder with a fixed structure, same every month. Files named with the period first so they sort chronologically. Nothing is emailed as a loose attachment.

Statements (outside records, one file each)

1. Every business bank account statement, including accounts with no activity.
2. Every credit card and line-of-credit statement, one file per card, not a combined summary.
3. Every loan and equipment-finance statement, showing the interest and principal split for the period.
4. The merchant processor settlement summary for the period, gross and net.

Payroll

1. The payroll register for every cycle that paid in the period, plus the tax-deposit confirmations.
2. Any pay run made outside the normal cycle, with a note on what it was.

Shop-generated records

1. The invoice register for the period and the open receivables list as of the last day.
2. The bill and payables list as of the last day.
3. Receipts or invoices for anything paid by card or cash that does not carry an obvious vendor name.
4. Any sales tax return filed during the period, as filed.

Owner items

1. A short note listing owner draws and contributions made in the period.
2. A note on anything unusual: a large purchase, a new lender, a customer write-off, a new revenue type.

Twelve items. Items 1 through 10 are documents, and their presence is a yes-or-no fact anybody in the office can confirm. Items 11 and 12 are the only two that require the owner, and they are short.

The completeness gate

The gate, applied per packet, is Boolean and has no partial state: all twelve manifest items are present, or the packet is not transmitted. An item that genuinely does not exist for the period is present as a one-line note saying so, which is different from being absent.

This is stricter than it first looks and it is the whole point of the SOP. A packet missing one card statement is not 92% of a packet. The reconciliation for that card cannot start, the categorization behind it cannot start, and the bookkeeper will either park the work and lose the context or start it and redo it. The cost of holding the packet one extra day to get the statement is one day. The cost of sending it incomplete is usually a week, because it re-enters the queue.

If a document is genuinely unobtainable by the due date - a lender that mails statements slowly is the common case - it is transmitted as a known gap with an expected date, and the bookkeeper sequences around it deliberately rather than discovering it.

Procedure

Step 1. Business day 1: freeze and assemble. Stop back-dating into the closed period. The office admin downloads all statements available, pulls the invoice and receivables registers, and starts the manifest checklist. Anything not yet posted by the outside party is noted with the date it is expected.

Step 2. Business day 2: chase the gaps. Only the manifest items still missing get chased, and only by the office admin. This is the step shops skip, and skipping it is why packets go out incomplete: everyone assumes the missing statement will appear on its own.

Step 3. Business day 3: transmit. The packet goes across complete, in one transmission, with the manifest checklist on top showing every item as present or as a noted gap with a date. Log the transmission. One transmission per month keeps a clean record of what the bookkeeper had when they worked.

Step 4. Business days 4 and 5: bookkeeper works and produces the open-questions list. The bookkeeper reconciles and categorizes, and every item they cannot resolve from the packet goes on one list, sent as a single batch on business day 5. Not a drip of individual messages. A batched list gets answered in one sitting; drips get answered never.

Step 5. Business day 7: owner answers the list. Every question, in writing, in one pass. Questions the owner cannot answer without a treatment decision get marked for the accountant in this same pass rather than sitting unanswered.

Step 6. Business day 9: draft statements back. The bookkeeper returns the profit and loss statement, the balance sheet, the reconciliation reports showing the unexplained difference on each account, and the list of any open items still unresolved with an owner and a date on each.

Step 7. Business day 10: owner review and sign-off. The owner reads the statements against the prior month, asks about anything that moved without explanation, and signs off. Sign-off is a real event: it marks the period closed and it is what makes back-dating into it a violation rather than a habit.

Step 8. Archive. The packet, the questions list with its answers, and the final statements are stored together for the period. Keep the records that support an item of income, deduction or credit at least until the period of limitations for the related return has run, which is the general recordkeeping instruction in IRS Publication 583; your accountant will tell you where your own periods land.

Worked example: one month's filled-in manifest

A two-crew shop, closing a month with nothing dramatic in it. The manifest as transmitted on business day 3:

Twelve items, twelve accounted for, one of them a noted "none." The packet transmitted on time.

The open-questions list came back with 6 items on business day 5. Four were owner-answerable and were answered on day 7: two unlabeled fuel-card charges that turned out to be a crew member filling a personal vehicle, one supply-house charge that belonged to a specific job and needed the job tag, and one transfer that looked like revenue and was actually an owner contribution.

The remaining 2 escalated to the accountant, both from item 12. The large tool purchase raised a repair-versus-asset question, and the customer write-off raised a timing question about when a receivable is treated as uncollectible. Neither is a bookkeeping call and neither is the owner's call. Both were sent to the accountant on day 7 alongside the owner's answers, and both came back before the day 9 draft, so the close held its calendar.

What the two escalations cost, and what they would have cost. Handled inside the calendar, they took the accountant a short exchange and delayed nothing. Handled the way most shops handle them - the bookkeeper picks a treatment, the owner never sees the question, and the accountant discovers it at year end - the tool purchase gets restated and the write-off timing gets moved, both of which change the prior year's profit and both of which mean the statements the owner reviewed and signed off on were wrong. The value of routing a treatment question when it appears is not the answer, it is that the answer arrives before you have built a year of decisions on the guess.

The one number to watch on this SOP. Track the count of open questions per month, nothing else. Six on a two-crew shop with two off-book-looking transfers is ordinary. The same shop returning 20 questions a month means the source discipline has slipped upstream - receipts not being captured at the counter, personal spending on a business card, job tags not applied at invoicing - and the fix is at the point of the transaction, not in the close. A count that climbs three months running is the signal, and it is visible only because the questions come as one batched list rather than a scatter of messages nobody counts.

References

• IRS Publication 583, Starting a Business and Keeping Records, on how long to retain records supporting a return
• See related: Month-End Close Checklist for a Service Business, Monthly Financial Review Process, The Reconciliations That Actually Catch Things, How to Ask Your Accountant a Question Worth Their Time