Handing bank statement CSVs to your accountant: a checklist

Published 19 October 2026 · by Tekiba

Before you start: ask what they want

Accountants differ. Some import CSVs into their own software and want a particular column layout or date format; some want the PDFs only; some give clients an upload portal. Ask three things: which file type, which date format, and how to send it. The rest of this list assumes CSV, with the PDFs as backup.

The checklist

1. Cover the whole period, with no gaps. The period is the tax year your accountant is working on. In the US that is usually the calendar year; for UK self-employment it is not, as HMRC puts it: “If you do not prepare accounts, you will need to record your income and expenses for each tax year (6 April to 5 April).” Statement periods rarely line up with either, so include the statements that straddle the start and end, and say so. Lay the periods side by side and check that each one starts the day after the last one ended.
2. One file per account. Keep each bank account and card in its own file, and keep business and personal apart. The IRS is plain about the accounts themselves: “You should keep your business account separate from your personal checking account.” A file that mixes accounts makes every balance check meaningless, because no single statement's balances describe it. How business and personal statements differ covers what changes between them.
3. Check every file against its statement. Opening balance plus every row should reach the closing balance. The IRS asks the same of the books themselves: “When you receive your bank statement, make sure the statement, your checkbook, and your books agree.” If you joined several months into one file, check each month at its own boundaries too; overlapping statement periods are the usual source of doubled rows. Reconcile a bank statement before you import it has the full set of checks.
4. Use one layout throughout. Same columns, same date format, same sign convention — money out negative — in every file. Year-first dates such as 2026-04-06 cannot be misread as day-first or month-first. If your accountant asked for a particular layout, use that instead.
5. Name the files so they explain themselves. Account, last four digits and dates are enough: checking-4417_2026-01-01_2026-12-31.csv. A spreadsheet of fifty statements called statement(23).csv costs your accountant time and you money.
6. Send the PDFs too. The PDF is the statement; the CSV is a convenience made from it. HMRC lists among the proof it accepts “bank statements, chequebook stubs”. Keep your own copies: HMRC says “You must keep your records for at least 5 years after the 31 January submission deadline of the relevant tax year.” The IRS counts from the return, not the statement: “Unless otherwise stated, the years refer to the period after the return was filed. Returns filed before the due date are treated as filed on the due date.” Its usual rule is shorter than HMRC's — “Keep records for 3 years if situations (4), (5), and (6) below do not apply to you.” — and its page lists the situations that make it longer.
7. Write a short note. One line per file with its opening and closing balance, plus anything that will raise a question: transfers between your own accounts (they appear in both files and are not income), a large one-off payment, a refund, an account opened or closed during the year, a month whose statement you could not get.
8. Send only what is needed, the way they ask. A statement carries your name, address, account number and everyone you paid. The ICO's principle for organisations is that personal data should be “limited to what is necessary – you do not hold more than you need for that purpose.” — a fair test for what you send, too: ask whether a personal account is needed before including it. If your accountant has an upload portal, use it. If files go by email, encrypt them, and follow the ICO's advice on the password: “Do not include the password within the same email as the encrypted file attachment.” Check the address before you press send.

An example note

Fictional statement figures, made up for this page.

Where LedgerDrop fits

LedgerDrop turns a statement PDF into a CSV in your browser and checks the rows against the balances the statement prints, so step 3 happens as you convert; the statement is not uploaded. The free CSV uses year-first dates, one signed Amount column and the statement's running balance where it printed one. LedgerDrop Pro converts several statements at once and can write them as one CSV with a column naming the file each row came from, or in QuickBooks Online and Xero layouts. If the CSVs are going straight into software, how to import a bank statement CSV into QuickBooks, Xero or Excel covers what each one expects. For what a statement reveals and how to keep copies under control, see bank statement PDF privacy.

What this page cannot tell you

What your accountant or your tax authority requires of you; the rules quoted are the IRS's and HMRC's general ones, and both list exceptions. Nor does it cover payroll records; for VAT and sales tax, see using a bank statement CSV to prepare sales tax, VAT and consumption tax returns. When in doubt, ask the person who will use the files.

Questions