How to convert a PDF bank statement to Excel safely

By Arron Child, reviewed by Arron Child. Updated 15 July 2026.

A statement PDF is a picture of a table. Excel needs the table itself. The gap between those two things is where conversions go wrong, so a safe conversion is less about extraction and more about proof: when you finish, you should be able to show that every row made it across and every amount is right.

Before you start: check the file

Only a digital PDF, downloaded from online banking, converts reliably. Open the file and try to select a line of text with your cursor. If the text highlights, you have a digital statement. If your cursor drags a box or selects nothing, you are holding a scan, and any tool that claims to convert it is guessing at pixels. Ask the account holder for the original download instead; every UK bank's online banking produces one. More on telling the two apart.

The safe route

  1. Convert locally if you can. A statement is one of the most sensitive documents a client will ever hand you. ukbankconv reads the PDF inside your browser tab, so the file never reaches a server; whatever tool you use, check its data handling page for a concrete claim, not the word "secure".
  2. Export to XLSX with real cell types. Amounts should arrive as numbers with a currency format, dates as dates, not text that Excel may reinterpret. Text-typed amounts are the root of most "SUM is wrong" mysteries.
  3. Keep debits and credits in separate columns, plus a signed amount column. UK statements print money out and money in separately; keeping both makes errors visible.

Prove the conversion, do not trust it

Reconcile before you use the sheet. Three checks catch nearly everything:

  • Opening balance plus total money in minus total money out must equal the closing balance, to the penny.
  • Each printed running balance must follow from the previous one plus that row's amount.
  • Row count in Excel must match the statement, remembering that brought-forward and carried-forward lines are markers, not transactions.

ukbankconv runs these checks automatically and refuses to label a result verified unless all of them pass; if you converted another way, the bookkeeper's checklist walks through doing them by hand, and the free statement balance checker will find the first break in a pasted table.

Common failure points to look for

  • A wrapped payee name split into a second, amount-less row.
  • The last transaction before a page break missing entirely.
  • Debits landing in the credit column on statements with drifting column positions.
  • 1,234.56 imported as 1.23456 or as text, depending on locale settings.

Any of these will show up as a reconciliation failure, which is exactly why the checks matter more than the extraction.

This guide describes converting data you are entitled to process. It is not accounting, tax, or legal advice. Reviewed 15 July 2026.