- Can I export to Xero?
- Yes — "Export for Xero" in the Export menu produces an OFX file Xero imports directly with no column mapping, verified with a real import into a Xero organisation. It's included on the Pro and Firm plans, alongside .QBO.
- How does ZeroParse handle debit vs. credit on a credit card statement?
- We normalize every statement to the same convention QuickBooks and Xero expect: money you spent (a purchase) exports as negative, money you received back (a payment or refund) exports as positive — whether the file is a bank account or a credit card statement. Card issuers often print it the opposite way on the page itself (a purchase shown as a plain positive number, since it increases what you owe); we detect a credit card statement automatically and flip it, so what you export is ready to import rather than something you'd need to invert by hand.
- What does the badge on each file mean — "Matches statement totals", "Running balance agrees", "Doesn't match statement", or "Verify against the statement"?
- After extraction, we check whether the rows we found add up to what your statement says about itself — its opening and closing balance, its own column totals, or the running balance printed beside each row. "Matches statement totals" means they add up to the balances or totals it prints, to the cent.
"Running balance agrees" is for transaction histories — the exports internet banking gives you, rather than monthly statements — which print no totals at all, only a balance on every row. Every row agrees with that balance, so nothing between the first and last row is missing or misread. It's a separate badge because it checks less: the first row's amount, and anything outside the dates the export covers, can't be checked this way.
The running balance is also checked on statements that print totals, because it is checked at every row rather than once at the end, so it can tell you which row something goes wrong at — and it catches a case the totals cannot: a file that is missing transactions whose amounts happen to cancel out.
"Doesn't match statement" means they don't, and we show you exactly which figures disagree. It also appears when the PDF itself is incomplete: if its page numbers say "Page 3 of 8" and the file has seven pages, or one page appears twice, the rows can't be the whole statement even if they add up to what the remaining pages print. "Verify against the statement" means your statement didn't print anything we could check against — no balances, no totals, no running balance — so we're telling you to eyeball it yourself rather than pretending it's fine. "Enter balances" beside it lets you type the opening and closing balance you can see, and the badge then reads "Matches balances you entered" or "Doesn't match your balances": the same check, against your figures instead of the statement's. It's a common enough outcome that we publish the actual rate across our own test corpus on the benchmark page rather than asking you to take a number on trust.
None of this is the same as an accountant reconciling your account against an independent record; it only checks that what we extracted is internally consistent with what your own statement says.
Edit an amount or delete a row afterward and we re-run the same check automatically, so the badge always reflects what you're about to export — and because that recheck runs entirely in your browser, fixing a flagged row never sends anything back to our servers or creates a new copy of your data there. Where a file printed nothing the check can be re-run from, the badge says "Edited since checked" instead.
Hover over or tap any badge in your workspace to see all of them, with a line on what each means.