Convert bank statements to CSV that import cleanly.
Standardised samples, locale-specific formats, and an on-page validator so you never guess which CSV layout your software expects.
99.6%
Verified against 1,000+ bank layouts.
Instants
End-to-end from PDF upload to CSV export.
10+ hrs/week hrs
Reported by accounting teams that automated imports.
One spec, two clicks to test
The Zera Books CSV spec removes guesswork. Download a synthetic sample, upload it to your accounting tool, and validate the file on this page before you post any real transactions.
What you can do in under five minutes:
- Benchmark the exact column order we export internationally.
- Share safe, non-PII samples with auditors and team members.
- Validate custom CSVs using the same rules as our import API.
Download sample CSVs
Every file is synthetic, versioned on GitHub, and mirrored on our CDN for fast downloads. Primary CTA keeps you in the app; GitHub is available for release notes and checksums.
Need a different bank or ERP? Tell support and we will add it to the public sample set.
Per-software mini guidance
Pick your platform, confirm which sample to download, follow the import path, and open the full guide if you need deeper walkthroughs.
Validate your CSV before import
Paste or load one of the quick examples to confirm the columns, delimiter, and transaction count—all in your browser.
CSV Validator
This validator requires JavaScript. For the best experience, use our web application which includes full validation functionality.
Validation requires:
- Date column (required)
- Either Amount column OR both Credit and Debit columns
- Description column (recommended)
- At least one transaction row
Top errors & quick fixes
Fast answers for the issues accountants surface most. Each fix links to a working sample and a deeper guide where it helps.
Why accounting teams trust this spec
"The US sample imported into QuickBooks with zero edits. Having the EU variant saved our UK rollouts."
"Validator caught a missing Description column before we uploaded. Saved a messy re-import."
"Clients love that the GitHub release is citeable—auditors have everything they need."
Need help fast?
Our support team responds in under one business hour during US & EU working days.
Contact supportPrefer email? daminmutti@zerabooks.com
Frequently Asked Questions
Straight answers for your import workflow—ready for humans, support teams, and search assistants alike.
Technical appendix
Collapsed by default—open if you need encoding or delimiter specifics.
Technical appendix
Collapsed by default—open if you need encoding or delimiter specifics.
File expectations
- UTF-8 encoding without BOM
- Comma, semicolon, pipe, or tab delimiters supported
- Date formats: MM/DD/YYYY, DD/MM/YYYY, or ISO 8601
- Decimal separator: dot or comma
- Line endings: CRLF or LF
Fields in human language
- Date – the transaction post date
- Description – memo/merchant text from your bank
- Amount – signed number (negative for money out)
- Credit / Debit – optional split columns for legacy ERPs
- Currency – optional ISO code when multi-currency is enabled
Related Resources
Compare converter tools
Bank StatementsConvert bank statements
PricingSee plans and pricing
AI CategorizationAuto-categorize transactions
CPA SolutionsTools for accounting professionals
QuickBooks ImportImport statements to QuickBooks
Xero ImportImport statements to Xero
Client ManagementOrganize client conversions