A clean, reviewed, audit-logged CSV
ProofRows exports three CSV profiles — generic, QuickBooks-ready, and Xero-ready — plus XLSX. Every export is logged with format, options, row count, and the SHA-256 of the output file. The CSV is yours, regardless of which tool you import it into.
What you can export today
Date, Description, Vendor, Category, Amount, Balance. Optional Status and Confidence columns. Best for Excel, Numbers, or any tool that isn't QuickBooks or Xero.
Strips to Date, Description, Amount (signed) or Date, Description, Credit, Debit. Uploads through QBO's Banking → Upload from file wizard without remapping.
Date, Amount, Payee, Description, Reference. Matches the column order Xero's bank-import wizard expects.
A real Excel workbook with one row per transaction, proper Excel number formatting, and a header row. Opens in Microsoft Excel, Google Sheets, and Apple Numbers.
QuickBooks Web Connect format for QuickBooks Desktop users. Drop the .qbo file into the bank feeds center; QuickBooks imports the transactions directly.
Direct QuickBooks Online push and direct Xero push are on the roadmap. Today, the export file is the wire.
The export modal, end to end
- 01Pick the format
Generic, QuickBooks, Xero, XLSX, or OFX. Each one shows a short description of where it drops.
- 02Pick the column layout
Signed Amount (one column) or two columns (Credit / Debit). Only relevant for the QuickBooks and generic profiles; Xero always wants signed Amount.
- 03Pick the date format
MM/DD/YYYY, YYYY-MM-DD, or DD/MM/YYYY. YYYY-MM-DD is unambiguous and recommended for new accounts.
- 04Decide what to include
Include flagged rows (default yes) or only confirmed rows. Include confidence notes (off for QuickBooks / Xero; on for generic).
- 05Download
The file streams to your browser. A row in export_logs is created with format, options, row count, and the SHA-256 of the file.
- 06Import to your accounting tool
Use the tool's native import wizard. The CSV is yours, the audit row is yours.
Safety properties of the export
- CSV injection prevention. Cells beginning with
=,+,-, or@are prefixed with a tab so spreadsheet apps do not interpret them as formulas. - RFC-4180 escaping. Fields containing a comma, double-quote, or newline are wrapped in double-quotes; internal double-quotes are escaped by doubling.
- Decimal precision. Two places of precision. Empty cells mean “no value”, not zero.
- LF line endings. Excel handles LF correctly. The file opens cleanly on every platform.
Full field-by-field reference: /guides/csv-format.
Export your first cleaned statement
A CSV you can defend in an audit.
150 free pages. No credit card. The export is logged, the math is reconciled, the row count is preserved.
Frequently asked questions
- Can ProofRows convert bank statement PDFs to CSV?
- Yes. ProofRows extracts transactions from bank-statement PDFs — text-based or scanned — and lets bookkeepers review, edit, validate, and export the results as CSV. The QuickBooks-ready and Xero-ready CSV profiles import cleanly into those tools through their native bank-import wizards.
- Does ProofRows work with scanned bank statements?
- Yes. Scanned and image-only statements are read with built-in OCR, then parsed into transactions the same way as text PDFs. Low-confidence rows from rough scans are flagged for review, and every statement still has to pass the balance check before export.
- Can I import ProofRows exports into QuickBooks?
- ProofRows exports QuickBooks-ready CSV (for the Banking → Upload from file wizard) and .qbo Web Connect files that QuickBooks Online and Desktop import natively. A direct QuickBooks Online API push is on the roadmap and should not be described as live yet. ProofRows is not affiliated with or endorsed by Intuit.
- Can I import ProofRows exports into Xero?
- ProofRows exports a Xero-ready CSV that supports Xero's bank-import workflow (Accounting → Bank accounts → Import a statement). A direct Xero API push is on the roadmap. ProofRows is not affiliated with or endorsed by Xero.
- Does ProofRows export to Excel (XLSX)?
- Yes — XLSX export is supported today. CSV files produced by ProofRows also open cleanly in Microsoft Excel, Apple Numbers, and Google Sheets.
- Is ProofRows a replacement for bookkeeping software?
- No. ProofRows is a statement-cleanup workspace. It prepares transaction data for import or reconciliation in accounting tools like QuickBooks Online or Xero. It is not a ledger of record.
- Who is ProofRows built for?
- ProofRows is built for solo bookkeepers, small bookkeeping firms, accountants, tax preparers, QuickBooks ProAdvisors, cleanup bookkeeping specialists, and fractional CFOs who receive bank statements as PDFs.
- How long do you keep my client's bank statements?
- Source PDFs are auto-deleted after the per-client retention window (default 30 days, configurable). The extracted transactions and export-log audit trail stay for the life of the account. Account deletion cascades and removes every row, file, and auth artifact in a single transaction.
- Do you train AI models on my client's bank statements?
- No. We do not train models on customer data. The extraction provider we use is contracted not to train on API requests, and our application does not write statement text back to the database from the model — the only path through is a strict schema validation.
- How accurate is the extraction?
- Confidence scores are surfaced per row so the bookkeeper can see which transactions the model is less sure about. The validation page enforces a beginning + Σ credits − Σ debits = ending balance check before any export. We do not claim 'perfect AI extraction' — every export is human-reviewed.
More questions? Contact support or read the full FAQ.