Synthetic data, not a customer statement
Every name, date, description, and amount in this resource is fictional. The sample exists to show output structure without exposing a filename, account number, balance, payee, or transaction from a real user.
Use it to evaluate whether the available fields fit your spreadsheet, bookkeeping, reconciliation, or import-control workflow before converting a statement.
Excel and CSV review fields
A reviewable table keeps the original transaction order and separates source-facing evidence from downstream categories. Date, description, debit, credit, signed amount, balance, currency, and a review status cover the most common controls.
- Excel is useful for filters, annotations, formulas, and human review.
- CSV is useful for repeatable system mapping and portable data exchange.
- The original PDF remains the control record for every converted row.
QBO and OFX structure for accounting imports
The downloadable QBO and OFX files use the same four fictional rows as the CSV. They add a statement date range, currency, account-type fields, signed transaction amounts, unique transaction IDs, and a closing ledger balance.
These files are for structure review and controlled import testing. They do not identify a real bank or account. Before generating or importing production output, confirm the destination account, currency, date range, debit and credit direction, opening and closing balances, and duplicate risk.
QuickBooks product and regional support changes over time. Use the current Intuit instructions linked from the QuickBooks converter page before a production import.
- CSV keeps rows portable for spreadsheet review and custom field mapping.
- QBO is an OFX-based Web Connect file used by supported QuickBooks Desktop workflows.
- OFX support depends on the destination product and its current import rules.
Checklist
- Statement period matches the source PDF
- Transaction rows remain in source order
- Date format is consistent
- Debit and credit direction is confirmed
- Running balance movement is plausible
- Repeated headers and summary totals are excluded
- Wrapped descriptions remain attached to their transaction
- Destination account and duplicate risk are checked before import
Download the synthetic sample
Use this fictional data to review columns and mapping. It is not a customer statement and should not be treated as an accounting record.
Reference table
| Date | Description | Debit | Credit | Balance | Review status |
|---|---|---|---|---|---|
| 2026-01-03 | Example supplier payment | 125.40 | 4,874.60 | Source row checked | |
| 2026-01-05 | Example incoming transfer | 850.00 | 5,724.60 | Credit direction checked | |
| 2026-01-08 | Example account fee | 12.00 | 5,712.60 | Fee retained | |
| 2026-01-11 | Example card settlement | 340.25 | 5,372.35 | Description kept on one row |
FAQ
Does this sample contain real bank statement data?
No. The sample is entirely synthetic and contains no customer, account, filename, payee, balance, or transaction from BankScanPro users.
Will every bank statement produce these exact columns?
No. Available fields depend on the source layout. Some statements use one signed amount column, while others separate debits and credits or omit a running balance on individual rows.
Can I import the sample CSV into QuickBooks?
Use it for format review only. Confirm current QuickBooks product and regional requirements, then map a verified statement output to the destination account in a controlled workflow.
Are the QBO and OFX downloads connected to a real bank?
No. Both files use fictional identifiers and transactions. They show representative output structure for review and controlled testing, not a live bank connection or a production accounting record.