Bank statement to Wave.
Reconciled before you import.
Convert a PDF bank statement into a .qbo file that Wave's Upload transactions screen accepts directly, with transaction IDs so a second upload of the same month does not double up, and a balance check against the printed statement before anything is uploaded.
Drop your bank statements here
One file or a whole year. PDF, scanned image, CSV, QIF or OFX. Up to 12 files at a time; long PDFs are split for you.
Not ready to upload your own? See a sample result
5 pages free, no account. The QuickBooks download appears on the results page.
Step by step: PDF statement to Wave
- Drop the statement on the home page and confirm the balance check is green.
- Click QuickBooks (.qbo). Wave reads OFX, QBO, QFX and ASO files, and the .qbo is the one with a stable ID on every transaction.
- In Wave: Accounting, then Transactions. At the top right click More, then Upload transactions.
- Choose the .qbo file and the Wave account it belongs to, then upload. The transactions appear in the Transactions list for review and categorising.
- Compare Wave's account balance after the upload with the printed closing balance on the statement.
What usually goes wrong, and how this avoids it
- Wave recommends OFX-family files over CSV because its CSV upload is limited to a few columns and fails on anything extra. The .qbo avoids the CSV path entirely.
- Wave has been reported to fail on OFX files that use a comma as the decimal separator, which some European banks produce. The .qbo written here always uses a decimal point.
- Uploading the same statement twice as CSV duplicates every row. The .qbo carries a FITID per transaction, which is what lets Wave recognise a repeat.
Wave questions
Does Wave accept .qbo files, or only .ofx?
Wave's help lists OFX, QBO, QFX and ASO as the preferred upload formats, with CSV as the fallback. A .qbo is an OFX 1.02 file with a QuickBooks tag inside it, and Wave reads it like any other OFX file.
What if Wave says it cannot read the file?
That message usually means an encoding or decimal-separator problem in a bank-issued file. Files written here are plain ASCII with a decimal point, so it is rare. If it happens, run the file through the free QBO checker at /tools/qbo-checker to see what is inside, then email support with the conversion ID.
Can I use the CSV instead?
You can, using Wave's CSV upload, but Wave asks for only a date, an amount and a description and rejects extra columns, so you would need to delete the Balance and Category columns first. The .qbo needs no editing.