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 | Signed 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.
The historical-data gap
Banks may keep downloadable PDF statements for longer than they keep transaction activity available as CSV or another data file. The exact window varies by bank, account type, and access channel, so 12 or 24 months is not a universal rule.
When a direct transaction export no longer covers the period you need, use the original statement PDF rather than rebuilding years of activity from screenshots or manually retyping every row.
One U.S. retail bank documents up to 18 months of downloadable CSV, QFX, or QBO transaction history and directs customers to statements for older transactions.
Read the official transaction-download policyAnother U.S. retail bank says downloads default to 90 days and can reach 18 months for some accounts, while online statement copies for most checking accounts can remain available for up to seven years.
Read the official account-activity policyThese dated policy examples explain why the access gap exists. They are not a claim that this converter has been validated for either bank. Availability can change, so check the provider's current policy before relying on a historical window.
Choose by next action
The extraction can start from the same supported PDF, but the output formats solve different jobs. Choose the file your next step actually needs.
CSV is a flat UTF-8 table. It is a practical choice when you need stable columns, a signed amount, or a smaller file to reshape for a database, script, or accounting-system import.
It does not preserve workbook formatting, multiple worksheets, review formulas, or visual summaries.
XLSX is the better fit when a person needs formatted Transactions, Summary, and Review worksheets with visible balance and provenance evidence.
See how the bank statement to Excel converter organizes the review workbook.
Microsoft documents that CSV keeps cell text and values but drops workbook formatting and other worksheet features. Review Microsoft's format guidance.
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.
A deterministic row identifier for review and downstream matching.
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.
A non-negative debit magnitude; blank when the row is not a debit.
A non-negative credit magnitude; blank when the row is not a credit.
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.
One calculation-ready value keeps direction explicit: debits are negative and credits are positive. Separate Debit and Credit columns remain available when a downstream workflow expects them.
This is the running balance printed for the transaction when the source statement provides one. The converter leaves it blank rather than inventing a balance that is absent from the PDF.
A row-level value from 0 to 1 helps prioritize manual review. It is evidence about extraction certainty, not a promise that the entire statement is correct.
The one-based PDF page number gives each row a direct route back to the original statement, so descriptions, amounts, and balances can be checked against their source.
All 12 production columns are shown. Blank Posting Date, Reference, and Credit cells mean those values were not present or do not apply to this example debit.
| Transaction ID | Transaction Date | Posting Date | Description | Reference | Debit | Credit | Signed Amount | Balance | Currency | Confidence | Source Page |
|---|---|---|---|---|---|---|---|---|---|---|---|
| tx-demo-0001 | 2026-06-03 | blank | UTILITY PAYMENT | blank | 86.42 | blank | -86.42 | 6053.80 | USD | 0.99 | 1 |
Illustrative, bank-neutral data. Your CSV reflects only fields available in the PDF you upload.
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.
Map deliberately
A reviewable accounting feed is not the same thing as a certified one-click import template. Keep the evidence columns while checking the file, then map only the columns required by the target system.
| Target workflow | Statement2Excel columns | Mapping note |
|---|---|---|
| QuickBooks three-column CSV | Transaction Date, Description, Signed Amount | Map to Date, Description, and Amount. |
| QuickBooks four-column CSV | Transaction Date, Description, Credit, Debit | Keep Credit and Debit separate; leave the non-applicable value blank. |
| Xero bank-statement CSV | Transaction Date and Signed Amount, plus supported descriptive fields | Assign columns in Xero's import flow and follow its current account-specific instructions. |
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.
Treat document text as untrusted input
CSV is plain text, but spreadsheet applications can interpret cells beginning with formula characters as executable formulas. Descriptions and references extracted from an uploaded document therefore need to be handled as untrusted text.
Statement2Excel neutralizes extracted Transaction ID, Description, and Reference values when they begin with a tab or line break, or when their first non-space character is an equals, plus, minus, or at sign. Dates and numeric fields are emitted from controlled values rather than carried through as untrusted document text.
Spreadsheet applications and downstream importers do not all interpret CSV in the same way. Keep software updated, review the file before opening or importing it, and do not treat CSV neutralization as protection against every possible spreadsheet behavior.
Read the OWASP CSV Injection guidanceThe 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.
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.
Yes. You do not need Microsoft Excel installed to create or download the UTF-8 CSV. You can review the file with a compatible spreadsheet, text editor, or data tool.
Check the bank's online statement archive or request older statement PDFs from the bank. When an older statement is available as a supported native-text PDF, you can convert that statement to CSV. Transaction-download and statement-retention windows vary by bank, account type, and access channel.
Encrypted PDFs are rejected. If you are authorized to access the statement, use the bank's download options or a trusted PDF application to create an unlocked copy before uploading it. Do not send us the document password. If you cannot create an unlocked copy, request one from the bank.
The current parser requires embedded text and rejects image-only statements because it cannot verify their transaction rows safely. Request the original native-text PDF or a transaction export from the bank. Treat any separate OCR result as unverified until every row has been compared with the source image.