VAT Review Using Bank Statements

This is written for accountants and bookkeepers who run pre-submission VAT checks. You know your way around input and output VAT already — what eats the time is the grind of getting clean transaction data out of a stack of PDFs and lining it up against the return without trusting a number you shouldn't.

Why bank statements are the right cross-check for VAT

The VAT return is built from the bookkeeping records; the bank statement is built by the bank. When the two agree, you've got independent corroboration; when they don't, you've found something. That's the whole value of bringing the bank into a VAT review — it's evidence the client didn't create.

Three checks do most of the work. First, completeness of output VAT: trade income landing in the bank account should map to sales the client has accounted for VAT on. A run of card-machine settlements or customer transfers with no matching sales invoices is a flag for under-declared output tax. Second, input VAT you can actually claim: supplier payments leaving the account point you to purchase invoices — and if the payment's there but the invoice isn't on file, you can't reclaim the VAT yet, no matter how obvious the spend looks. Third, timing: the bank shows you when money moved, which helps you test whether a transaction sits in the right VAT period rather than being pulled forward or pushed back across a quarter-end.

None of this replaces the VAT invoices — HMRC wants the invoice as the evidence to reclaim input tax, not the bank line. The bank statement is the net you drag across the quarter to find what the invoice file missed.

Reconcile the data before you review the VAT

Here's the part people skip, and it's the part that quietly ruins reviews. A converter that turns a PDF into a grid but silently drops one line on a long statement gives you a tidy spreadsheet that's wrong — and you'll cross-check the VAT return against it with full confidence, which is the worst kind of error.

The defence is the running balance. If the extracted transactions don't add up from opening to closing, a line is missing or misread, and you need to know that before the VAT work starts.

Export Bank Statement builds that check into the conversion. After it extracts the transactions from the PDF, it recomputes the balance line by line and flags any statement that doesn't reconcile — opening plus net movement against the stated closing figure. You get a clear pass or a clear warning before you trust the data for a VAT cross-check. It keeps the balance column too, which most exports throw away; that column is what makes the check possible at all.

It reads scanned and photographed statements via OCR as well, which matters for VAT because that's where figures get misread — a "1,920.00" picked up as "1,020.00" is a 150 swing in the VAT you'd compute from it. A misread figure breaks the running total, so the reconciliation flag catches exactly the errors that would otherwise feed a wrong number into your return check.

A VAT review workflow that holds up

This is the sequence I run for a quarter. It's deliberately mechanical, because mechanical is what you can defend if HMRC ever asks how you checked.

1. Convert the full period, in order. Pull every statement covering the VAT quarter, plus a few days either side of each quarter boundary so you can test cut-off. Confirm there are no gaps in statement numbers — a missing statement is a hole in completeness.
2. Reconcile each statement to itself. Opening balance plus money in, minus money out, equals closing. Do it per statement so an out-of-balance result is isolated to one month, not buried across the quarter.
3. Convert to Excel and sort by type. With clean reconciled data in a spreadsheet, filter the money-in column against the sales ledger and the money-out column against purchases. This is far faster than reading a PDF, and it's where the analysis actually happens.
4. Test output VAT for completeness. Trace significant receipts to sales invoices. Unmatched trade income is your prompt to ask whether output VAT was declared on it.
5. Hunt for missed input VAT. Scan payments for VATable spend the client forgot to claim — fuel, subscriptions, one-off equipment, professional fees. Each one needs a valid VAT invoice before you reclaim; the bank just tells you where to look.
6. Check timing across the quarter-end. Confirm transactions near the boundary fall in the correct period. Reverse-charge and import-VAT items deserve a second look here.
7. Reconcile your findings to the return. The VAT you'd expect from the bank-led review should broadly agree with the figures on the return. A material gap is the whole point of doing this.

Step 2 is the gate. Steps 5 and 7 are where you earn the fee.

A worked example, and how small the error can be

A client's quarter runs across four statements, one of them a fourteen-page current account. On page nine, a 3,240.00 payment to a VAT-registered supplier gets misread during extraction as 3,210.00. Both look plausible. But now the statement is 30 out, it won't reconcile, and — more to the point — if you'd reviewed VAT off that bad line you'd have computed roughly 5 less reclaimable input VAT and never noticed. The reconciliation flag stops you at the 30 difference before any of that reaches the return. Find the typo, fix the line, then review.

That's the difference between a tool that converts and one that verifies: thirty pounds on one line is invisible by eye and obvious to a running-balance check.

Where MTD and the honest limits sit

Under Making Tax Digital for VAT in the UK, returns are filed from digital records through compatible software with a digital link from source to submission. A converted spreadsheet that reconciles fits that picture as your reviewable working copy — but be clear on the boundary: this is a conversion-and-checking tool, not bridging software, and it doesn't file your return.

The other honest limit: 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 over a live bank-feed API. The path is convert, confirm the reconciliation result, then import the CSV. For a VAT review that's the right shape anyway; you want a reviewed file you can point to, not a silent sync. If you're prepping the same client for audit, the reconciled export carries straight across, and bank statement analysis for accountants covers the patterns that often surface missed VATable spend.

On privacy: files are processed then deleted, and they're never used to train AI — easy reassurance to give someone handing over a quarter of bank data.

This is general information for professionals, not tax advice — apply your own judgement and the client's specific facts.