How to find missing bank statements before reconciliation

A reconciliation starts with a population of transactions. Before explaining differences between a bank balance and a ledger balance, check whether the statements you received cover the accounts and periods you intended to review.

A spreadsheet can add every imported row correctly while an entire statement is absent. The total answers a question about the rows in the file. It does not, by itself, establish which rows should have been there.

This guide uses a synthetic account and illustrative figures. It describes a practical document check, not a conclusion about any real account.

1. Define the period and accounts first

Write down the account identifier, currency, start date, and end date of the review. Include accounts with no movement if they are part of that scope. Keep each account and currency separate when checking continuity.

An April statement cannot establish whether a February statement exists. Nor can continuity in one account establish that you have discovered all of an organisation’s accounts. The account list and the transaction population are separate evidence requirements.

Record where the account list came from and who confirmed it. That gives the later statement check a defined scope.

2. Inventory the source statements

For each statement, record its account, period, opening balance, closing balance, filename, and source. Keep the original file alongside the imported rows. If a bank export does not declare a complete statement period or opening balance, record that limitation rather than inferring one from the first transaction date.

A missing transaction date is not automatically a missing statement. There may have been no activity that day. Statement coverage and transaction activity answer different questions.

A compact inventory might look like this:

Statement	Opening balance	Closing balance	Coverage
January	100,000.00	125,000.00	1–31 January
February	125,000.00	112,780.50	1–28 February
March	Not supplied	Not supplied	Unknown
April	0.00	18,500.00	1–30 April

The missing March document is a coverage gap. The difference between February’s closing balance and April’s opening balance is a separate, measurable continuity exception.

3. Check each statement internally

Use the bank’s balance and sign conventions to compare the statement’s opening balance, net movement, and closing balance:

Opening balance + net movement = closing balance.

For an export where credits increase the balance and debits reduce it, net movement is credits minus debits. Confirm the convention for the statement you are reading, particularly for credit cards and overdrafts.

If the calculation fails, investigate before treating the imported transactions as a complete statement. Possible causes include an unread row, a wrong sign, a misread column, or an export that does not represent the complete statement.

A successful calculation is useful evidence, but it is not sufficient on its own. Two omitted rows could offset each other. An entire omitted statement could begin and end at the same balance. Retain the document inventory and coverage check even when the arithmetic works.

4. Check continuity between statements

For consecutive statements of the same account, compare the earlier closing balance with the later opening balance. In the synthetic inventory above:

112,780.50 − 0.00 = 112,780.50 to explain across the gap.

That amount is not automatically an expense, loss, or adjustment. It describes a difference between two observed balances. The March statement may explain it through ordinary transactions, but that remains a hypothesis until the document is obtained and checked.

Do not enter a balancing transaction merely to make the chain join. Doing so hides the question the control was meant to raise.

5. Separate missing evidence from unread evidence

If a statement was supplied but a row could not be read, keep the row in an exception list with its position and reason. If a statement was not supplied, keep the missing period in the document request list.

These exceptions need different follow-up. Re-exporting or inspecting a difficult row can resolve a reading problem. It cannot resolve a statement nobody supplied.

banktrail preserves source references for imported transactions and reports balance-chain exceptions. A reported break is a starting point for investigation; it does not identify a payer, establish a payment’s authority, or explain the business purpose without supporting evidence.

6. Close the gap with evidence

Request the missing statement for the exact account and period. When it arrives, confirm its account, dates, and balances, import it, and rerun both the statement-level and cross-statement checks.

Keep the original exception and record what resolved it. If the file is still unavailable, state the remaining limitation plainly: the review covers the supplied statements, and completeness for the missing period has not been established.

A useful completion checklist is:

• The account list and review period are documented.
• Every required period has a statement or an explicitly recorded limitation.
• Each statement’s arithmetic has been checked using its balance convention.
• Consecutive statement balances have been compared.
• Unread rows and missing documents remain distinguishable.
• Each resolved exception points to the evidence that resolved it.

See the checks in context

The worked payroll example shows the next layer of review: two matching debits remain two transactions, while the conclusion about an erroneous payment depends on additional evidence.

See the supported file formats and their limits before preparing statement exports. For a review sequence that separates unread rows, statement footing, and balance-chain gaps, read how to review a bank statement reconciliation exception.

Watch the banktrail walkthrough to see statement imports, evidence gaps, and document annotations. To work with your own account statements, create a workspace.