Statements into QuickBooks

What file formats does QuickBooks Online accept?

QuickBooks Online accepts a list of transactions as a .qbo, .ofx, .qfx, .csv or .txt file, and the United States version additionally accepts an account statement as a PDF or an image file.

The difference between those two things is the whole point of this page. A row list is a file of transactions that QuickBooks reads directly, one line each. An account statement is the document your bank printed, which QuickBooks has to extract the rows from before it can do anything with them, and that second path exists in one country's version of the product.

Source: Intuit's help article on uploading transactions manually, in each region's own version of it. The United States, United Kingdom and Australian versions were read on September 12, 2026, the Canadian and South African versions on September 10, 2026. Intuit revises these pages, so check the version for your country if something behaves differently.

How do I import a converted statement into QuickBooks Online?

Convert the PDF, download the QBO file, then upload it through the Link account dropdown on the Bank transactions screen and pick the account it belongs to.

1. Convert the PDF and read the balance check. Fix any flagged row against the PDF first, because fixing it after it has become a transaction means finding it again in the register. Convert a statement.
2. Open Bank transactions. Go to Transactions, then Bank transactions. Menu names move between QuickBooks layouts, so treat this as the generic route.
3. Choose Upload from file. Open the Link account dropdown and select it, then drag the .qbo or .csv file in.
4. Pick the account, and if it is missing, create it here with the right type. A bank statement belongs to a Bank type account and a card statement to a Credit Card type account.
5. For a CSV only, tell QuickBooks which column holds the date, the description and the amount, choose the date format that matches the file, and say whether the amount is one column with money out negative or two columns.
6. Confirm and import. The rows arrive under For review. Nothing has reached the books until you categorize or match them.

The error messages, and what each one usually means, are in importing a bank statement into QuickBooks Online.

What is actually inside the .qbo file?

A Web Connect file: OFX 1.0.2 written in Intuit's dialect of it, whose structure is checked against the format's own rules on every release rather than once by hand.

Nine conformance checks run before any build ships. Between them they verify:

• The header. The nine header lines Web Connect expects, in order, then a blank line, then the document. The header declares US-ASCII and readers take that at their word, so the check reads every byte in the file and confirms it.
• The structure. Every aggregate opened and closed in the right order, in all three variants we write: OFX, QBO and QFX.
• The sign-on block, which a reader reads before anything else: a status code of zero, a fourteen digit server timestamp, a language, and the financial institution block.
• The bank identifier. INTU.BID sits inside the sign-on block for the two Intuit dialects, and is absent from plain OFX, where it does not belong.
• The account. A currency, a bank account block, and an account type drawn from the documented set. A card statement instead uses the credit card message set, with the card account block and no bank id, which is the shape the format defines for it.
• The period. A transaction list with a start and an end date in the right order, and a ledger balance stamped to the end of the period.
• Every transaction: a type of debit or credit, a fourteen digit posting date, a signed amount with exactly two decimal places, a unique identifier of at least eight characters, and a payee within the 32 characters the format allows, with longer text moved to the memo field so nothing is dropped.
• The sign contract: money out negative, money in positive, checked on real rows rather than asserted.
• Stable identifiers. The same row exported twice produces the same identifier, so importing a corrected file adds what changed instead of a second copy of everything.

QBO, OFX, QFX and QIF: which is which covers where these formats came from and why there are four of them.

Which CSV shape does QuickBooks want?

Either three columns, date, description and amount, or four columns, date, description, credit and debit, in English and with one consistent date format throughout.

Intuit's United Kingdom article adds the housekeeping that trips most files: take the word "amount" out of the credit and debit headers, leave a cell blank rather than writing a zero in it, take stray numbers out of the description column, split the day of the week away from the date if your bank prints both in one cell, and prefer dd/mm/yyyy.

Every conversion here includes a CSV built for exactly this: three columns, date, description and one signed amount with money out negative, and no balance column to remove. The seven column CSV is the one to open when a person is going to read it, and this one when software is. How each format is written.

Why the statement rather than the bank feed?

Because the feed usually reaches back about ninety days, and the work that needs doing is often older than that.

A late start, a client who arrives in March with last year's books, a closed account, an account that was never connected: in all of those the PDF archive is what exists and the feed is not. Why the feed stops at ninety days goes through the cases. The same conversion also covers Xero and MYOB, and a scan or a phone photograph is read the same way as a clean download. Paper and photos.

Convert a statement