FROM PDF ROWS TO STRUCTURED DATA

Extract Transactions from a Bank Statement PDF

To extract transactions from a supported bank statement PDF, open the converter, select the file and read its transaction table into Date, Description, Debit, Credit and Balance fields. Review the preview against the PDF, then download Excel or CSV. Clear English tables with separate debit and credit columns are the supported starting point.

Try the converter with your own supported statement ↗
Supported files and output

Accepted files: PDF, PNG and JPG. Maximum file size: 10 MB. PDF page limit: 5 pages. Output fields: Date, Description, Debit, Credit and Balance. Exports: Excel/XLSX and CSV. Statement processing: browser-side, for supported clear English transaction tables.

Start with the transaction table, not the account summary

Find the dated list of money entering and leaving the account. An opening balance, a monthly total and an account summary are not interchangeable with individual transaction rows. The goal is a structured list you can trace back to the source, rather than a copy of every label printed on the PDF.

Check all relevant pages before selecting the file. Look for a continued table, repeated column headers and a separate section that repeats the same transactions. Decide which pages contain the rows you need. If you deliberately export only a page range, keep that range with the output and describe it as a partial extraction.

A digital PDF can contain selectable text; a scan contains a page image that needs recognition. Both can enter the existing workflow when their table layout is supported. For a scan, confirm that dates, decimal points and the rightmost balance column are legible. The OCR overview explains how recognition differs from reading digital text.

Extract and inspect the five fields

  1. Open the converter. Sign in to a verified account, or create and verify one. The current trial allows one successful conversion without a card.
  2. Select the PDF. Keep it within the 10 MB and five-page limits. Unlock a password-protected document on your device before using it.
  3. Check the page selection. All pages are selected by default. Use a specific range only when you intend a partial export.
  4. Run conversion. Supported digital tables use text extraction; supported scanned tables use browser-side OCR. Keep the tab open while processing.
  5. Read the preview. Check Date, Description, Debit, Credit and Balance before choosing the final file format.

Each output row should represent one transaction. A description that wraps onto another line in the PDF must still belong to the correct date and amounts. An unused debit or credit cell is blank; do not treat a blank field as evidence that an unreadable amount was zero. The bank statement extractor page describes the supported fields and general extraction limits.

Verify completeness as well as individual numbers

Compare the first and last transaction on each selected page, then work through the intervening rows. Count the transactions and look at page breaks for missing or duplicated entries. Check the full date, the description, the decimal position and the debit-versus-credit direction. A successful download does not prove that the table is complete.

Where the statement supplies running balances, compare the sequence with the source. Investigate warnings by finding the original row; do not alter an amount just to make arithmetic pass. A matching final balance is one useful check, but opposite errors could cancel each other. Review every row you intend to use.

Use the fictional three-transaction example to understand what a known output looks like. Its ending balance is 2,295.50. This demonstrates that sample, not coverage of other banks or layouts.

Choose Excel or CSV after reviewing the rows

Excel provides a Transactions worksheet with five columns and formatted numeric amounts. Follow the general PDF-to-Excel guide for workbook review. If you need plain tabular text, use the CSV converter workflow and check your destination application's field and date requirements before import.

After extraction, labels require a separate workflow. See how to categorize bank statement transactions with rules, AI suggestions and review. BankStatementMate exports five fields; it does not generate transaction categories.

When the PDF cannot be extracted reliably

Blurred scans, cropped columns, handwriting and unsupported layouts can prevent a usable result. OCR can confuse characters and decimals even when a preview appears orderly. A single signed Amount column is not the same structure as separate Debit and Credit columns. Unsupported or ambiguous input can fail instead of silently supplying invented rows.

Obtain a clearer original when text is unreadable. If the structure remains unsupported, use another method or manual entry and verify the result. Changing the output format cannot repair a recognition error. For scan preparation and workbook-specific checks, see scanned bank statement to Excel.

Select a PDF and review its transactions ↗