Home · Free tools · PDF statements to Excel

Getting a PDF statement into a spreadsheet: the three routes

The fastest way to get a bank statement into Excel is usually not to convert the PDF at all. Most banks will hand you CSV, OFX or QIF from the same screen the PDF came from, and a structured export beats every converter because nothing is being guessed. This page is about choosing between the routes. If you already know the PDF is all you have, the bank statement converter does the conversion here in your browser.

Route 1 — ask the bank for CSV (try this first)

Look on the statements or transactions screen, usually within two clicks of the PDF download, for Export, Download, or a small spreadsheet icon. Common formats and what they are worth:

  • CSV — opens anywhere, and it is exact. Take this if it is offered.
  • OFX / QFX / QIF — designed for accounting software; carries transaction types and running balances that CSV often loses.
  • XLSX — occasionally offered, and just as exact.

A structured export takes seconds, has no misread decimals, and costs nothing. Most people convert PDFs because they never saw the export button.

Route 2 — the PDF has real text

Open the PDF and try to select a number with your cursor. If it highlights, the characters are real and no model is involved: copy the table and paste it into a spreadsheet. The usual mess afterward is columns arriving as one blob of text — that is a splitting job, not an extraction one, and a viewer plus a split step handles it.

If nothing highlights, the page is an image of text and you are on route 3.

Route 3 — a scanned statement

Now a model has to read it, and the question becomes where the document goes.

The free online converters that dominate results for this take an upload. A bank statement is the highest-sensitivity document most people own: account numbers, balances, and a complete record of where someone spends money and with whom. Read what a converter says about retention before you drag the file in, and treat anything unstated as unbounded.

Neither the converter on this site nor TableDI 2 reads a scan: both need a PDF with a text layer, and a scanned page is a picture. If a scan really is all you have, ask the bank for the export first; failing that, use an OCR service you trust with the document, and check the closing balance afterward.

What to check before you trust the numbers

  • Row count — a page break mid-table is where transactions go missing.
  • The closing balance — add the transactions to the opening balance and compare. This one check catches most misreads.
  • Debits and credits — some statements use two columns, some one column with signs, some parentheses for negatives. Getting this wrong flips the sign on half your data.
  • Dates — 03/04/2026 is March or April depending on the bank's country.

Once the transactions are in a table

The reason to do this is almost never the conversion itself — it is the summary you want afterward. The monthly report generator on this site takes a CSV of transactions and gives you a month-by-category breakdown with totals, in your browser, with nothing uploaded.

If the same statement has to be matched against your ledger every month, that is the work TableDI 2 is for. TableDI 2 is a desktop app for file work you redo every period: it keeps your sources, rules and delivery as a job, so next month you drop in the new files and run it again. Everything runs on your own machine. It accepts bank statements as text-layer PDFs, and before each run its preflight checks that the opening balance plus the transactions equals the closing balance.

Questions people ask

How do I convert a PDF bank statement to Excel for free?

Check whether your bank offers CSV or OFX export first — it is free, exact, and usually two clicks from the PDF. If the PDF has selectable text, copy and paste it. Only a scanned statement needs a converter, and that is the case where it matters most who receives the file.

Is it safe to upload a bank statement to a conversion website?

Treat it as handing that company your account number, your balances and a full record of your spending. Some services are careful and say so in writing; many say nothing about retention. When the bank's own CSV export exists, it is both safer and more accurate.

Does TableDI upload my documents?

No. The tools on this site read the file with JavaScript in your tab, and TableDI 2, the desktop app, reads it on your own machine. The one exception is optional: if you add an AI key in TableDI 2, drafting a job sends the column names and the first 50 rows straight from your machine to the AI provider you chose — never the whole file, and never through anything of ours.

Can it handle credit card and brokerage statements too?

Same three routes. Brokerage statements are the hardest of the three because positions, trades and cash movements have different table shapes on one page — check the row count per section rather than the document total.

Why did the totals come out wrong?

Nearly always one of three things: a page break dropped rows, the debit/credit convention was misread so signs are flipped, or the decimal separator was read as a thousands separator. Compare the closing balance against the statement — it catches all three.

Doing this every month?

In TableDI 2 you do it once, then save it as a job. Next month you drop in the new files and run it again.

macOS, Apple silicon and Intel; Windows is in progress (what to do meanwhile). Free is not a trial — no account, no card.

Last reviewed 2026-09-11 by the TableDI team. Something wrong on this page? Tell us — it is one inbox, read by the people who build TableDI.