BankXL / Practical guide

Convert PDF bank statement to CSV with dates and signs intact

Prepare a transaction-only CSV, preserve a reference copy and check the destination schema before an import.

Obtain structured transactions if possible

To convert a PDF bank statement to CSV, first check your bank's downloads for a CSV covering the same account and period. Using that file is simpler than extracting the PDF and can avoid a paid conversion. Save both originals. If PDF is the only source, Tabula can extract selectable-text transaction regions into CSV locally for free. Where available, Excel's PDF connector can also produce a table that you save as CSV. A scanned statement needs OCR or careful manual transcription before CSV formatting is useful.

Decide what each row means

Create one logical transaction per record. Useful working columns are printed date, description, signed amount, printed running balance and a source-page reference. Exclude statement opening balances, page carry-forwards, minimum-payment notices and repeated headers from transaction activity. Combine a wrapped description with its transaction only after comparing it with the PDF. Keep intermediate extraction columns until you finish checking; deleting them too early makes a misplaced amount harder to trace. A CSV file has no separate worksheets, so keep your review notes in a workbook alongside it.

Resolve signs and dates before export

For a cash account, normalize deposits as positive and withdrawals as negative. If the source has separate Debit and Credit columns, confirm which is money out and calculate credit minus debit. Check a known fee, deposit and reversal. Credit-card statements may show positive debt instead; confirm the destination's convention rather than copying bank-account assumptions. Dates should include the correct year and use the format required by the recipient. Retain the printed date in your working file so a day/month decision remains reviewable later.

Treat CSV as a data format

Use your spreadsheet's CSV export instead of joining cells with commas by hand. A description containing a comma, quotation mark or line break needs correct quoting. Choose the delimiter and encoding the destination expects, then inspect the saved file through an import preview. Excel can reinterpret reference numbers and dates when a CSV is opened directly; use its text-import controls instead. Formula-like descriptions also need care in spreadsheet workflows. Retain an unchanged source copy rather than editing the only version to satisfy a particular importer.

Verify before loading another system

Compare row counts and signed totals with the complete statement. Check the first and last records from every page and review all omitted lines. Opening balance plus full-period activity should equal closing balance, but offsetting errors can still pass that check. Map only the columns your destination requests and test a small period before a larger import. QuickBooks Desktop's Web Connect file import accepts only .qbo files; CSV, QFX, OFX and QIF are not accepted through that file-import route. A CSV download therefore still needs a separate compatible workflow when Desktop bank feeds are the destination.

Write a small destination contract

Before producing the delivery file, write down its exact headers, date pattern, delimiter, encoding and amount convention. For example, a recipient may require Date, Description and Amount, with a four-digit year and signed dot-decimal values. That is an example specification, not a universal CSV standard. Keep printed balance and page references in the review workbook even if the recipient cannot accept them. Export a delivery copy from the checked data, then read it back through a CSV-aware importer. Compare the resulting fields with the contract rather than judging the file by its extension or how it looks in a text editor.

Check a description containing punctuation

Use a synthetic description such as Stationery, "office" supplies to test the export. In comma-separated CSV it needs an enclosing pair of straight quotes, with each internal quote doubled: "Stationery, ""office"" supplies". Let the exporter write that syntax; do not remove meaningful punctuation to make a broken file appear valid. A quoted line break can make one transaction occupy several physical text lines, so counting newline characters is not a reliable transaction count. Compare parsed records instead. Keep a delivery log naming the account, covered period, checked row count and whether the file is complete or partial.

Where BankXL fits

BankXL exports statement transactions as CSV or XLSX after preview and correction; it does not generate a Web Connect file. One conversion accepts one PDF up to 15 MiB, 100 pages and 3,000 transactions, excluding encrypted files and decimal-comma amounts. The trial extracts the first two pages with data within the first six source pages, rather than a selected date range. For a longer statement, remaining successful pages require credits before the CSV can represent the whole document. Save the downloaded result locally within the 24-hour retention window.

Check two pages with data free See page packs

Written by Zijian Xiao. Examples are synthetic. Review all extracted results against your original PDF.