Bank statements

Why your budget app cannot read a PDF statement, and what to do

Why a budget app cannot read PDF bank statements, with a gig worker's weekly payouts as the example, and the file types and checks that fix it.

Editorial illustration for Why your budget app cannot read a PDF statement, and what to do

A PDF is a picture of a page, not a table of transactions. Your budget app cannot read PDF bank statements when it has to guess where one column ends and the next begins, and gig income makes that guessing harder. The practical fix is to try a CSV or Excel file of the same dates, or to use an importer built around PDF statements and then review every row.

What a PDF actually contains

Inside a statement PDF there are no rows and no columns, only snippets of text placed at coordinates on each page. A human eye sees a neat table. A program sees fragments such as a date, then a gap, then half a narration, then a number. If a long narration wraps onto a second line, the program may treat that line as a new transaction with no date.

Why gig income breaks the guess

A delivery or ride-hailing worker's money moves in many small pieces: weekly payouts from a platform, fuel paid by UPI, a daily phone recharge, an instalment on the vehicle, a cash tip that never shows up at all. The narrations are long and cryptic, and they wrap. Here is how one week might look on a statement.

DateNarration (wrapped)DebitCredit
03 MarUPI platform weekly payout ref 4821-₹6,420
03 MarUPI fuel station₹1,100-
04 MarUPI phone recharge₹239-
06 MarVehicle EMI auto debit₹3,850-

Credits minus debits for that week are ₹6,420 - (₹1,100 + ₹239 + ₹3,850) = ₹1,231. A reader that drops the wrapped line on the first row will lose the payout amount or attach it to the wrong date, and your weekly picture is off by thousands.

Other reasons the import fails

  • The PDF is a scan or a photo, so there is no text to read at all.
  • The file is protected, and the app needs it opened with your own file password first.
  • Page headers and footers repeat on every page and get read as transactions.
  • Debit and credit sit in one column with a 'Dr' or 'Cr' marker instead of two columns.
  • Dates are written in a format the app does not expect.

What should I try first?

  1. Look in your bank's statement download for a CSV or Excel option for the same dates. Check your own statement screen, since menus differ.
  2. If only PDF is offered, download the text version rather than screenshotting or printing it.
  3. Split a long period into shorter windows. Errors multiply over many pages.
  4. Open the first and last pages and note the opening and closing balance, so you can check the result.
  5. After import, compare the app's total debits with the statement's total debits.

Where SpendixAI fits

Statement import is the core flow in SpendixAI: you upload a PDF, CSV or Excel statement, pick the account, and review the rows before anything is saved. It does not connect to your bank and never asks for net-banking logins. No importer can promise that every layout parses perfectly, so the review step matters, and an Import failed notification tells you when a file did not go through. An optional feature for reading an unfamiliar statement layout does process the uploaded document, so use it only if you are comfortable with that.

How do I check a parsed result is complete?

Use the statement's own numbers as the test. The first page usually shows an opening balance and the last page a closing balance. After import, opening balance plus total credits minus total debits should equal the closing balance. Say opening is ₹4,200, credits are ₹31,500 and debits are ₹29,300. Then ₹4,200 + ₹31,500 - ₹29,300 = ₹6,400. If your closing figure is different by exactly one payout, a row was missed. Fix it before you build anything on top of the data.

  • Count rows per page against your import.
  • Look for dates out of order.
  • Look for rows with an amount but no date.

A short checklist before you give up

  • Tried CSV or Excel for the same dates?
  • Is the PDF text-based, not a scan?
  • Shorter date windows?
  • Totals matched against the statement?
  • Cash earnings added by hand so the week is complete?
SPENDIXAI JOURNAL

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

Explore your reports