When an online bank statement converter fails, the cause is usually the file rather than the tool: a scanned or image-only PDF, a locked PDF, an unusual layout, or a very long statement. Work through those four in that order, then compare the output with your statement's totals before you trust a single row. This applies to bankstatementconverter and similar services; nobody outside a tool can see why it failed, so treat this as a checklist for the file in your hands.
Which problem does your file have?
| What you see | Likely cause | What to try |
|---|---|---|
| Upload works but the output is empty | The PDF is a picture of a statement, not text | Download the statement again from your bank's own statement page instead of scanning or photographing a printout |
| Error straight away | The PDF is password-protected | Open it with the password your bank set; the bank's statement email or help page explains how that password is formed |
| Rows appear but columns are shifted | Long descriptions wrap onto two lines, or the layout is unusual | Compare page one of the PDF with the output and note which column drifts |
| Fails only on big files | Too many pages in one go | Convert one month at a time |
How do I know the converted file is correct?
Reconcile it. Statements obey simple arithmetic: opening balance plus credits minus debits equals closing balance. Say your April statement opens at ₹42,500, shows credits of ₹1,10,000 and debits of ₹96,300. The closing balance should be 42,500 + 1,10,000 - 96,300 = ₹56,200.
Now add up the converted file. If its debits total ₹90,300, you are missing ₹6,000 of debits, which is probably one dropped row such as a rent payment. Search the PDF for amounts of exactly 6,000 and add the missing line by hand. Do this check every time; a converter that drops one row looks perfect at a glance.
- Note opening and closing balance from the statement's first and last page.
- Total the credit and debit columns of the converted file.
- Check opening + credits - debits equals closing.
- Compare the row count with the number of entries you can count on the PDF.
- Fix any gap by hand before the file goes anywhere else.
Why do dates and amounts come out wrong?
- Dates read as text such as 05/04/2025, so sorting by date fails. In Excel or Google Sheets, if the text sits in A2, =DATE(RIGHT(A2,4), MID(A2,4,2), LEFT(A2,2)) builds a real date.
- Amounts arrive as text with lakh-style commas such as 1,10,000. =VALUE(SUBSTITUTE(C2, ",", "")) turns the text into a number.
- Debit and credit share one column with Dr or Cr after the figure. Split them into two columns before summing.
- A closing-balance column is mixed into the rows. Keep it, but never include it in a sum.
Is it safe to keep uploading statements to free converters?
A statement carries your account number, your balances and every merchant you paid. Before uploading, read what the service says about how long files are kept and whether you can delete them. A converter should never ask for net-banking logins; if one does, close the page.
What if the converter keeps failing?
Try your bank's own export first. Many banks let you download transactions as CSV or Excel from the statement page, which skips PDF reading altogether; check your own bank's screen for the option because layouts differ.
If you want the rows in an expense tracker rather than a sheet, SpendixAI accepts bank or card statements as PDF, CSV or Excel. You pick the account first, review the rows before anything is saved, and possible duplicate imports are flagged. It does not promise that every layout parses perfectly, so the review step matters.
How do I clean the file once it is converted?
Multi-page statements leave traces. Each page may repeat the column headings, carry a line such as balance brought forward, or end with a page total. Left in, those lines get summed along with real transactions.
- Delete repeated heading rows, then sort by date to see whether anything looks out of place.
- Remove lines that carry a balance forward, since they are not payments. If a statement shows a balance of ₹56,200 carried over, leaving it in adds ₹56,200 to your credits.
- Look at the last row of one page and the first row of the next, where a transaction is sometimes cut in two or read twice.
- Keep one column for the signed amount so that debits are negative.
Ten minutes of cleaning at this stage saves a confusing report later.
Checklist before you retry
- Is the PDF text-based, not a photo?
- Did you unlock it with the right password?
- Did you try one month at a time?
- Do opening, credits, debits and closing balance agree after conversion?
- Have you deleted uploads you no longer need?
Useful ideas start with a clearer picture of your own spending.
Explore your reports
