Export Bank Statement — bank statement PDF to Excel
event_availableGuide

Year-End Bank Statement Review

How to run a year-end bank statement review: gather every month, reconcile each statement, tie to the cash book, and hand the accountant clean data.

bolt

A year-end bank statement review is the pass you make before the accounts are finalised: you gather every month of the period, convert each statement to clean data, reconcile it against the running balance, and tie the lot to the cash book or ledger. The whole point is to catch what's missing or misread now, while there's still time to fix it, rather than after the figures are locked. If a statement won't reconcile — opening balance plus money in, minus money out, not equalling the closing balance — a transaction has been dropped or mistyped, and you've found it on your own terms.

This is written for accountants and bookkeepers doing the year-end close. You know the routine; what burns the time is the mechanical bit at the front — turning twelve months of PDFs into reliable, reconciled data the rest of the close can stand on. And at year-end the gap between a statement that looks neat and one that's actually complete matters more than anywhere else in the cycle: every downstream figure — the bank balance on the balance sheet, the VAT reclaimed, the profit reported — inherits whatever's wrong in the source. So the review starts with one discipline: prove the data before you analyse it.

Gather the complete period, in order

Before any conversion, line up the full set: every statement covering the financial year, plus the period either side so you can test the year-end cut-off. The closing balance on the last statement is the figure that lands on the balance sheet, and you need the next opening balance to confirm continuity into the new year.

Check the statement numbers run consecutively. A gap in the sequence is the most common completeness hole at year-end, because a missing month breaks nothing visibly — the data you do have still reconciles to itself, and the hole only shows when you tie month-to-month. Confirm the chain is unbroken before you start: each month's closing balance becomes the next month's opening, all the way to the year-end.

If the client banks across more than one account — current, deposit, a card — treat each as its own chain, with its own set and its own reconciliation. Mixing them is how a transfer between two of the client's own accounts ends up counted once, or not at all.

Convert and reconcile each statement

Here's the sequence I work through for a year's worth of statements. It's deliberately repetitive, because repetition is what stops a tired eye on the fortieth page from waving an error through.

  1. Convert each PDF, keeping the balance column. Pull date, description, money in, money out and the running balance into a spreadsheet. Most exports discard the balance column — keep it, because it's your checksum for everything that follows.
  2. Reconcile each statement to itself. Opening balance plus net movement should equal the stated closing balance. Do it per statement, not once for the whole year, so an out-of-balance result is pinned to one month instead of buried across twelve.
  3. Tie each closing balance to the next opening balance. This proves you haven't skipped a period and that the chain runs continuous from the start of the year to the end.
  4. Agree the year-end closing balance to the figure going into the accounts. This is the number on the balance sheet — the real, reconciled closing balance off the bank's own document, not a transcribed approximation.
  5. Flag anything unusual for the cash-book stage. Round-sum transfers, large one-offs, anything dated close to year-end — note them now so you can trace them when you tie to the ledger.

Step 1 is where the hours hide. Step 2 is where the reconciliation check earns its place.

Where the reconciliation check changes year-end work

Most converters stop at "we turned your PDF into a grid," with no way to know whether they got every line — and at year-end, a converter that silently drops one transaction is worse than no tool at all, because you'll trust a wrong figure when accuracy matters most.

Export Bank Statement does the part the year-end actually needs: it treats the running balance as a checksum on every line. After extracting the transactions, it recomputes the balance from opening to closing and flags any statement that doesn't reconcile. You get a plain pass or a plain warning before you trust a single figure — the same completeness check a careful preparer does by hand, run on every line of every month, without getting tired on page forty.

It reads scanned and photographed statements via OCR too, which matters because older clients often hand over a year as a stack of scans, and scans are where figures get misread. A blurred "8" taken for a "3", a thousands comma swallowed — those break the running total, so the flag catches them instead of letting them slip into the close.

One honest limit, because it shapes how this slots into the close: the tool converts statements and exports a clean CSV — including Xero, QuickBooks and Zoho Books' native bank-import formats — but it does not push transactions into those packages over a live bank-feed API. The path is convert, confirm the reconciliation result, then import the CSV. That's the right shape for a year-end anyway: a reviewed file you can attach to the working papers, not a silent sync you can't point at.

Tie the reconciled data to the cash book

Once every statement reconciles and the chain is continuous, the bank data is trustworthy and you can do the part that's actually a review: tie it to the cash book or nominal ledger.

With the year in a spreadsheet, filter the money-in column against recorded receipts and the money-out column against recorded payments. Anything on the bank with no matching ledger entry is a transaction the books missed — a direct debit nobody posted, bank charges never coded, interest received, a card payment that slipped through. Each shifts the result, so you want them before the accounts close: a year of unposted bank charges is a real expense the client is entitled to, sitting unclaimed.

Work the other direction too. A ledger entry with no matching bank line is either a genuine timing difference — a cheque not yet presented, a payment in transit at year-end — or an error to correct before sign-off. The bank, built by someone other than the client, is the independent record that tells the two apart.

Hand the accountant clean data

The output of a good year-end review is data the next person can trust without a single question back to you — whether you're the bookkeeper passing to the accountant or the practice passing to a reviewer. Name each export by account and period, keep the original PDFs alongside the converted spreadsheets, and where a statement was flagged and you fixed a line, leave a one-line note saying what and why. Hand over the reconciliation result itself, so the accountant sees the whole year ties rather than taking it on trust.

If the same client needs an audit, the reconciled export carries straight into the audit file; if there's a VAT angle, the same clean data feeds a VAT review using bank statements without re-keying. On privacy, which clients ask about more each year: files are processed then deleted, and never used to train AI. This is general guidance for professionals, not accounting or tax advice; apply your own judgement and the client's facts.

Frequently asked questions

What is a year-end bank statement review?keyboard_arrow_down

It's the check an accountant or bookkeeper runs before finalising the accounts: gather every statement for the year, convert each to clean data, reconcile it against the running balance, and tie it to the cash book or ledger. The aim is to catch missing or misread transactions while there's still time to correct them, and to confirm the year-end bank balance going onto the balance sheet is the real, reconciled figure.

How do you reconcile bank statements at year-end?keyboard_arrow_down

Reconcile each statement to itself first — opening balance plus money in, minus money out, must equal the stated closing balance. Then tie each closing balance to the next month's opening to prove the year is continuous, and agree the year-end figure to the balance going into the accounts. Working per statement isolates any error to one month rather than burying it across the year.

How do I find a transaction the books missed before year-end?keyboard_arrow_down

Reconcile the bank data first so you know it's complete, then filter the converted spreadsheet's money-in and money-out columns against the cash book. Any bank line with no matching ledger entry is a missed transaction — unposted charges, an unrecorded direct debit, interest received. Because each statement reconciles before you match, a gap you find is a real omission, not a conversion error.

Can it import the data straight into Xero or QuickBooks for year-end?keyboard_arrow_down

It exports the reconciled data as a CSV in Xero, QuickBooks and Zoho Books' native bank-import formats, which import as reconcilable statement lines. It does not push transactions over a live bank-feed API — the path is convert, confirm the reconciliation result, then import the CSV, which keeps a reviewed file in your working papers.

Does it handle a year of scanned statements?keyboard_arrow_down

Yes, via OCR. Older clients often hand over the year as scans or phone photos, the highest-risk source for misread figures. The running-balance check is what makes scans safe — a digit read wrong breaks the total and gets flagged, instead of quietly skewing a figure that ends up in the finalised accounts.

verified

Try it on your own statement

Clean Excel/CSV, with every transaction checked to balance.

upload_fileConvert free
Keep reading

More guides

verifiedChecked to balance

Convert your bank statement — every transaction verified

Upload any PDF, get clean Excel or CSV ready for Xero & QuickBooks. Scanned statements too.

upload_fileConvert a statement free