Date
Recognized transaction date, written as YYYY-MM-DD when present.
Use this bank statement to CSV converter for one digital or scanned PDF at a time. Review the file rules below, then download the validated result without leaving this page.
Or drop it here.
Sign in to upload · Get 20 free credits
Sign in before a file is selected or uploaded.
One physical PDF page equals one credit. Failed conversions cost 0.
This fictional file was generated with the current CSV exporter. It demonstrates the bank-account header contract and file behavior; it is not a customer statement or a promise that every source contains every value. Use this bank statement to CSV example to inspect the exact column order before you work with your own file.
fictional-bank-statement.csv
Fictional example, not a customer statement
The invisible UTF-8 byte-order mark at the beginning of the download is not printed in this preview.
Date,Value Date,Description,Debit,Credit,Balance,Cheque No,Status,Check reason
2026-07-01,2026-07-02,Monthly service,12.00,,1238.50,,Ready,
2026-07-03,2026-07-03,Transfer received,,250.00,1488.50,,Ready,Fictional sample data for file-format demonstration only.
Inspect the actual UTF-8 BOM, English headers, ISO dates, empty missing values, decimal text, comma delimiters, and CRLF line endings before converting your own statement.
Download fictional CSV sampleA successful bank-account export uses nine columns in this exact order. Optional source values stay empty rather than being replaced with invented text.
Recognized transaction date, written as YYYY-MM-DD when present.
Value or effective date, written as YYYY-MM-DD when present.
Transaction text preserved for review.
Money-out decimal value when present.
Money-in decimal value when present.
Running balance when available and validated.
Cheque or source reference value when present.
Row review status from the current export contract.
Row-level extraction issue when a value still needs attention.
A credit card export uses a different 14-column contract: Date, Transaction Date, Posting Date, Description, Debit, Credit, Balance, Transaction Type, Original Amount, Original Currency, Card Suffix, Reference, Status, and Check reason. Fields not present in the source remain empty.
These rules describe the current exporter. They do not promise that every importing application will interpret the file in the same way.
The download begins with UTF-8 BOM bytes so compatible software can detect UTF-8 text more reliably.
Available dates are written as YYYY-MM-DD, not localized display text.
Missing values become empty fields, not 0, null, or guessed text.
Amounts use decimal text such as 12.00 without currency symbols or thousands separators.
Fields are comma-separated and rows use CRLF line endings.
Commas, double quotes, or line breaks inside a value trigger CSV quoting; embedded quotes are doubled.
CSV
CSV is a portable row-and-column format, but each destination can have its own mapping rules. A bank statement to CSV workflow should include a raw-text check, a table check, and a comparison with the original PDF. Confirm the header set, transaction count, dates, money direction, and review status before adding the file to another system. If a destination asks you to map fields, use its current instructions instead of assuming that similar labels mean the same thing.
Use the statement as the source when checking dates, descriptions, amounts, and balances.
If an application asks, select UTF-8 and comma-separated values.
Make sure the bank-account or credit-card column set matches the statement type.
Confirm ISO dates, Debit for money out, Credit for money in, and any available Balance.
Compare the transaction count and review Status or Check reason before importing.
Choose the receiving columns required by your workflow; no automatic compatibility is promised.
Upload, processing, result review, and download stay in the tool at the top of this page.
Select one eligible digital or scanned statement PDF after signing in.
The service reads the statement and organizes recognized transactions.
No finished download is produced until the transaction and financial checks succeed.
Open the successful result and choose CSV without leaving this page.
All three downloads come from the same successful conversion. Choose by what you need after download.
CSV
Choose CSV for a simple text table when you plan to inspect or map columns yourself.
Excel XLSX
Choose XLSX for a formatted Transactions worksheet, frozen headers, filters, and cell formatting.
JSON
Choose JSON when a compatible technical workflow needs machine-readable transaction objects.
CSV does not carry Excel workbook formatting, formulas, filters, or destination-specific account mappings.
A CSV download is created only after the statement can be interpreted and the required checks succeed.
A damaged file, unsupported document, or unreadable page can stop before conversion.
Unresolved extraction or financial validation prevents a finished download.
One physical PDF page equals one credit. Open Pricing when the account does not have enough credits.
Expired and cancelled conversions do not create new downloads. Start again with an eligible PDF.
Failed conversions cost 0 credits, and reserved credits are released when validated exports are not produced.
These answers describe the current CSV contract and the limits you should check before importing the file elsewhere.
A bank-account CSV uses Date, Value Date, Description, Debit, Credit, Balance, Cheque No, Status, and Check reason. Credit card exports use the separate 14-column contract shown on this page.
Yes. The current exporter writes UTF-8 with a byte-order mark at the start of the file.
Available dates use YYYY-MM-DD. Missing source values remain empty fields rather than becoming zero, null, or guessed text.
The current exporter applies standard CSV quoting when required and doubles embedded double quotes.
This page does not promise direct compatibility with QuickBooks, Xero, or another destination. Review the required fields and map the exported columns yourself.
Yes. After sign-in, this page uses the same real upload, validation, credit, processing, result, and download flow as the main converter.
Yes. A successful conversion provides XLSX, CSV, and JSON downloads from the same validated transaction result.
No finished download is created when the required checks cannot produce a safe result. Failed conversions cost 0 credits, and reserved credits are released.
Compare the spreadsheet workflow, all output formats, current credits, and file-handling policy.
EXCEL WORKFLOW
Review XLSX fields, workbook formatting, filters, and reconciliation steps.
See XLSX workflowCONVERTER
View the general converter and all available output formats.
View all output formatsCREDITS
Compare the current monthly, yearly, and one-time credit options.
View pricingFILE HANDLING
Read the current policy for source files, results, retention, and deletion requests.
Read privacy detailsUse the same tool at the top of this page to upload one PDF and download the validated CSV.