A month-end close checklist organizes the source records, reconciliation work, outstanding questions, and review responsibilities for the period being closed. Agree the process with the qualified person maintaining your books so document collection and completed accounting review remain distinct.
The close-packet index below helps an owner supply information and track what is ready, missing, or awaiting a decision. It supports the review without prescribing accounting adjustments, tax treatment, or filing steps.
Agree the period and responsibilities
Confirm the month being reviewed, the accounts included, the document submission date, and who prepares and reviews each task. Ask how late documents will be handled and how changes to a reviewed period should be recorded.
Use a schedule that fits the business and the professional doing the work. A generic deadline doesn’t establish that records are complete. If a required document is missing, the close checklist should show the exception instead of hiding it behind a completed status.
Define the scope of the packet before requesting documents. Identify the entities or activities included, the accounts that need review, and any new account or process introduced during the month. Ask the professional responsible whether the usual checklist needs changing. A familiar monthly folder can look complete while omitting a new source of transactions.
Separate preparing, reviewing, and approving work. In a small business, the same person may perform more than one role, but the checklist should still show what each stage means. Agree who answers operational questions and who decides accounting treatment. That distinction prevents a document collector from marking a review finished simply because all requested files have arrived.
Assemble the source records
Gather statements for relevant bank, card, loan, and payment-processing accounts. Include sales records, customer invoices, supplier bills, and other support requested by the person maintaining the books. Use full statements rather than relying only on a current balance screenshot.
The IRS emphasizes preserving supporting documents behind business entries. Organize the packet so the reviewer can connect an entry to its source. A folder of receipts is difficult to review when filenames and references give no indication of the period or transaction.
Organize the documents around the period and the accounts being reviewed. Use filenames or an index that makes the source, coverage dates, and document type clear. Confirm that files open and include all relevant pages before passing them on. A partial statement can leave the reviewer unable to understand the activity even when the closing balance is visible.
Keep the source document separate from a working note about it. If a transaction needs explanation, put the question in the index and point to the original record. Don’t alter a statement to make it easier to interpret. Ask for the missing information through the responsible person and preserve the answer with the review trail.
Assign reconciliation to the appropriate person
Reconciliation compares the accounting records with supporting account information and explains differences. Ask the bookkeeper which accounts require reconciliation and what evidence will show that the work has been completed and reviewed.
Baker Tilly’s month-end checklist includes account reconciliations and review of receivable information among its tasks. Your checklist needs to reflect your business, not every item in a larger organization’s process. Don’t enter an unexplained adjustment simply to make a difference disappear.
Ask what the reviewer needs from you when a difference appears. You may be able to identify a transaction, locate a document, or confirm an operational fact. Supply that information without deciding on an adjustment you aren’t qualified or authorized to make. The record should connect the question, the supporting answer, and the professional’s resolution.
Give unresolved differences an explicit status. Distinguish work that hasn’t started from work that has been prepared but still needs review. If the professional explains that a report remains provisional, preserve that qualification when sharing it internally. A polished report should not obscure the fact that some supporting work is still open.
Review unpaid items and unusual activity
Ask for the outstanding customer and supplier items relevant to your accounting system. Identify disputed invoices, missing documents, refunds, and unfamiliar transactions for investigation. Give each question an owner and a date for response.
Separate a factual explanation from an accounting decision. You may know what was purchased or which project an invoice belongs to. The bookkeeper or CPA should determine the appropriate accounting treatment when judgment is needed. Don’t make tax-deduction or filing decisions from this checklist.
Look for the business explanation behind an item before drawing a conclusion from its age or description. Ask whether an invoice is disputed, awaiting documentation, partly settled, or affected by a correction. Record what the person responsible actually confirms. The close packet should not convert a guess about a customer’s intention into an accounting fact.
Keep the response process visible. Assign someone to obtain missing operational information, and give the bookkeeper or CPA the records needed for their review. If an item carries into the following month, preserve its original reference so the question doesn’t become disconnected from the transaction. Don’t recreate it as a new issue without its history.
Build a close-packet index
The index shows what is present, who handles it, and what remains unresolved. Put document locations in the reference column so the reviewer doesn’t have to search multiple message threads.
| Packet item | Document reference | Preparer | Reviewer | Status or open question |
|---|---|---|---|---|
| Bank and card statements | ______ | ______ | ______ | ______ |
| Sales and payment records | ______ | ______ | ______ | ______ |
| Supplier bills and expense support | ______ | ______ | ______ | ______ |
| Relevant account reconciliations | ______ | ______ | ______ | ______ |
| Outstanding customer and supplier items | ______ | ______ | ______ | ______ |
| Proposed adjustments and approval | ______ | ______ | ______ | ______ |
| Reports and review notes | ______ | ______ | ______ | ______ |
Use precise statuses: missing document, awaiting answer, prepared, or reviewed. A file being uploaded doesn’t mean its contents have been checked. Keep those stages separate.
Use the reference column to make the packet navigable. The reviewer should be able to move from the index to the exact statement, invoice, reconciliation, or explanatory note. A folder name that contains many unrelated files may not be specific enough. Add a document name or other clear reference when that would prevent searching through message threads.
Keep an exception note for each item that is not ready. Identify what is missing, who is obtaining it, and when it will be checked again. Ask the professional responsible how the unresolved item affects completion of the close. A complete index can accurately show an incomplete review; its purpose is to describe the state of the work, not make every row look finished.
Review the reports before relying on them
Ask the professional responsible for the books which reports are ready and which remain subject to unresolved items. Review unfamiliar balances and significant changes with them. Request an explanation you can connect to the underlying records.
Use the completed review to inform later planning, but keep past activity separate from a cash forecast. The site’s 90-day cash-flow planning resource addresses the forward-looking task. A month-end packet documents what happened and what still needs resolution. It doesn’t establish future revenue, payment timing, or tax savings.
Ask for explanations that distinguish a business event from an accounting presentation issue. If a balance looks unfamiliar, identify the exact line and period rather than asking generally whether the report is correct. Keep the answer with the version reviewed. If the report is revised, make sure anyone using the earlier version knows which one is current.
End the review with an agreed list of completed work and open questions. Confirm how later documents or corrections should be handled and who can authorize changes. Use the reviewed information as an input to future planning while preserving its limits. A close packet provides a record of the past period; the owner and advisers still need to assess the assumptions behind future decisions.
What belongs in the close packet?
- Source statements and transaction support.
- Reconciliations and outstanding-item reports.
- Questions, owners, and documented approvals.
- Reviewed reports and remaining exceptions.
Close the period with exceptions visible
Agree which tasks are finished and how any unresolved item will be handled. Save the reviewed packet and the version of the reports used for decisions. A dependable close record lets you see what was checked, who checked it, and which questions still require professional follow-up.
References
Internal Revenue Service: What kind of records should I keep?
