Converting a year of bank statements to Excel at once, without uploading any of them

If you keep the books for other people, statement season is a folder, not a file. This is how to get a whole folder into spreadsheets in one run, with every statement staying on your own machine.

Last checked 2026-11-02.

Convert a folder of statements

Why bookkeepers cannot use the first converter they find

A single statement is a disclosure about one person. A bookkeeper's folder is a disclosure about every client at once: names, account numbers, payroll, rent, who they pay and when. Uploading that to a converter whose privacy policy you have not read is not a small risk taken once, it is the same risk taken sixty times a quarter.

The engagement letter usually says something about safeguarding client records, and many clients now ask outright where their documents go. "Into a website I found on Google" is not a good answer. "Nowhere, the conversion runs on my computer" is, and it is one you can demonstrate rather than assert.

That is the point of doing this in the browser. Our PDF to Excel tool reads the PDF, runs character recognition on scans, and writes the workbook on your own machine. The page is served with a security policy that forbids it from opening a network connection, so even a bug in our code could not upload a file. Open the developer tools, watch the network tab, and convert: nothing leaves.

Before you convert anything, check for an export

This is worth knowing before you build a monthly conversion habit, because a real export beats any conversion: nothing is guessed. Most banks offer CSV, OFX or QBO downloads a click or two away from the PDF, and most accounting packages import those directly. If your client can give you a bank feed or an export, the converter is the wrong choice for that client, and the right move is to ask once.

Conversion is for the rest: the small bank with PDF-only statements, the client who sends a shoebox of printed pages, the historical year you need for a catch-up job where the online banking history has already rolled off.

Doing the whole folder in one run

On the free tier the tool takes three files at a time, and three statements is one quarter of one client. The paid plan exists for the folder: drop any number of PDFs, and they come back as one workbook each, plus a single ZIP holding all of them. One run is one run, however many files are in it.

Name the files before you start. Each workbook takes its name from its PDF, so `acme-2026-03.pdf` becomes `acme-2026-03.xlsx`. A folder named consistently sorts itself.
Answer the OCR question once. If any statement in the batch is a scan, the tool asks once whether to read scans with OCR, then applies the answer to the whole folder. Text PDFs in the same batch are read directly and never go through recognition.
Expect a note, not a failure, for a bad file. A statement that needs a password, or a file that turns out not to be a PDF, is named in a note at the top of the results while the rest of the folder converts. Fix the one file and run it alone.
Download the ZIP. One archive, one workbook per statement, in the order you dropped them.

A year of twelve statements, two of them scans, takes about a minute on an ordinary laptop. The scans are what take the time; a text PDF converts in well under a second.

The checks that catch what converters get wrong

Run these on every workbook. They take less time than reading this paragraph and they find nearly everything:

Sum the amount column and compare it with the statement's own closing balance movement. A mismatch means a value landed in the wrong column, which this guide explains.
Count the rows against the number of transactions printed on the statement. Missing rows are usually a description that wrapped onto two lines and became its own row.
Check the first and last transaction on each page. Page edges are where every converter is weakest.
For scans, spot check five figures. Recognition mistakes hide well in a column of numbers; a 3 read as an 8 does not look wrong until the total does.

If the client's statements have separate debit and credit columns, confirm that empty cells stayed empty rather than shifting the row left. And delete the summary block that most statements print above the transactions; it comes through as a few ragged rows at the top.

What to tell the client

One sentence covers it: the statements were converted on our own computer with a tool that does not upload files, and we can show the network log if you would like to see it. Clients who have been asked for documents by a dozen online services tend to notice when one firm does not ask them to trust a stranger.

For firms that want it in writing, the privacy page on this site describes exactly what the tool does and does not do, and the security policy that enforces it is visible in the page's response headers.

Questions people ask

How many statements can I convert at once?

Three at a time on the free tier. Any number on a plan, at up to 200 MB per file, with one ZIP for the lot. See Free vs Pro.

Are client statements uploaded anywhere?

No. The PDF is read, recognized and written to a workbook inside your browser. The page's security policy forbids the tool from opening a network connection, which you can confirm in the network tab while it runs.

Does it handle scanned statements?

Yes, with OCR that runs on your computer after a one-time download of the recognition engine. Read how scanned PDFs are converted, and check a few figures by hand afterward.

Will the workbooks open in Excel, Google Sheets, and my accounting software?

The output is a standard .xlsx, or CSV if you prefer. Excel, Google Sheets, LibreOffice and Numbers open it, and most accounting packages import CSV.

What if one statement needs a password?

It is named in a note and skipped; the rest of the folder converts. Remove the password from that file and run it on its own.

Try it

Drop the folder, answer the OCR question once, download one ZIP. Nothing is uploaded, and you can watch the network tab while it works.