How to prepare bank statements for an accountant

Why handovers cost so much

Ask any practice where the hours go on a small-business year end and the answers are consistent: chasing missing documents, typing or importing transactions, working out what unexplained payments were, and establishing whether the data is complete. Only the last part of the job is accounting.

Worse, that work is done at the least efficient possible time — months after the transactions happened, by someone who was not there, asking a client who no longer remembers. A payment you could have identified in five seconds in March takes an email thread in November.

Every step below exists to move work from that expensive moment to a cheap one, and most of them cost you minutes.

What accountants actually want

Notice what is not on that list: categories, journals, opinions on treatment, or a tidy narrative. Those are their job, and a client who guessed at them creates work rather than saving it.

Step 1 — List every account before you gather anything

Start with a written list rather than the pile of PDFs you happen to have: business current accounts, savings accounts that received transfers, every credit and charge card, loans and finance agreements, payment processors, and any personal account or card that paid for something business-related.

Then hunt for the ones you forgot, because there always are some. The account opened for one project. The card used for a single subscription. The processor that paid out twice and was never mentioned. The account closed in June. A quick scan of transfers out of your main account usually reveals all of them.

Send that list with the pack. An accountant who knows there are five accounts and has five sets of statements is in a completely different position from one who has five sets and no idea whether that is all of them.

Step 2 — Collect every month, unbroken

For each account, download every statement covering the period, plus the last statement of the previous period so opening balances can be verified rather than assumed.

Name the files consistently — account, year, month — and put them in one folder per account. This is genuinely the highest effort-to-value step in the whole guide: consistent names make a missing month visible at a glance instead of discoverable three weeks later.

If a statement is unavailable, request it now. Banks generally provide historical statements including for closed accounts, sometimes for a fee, and it is the one part of this process with a lead time you do not control.

flowparse.io

Step 3 — Convert them into data, do not retype

A PDF is a picture of a table. Your accountant needs the table: date, description, signed amount, running balance, one row per transaction, sortable.

Converting the statements produces exactly that from any bank without a template, including scans and photographs. Two details decide whether the result is usable: debits and credits must collapse into one signed amount so refunds reduce costs rather than inflating them, and the running balance must never be exported as the transaction amount — an error that puts a plausible wrong number on every row.

Do not retype. Transcription introduces errors at a stable rate no amount of care removes, and every one of them becomes a reconciliation difference your accountant has to investigate at their hourly rate.

Step 4 — Prove the pack is complete

This is the step that changes how your accountant treats everything else you sent. A statement extracted with three rows missing looks perfect: the rows that are there are correct, nothing is flagged, and the shortfall only appears when something refuses to reconcile.

Two checks settle it. Within each statement: opening balance, plus every transaction, equals the printed closing balance — this runs automatically per accountand names the rows where the arithmetic breaks. Across statements: each period's closing balance equals the next period's opening balance, with no gaps.

Say in your covering note that you ran both. It takes one sentence and it removes an entire category of doubt — and of billable investigation.

flowparse.io

Step 5 — Consolidate, with a reference on every row

Several accounts across twelve months is dozens of documents. Merging them by hand is where mismatched columns and double-processed files enter.

Smart Merge consolidates up to a hundred statements into one workbook with unified columns, duplicate detection across overlapping periods, and a source-file reference on every row — so a question about a single figure is answered in ten seconds instead of a re-derivation.

Keep an account column too. A consolidated sheet where you cannot tell which account a row came from creates exactly the ambiguity the consolidation was supposed to remove.

flowparse.io

Step 6 — Categorise only what you actually know

Light categorisation helps: your recurring suppliers, your obvious costs, the payments you can identify instantly. Sort by payee and label the top twenty — it is half an hour and it removes hundreds of questions.

Guessing does not help. A wrong category has to be found and undone, which costs more than a blank one, and it can quietly survive into the accounts if it looks plausible. Leave uncertain rows blank rather than optimistic.

Four categories should never be guessed at all: transfers between your own accounts, owner draws and injections, anything that might be a capital purchase, and anything that might be personal. Flag those for discussion — they are the ones that distort a set of accounts, and they are decisions rather than labels. Our categorisation guide covers the mechanics.

Step 7 — Write the gaps down and send them

Every real handover has gaps. The difference between an expensive one and a cheap one is whether they are disclosed or discovered.

• Statements you could not obtain, and what you did to try.
• Payments nobody can identify — payee, date, amount, what you know.
• Costs with no receipt or invoice, listed rather than hidden.
• Anything unusual: an asset bought, a loan taken, a grant received, a one-off refund.
• Personal spending that ran through a business account.
• Any period where the business changed shape — new account, new structure, new activity.

A short honest list is a professional handover. Silence about the same items is the thing that turns a two-day job into a two-week one.

What format to send

If your accountant specifies a format, send exactly that — a file that drops into their system beats anything you could tidy manually.

If they have no preference, send an Excel workbook plus the original PDFs. Excel because it is universal, sortable and reviewable; PDFs because they are the evidence. If they keep your books in accounting software, the same extraction also produces QBO, OFX, a Xero statement CSV and DATEV files, so ask which they want before exporting.

One workbook per entity, one row per transaction, one column set throughout. Multiple tabs per month look organised and are harder to work with than a single flat table with a period column.

flowparse.io

Receipts, invoices and the documents behind the payments

Statements prove that money moved; invoices and receipts prove what it was for. For anything material — and for every tax claim that depends on the nature of a cost — your accountant needs the document, not the payment line.

Send them organised by period, and if they only exist as paper or photographs, convert them into a schedule with merchant, date, total and tax so they can be matched to payments by amount and date rather than opened one by one.

Where documents are missing, recover what you can from supplier portals and email, then list what remains. Whether a cost can be claimed without its document is a question of law and circumstance — it is your accountant's answer to give, and it is much easier to give against a short specific list.

flowparse.io

The covering note that saves a week

Half a page, sent with the pack, answering the questions your accountant would otherwise have to ask over three separate emails.

What the business did this period and anything that changed. Which accounts are included and why the list is complete. Confirmation that every statement reconciles to its closing balance and that the periods are unbroken. What is missing. What is unusual. And the specific things you would like them to look at.

It takes fifteen minutes and it is the single highest-leverage item in this guide — because it converts their first week from investigation into work.

What not to do

The deleted-personal-transactions one deserves emphasis. It feels like tidying and it is the most damaging item on the list: once rows are removed, the account no longer agrees with the bank, and your accountant now has an unexplained difference to chase that you created deliberately.

A worked example: a two-hour handover

A small consultancy: one business current account, one card, one payment processor, twelve months.

First twenty minutes. Write the account list. A savings account that received two transfers turns up, and a card closed in September — both would have been holes. Download all statements, named by account and month. Two card statements are outside the download window and are requested from the bank the same morning.

Next thirty minutes. Convert all thirty-eight documents in one batch. One statement fails the balance check — two rows lost behind a mid-page summary box — and is re-processed. The period sequence check finds one month never downloaded. Both are fixed before anything is sent.

Next forty minutes. Consolidate into one workbook with account and source-file columns. Sort by payee, label the top eighteen, leave the rest blank. Pair nine transfers between own accounts so they are not read as income and expense.

Last fifteen minutes. Write the covering note: accounts included, both checks passed, fourteen payments with no receipt listed, one asset purchase flagged, two requested statements still outstanding with dates. Send the workbook, the PDFs and the note.

What the accountant does not do afterwards: chase, retype, or wonder. That is the entire return on two hours.

The questions you will be asked anyway

Whatever you send, a handful of questions come back. Answering them in advance is the cheapest possible use of fifteen minutes, because each one otherwise costs an email round-trip at their hourly rate and yours.

None of these require accounting knowledge to answer. They require knowledge of your own business, which is exactly the thing you have and your accountant does not.

Making the next handover smaller

The best version of this guide is the one you barely need, because the pack assembles itself as the year goes along rather than in a weekend afterwards.

Three habits do most of it. Convert the non-feed accounts monthly rather than annually — it takes minutes and the transactions are still fresh in memory. Keep one folder per account with a consistent naming convention, so the pack is a copy rather than a hunt. And deal with unidentified payments in the month they happen, when you can still remember what a supplier was for.

Practices that ask clients for a quarterly pack rather than an annual one report the same thing consistently: the questions get answered, because they are asked while the answers still exist. If you want a rhythm to follow, the month-end close checklist is the light version, and bookkeeping with AI covers what to automate around it.

More than one business, or a business and a rental

If you run two entities, or a company alongside personal rental income, keep them in separate packs from the start. One workbook per entity, one folder of statements per entity, one covering note each.

Mixing them is the single most reliable way to create work: an accountant then has to separate what you combined, using guesses about which account belongs to which activity, and the errors that result are the kind that surface a year later in the wrong set of accounts.

Where a genuinely shared account exists — one card used across both — say so explicitly and let them decide how to split it. That is a judgement with tax consequences, and it is theirs to make rather than yours to assume.

If you are the accountant receiving this

The same guide works in reverse as an onboarding document. Send clients the account list template, the naming convention and the two completeness checks, and the quality of what arrives changes immediately — most clients are not being difficult, they simply have never been told what good looks like.

For the clients who will never do it, do it yourself in batch: convert every client's statements in one sitting rather than switching context per client. See the accountants' workflow, batch processing and, for volume, the API.

And consider moving the whole thing quarterly. Four small handovers produce better records than one large one, because the questions are asked while the answers still exist — the close checklist is the rhythm that supports it.

When to send it

Earlier than you think, and earlier than the deadline suggests. Every practice has a compression period where most clients arrive at once, and work that lands inside it competes with everything else for the same hours.

Ask your accountant when their quiet weeks are and aim for those. The same pack reviewed in a quiet month gets more attention, more questions asked, and usually a better result — and if something is missing there is time to find it rather than to work around it.

Send it complete rather than in instalments, too. A pack that arrives in four emails over three weeks gets started four times, and the restart cost is real. The exception is anything you know will take the bank weeks to produce: tell them that is coming, send the rest, and let them plan around one known gap instead of an unknown number of them.

Sending it securely

A handover pack is a complete picture of your finances — account numbers, counterparties, balances. Use your accountant's portal if they have one; if not, a shared drive with access controls beats email attachments, and email beats a public link.

On the conversion side: 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 — the detail is on the security page. FlowParse is hosted and cannot be self-hosted, and it is not an archive: keep your own copies of the originals, because retention obligations stay with you.

The handover checklist

Frequently asked questions

Keep reading