Why QuickBooks Rejects Your QBO File

QuickBooks refuses QBO files with errors that name no cause. The four real reasons, how to tell which one you have, and the duplicate-transaction failure that produces no error at all.

QuickBooks rejects Web Connect files with messages that describe the symptom and never the cause. We couldn't read the file, or an OFX error code, or nothing at all — the import appears to work and no transactions arrive.

There are four real causes. Three produce an error; the fourth is silent and is the one that costs you money.

1. The file has no bank id

A QBO must carry an `<INTU.BID>` tag identifying the issuing institution. A file without one is not a valid Web Connect file, and QuickBooks says so in words that do not mention the tag.

This is the usual result of renaming a .ofx to .qbo. The extension changes and the contents do not, so the tag QuickBooks is looking for was never there. It is also the usual result of a converter that produces plain OFX and labels it QBO.

2. The bank id was overwritten with a generic one

Subtler, and common with free converters. The file has an `<INTU.BID>`, but it is a placeholder rather than your bank's real identifier.

Sometimes this works. Sometimes QuickBooks associates the transactions with the wrong institution, or refuses the file, and you are left with an error that looks identical to having no tag at all.

If your source file already had a real bank id — as any file your bank gave you does — a conversion should carry it across rather than replace it. That is what our OFX to QBO and QFX to QBO converters do; the placeholder is only ever used when there was nothing to preserve, as when starting from a CSV.

3. A date QuickBooks cannot read

`<DTPOSTED>` must be YYYYMMDD. Not DD/MM/YYYY, not a locale format, not a date with a stray space.

A date QuickBooks cannot parse is not reported as an error. The transaction is simply not there afterwards. If your import succeeded but came in short, count the rows before assuming it worked.

4. Repeated transaction ids — the silent one

This is the failure worth knowing about, because nothing tells you it happened.

Every transaction in a QBO carries a `<FITID>`, a unique identifier. QuickBooks uses it to avoid importing the same transaction twice, which is genuinely useful — re-import the same file and you do not get everything twice.

But if two different transactions share a FITID, QuickBooks silently keeps the first and discards the second. No error. No warning. A transaction that simply is not in your books.

The fix is for ids to be derived from each transaction's full contents including its position, so two otherwise identical transactions still differ. Every ledger file this site produces does that.

Working out which one you have

  1. Open the file in a text editor A QBO is plain text. If it opens as gibberish, it is not a QBO at all.
  2. Search for INTU.BID Absent means cause 1. Present but generic — 3000, or all zeros — may be cause 2.
  3. Look at one DTPOSTED It should read like 20240301. Anything with slashes will not import.
  4. Count your FITIDs Count the STMTTRN blocks, then count the distinct FITID values. If the second number is smaller, transactions will be dropped silently.
  5. Import one month first Then compare the register against the statement before importing the rest.

Frequently asked questions

QuickBooks Online says the file is not supported. Same causes?

Mostly. QuickBooks Online is stricter about file age — it may refuse transactions older than a certain window regardless of whether the file is valid.

Can I edit the INTU.BID by hand?

Yes, it is plain text. Whether that helps depends on whether you know your bank's real id. Guessing one is not better than the placeholder.

My import worked but the amounts are the wrong way round.

That is a converter problem, not a QuickBooks one: the source's direction was misread. Check a known deposit — if money in is showing as money out, the whole file is inverted and needs reconverting.

Is there a way to check a QBO before importing?

Convert it to something readable first. QBO to CSV or QBO to PDF both show you exactly what is in the file before QuickBooks swallows it.

Convert a statement now

Convert a bank statement PDF to Excel, or see every format. More in the guides.