Skip to content

Find missing transactions after bank statement PDF extraction

Troubleshoot missing rows in extracted bank statement CSVs. Check page breaks, scanned pages, totals and the complete source PDF before importing.

Upload statement PDFs

How does this work?

When transactions are missing from an extracted bank statement, compare the CSV with the original PDF page by page. Check complete page coverage, the first and last transaction on each page, and debit and credit totals. Re-extract a clearer complete PDF if needed, then review the replacement output before importing it.

Updated · Accounter product workflow guide

  1. 1.Confirm the PDF includes every page of the intended account and statement period. Check printed page numbers and the final page.
  2. 2.Compare the first and last transaction on each PDF page with the extracted rows. Page boundaries are useful places to find omissions.
  3. 3.Identify unreadable scans, cropped columns, rotated pages and tables that continue on the next page. Download the original digital statement where possible.
  4. 4.Compare transaction amounts and totals, keeping repayments, refunds and bank fees visible. A row count alone is not proof of completeness.
  5. 5.Retry extraction with the complete readable PDF and compare versions before replacing a CSV. Avoid importing both versions into the same ledger.

Try statement extraction

Preview the extracted rows before downloading. CSV downloads require an account and available credits. For batch processing, sign in and use available page credits from a purchased pack or subscription. Enter passwords per file when prompted.

Upload your bank statement

Drop your bank statement PDF here, or click to browse

PDF only · up to 20 MB

Your PDF is read by Accounter using Google and OpenRouter AI services, outside South Africa. Without an account, the preview and the PDF are deleted within 3 hours. How we handle statements

No account needed to preview. Sign in only when you want the CSV.

Read our privacy policy and extraction pricing before uploading.

Example: a transaction at a page boundary

Fictional example: page one ends with a R250 debit dated 12 September. Page two begins with another R90 debit on the same date. The CSV contains only the R90 row. Compare the page-one footer and transaction line, confirm the R250 is a posted transaction, and correct or re-extract it. Do not assume two transactions on the same date are duplicates.

Troubleshooting your statement

A whole page is missing

Check whether that page was included, readable and upright. If you split a PDF, confirm that every output page was retained and reviewed.

Only the last row on a page is missing

Inspect the page boundary for a cropped amount or description continuation. Use the original full PDF for the next attempt.

The PDF has summary entries

Distinguish actual posted transactions from opening balances, totals, pending items and account summaries. Summary lines do not always belong in a transaction CSV.

Frequently asked questions

Can AI extraction miss transactions?+

Yes. Layout, readability and extraction errors can omit or misread rows. Compare output with the source statement before relying on it.

Is the CSV row count the same as the PDF line count?+

Not necessarily. A transaction may span multiple printed lines, while headers and summary rows are not transactions. Compare actual transactions rather than all text lines.

Should I merge a partial CSV with a retry?+

Only after comparing both outputs with the PDF. Blindly appending retries can duplicate transactions already present.

Can I use a screenshot instead?+

A complete original PDF is preferable. A screenshot may omit columns or rows, and cropped or low-resolution input can make omissions harder to diagnose.

Related extraction workflows

Bank statement extractionFix CSV import errorsOpen statement CSV in ExcelStatement history