How to import bank transactions into QuickBooks without bank feeds
Bank feeds are the happy path in QuickBooks, right up until they are not. The connection drops and asks you to re-authenticate every few weeks. The feed only reaches back 90 days, and you need January. The account is a business card the aggregator never supported. Or you are catching up a client whose bank connection was never set up in the first place.
The fallback that always works is file upload — and it has one advantage over feeds worth knowing about: you can verify the file is complete before it touches your books.
What QuickBooks accepts
QuickBooks Online accepts three file formats for manual import: CSV, QBO (which is OFX under a different extension), and QFX. QBO is the one to prefer when you have it. A CSV is just columns; QuickBooks has to ask you which column is which, and it has no idea whether two identical coffee purchases are one transaction imported twice or two real purchases. A QBO file carries a FITID — a unique id per transaction — so QuickBooks can recognise a duplicate on its own.
The steps
- Download the statement from your bank as a PDF. Look for "Statements & Documents" in online banking. Do not screenshot it — a screenshot has no text layer.
- Convert the PDF into a transaction file. This is the step StatementSnap handles: drop the PDF in, check the table, export as QBO.
- In QuickBooks Online, go to Transactions → Banking → Upload from file.
- Pick your QBO file and choose the account it belongs to.
- Review the imported transactions in the For Review tab and accept them.
Check the arithmetic before you import
This is the part most workflows skip. Before you import anything, confirm the file is complete: the beginning balance plus every transaction should equal the ending balance printed on the statement. If it does not, a transaction was missed, and you will spend far longer hunting the discrepancy in QuickBooks than you would have spent catching it now.
StatementSnap does this check for you and shows the result as a badge before you export. A green badge means the arithmetic closes to the cent. It is computed in code rather than asserted by a model, so it is evidence, not a claim.
Credit cards behave differently
On a credit card statement, the bank reports what you owe as a positive number. Purchases increase it; payments decrease it. That is the opposite sign convention from a checking account, and mixing the two up is a classic source of a register that will not reconcile. Whatever tool you use, confirm that purchases land as negative and payments as positive before importing.
When CSV is fine
If you are importing into a spreadsheet rather than QuickBooks — building a cash-flow model, or handing a client a summary — CSV is the simpler choice. Just make sure the amounts arrive as real numbers rather than text, or every formula downstream will silently return zero.