Your PDF bank statement will not convert: what to check
By the Banking Converter editorial team
Published
Most conversion failures come from one of five causes: the page is an image rather than text, the file is encrypted, the statement is a summary rather than a transaction list, the layout puts a table where no header describes it, or the file is not a statement at all. Each has a distinct symptom, so the message you get narrows it down quickly.
Symptom to cause
| What you see | Likely cause | What to do |
|---|---|---|
| No transaction table found | The pages are scanned images, or the document has no transaction list | Check whether text can be selected in a PDF reader |
| A password prompt | The PDF is encrypted, as issuer-mailed statements often are | Supply the password, or remove it and re-upload |
| Far fewer rows than the statement shows | A block of transactions sits under a heading the extractor did not read as a table | Report it — this is a layout to fix, not a setting |
| Dates a year out | The statement prints day and month only, and the year had to be inferred | Check the period on page 1 covers a year boundary |
| Balances do not reconcile | A row is missing, duplicated, or an amount was read on the wrong side | Read the Conversion Report: it says which check failed and by how much |
| Descriptions merged or split oddly | The description wraps over several printed lines | Confirm the flagged rows in review; edit if a line attached to the wrong row |
First: is it text or a picture?
This one distinction explains most outright failures. Open the PDF and try to select a line of text with the cursor.
- If text highlights, the PDF has a text layer and should convert directly.
- If nothing highlights, or the whole page highlights as one block, the page is an image. It was scanned, photographed, or produced by printing to PDF from a scanner.
Image-only pages are handled with OCR, which is included on every plan. Quality matters more than anything else here: a flat, well-lit, straight scan at 300 dpi reads well, while a photograph taken at an angle in poor light may not. There is more in converting scanned statements.
A hybrid document — some pages text, some scanned — is common when a statement has been partly re-printed. Each page is classified on its own, so the text pages convert directly and only the scanned ones go through OCR.
Encrypted and password-protected files
Banks frequently email statements encrypted with a password derived from your date of birth, postcode or account number. Two different protections exist and they behave differently.
- A user password stops the file opening at all. You must supply it.
- An owner password allows opening but forbids copying or printing. This is what stops you selecting text even though the page is clearly text.
Password-protected PDFs are supported on paid plans; the password is used once to open the document and then discarded. On the free plan, remove the password in a PDF reader first and upload the unprotected copy. The full explanation is here.
Documents that are not transaction lists
Some documents banks call statements contain no transactions at all, and no converter can produce rows that are not there.
- Annual summaries and interest certificates: totals only.
- Credit card statements showing just a minimum payment and a balance, with the transactions in a separate document.
- Mortgage or loan statements listing scheduled payments rather than an account's activity.
- Screenshots of online banking, which show a fragment of a list without the period or the balances that let it be checked.
Download the transaction statement for the period from online banking instead; see downloading statements.
When rows are missing
This is the failure worth taking seriously, because the output looks plausible. The checks exist to catch exactly this.
- Read the Conversion Report. If the balance check failed, the difference is the size of what is missing.
- Compare the row count against any count the statement prints, such as "28 Debit(s) This Period".
- Compare the extracted totals against the statement's own totals for credits and debits.
- Look at the first and last dates. Missing rows often sit at the start or end of a page.
- If a whole section is absent, note which page it is on and report it.
Layouts that lose a block usually do so for a structural reason — a second table on a page whose first table had the only recognised header, or a heading that looks like a column label. Those are fixed in the extractor rather than worked around, so reporting one is worth more than editing around it.
Reporting a statement that will not convert
The most useful report says what the statement should have produced, because that is what makes a fix verifiable.
- The bank and the country.
- How many transactions the statement contains, and how many were extracted.
- Which page a missing block is on.
- The totals the statement prints for the period.
Send it through contact or the feedback control on the conversion itself, which attaches the conversion reference automatically. The document is not needed to start with — the structure usually is.
Frequently asked questions
The file opens fine in a reader. Why can nothing be extracted?
Either the page is an image of text, or the PDF carries an owner password that forbids extraction. Both look identical when reading and are distinguished by trying to select text.
Can a statement be too long?
Plans limit pages per file rather than transactions, and long statements convert normally. A very long file simply takes longer, and the per-file page limit is on the pricing page.
Why did dates come out a year early?
Statements that print only day and month need the year inferring from the period. Where a period crosses a year boundary the inference can be wrong, which is why dates are checked against the statement period and anything outside it is flagged.
Does a failed conversion use my page allowance?
No. Failed conversions are not counted.
Other bank statement converters
About the author
The Banking Converter editorial team is the engineering group that builds and tests the conversion engine: the parsers for regional date and number formats, the reconciliation checks and the CSV, Excel, JSON, OFX and QBO exporters. Guides describe what the software does and what the formats require; they are not financial, legal or tax advice.