What a statement can and cannot do for VAT
A bank statement is a complete record of money movement and a poor record of tax. It shows that £4,800 went to a supplier on the 14th. It does not show whether that included VAT, at what rate, whether any of it was zero-rated, or whether the supplier was even registered.
So the honest framing is this: statements are excellent for completeness — finding every payment that should have a purchase invoice behind it — and useless as evidence of the VAT inside those payments. Both facts matter, and most VAT trouble comes from confusing them.
This page covers the first job properly: turning a quarter of statements into complete, sortable data that shows exactly which payments have no invoice attached yet, and which reconciles cleanly to what you actually paid or reclaimed.
Why the invoice is the evidence
Across VAT systems the principle is consistent: to reclaim input VAT you need a valid invoice from a registered supplier, showing the tax separately and identifying you as the customer. A payment record is not a substitute for it, however clearly it shows the money leaving.
This is not a technicality, and it has a practical consequence: a payment with no invoice behind it is not a claim, it is an unsupported number. Finding those payments early — while the supplier will still cheerfully send a copy — is the highest-value thing statements do in a VAT quarter.
The corresponding advice is unglamorous and effective: when a purchase matters, ask for a proper invoice at the point of sale. Nothing recovers a document that was never issued, and no software creates one.
The job statements are actually good for
Completeness testing. Take every payment out of the business in the quarter, exclude the categories that cannot carry input VAT — wages, transfers, loan repayments, dividends and so on — and ask a single question of what remains: does each of these have a purchase document?
The gaps that turns up are the point. Every quarter has a few: the subscription nobody files, the supplier who emails invoices to a personal address, the card payment nobody recognised. Each is either a missed reclaim or an unsupported one, and both are worth finding before the return is filed rather than during an inspection.
The same exercise on the income side finds sales receipts with no corresponding sales invoice, which is the more serious direction of error.
Step 1 — Extract the quarter completely
Convert every account for the quarter — current account, cards, any processor — into one table with date, description, signed amount and running balance. Statement conversion handles any bank's layout without a template, including scans.
Then prove it is complete, because a quarter missing a fortnight will pass a review unnoticed and fail an inspection loudly. The balance check tests each statement against its own opening and closing balance and names the rows where the arithmetic breaks.
Consolidate the accounts into one dataset with a source-file reference per row, so any figure can be traced back to the document it came from — see Smart Merge.
Step 2 — Separate what could carry VAT from what cannot
Not every payment is a candidate. Wages, transfers between your own accounts, loan capital, dividends, most bank interest and payments to the tax authority itself do not carry reclaimable input VAT, and separating them first shrinks the review list considerably.
What remains is the population that needs documents: suppliers, subscriptions, equipment, professional fees, fuel, travel and the rest. Sort it by payee so recurring suppliers become one decision each rather than a dozen.
Then flag the ones you know need care — mixed-use costs, anything with a partial-exemption angle, purchases from abroad. Those are not spreadsheet decisions, and marking them is how they reach your accountant rather than silently reaching the return.
Step 3 — Match payments to purchase invoices
With the payment list in one column and your invoices in another, matching is mechanical: by amount and date first, then by supplier for anything that does not pair automatically.
If the invoices are PDFs rather than data, extract them too — supplier, invoice number, date, net, tax and total — so the comparison is table against table rather than document against spreadsheet. Invoice extraction and an invoice register do that in one pass.
The output is a short, specific list of payments with no invoice. Chase those; most arrive within a day, and the ones that do not are the ones you needed to know about.
Step 4 — Reconcile the VAT account to what actually moved
There is one place where statements are direct evidence in a VAT context: the payments to and refunds from the tax authority. Every such transaction should correspond to a filed return, and the control account should agree with the sum of what has been filed and paid.
This reconciliation catches a specific and unpleasant class of error: a return filed but never paid, a payment made twice, a refund received and never recorded. Each is invisible in the return itself and obvious in the bank.
Do it every quarter rather than annually. A single unexplained difference in a control account is a ten-minute job in the quarter it happened and a forensic exercise a year later.
The traps that distort a VAT quarter
A payment to a card provider is a transfer, not a purchase — the purchases are the individual card transactions, and treating the settlement as a cost double-counts everything on that card.
Processor payouts arrive net of fees. The fee is a cost in its own right, often carrying VAT, and it is invisible if only the payout is recorded.
Payments on account and deposits do not necessarily follow the invoice, so the tax point can sit in a different period than the payment. That is precisely the sort of question the statement cannot answer and the invoice can.
And a supplier who is not registered charges no VAT at all, regardless of how large the payment looks. Assuming a rate because the amount is round is one of the most common self-inflicted errors in a reclaim.
If you account for VAT on a cash basis
Under a cash-accounting scheme the payment date is what drives the return, which makes bank data considerably more central than it is on an invoice basis — the statement is close to the primary schedule.
Even then the invoice remains the evidence for the amount of tax; the statement establishes when it was paid. Both, again, rather than either.
Whether such a scheme is available to you, and whether it suits your business, is a question for your accountant. This page is about producing the underlying data cleanly whichever basis you are on.
If you file digitally
In the UK, VAT returns must be kept and filed with compatible software under Making Tax Digital, with digital records rather than retyped summaries. FlowParse is not HMRC-recognised MTD software and does not submit anything to HMRC.
What it does is the step before: turning statements and invoices into structured data you import into whatever MTD-compatible system you use. See Making Tax Digital and bank statements for how that boundary works in practice.
Other jurisdictions are moving the same way, and the pattern is identical: extraction and preparation on one side, an authorised filing system on the other. The boundary is deliberate, not a limitation we regret.
A routine that takes an hour
Download
Every account's statements for the quarter, plus the processor reports, into one folder.
Extract
Convert them in one batch and verify each against its closing balance.
Classify
Exclude wages, transfers and other non-VAT items; sort the rest by payee.
Match
Pair payments with purchase invoices; produce the list of gaps.
Chase
Request the missing invoices while the supplier still remembers.
Reconcile
Agree the VAT control account to payments and refunds in the bank.
Hand over
Give your accountant the dataset, the gap list and the flagged judgement items.
What to keep, and for how long
Keep the invoices. They are the evidence, retention periods for VAT records are long in most jurisdictions, and a spreadsheet derived from them is not a substitute.
Keep the statements too, as the corroboration and as the record of what was paid. And keep the working dataset with its source references, because it is what makes any single figure explicable later.
Be clear that an extraction tool is not an archive: FlowParse deletes the original document immediately after processing, which is good for privacy and means the retention obligation stays entirely with you. The audit preparation guide covers what a durable evidence pack looks like.
Who this helps
Small VAT-registered businesses
Where the quarter is prepared from the bank and a pile of invoices.
Bookkeepers
Running the same quarter-end for many clients, wanting the gap list fast.
Businesses on cash accounting
Where payment dates drive the return and bank data is central.
Anyone catching up late
Several quarters behind, needing a complete record before anything else.
Completeness is the whole point here
A VAT quarter built on an incomplete payment list understates both what you owe and what you can reclaim, and the error is invisible: nothing looks wrong about a list that is simply shorter than reality.
That is why every statement is checked against its own balances, and why the month-to-month sequence check matters. See extraction accuracy for what these checks prove — they prove the extraction matches the statement, not that the statement is complete evidence for a claim.
Handling the documents
Uploads run over TLS, processing happens in EU data centres, the original PDF is deleted immediately after extraction, extracted data is encrypted at rest, and documents are never used to train models — see the security page. FlowParse is hosted and cannot be self-hosted.
What each document actually evidences
Keeping this distinction straight prevents most VAT trouble, so it is worth stating as a table rather than a paragraph.
| Question | Bank statement | Purchase invoice |
|---|---|---|
| Did money move? | Yes — this is what it proves | No |
| When was it paid? | Yes, definitively | No |
| What was bought? | Only a description someone typed | Yes |
| How much VAT was in it? | No | Yes — separately stated |
| Was the supplier registered? | No | Yes — registration number |
| Is it your claim to make? | No — the account is yours, the purchase may not be | Yes — it names the customer |
The items that are not spreadsheet decisions
Some costs are genuinely not a categorisation problem. Anything used partly for business and partly privately, anything bought before registration, purchases from abroad, entertainment, vehicles and fuel, and businesses making both taxable and exempt supplies — every one of these has rules that vary by jurisdiction and by circumstance.
The correct handling in a data-preparation workflow is not to decide them. It is to flag them so they arrive at your accountant explicitly, with the payment, the invoice and any context you have.
A flagged row that gets a two-minute answer is cheap. The same row silently categorised by a rule of thumb is the one that shows up in an inspection.
A worked example: one quarter, one hour
A small agency with a current account, a company card and a payment processor. The quarter is three months of statements across three accounts — nine documents.
Conversion and the balance check take about ten minutes, and one statement fails: a card statement whose promotional panel swallowed four rows, re-processed immediately. Excluding wages, transfers, loan repayments and tax payments removes roughly a third of the rows from the review list.
Sorting the remainder by payee, twenty-two suppliers cover most of it. Matching against the extracted purchase invoices leaves eleven payments with no document — six are recovered from supplier portals the same afternoon, three arrive by email the next day, two are subscriptions that turn out to be billed to a personal address and get fixed at the source.
The VAT control account reconciles to the two payments visible in the bank. What goes to the accountant is a complete quarter, eleven resolved gaps, and four flagged judgement items. The quarter that used to take a day took an hour.
When you find an error after filing
Reconstructing a quarter properly sometimes surfaces something in a period you have already filed: a reclaim you missed, or one you should not have made.
How to correct it — adjust the next return, notify separately, or something else — depends on the size of the error, the jurisdiction and the rules that apply to you. It is a question for your accountant and, in some cases, for the tax authority directly. We deliberately do not give a rule of thumb here.
What helps either way is evidence: a complete extraction of the period concerned, the documents behind the affected transactions, and a clear note of what was found and when. A well-documented correction is a routine event; a vague one is not.
The exclusion list that shrinks the work
Before reviewing anything, remove the payments that cannot carry reclaimable input VAT. On a typical quarter this removes a third to a half of the rows, and it is the fastest single improvement to the exercise.
| Payment type | Include in the review? | Why |
|---|---|---|
| Wages and salary | No | Not a supply of goods or services to you |
| Transfers between own accounts | No | No purchase happened |
| Loan capital repayments | No | Finance, not a supply |
| Payments to the tax authority | No | Reconcile separately to the control account |
| Owner drawings or dividends | No | Not a business cost |
| Supplier payments | Yes | Needs a purchase invoice |
| Subscriptions and software | Yes | Frequently missing an invoice |
| Card settlements | No — but the card transactions are | The settlement is a transfer |
Do not forget the output side
Most attention goes to reclaims, and the more serious errors sit on the income side, because understating output tax is the direction tax authorities care about most.
The check mirrors the purchase one: every receipt into the business should correspond to a sales invoice or a documented reason why not — a loan drawdown, a refund, a transfer, a capital injection. Deposits with no sales document behind them are the ones to look at.
Processor and marketplace deposits deserve particular care, because they arrive net. The taxable supply is generally the gross sale rather than the payout, and reconstructing sales from payouts alone will understate both the sale and the fee. The platform report is the other half of that picture.
The boundary, stated plainly
FlowParse turns documents into data. It does not compute your tax, decide what is deductible, apply a rate, issue a form or file anything with any tax authority. Those are decisions about your circumstances and the law where you live, and they belong to you and your accountant.
It is also worth being precise about what a bank statement proves. It proves a payment happened: this amount left this account on this date, to this counterparty. It does not prove what was bought, whether the cost was for the business, or how much tax was inside it. For anything where the tax authority wants to see the nature of the expense — a VAT or sales-tax claim above all — the invoice or receipt is the evidence and the statement is the corroboration.
What that leaves is still the slowest part of the job: getting a year of transactions out of PDFs, complete, correctly signed, in one sortable place. That is what this page is about.
Start with one quarter
Convert the current quarter for your main account, exclude the non-VAT categories, sort by payee and see how long the missing-invoice list is. For most businesses it is shorter than feared and more specific than expected — which is exactly what makes it actionable.
Then repeat it every quarter as a routine rather than a rescue. The version of this work that takes an hour and the version that takes a day are the same work, done at different times.
Get the quarter complete before you file
Convert every account, prove nothing is missing, and produce the specific list of payments still waiting for an invoice — in about an hour.