Converting a year of bank statements at once
Year-end is the point where converting statements one at a time stops being reasonable. You can drop a whole year in together. Each PDF is read and checked on its own, and only then are the results merged into a single table in date order — which matters, because a problem in March’s statement stays attached to March rather than quietly spreading across the year.
Each statement keeps its own verdict
Every file is reconciled against its own printed balances before anything is combined. The merged view carries those verdicts with it: a flagged row still points at the statement and the page it came from, and a file whose figures could not be checked at all — a card statement with no running balance, say — does not drag down the files that could be.
Overlapping statements, and the duplicate rule
Downloaded statements often overlap at the edges, and the same transaction can appear at the end of one and the start of the next. A row is treated as a duplicate only when its date, its signed amount, its description and its position among that day’s transactions all match — and, where both statements print a running balance, when the balances match too.
That last condition is the one that earns its keep. A current account and a savings account can both show an identical transfer on the same day for the same amount with the same wording. Dropping one of those would delete a real transaction and leave a year that looks tidy and is wrong. Their running balances differ, so both survive.
The cost of that caution: a genuine duplicate whose balance was misread stays in the table. It stays in flagged, though, where you will see it — which is the right way to be wrong about it.
Why the download may be more than one file
If you are exporting to QuickBooks as a CSV, a year of transactions will not fit inside the size limit QuickBooks imposes on an upload. Rather than handing you a file it will reject, the export splits into parts that each fit, and every part carries its own header row so each one imports on its own. Import them in order and the result is the same as one file would have been.
The QBO route avoids the limit and the column mapping entirely, and is worth preferring where your software accepts it. Importing into QuickBooks Online covers that path.
A sensible order of work
- Gather the PDFs from online banking rather than scanning paper — a downloaded statement carries a text layer, a scan does not.
- Drop them in together and let every file finish before reading anything.
- Deal with flagged rows first, statement by statement. They are usually few, and each one names its page.
- Decide what the file should say about anything left unresolved: flagged rows can be marked in a status column, or the file held back until they are settled.
- Export once, and keep the original PDFs. The export is a derived document; the statement is the record.
What a year will not tell you
Merging does not re-check anything. It carries forward what each statement proved on its own, because a row cannot become more trustworthy by sitting next to other rows. If three months of the year are card statements with no running balance, those months arrive unchecked no matter how clean the other nine are — and the results say so rather than averaging it away.
Need the file first?
Convert your statement here. Free, no account, nothing uploaded.