Convert a bank statement to QuickBooks (.QBO)

QuickBooks imports bank transactions from a .QBO file, the Web Connect format. ZeroParse turns a PDF statement into one, with every amount signed the way QuickBooks expects.

No AI. No Hallucinations. Just Deterministic Math.

How it works

  1. Upload the statement

    Bank account or credit card, text-based or scanned.

  2. Check it against the statement

    We add up the rows we found and compare them with the opening and closing balance, the column totals, or the running balance your statement prints. You see whether they match before you export, and which figure disagrees if they don't.

  3. Export for QuickBooks

    Choose .QBO and import it in QuickBooks, picking the account the transactions belong to. .QBO export is part of the Pro and Firm subscriptions; CSV export is available on every plan.

The transaction table: a payroll credit of 4820.00 categorized as Income, a rent direct debit of -1850.00 as Rent, a coffee card payment of -6.40 as Meals & Entertainment.
The editable table you export from: amounts signed, categories applied, every cell correctable.

What to know

Signs ready for import

Money spent exports as negative and money received as positive, for bank accounts and credit cards alike. Card statements that print purchases as positive are detected and flipped for you.

No account numbers inside

We never keep account or routing numbers, so the file carries placeholders. QuickBooks asks which of your accounts to import into anyway.

Several cards in one PDF

Consolidated statements are extracted in full. Where the statement's arithmetic proves which account each row belongs to, an Account column says so.

Common questions

Can I export to QuickBooks?
Clean CSV export is available on every plan, including Free. .QBO export (QuickBooks' Web Connect format) is included on the Pro and Firm plans. QuickBooks Online takes up to 1,000 transactions and 350 KB per upload, so a larger export arrives as several .QBO files in one zip, in date order: upload each file in turn.
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.
My statement covers several cards or accounts in one PDF. What happens to them?
All of them are extracted — nothing is dropped, and the rows come out in the order the statement prints them. Where the statement gives each account its own opening and closing balance, we also work out which account every transaction belongs to and show it in an Account column you can sort, filter and export. We only fill that column when the statement's own arithmetic proves the split: each account's transactions have to add up to exactly the movement that account prints for itself. If two different splits would both add up — which happens when one card had no activity that period — we leave the column blank rather than guess, because a wrong account name is worse than none. The .QBO and Xero exports write one file per account (in one zip when there are several), because those formats describe a single account per file and putting three registers into one would be wrong on import. Import each file into its own account.
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.

All questions and answers

Try it on your own statement: 50 free PDF credits

No card required. CSV, Excel and OFX files are free on every plan.