Catch-Up Bookkeeping: Rebuilding Months of Records From Bank Statements

Where do I start when the books are months behind?

Start with an inventory, not with data entry. List every account that money moved through during the gap: checking accounts, savings, every credit card, and any account you closed along the way. Money you spent from an account you forget is money your books will never show.

Then download the statements — every month of the gap, for every account on the list. Banks typically keep 12–24 months of PDFs available online; older ones may need a support request, so ask early. If your bank lets you download one multi-month PDF per account, take it: merged files convert cleanly, each statement period verified separately.

Resist the urge to start categorising the most recent month first. Work oldest to newest — categorisation rules you build on early months apply themselves to later ones, and opening balances only make sense in order.

How do I get months of statements into a workable format?

Retyping a year of statements is the failure mode: slow, and every keystroke a silent-error risk that surfaces as a mysterious imbalance months later. Convert instead, and let arithmetic do the checking.

• Upload each statement (or the merged multi-month PDF) to BankStatementWise. Each statement reconciles to the cent against its own opening and closing balances; rows the converter can't verify are flagged for review rather than silently guessed.
• Review the flags as you go, month by month — a few seconds per statement while the context is fresh beats a marathon audit at the end.
• With a free account, every conversion stays in a searchable workspace, so the whole catch-up project lives in one place and can be re-exported anytime in Excel, CSV, JSON, or OFX.

Scanned or photographed statements from a filing box work too — scans are supported, and misread digits break the balance arithmetic, so they get caught instead of absorbed into your books.

How do I make sure no month — and no transaction — is missing?

Gap-checking is the step that separates a defensible catch-up from a hopeful one, and it's mechanical:

• Continuity: for each account, every month's closing balance must equal the next month's opening balance. A mismatch means a missing statement or a statement from a different account slipping into the pile.
• Completeness within each month: the statement's own reconciliation (opening + credits − debits = closing) proves the extracted rows are the complete set — a dropped transaction cannot hide, because the arithmetic won't tie without it.
• Cross-account transfers: a transfer out of checking should appear as a transfer into savings (or a card payment) on the other side. Matching these catches both missing accounts and double-counting.

Do the continuity check the moment each account's statements are converted, before categorising anything — finding a missing March in April costs minutes; finding it at tax time costs a filing extension.

How do I categorise and import the backlog?

With verified transactions in hand, categorisation is bulk work, not detective work. Sort by description in the spreadsheet and categorise in runs — fifty rows of the same subscription take one decision, not fifty. Card statements matter here: they carry the itemised expenses that the bank side only shows as monthly card payments (see converting card statements).

Then import period by period into your accounting tool — the mechanics are covered in the QuickBooks and Xero guides. Import oldest month first, reconcile it inside the tool, and only then import the next; a mistake caught one month in is trivial, the same mistake discovered after a year of imports is not.

Keep the converted statements. If an accountant, lender, or tax authority later asks how a number was derived, you have the bank's own document, the extracted data, and a reconciliation tying them together — which is precisely the audit trail catch-up work usually lacks.