How to Convert a Year of Bank Statements at Once

TL;DR: To convert a year of bank statements at once, download the twelve monthly PDFs for the account, upload them as a single batch of up to 50 files, turn on merging so they combine into one continuous extraction, then export one QFX file for Quicken or one OFX file for MS Money and other software that reads the open format. Merging only makes sense when every document belongs to the same account. Import in date order, avoid overlapping periods, and back up the destination file first. The whole job takes minutes rather than the afternoon that twelve separate conversions and twelve separate imports would cost.

Why a year of history has to come from statements

Most large US banks serve roughly 90 days of downloadable activity through the connection your finance software uses. That limit is set at the bank, not in your software, so it does not matter how many times you disconnect and reconnect the account. If you notice in November that the feed broke in March, reconnecting picks up from about August and the missing months stay missing.

The statement archive is the exception. Banks keep monthly PDF statements available for years, often seven, long after the transaction download screen has stopped serving the same period. Those documents contain exactly the same transactions in printed form. Converting them is the practical route to loading a full year, and for some account types it is the only route there is.

This is also why the job tends to arrive all at once rather than gradually. Nobody converts a year of statements because they felt like it. They do it because a bookkeeper took on a client with nothing in the software yet, because a tax year has to be rebuilt from documents, or because a switch to new finance software left the history behind.

How do I convert multiple bank statements at the same time?

Select all the PDFs in one upload instead of adding them one at a time. A bulk bank statement converter takes up to 50 files in a single batch, each up to 50MB, and extracts the whole stack in one pass. The statements can come from one account or from several different banks, because each document is read on its own layout rather than through one shared template.

The part that saves the most time is not actually the upload. It is the other end. Twelve separate conversions produce twelve files, which means twelve import dialogs in your finance software, twelve chances to pick the wrong account, and twelve entries in a downloads folder that all look alike. One merged file means one import.

Should you merge the statements or keep them separate?

Merging combines the documents into a single extraction before any transactions are read out. It is the right choice in exactly one situation: every file in the batch belongs to the same account. Twelve monthly PDFs for one checking account merge into one continuous file covering the year, you review one transaction table, and you run one import.

Leave merging off whenever the batch spans more than one account. A merged file holding a checking account, a savings account and two credit cards produces one transaction list that has to be pulled apart again before any of it can be imported, and separating transactions after the fact is considerably more work than never combining them. The same applies to client work: run one batch per client, because mixing client data into a single file creates a separation problem nobody wants to explain later.

One less obvious case where merging helps is a statement the bank split across two PDFs. That is still one statement period, so merging restores it to a single document before extraction rather than producing two fragments with a break in the middle.

Which format should you export for a year of history?

Format matters more in bulk than it does for a single statement, and the reason is duplicate handling. QFX and OFX both carry a unique identifier on every transaction. When two batches overlap at a month boundary, which happens constantly when history is loaded in pieces, that identifier is what lets your software recognize a line it already has instead of adding it a second time.

CSV has no such field. A CSV import is rows and nothing more, so importing January twice puts January in twice, and finding it afterwards is a manual job. CSV is a fine choice when the destination is a spreadsheet and you intend to sort and total it yourself. It is a poor choice for loading a year into finance software.

For Quicken specifically, export QFX. Quicken imports QFX, QIF, CSV and QXF files, and a plain OFX file is not on that list, which catches people out because the two formats look interchangeable and are not. Renaming the extension does not help, since the identifiers Quicken checks live inside the file. For MS Money, GnuCash, Banktivity, Moneydance or Xero, plain OFX is the right pick. There is more detail on the differences on the bank statement to OFX converter page.

How do I import a year of transactions into Quicken?

Convert the statements to QFX, then import through File, then File Import, then Web Connect File, selecting the existing account rather than letting Quicken create a new one. Quicken cannot read a PDF directly, so the conversion step is not optional. Back the file up before you start, because a large import is not something you want to unpick by hand.

Load the periods in date order so the running balance reads sensibly as you go, and work in non overlapping ranges wherever the statements allow it. The transaction identifier in a QFX file gives Quicken a real basis for spotting repeats, but avoiding the overlap is still less work than reviewing a duplicate prompt on every line of a shared month. The full walkthrough sits on the convert bank statement to Quicken page.

Can you convert statements from different banks in one batch?

Yes, and for anyone doing client work it is the normal case. Every bank lays its statement out differently, so a folder holding Chase, Wells Fargo and a local credit union statement converts in one pass without sorting the files first. What you should not do is merge that batch, for the reasons above. Keep mixed batches unmerged and you get one file per statement, each ready for its own register.

What about scanned statements from older years?

Scans, photographed pages and image only PDFs go into the same batch as ordinary text PDFs. This matters more than it sounds, because the older a statement is the more likely it is to be a scan, and those are precisely the periods that are hardest to obtain any other way. Give scanned documents a closer accuracy check than text PDFs, since image quality affects how cleanly amounts read.

How do you check accuracy across fifty documents?

Nobody is going to read every line of a year of statements, so check the things that fail loudly instead. Compare the transaction count and the closing balance of each extraction against the printed statement. A missed or misread amount changes the total, so a closing balance that matches is strong evidence the lines in between are correct.

That check takes a few seconds per statement and it is far more reliable than skim reading hundreds of rows. It is also the check worth doing before the import rather than after, because fixing an extraction is trivial and unpicking a bad import is not.

Fitting this into a wider catch up

Converting the statements is usually the first item on a longer list. A year of bank history rebuilds the cash side of the books, but the same catch up almost always arrives with a pile of supplier paperwork attached, and it is worth pulling the line items out of those invoices automatically at the same time rather than keying them in once the transactions are already loaded. Doing both from documents, in the same sitting, is what turns a stack of PDFs into a set of books that actually reconciles.

The short version

Download the twelve statements. Upload them as one batch. Merge them if they are all the same account, and do not merge them if they are not. Export QFX for Quicken or OFX for everything else that reads the open format, keep CSV for spreadsheets, then import in date order without overlapping periods and check each closing balance on the way through. That is the whole job, and it is a short one once it stops being twelve separate jobs.