Guides · October 3, 2026

How to Convert a Scanned Bank Statement to Excel

Paper statements still turn up everywhere: an old account you closed years ago, a box of records for a tax return, a client who hands over a folder instead of a login. Once those pages are scanned, you have a PDF, but not a spreadsheet. This guide covers how to get a scanned bank statement into Excel (or CSV), how to make a scan that reads well, and what to check before you trust the numbers.

The quick way

  1. Scan the statement to a PDF (tips below for a clean scan). Only PDF files are accepted, so phone photos of the pages need to be combined into one PDF first.
  2. Upload it to statementconvert.ai: drag and drop the file.
  3. Preview the extracted rows and look at whether the result agreed with the balances printed on the statement.
  4. Download as Excel (.xlsx), CSV, JSON or XML.

No account is needed to preview: without one, the preview shows the first rows in full and the rest as date and amount. Signing in free with Google shows every row and unlocks the download, and the free plan covers up to 5 statement pages a month.

Digital PDF vs scanned PDF: why it matters

Not every PDF is the same kind of file, and the difference decides how hard the conversion is.

Digital PDFScanned PDF
Where it comes fromDownloaded from online bankingMade by a scanner, copier or phone camera
What is insideReal text characters, laid out on a pageA picture of the page
Can you select a word?YesUsually no, unless an OCR text layer was added
Typical conversion qualityHighGood when the scan is clear, weaker when it is not

A quick test: open the PDF and try to highlight a single word. If you can select and copy it, the file has a text layer and is most likely digital. Scanners and scanning apps sometimes add an OCR text layer to a scan, so a selectable word is a strong hint, not proof. If nothing highlights, or the whole page highlights as a block, you are looking at a scan.

If you can still download the same statement as a digital PDF from online banking, that copy will almost always convert more cleanly than a scan of a printout. Scans are the right route when paper is all you have.

How a scanned statement gets read

Many older tools turn a scan into text with OCR first and then try to rebuild the table from that text, which is where columns drift and amounts end up next to the wrong description.

statementconvert.ai works differently. Each page is read by an AI model (OpenAI first) that looks at the page image itself, so it sees the table the way you do: rows, columns, headings and wrapped descriptions. When a page fails the checks, a second model (Anthropic) re-reads it. The rows are then checked against the balances and totals printed on the statement, where there are any, and the result tells you whether they matched.

That makes a clear scan readable in many cases. It does not make a poor scan perfect. Blurred digits, faint print and cut-off edges are hard for any reader, human or machine.

Scan quality tips that make a real difference

A few minutes at the scanner pays off more than anything else in this guide.

Resolution

  • Scan at 300 DPI or higher. Lower settings blur small digits like 3, 5 and 8.
  • Phone scanning apps usually do fine if the page fills the frame and the photo is sharp, and most can export the pages as one PDF. Plain camera photos need combining into a PDF before upload, since only PDFs are accepted.

Straight, flat pages

  • Lay the page flat. Curled pages and folds bend the rows, and a bent row is easy to misread.
  • Keep the page square to the scanner glass. A slight tilt is usually fine; a steep angle is not.
  • Remove staples and unfold creases before scanning.

Contrast and light

  • Use grayscale or black-and-white with strong contrast. Dark backgrounds and faded toner make digits harder to read.
  • With a phone, use even daylight or a bright room, and avoid your own shadow across the page.
  • Turn off heavy filters or "beautify" modes that smooth out fine print.

Full pages, right order

  • Capture each page edge to edge, including the header, the summary box and the last line of the table.
  • Keep pages in order in one PDF per statement, so the balances carry from one page to the next.
  • Include the summary page. The opening and closing balances are what the result is checked against.

What to check in the preview

The preview is the moment to catch a misread before you download. Without an account it shows the first rows in full and the rest as date and amount; after signing in free with Google, every row is shown in full. For a scanned statement, this checklist covers the common slips:

  • The balance check result. If the result says the rows agreed with the balances printed on the statement, the extracted figures match the balances that were checked. If it says they did not, the rows and the statement differ somewhere, and comparing them shows where.
  • Row count. Count the transactions on one page of the paper statement and compare with the preview for that page. The Excel file has a Page column, which makes this quick.
  • Look-alike digits. Scan for 1 vs 7, 3 vs 8, 5 vs 6 and 0 vs 8 in a few larger amounts.
  • Signs. Withdrawals and debits on a checking account come out negative. On a credit card, purchases are positive and payments are negative.
  • Dates. Check the first and last rows fall inside the statement period, especially near a year end.
  • Wrapped descriptions. Long merchant names sometimes wrap onto a second line on the page; each transaction belongs on one row.

What the balance check does and does not prove

Most statements print an opening balance, a closing balance and often totals for deposits and withdrawals. Those printed numbers are an independent check on the rows. If every row was read correctly, the arithmetic works: opening balance plus deposits minus withdrawals lands on the closing balance.

For scans this matters more than for digital files, because a single misread digit breaks the arithmetic. A match means the extracted figures agree with the printed balances and totals that were checked. It does not prove every row is right, because two errors can offset each other. A mismatch means the rows and the statement differ somewhere; comparing the rows with the statement shows where.

Some statements print no balances at all, and some scans cut them off. In that case there is nothing to check against, and the preview is your only check, so a careful look at the rows matters more.

Honest limits

Scans are where conversion is most likely to go wrong, so it is worth being plain about the limits:

  • Very low-resolution, blurred or faded scans may come back with misread amounts or missing rows.
  • Handwritten notes, stamps or highlighter over the table can confuse the reading of that row.
  • Cut-off columns cannot be recovered. A cropped balance column removes information the reader needs.
  • Photos taken at an angle with heavy shadow are harder than flat scans.

When a page reads badly, rescanning it more clearly is usually faster than fixing rows by hand.

Is it safe to upload a scanned statement?

A scan carries the same sensitive details as the original, so the question is the same as for any upload. We never store your statement: it travels over HTTPS, is processed in memory, its pages are read by our AI providers (OpenAI, and Anthropic for a second reading), and it is then discarded. The providers do not train on it and may keep request logs for up to 30 days. The privacy page has the details, and Is it safe to upload your bank statement online? covers what to look for in any tool.

Many scanned statements at once

If you are digitizing a year of paper statements, paid plans accept up to 12 statements in a single upload and start at $7.99 a month for 100 pages. Each file keeps its own name in the Source File column, so rows from different months stay traceable. Bookkeepers working through client paperwork can see the accountants and bookkeepers page.

For the full set of conversion methods, including the manual ones, see how to convert a PDF bank statement to Excel. If the file is headed into accounting software, converting a bank statement to CSV explains the CSV side.

Convert your scanned statement now

Convert a bank statement to Excel: upload your scanned PDF, preview the transactions and whether they agreed with the printed balances, then sign in free to see every row and download Excel, CSV, JSON or XML. Free for up to 5 statement pages a month, and no account needed to preview.

Frequently asked questions

Can a scanned bank statement be converted to Excel? Often, yes. statementconvert.ai sends each page to AI models that look at the page image, not only a text layer, so a clear scan can usually be read. Scans are more error-prone than digital PDFs, so the preview, and whether the result agreed with the balances printed on the statement, are worth a look before you download.

How do I know if my PDF is scanned or digital? Open the PDF and try to select a word with your cursor. If you can highlight individual words and copy them, the PDF has a text layer and is most likely digital. Scanned PDFs can also carry an OCR text layer, though, so this test is a strong hint, not proof. If the whole page selects as one picture, or nothing selects at all, it is a scan or a photo.

What scan settings give the best result? Scan at 300 DPI or higher, keep the page straight and flat, use good even light with no shadows, and include the full page edge to edge. Black-and-white or grayscale scans with strong contrast tend to read more cleanly than dark or faded ones.

What happens if the totals don't match after converting a scan? The result tells you the balances or totals printed on the statement did not agree with the rows that were read. The rows and the statement differ somewhere, and comparing the preview with the paper page shows where. If the scan is poor, rescanning the page more clearly is often the quickest fix. A match, for its part, means the figures agree with the printed balances that were checked; it does not prove every row is right, because errors can offset each other.

Is my scanned statement stored? Not by us. It travels over HTTPS, is processed in memory, its pages are read by our AI providers (OpenAI, and Anthropic for a second reading) and it is then discarded. The providers do not train on it and may keep request logs for up to 30 days; the privacy page has the details.