The month-end close checklist for statement reconciliation

If you close the books without a fixed sequence, something eventually slips: a transfer counted on one side of the ledger but not the other, a statement balance a day behind where it should be, a variance nobody chased down before the file went to the accountant. A month end close checklist for bank reconciliation exists to catch these problems inside the month they happen, not two closes later, when the discrepancy has folded itself into a dozen other entries and nobody can say where it started.

Why the sequence matters

Each stage of a close depends on the one before it. You cannot reconcile a bank account against the ledger if the statement figures feeding that reconciliation have not themselves been checked. You cannot investigate a variance sensibly if you have not first ruled out the two most common causes: an unmatched transfer and a conversion error in the source data.

Running the checklist out of order does not save time. It just means you find the same error later, after it has already been used to justify three other numbers.

The checklist

The steps below cover a standard month end close for a set of bank accounts. Some businesses add a step for petty cash or merchant processor statements; the shape stays the same.

1. 1

   Gather every statement for the period

   Collect statements for every account on the books, including accounts with low activity. A missing statement is the single most common reason a close gets reopened.
2. 2

   Convert each statement into a working format

   Turn each statement document into a spreadsheet with one row per transaction and a running balance column. Keep the original document alongside the converted file so you can check either against the other.
3. 3

   Verify the running balance on every account

   Recalculate the balance line by line and compare the final figure to the closing balance printed on the statement. Treat any mismatch as a stop, not a rounding note.
4. 4

   Match transfers between accounts

   Confirm that every transfer out of one account has a corresponding transfer into another, in the same period. Flag anything that only shows up on one side.
5. 5

   Reconcile each account against the ledger

   Compare the verified statement balance to the ledger balance for the same account and date. Note the exact difference if the two do not match; do not round it away.
6. 6

   Investigate every variance

   Trace each unexplained difference to a specific transaction: a timing difference, a duplicate entry, an unmatched transfer, or a data entry mistake. Resolve it before moving to the next account.
7. 7

   Sign off and lock the period

   Record who reviewed each account and when, then lock the period in the accounting system so prior-period entries cannot be edited without a visible trail.

Matching transfers between accounts

Transfers between a client's own accounts are a recurring source of month-end variances, and they are rarely caused by anything dramatic. One leg posts on the last day of the month, the matching leg posts on the first day of the next. One account is on your desk for conversion, the other was overlooked because nobody thought of it as part of the close.

Most accounting platforms handle this with a transfer clearing account: money leaving one account is booked against the clearing account rather than closed off immediately, and the matching leg clears it back to zero once it arrives. When a transfer's second leg is missing or misdated, the clearing account does not net to zero, and that nonzero balance is exactly what tells you to go looking. It is a useful safeguard, but it only works if someone actually reviews the clearing account balance before signing off, rather than treating a small residual as immaterial. For a closer look at how to find the missing leg across several statements, see tracing transfers between accounts.

Catching what the conversion missed

Statement conversion is one stage in the checklist above, not the whole job, but it is worth doing carefully because everything downstream depends on it. Two failure modes show up often enough to check for by default.

• Digit misreads. A statement read by OCR can turn a 3 into an 8 or drop a decimal point, and the error only surfaces once the running balance stops matching the printed closing figure.
• Split rows. A transaction description that wraps onto two lines can sometimes get extracted as two separate rows instead of one, with the amount attached to the wrong row or missing from one of them entirely. The fix is not a formula that guesses which half is correct; it is checking the running balance against the statement's own figures and locating the exact row where the two diverge.
• Truncated descriptions. Codes and abbreviations that made sense on the bank's own display can lose meaning once extracted, which matters later when you are categorising transactions rather than just balancing them.

A short check table makes the verification step concrete rather than abstract:

For a fuller walkthrough of what to check and in what order, how to verify a converted bank statement in four checks covers the same ground in more depth. If a mismatch turns up and you cannot immediately see why, finding the row where a converted balance stops reconciling walks through the isolation process step by step.

Reconciling against the ledger and investigating variances

Once every statement is verified and every transfer is matched, the reconciliation itself should be quick: compare the verified statement balance to the ledger balance for the same account on the same date. A difference here usually traces to one of a small set of causes: a transaction posted to the wrong period, a duplicate entry, a transfer that has not fully cleared, or a data entry error somewhere upstream.

Write the amount of the difference down before you start looking for it. It is easy to convince yourself a small variance is immaterial and close the account anyway; that habit is how a one-off rounding error turns into a pattern nobody notices until the annual audit.

Signing off and locking the period

Locking the period is a mechanical step, not a formality. In most accounting systems it means setting a closing date so that transactions dated before it cannot be added, edited, or deleted without an explicit override, which is usually logged. Do this account by account as each one clears, rather than waiting until every account in the business is done, so a delay on one account does not hold up the ones that are already reconciled.

Keep the supporting file for each closed account: the converted statement, the reconciliation working paper, and a note on how any variance was resolved. Retention requirements differ by jurisdiction and by what the records are used to support, and how long converted bank statement records need to be kept sets out the general ranges. A close that locks cleanly this month is also the one that saves the most time next month, since the opening balances are already known to be right.