Getting started

PDFTables not working: why bank statement conversions go wrong

PDFTables not working on your bank statement? The usual causes, a check that proves a converted file is complete, and what to do if the table breaks.

Editorial illustration for PDFTables not working: why bank statement conversions go wrong

When a PDF-to-Excel converter such as PDFTables fails on a bank statement, the cause is usually the file, not the tool: the PDF may be a scanned picture, locked, or laid out so rows wrap across lines. You can find out which in a few minutes, and a simple balance check tells you whether the output you did get is trustworthy.

Why does a statement PDF fail to convert?

  • The PDF is a scan or a photo. Text cannot be selected, so there is nothing to read as a table. Try selecting a line of text with your cursor; if it will not highlight, it is an image.
  • The PDF is locked. Many bank statements need the owner to type the statement's own opening code before the file will open. A converter may refuse locked files, so open it normally and save an unlocked copy only if that is allowed for your document.
  • The narration wraps over two or three lines, so one transaction becomes several rows.
  • Debit and credit are in one column, or the running balance sits on the same line as the amount.
  • Page headers and footers repeat on every page and land in the middle of your data.

We cannot say how any particular converter handles each case, so check its own help for file limits. What you can do is look at the result.

A balance check that proves the conversion

Every statement has an opening balance, a closing balance, and rows in between. If the converted rows are complete, then opening balance plus total credits minus total debits must equal the closing balance. Use Excel or Google Sheets.

  1. Put the opening balance in a cell, say F1.
  2. Total the credits column: =SUM(C2:C300). Put the result in F2.
  3. Total the debits column: =SUM(D2:D300). Put the result in F3.
  4. In F4 type =F1+F2-F3 and compare with the closing balance printed on the statement.

Say the opening balance is ₹42,000, credits add up to ₹65,500 and debits to ₹58,300. Then 42,000 + 65,500 - 58,300 = ₹49,200. If the statement's closing balance says ₹49,200, you have every row. If it says ₹48,950, you are ₹250 out, so a row of ₹250 is missing or doubled.

How do I find the missing row?

Gap sizeLikely causeWhat to look at
Equals one amount in the statementOne row droppedSearch the PDF for that amount
Equals double an amountOne row doubledSort by amount and look for twins
Matches a page's totalA whole page skippedCheck the first and last row of each page
Small odd numbersText read as numbers wronglyLook for commas or minus signs stuck in cells

Do I need a converter at all?

Often not. Look at the statement download options in your bank's own channels for a CSV or Excel file, and check its help pages for the route, since layouts differ. A native spreadsheet file skips the PDF problem altogether, and the same balance check still applies.

SpendixAI accepts statements as PDF, CSV or Excel, so you can upload the file you have without converting it first. You pick the account, review the rows before saving, and fix anything that did not read correctly. we would not promise that every layout parses perfectly, which is why the review step exists.

What to do when the table still breaks

  • Try the CSV or Excel statement route first.
  • Download the statement again in a different date range, such as a single month.
  • Fix the few bad rows by hand rather than redoing the whole file.
  • Keep the original PDF untouched as the reference copy.
  • Never upload a statement to a site you do not trust, and check what a tool says it does with your file.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports