Fix PDF to Excel Conversion Errors

When a bank statement conversion fails, it usually involves a few common problems. The PDF might be locked, it could be a scan (which is basically images), the statement layout may be complex, or the file might “convert,” but the numbers don’t match up afterward.

Use this page as a checklist to identify the issue in two minutes, fix it, then do a quick sanity check before importing anything.

Quick check: what type of PDF is this?

Open the PDF and try to select text with your mouse.

• If you can highlight the transaction text, it’s a downloaded PDF.
• If you can’t highlight anything and it feels like a photo, it’s a scanned PDF.

Also, if the PDF asks for a password to open, it’s password-protected.

That should help you decide the right fix most of the time.

1) Password-protected PDF

If the converter refuses the file, fails immediately, or gives a blank or partial sheet, the PDF is often locked.

If your converter supports passwords, enter it during upload.

If it doesn’t, create an unlocked copy by opening the PDF (enter the password) and “printing” it to a new PDF. Windows often shows Microsoft Print to PDF. Then upload the unlocked copy.

If you don’t have the password, download the statement again from the bank portal or get the correct password from the account owner.

You can use our free unlock PDF tool to unlock PDFs.

2) Scanned (image) PDF

If the output is blank, incomplete, or looks like nonsense, you likely uploaded a scan.

Scans are harder because there’s no selectable text, so the converter has to interpret the page layout. If the scan is blurry, skewed, or heavily compressed, conversion quality drops sharply.

Fix this by using a converter that supports scanned statements and keeps rows and columns intact.

3) Columns are shifting or misaligned

If dates end up under descriptions, amounts shift to the wrong column, or page two looks different from page one, this is usually a problem with the statement layout (multi-column, spacing changes, repeating headers, etc.).

Fix this by not trying to fix it in Excel first. Re-run using a tool that’s made for bank statement tables. Then spot-check a few tricky rows (long descriptions, large amounts) — those are the first to break.

Option: For scanned, multi-column, and password-protected PDFs (enter password during upload), you can use SmartBankStatement to export Excel, CSV or QuickBooks.

4) Descriptions are split across multiple rows

If one transaction becomes two or three rows, it’s usually because the narration wrapped onto the next line and the converter treated it as a new transaction.

Fix this by using a converter that keeps wrapped lines attached to the same transaction.

If you’re already working in Excel, be careful. Sorting or deleting “blank” rows can detach amounts from the correct dates. First, make sure each amount still matches the same row when compared to the PDF.

If your narration is breaking into extra rows, SmartBankStatement stitches continuation lines back into the correct transaction row before export.

5) Debit/Credit is flipped (or signs look wrong)

If money out shows up as credit, money in shows up as debit, or everything appears as positive, the statement is using a convention that your converter guessed wrong (CR/DR tags, two amount columns, parentheses, etc.).

Fix this by deciding what your output should look like and keeping it consistent: either separate Debit and Credit columns, or a single Amount column where debits are negative and credits are positive.

Then validate using rows you already know (salary credit, EMI debit, card payment debit). If the direction looks wrong, don’t import.

If you notice debit and credit getting flipped or missing after conversion, SmartBankStatement can help detect and auto-correct these gaps.

6) Dates are wrong (DD/MM vs MM/DD)

If 02/03/2026 becomes February 3 instead of March 2 (or vice versa), the date format is unclear.

Fix this by matching the statement’s format and keeping it consistent across the file. If you’re importing into QuickBooks or Xero, match what the importer expects and don’t mix formats within the same CSV.

7) The balance doesn’t tie (most dangerous)

If the ending balance doesn’t match the statement, something likely went wrong: a row was missed, merged, or an amount was misread. This error can waste hours later because it’s not obvious at a glance.

Treat it as a stop sign. Don’t import. Re-run conversion with the right method for your PDF type, then do a quick check: spot-check a few rows and confirm the ending balance matches.

If you want a faster way to catch and fix this, SmartBankStatement runs reconciliation checks, flags (and in many cases auto-corrects) balance drift before you export.

Deeper walkthrough here: How to reconcile bank statements in Excel.

8) The file is huge and conversion times out

Very large PDFs (hundreds of pages or years of statements) are slower and more likely to fail.

Fix this by splitting the file by month or year and converting in smaller batches. It’s faster, easier to validate, and simpler to re-run if one batch fails.

We also provide free tools to split and compress PDFs.

QuickBooks/Xero import failures are usually formatting details

Even if the Excel looks fine, imports often fail due to small issues: date format, amount signs, extra header rows, blank lines, hidden currency symbols, or mismatched columns.

Once the ledger is correct, export to the exact format required: How to import into QuickBooks & Xero.

Key takeaway

If the output looks “mostly fine,” still verify it. The dangerous failures are subtle: a shifted column, a missing row, or a balance mismatch. Treat balance drift and debit/credit direction errors as stop signs before importing.

Next step

Before importing anything, do two checks: spot-check a few rows against the PDF, and if a balance column exists, confirm the ending balance matches. If those checks fail, fix the conversion first. It’s always cheaper than fixing financial books later.