Home › Blog › Reconciliation & Verification › Opening and closing balance checks, and continuity across months
Use opening and closing balance checks and month to month continuity to prove a full year of statements has no gaps, overlaps, or missing periods.
By StatementVerified Editorial · November 4, 2026 · 7 min read · Filed under Reconciliation & Verification
Every statement makes two promises: here is where the account started, and here is where it ended. Checking those two numbers, and checking that each month ending becomes the next month beginning, is the fastest integrity test in bookkeeping. It requires no software, no categorization, and no judgment about what a transaction was for. It simply asks whether the chain of balances is unbroken. A broken chain means something is missing, doubled, or dated in the wrong period, regardless of how tidy the individual transactions look.
This guide explains how to run opening and closing checks on a single statement, how to extend them into a continuity check across a full year, and how to use breaks in the chain to locate missing statements, overlapping conversions, and prior period corrections. For catch up projects, where a year or more of statements arrives at once, the continuity check should be the very first step, before any file is imported, because it validates the completeness of the whole set in minutes.
For one statement, take the opening balance exactly as printed and add every signed transaction in the activity list. The result must equal the closing balance exactly as printed, to the cent. Use the statement own presentation of signs, and be careful with accounts that present a balance owed rather than a balance held, such as credit cards and lines of credit, where an increase in charges raises the amount owed. The arithmetic still holds, but the intuition reverses, and most single statement failures on card accounts are sign interpretation errors rather than missing data. Write the check down as a workpaper line, not as a mental nod, so the proof can be reperformed later.
If the check fails, the size of the failure is your first diagnostic, as with any reconciliation difference. A failure equal to a section subtotal suggests a summary was counted or a section was skipped. A failure equal to the opening balance itself suggests the opening was added twice or taken from the wrong statement. A small failure suggests a fee, an interest line, or a misread digit. Resist importing a failing statement on the theory that the month end reconciliation will find it. The month end process uses the same anchors, so it will find the same failure, later, with categorized transactions now attached to the problem.
Continuity extends the check across time. The closing balance of one statement must equal the opening balance of the next statement for the same account, with no exceptions for a healthy set. Lay the statements in date order and compare each adjoining pair. When a pair disagrees, something happened between the two documents: a statement is missing from the sequence, a period was skipped in a download, the account had a mid cycle statement after an address or ownership change, or a statement was reissued with corrections. Each possibility has a different remedy, and the disagreement amount often distinguishes them, since a missing month usually creates a large jump equal to that month net activity.
Record the chain in a simple schedule: statement end date, opening balance, closing balance, and a yes or no for continuity with the next statement. That schedule becomes the map for the entire catch up project. Months inside a continuous chain can be converted and imported in order with confidence in their boundaries. Breaks get resolved first, by obtaining the missing statement from the bank or the client, before any import crosses the break. Importing across an unresolved break almost guarantees duplicated or missing boundary transactions that are painful to untangle after categorization has begun.
A gap and an overlap can produce similar symptoms in the books, a balance that will not reconcile, but continuity separates them cleanly. In a gap, the chain breaks and the jump equals the missing period net movement, and no statement in your set covers those dates. In an overlap, the chain itself may look continuous because the statements are genuine, but the same dates were converted or imported twice, so the books contain activity the chain never promised. That is why the continuity schedule should also record transaction date ranges and counts per statement. Overlapping imports reveal themselves as counts that exceed the statement own counts for the shared dates.
Also watch for the silent gap inside a single document: a downloaded statement that jumps from one month to a later month because the bank portal defaulted to a custom range, or a scanned set where a middle statement was never included in the scan. The client may sincerely believe they sent everything. The chain does not rely on belief. If the dates and balances do not connect, a document is missing, and asking for it early, with the exact dates the chain shows as uncovered, gets a faster and more accurate response than a vague request for more statements weeks into the project.
Occasionally the chain breaks because the bank corrected history. A reissued statement can show a different opening balance than the original prior closing balance when a late fee reversal, an error correction, or a returned item was applied retroactively. When that happens, do not force the chain. Obtain both versions, identify the correcting entry the bank describes in its notices, and record the correction in the books in the period the bank applied it, with a note referencing the reissue. The corrected chain should then connect from the reissued figures forward, and your schedule should show which version is authoritative so the superseded statement is never converted by mistake.
A similar break can originate inside the books rather than at the bank, when a prior period transaction is edited, deleted, or recategorized in a way that changes a reconciled balance. The statements still chain perfectly, but the book opening balance no longer matches the statement opening balance. That pattern, statements continuous and books discontinuous, tells you the problem is internal, and the audit trail or change log in the accounting system becomes the document to bisect. Distinguishing a bank side break from a book side break at the start saves hours of searching the wrong record set.
For ongoing clients, run the continuity check at intake every month, not just during cleanup. When a new statement arrives, confirm its opening balance equals the prior closing balance you already hold, confirm its own activity ties opening to closing, and only then convert and import. The two checks take minutes and they quarantine problems to the month that introduced them. A practice that checks continuity monthly will never face a year end surprise larger than one month, while a practice that checks annually can face a break whose origin month nobody remembers.
File the schedule with the statements, update it as new statements arrive, and let it double as your import coverage log. Over time it becomes one of the most valuable workpapers in the client file: a one page proof that the bank record is complete, in order, and unbroken, on which every reconciliation, tax return, and lender package for that account quietly depends. Balances that chain cleanly do not guarantee every categorization is right, but they guarantee the raw material is whole, and wholeness is the foundation every other bookkeeping judgment stands on.
Do not import across the break. First confirm both figures come from statements for the same account. Then check for a missing statement covering the dates between them, a custom range download that skipped a period, or a reissued statement with a correction. Request the exact missing dates from the bank.
Yes, with reversed intuition. The amount owed at the end of one cycle becomes the previous balance at the start of the next. Payments, credits, charges, fees, and interest explain the movement between them, and the summary box on the statement states that arithmetic explicitly for you to test.
That pattern points inside the books: a prior period edit, deletion, or duplicate changed a reconciled balance. Use the accounting system change log to find what moved after the period was closed, restore or correct it, and re prove the book opening against the statement opening.
Reconciliation & Verification · November 2, 2026
Learn how bank reconciliation works step by step, using the bank statement as the referee for every balance, transaction, and difference for any account.
Reconciliation & Verification · November 4, 2026
The nine most common reasons a converted statement does not tie out, how each one changes the difference, and how to isolate the real cause fast.
Reconciliation & Verification · November 3, 2026
Understand what reconciled, flagged, and unverified verification outcomes mean for a converted statement, and what to do next with each one.
Convert a statement now and watch the reconciliation check verify it against the statement itself.
Your first conversion is free — no card, no sign-up — and every result is reconciled against the statement itself before you download it.