Benchmarks & Validation

What Exact Statement validates today and how to verify exports before import.

Mar 15, 2026

Exact Statement does not publish a single public “accuracy percentage” yet. Instead, the product exposes validation signals you can use before import.

Validation Signals Available Today

Check	Where you see it	What it helps catch
Preview table	Dashboard preview	obvious column-shift or parsing issues
Balance warnings	File status and warning summary	rows where the running balance chain may not match
Multiple export formats from one normalized dataset	Preview/export switcher	format-specific issues before download
Failed-job refunds	Dashboard and billing records	processing failures that should not consume credits

Recommended Review Workflow

Confirm the statement period and account.
Check whether any rows are flagged with balance warnings.
Preview the same file in the export format you actually plan to download.
For QBO, verify the date format and debit/credit direction.
For Xero, verify the amount sign and Transaction Type column.
Use the destination app's own import preview before final import.

Statement PDFs are not one consistent machine format. Different banks, years, products, and scan qualities can all change the layout. The safest workflow is not “blind export”, but “export plus review”.

Output Checks By Format

QBO 3-column

one Amount column
positive amount = money in
negative amount = money out

QBO 4-column

Credit and Debit are split into separate columns
only one of the two should be filled per row
values are exported as positive numbers in their destination column

Xero CSV

signed Amount
Transaction Type derived from the amount sign
one consistent date format throughout the file

XLSX

keeps the selected date format
includes balance, currency, and account identifier fields for review

Contact

If a file looks wrong, send the upload ID and row range to support@exactstatement.com.