How Can I Verify Extracted Transactions?

The most reliable way to verify extracted transactions is a running-balance reconciliation check: take the opening balance, add every extracted transaction in order, and confirm the result equals the closing balance printed on the statement. If the two figures match, nothing was dropped or misread. If they don't, a line is wrong, and you've caught it before trusting the numbers. Back that up with a quick spot-check of a few rows, a totals tie-out, and a row count against the statement.

That reconciliation step is the part most converters skip, and it's the one that actually proves the data is complete. Export Bank Statement runs it automatically on every file and flags any statement that doesn't reconcile.

Start with the reconciliation check

Reconciliation is the only check that tests the whole statement at once. Every other method samples; this one accounts for every penny.

The maths is simple. Opening balance plus the sum of all transactions should equal the closing balance. A real example: if your statement opens at £2,140.00, the debits and credits in between net to £3,512.18, and the statement closes at £5,652.18 — it reconciles. The extraction held.

When it doesn't reconcile, the gap tells you something specific went wrong. A transaction near a page break got skipped. A figure was misread — a 3 read as an 8, or a decimal point shifted. A debit got picked up as a credit. The size of the discrepancy often points straight at the culprit. A £45.00 gap means you're hunting for a single £45.00 line; a doubled figure usually means a row was read twice.

Export Bank Statement does this re-derivation for you the moment a file is converted, opening through closing, and marks the statement as reconciled or flags it. You're not eyeballing a wall of numbers hoping you spot the odd one out.

Then spot-check, tie out, and count

Reconciliation tells you the totals are sound. A few quick manual checks confirm the detail is too.

• Spot-check a sample. Pick five or six rows at random — and always include the first and last transaction on each page, since page edges are where extraction tends to slip. Compare each against the PDF: date, description, amount, debit-or-credit direction.
• Tie out the totals. Many statements print a total of money in and money out for the period. Sum your extracted credits and debits separately and check they match those printed totals.
• Count the rows. Count transactions on the statement, count the rows in your Excel or CSV file, and confirm they're equal. A mismatch means a line was added or lost — duplicates and dropped rows both show up here.

These take a couple of minutes and they catch the errors reconciliation can mask. Two offsetting mistakes — say, a £20.00 credit misread as £20.00 twice in different places — can still balance to the right closing figure while the detail is wrong. The sample and the row count expose that.

A note on what verifying does and doesn't do

Verifying confirms the *extraction* is faithful to the *statement*. It doesn't push anything into your accounting software. With Export Bank Statement the path is convert, verify, then import the CSV into Xero, QuickBooks or Zoho Books yourself — there's no live bank-feed API quietly syncing transactions in the background. You produce a clean, reconciled file and import it as statement lines you can trust.

Frequently asked questions

What does it mean if my statement doesn't reconcile?

It means the extracted transactions don't add up from the opening balance to the closing balance. Something was misread, dropped, or duplicated. The size of the gap usually points to the specific line, so you can find and fix it before importing.

Is reconciliation enough on its own?

Almost. It proves the totals are complete, but two offsetting errors can still balance. Add a quick spot-check of a few rows and a row count against the statement to confirm the detail, not just the total.

How do I verify a scanned or photographed statement?

Run it through OCR to extract the transactions, then apply the same checks. Export Bank Statement handles scanned and photographed statements and runs the reconciliation check on the result, so OCR errors get flagged like any other.

Do I have to do the reconciliation maths by hand?

No. Export Bank Statement re-derives the running balance automatically on every converted file and tells you whether it reconciles. The manual spot-check and row count are quick extra confidence on top.

For related reading, see common PDF extraction errors and how to detect duplicate transactions. More UK guidance lives on the UK hub and the FAQ pillar.

CTA: Want the totals checked for you? Convert your statement and verify it reconciles before you import a single row.