Bank statement PDF won't convert? Nine causes and how to fix them
When a statement converts badly, the cause is nearly always one of a small number of layout problems. Match your symptom to the table, apply the fix, and verify the result with a balance check.
By Muhammad Sharif · October 2026 · 9 min read
Statement converters fail in predictable ways, because bank PDFs fail in predictable ways. The tool is not reading a table, it is reconstructing one from text positions, and each of the layouts below breaks a different assumption. If you can name your symptom, you can usually fix it in minutes without retyping anything.
Symptom to cause: the quick table
| What you see | Most likely cause | Jump to |
|---|---|---|
| "No transactions found" or an empty table | Scanned image, or a protected file | 1, 2 |
| Some rows missing | Dates in an unrecognised style, or rows in separate sections | 3, 4 |
| Descriptions cut short or split over two rows | Wrapped description text | 5 |
| All amounts positive | Separate withdrawal and deposit columns | 6 |
| Reference numbers treated as amounts | Long numbers next to real figures | 7 |
| Totals or interest summaries appear as transactions | Summary tables that look like rows | 8 |
| Day and month swapped | Ambiguous date order | 9 |
1. The PDF is a scan or a photo
If you cannot select the text in the PDF with your mouse, there is no text to extract. The page is a picture. Text-extraction tools, including this site's converter, will report no transactions. Fix: download the statement again from your bank's website instead of using a scan, or run OCR on the file and then convert the resulting searchable PDF. The scanned versus text-based guide covers how to tell the difference in ten seconds.
2. The file is password protected
Some banks encrypt statement PDFs with a password based on your date of birth, last digits of your card or account number, or a code from a welcome letter. A browser-based tool cannot read the contents without the password. Fix: open the file in a PDF reader, enter the password, then print to PDF (or use "Save As" without protection) to create an unprotected copy. Delete the unprotected copy once you are finished, because it contains the same sensitive data in the clear.
3. Rows are skipped because the date is not recognised
Transaction detection starts with the date. Most converters recognise numeric styles such as 03/04/2026 or 2026-04-03, and written styles such as 03 Apr 2026 or Apr 3, 2026. A statement that prints dates as "3 April" without a year, or with unusual separators, may be partly missed. Fix: convert what you can, compare the row count to the statement, and add the missing rows by hand. If a bank omits the year in each row, check whether the statement period at the top gives it to you.
4. Transactions are split across sections
Credit card statements, and combined checking-and-savings statements, group transactions under headings: payments, purchases, fees, interest. Each section may have different columns. A converter reading line by line copes with most of these, but section subtotals and "continued on next page" lines can confuse it. Fix: verify per-section subtotals against the statement, and exclude any subtotal rows from your sheet.
5. Descriptions wrap onto a second line
Long merchant names, transfer references and check details often continue on a line below the amount. If the second line is read as its own row it shows up as a transaction without a date or amount. Good converters merge these continuation lines back into the row above. Fix: if you see orphan rows, merge their text into the description above and delete the row. In Excel, =A2&" "&B3 in a helper column does it quickly; copy and paste values back.
6. All amounts come out positive
Many statements print withdrawals and deposits in two separate columns and never show a minus sign. When a row is read as one line of text, the converter sees a single number and cannot tell which column it came from. Better tools infer the direction from the running balance: a row whose balance went down by the amount is a withdrawal. Fix: if the statement has a balance column, rely on a converter that uses it, and confirm with the balance test. If it has no balance column, sort the amounts by hand with the PDF open beside you. The guide to debits, credits and signs shows a formula-based approach.
7. Reference numbers mistaken for amounts
UPI, NEFT, check and wire references are long strings of digits that sit in the same line as the money columns. Converters protect against this by ignoring very long whole numbers without decimals, but shorter reference numbers with a decimal point or in a narrow format may slip through. Fix: amounts should have exactly two decimal places. Filter your Amount column for values with no cents, or unusually large values, and compare against the PDF.
8. Summary tables look like transactions
Account summary boxes ("Total deposits", "Total fees", "Year to date interest") contain a label and a number, and sometimes a date range, which can resemble a transaction. Fix: delete those rows, and always run the balance reconciliation. A summary line included by mistake changes your total and the test will fail, telling you where to look.
9. Day and month are swapped
A date such as 05/04/2026 is 5 April in most of the world and 4 May in the United States. If every date on the statement has a day of 12 or less, nothing in the file can settle it. Better converters look for a date above 12 elsewhere in the same statement to decide. Fix: find a date in the 13th to 31st range, confirm how it was read, and compare the first and last transaction dates to the statement period printed in the header. See the date format guide for the Excel techniques that fix this safely.
If none of these match
Layouts that are dense, landscape, or multi-column (for example a statement printing two accounts side by side) can defeat any line-based parser. Try exporting a single page range from the PDF with your reader's "Print to PDF" function, converting that, and comparing it against the original. If you find a bank layout that fails, send us the bank name and a description; real examples are how the converter improves, and you should never email a statement itself.
Frequently asked questions
Why does the converter find only some pages of my statement?
Usually the missing pages use a different layout, such as a fee summary or a continuation page without a header row, or contain rows with unrecognised dates. Compare the row count by page against the PDF.
Will a different converter fix it?
Sometimes, but the underlying issues are the same for every tool. A scan stays a scan, and an ambiguous date stays ambiguous. It is faster to fix the cause than to try tools one after another, especially if each one uploads your statement to a different server.
Is it worth retyping a statement by hand?
For a handful of rows, yes. For more than a page, a converter plus a balance check is faster and less error prone than typing, because the check tells you exactly which row to fix.
