Skip to main content

Sample output

Sample Bank Statement Conversion Output

Inspect a privacy-safe synthetic transaction table, download the CSV, and see how the same reviewed rows prepare for Excel or QuickBooks workflows.

Updated 2026-07-15

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.

Preparing the same rows for QuickBooks

QBO and OFX add structured financial and account fields around the reviewed transaction rows. Before generating or importing the file, confirm the destination account, currency, date range, debit and credit direction, 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.

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

DateDescriptionDebitCreditBalanceReview status
2026-01-03Example supplier payment125.404,874.60Source row checked
2026-01-05Example incoming transfer850.005,724.60Credit direction checked
2026-01-08Example account fee12.005,712.60Fee retained
2026-01-11Example card settlement340.255,372.35Description 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.