Reviewable CSV export
This bank statement to CSV converter turns supported native-text PDF transaction tables into structured rows with signed amounts, balance checks, confidence evidence, and source-page references.
| Date | Description | Debit | Credit | Amount | Source |
|---|---|---|---|---|---|
| 2026-06-01 | ACME PAYROLL | — | 3,200.00 | 3,200.00 | p. 1 |
| 2026-06-03 | UTILITY PAYMENT | 86.42 | — | -86.42 | p. 1 |
| 2026-06-07 | OFFICE SUPPLY | 142.18 | — | -142.18 | p. 2 |
Sample output shown. Your CSV reflects the fields available in the PDF you upload.
Stable field contract
The export carries both separate debit and credit columns and a signed amount. That makes the same file useful for review, spreadsheet analysis, and deliberate mapping into downstream accounting workflows.
The transaction date normalized as YYYY-MM-DD.
The posting date when the source statement reports one.
The reconstructed transaction description, protected from spreadsheet formulas.
A transaction reference when it is present in the PDF.
Separate non-negative debit and credit magnitudes.
Debits are negative and credits are positive for consistent downstream calculations.
The reported running balance when the statement includes it.
The normalized three-letter currency code.
Row-level extraction confidence for review prioritization.
The PDF page where the transaction was found.
Reject encrypted, scanned, malformed, or unsupported input before creating an export.
Identify columns, join wrapped descriptions, and retain transaction direction and page provenance.
Compare signed transaction movement with opening, running, and closing balances.
Write UTF-8 CSV with stable columns and neutralize formula-like user-controlled text.
The CSV uses a versioned, bank-neutral field order and an explicit signed-amount convention: debit is negative; credit is positive.
It is designed for review and controlled downstream mapping. It does not claim one-click compatibility with QuickBooks, Xero, or a bank-specific importer until those import paths pass their own evidence gates.
Use an original native-text PDF with recognizable statement metadata and transaction tables. The current parser is evaluated against bank-neutral U.S.-style layouts.
Scanned, encrypted, malformed, ambiguous, and unsupported documents fail clearly. No CSV is created from transactions that cannot be verified safely.
The current converter accepts supported native-text, U.S.-style bank statement PDFs. Scanned images, encrypted files, and layouts that cannot be verified safely are rejected without inventing transactions.
The CSV provides a stable accounting-feed field set, including signed amount, debit, credit, balance, currency, confidence, and source page. It is not presented as a QuickBooks- or Xero-specific import template; check and map the columns required by your accounting system before import.
Text extracted from the PDF is neutralized when it begins with spreadsheet formula prefixes, including equals, plus, minus, and at signs. Numeric amounts and ISO dates are emitted as controlled values.
Balance reconciliation runs before export, and the job is marked for review when the statement does not reconcile. The CSV keeps signed amounts, running balances, confidence, and source pages so you can compare rows with the PDF.