QBO vs. OFX vs. CSV: What QuickBooks Needs

QuickBooks doesn't take one universal import file — it takes a specific one, depending on which version you run and where the file is headed. Send the wrong format and you'll get a rejected import or a mess of unmatched transactions, not a clean bank feed.

That's the part that trips people up. QBO, OFX, and CSV all sound interchangeable from the outside, but QuickBooks treats them very differently depending on whether you're on Desktop or Online.

QBO: the one format both versions understand

QBO is the format QuickBooks recognizes natively across both Desktop and Online. It's the safest default when you're not sure which format a specific import screen wants, and it's the format most bank-statement converters, including Skyline Convert, treat as the primary output.

OFX: built for Online's bank feed

OFX is the format QuickBooks Online expects when you're feeding transactions into its bank feed manually, rather than connecting the account live. It's a natural fit for exactly the situation a live feed can't cover — a closed account, an older statement, or a bank that doesn't offer a feed at all.

IIF: the Desktop-only holdover

IIF predates QBO and is specific to QuickBooks Desktop. It still shows up in older bookkeeping workflows and some Desktop-specific import screens, which is why Skyline Convert supports it as an output option alongside QBO.

CSV: the fallback, not the shortcut

CSV will import into almost anything, which is exactly why it's a fallback rather than a first choice. A raw CSV export needs every column mapped to what QuickBooks expects — date format, amount sign, payee field — before it will import cleanly, and that mapping step is where a lot of manual cleanup creeps back in.

Where the source file fits into this

None of this depends on where the data started out. Whether the original is a PDF bank statement, a CSV export from a bank portal, or even an older QBO or OFX file from a different system, the question is the same: which output format does the destination actually expect. Skyline Convert reads CSV, PDF, QBO, OFX, and QIF as input and produces QBO, OFX, IIF, or CSV as output, so the starting format doesn't limit which of the four you end up with.

It's worth separating the input question from the output question entirely, since they get confused with each other easily. The input format is whatever a bank or a previous system happened to hand you — you don't control that. The output format is the one thing you do control, and it's the one that determines whether the import actually works.

Picking the right one without guessing

If you're on QuickBooks Desktop, export QBO or IIF. If you're on Online and feeding a file into the bank feed, export QBO or OFX. Reach for CSV only when neither format fits — a different accounting tool, a manual reconciliation in a spreadsheet, or an import screen that specifically asks for it. Our full walkthrough on converting a PDF bank statement to QuickBooks covers the process end to end, including which format Skyline Convert outputs by default for each version.

Frequently asked questions

Can I just always export CSV to be safe?

You can, but you'll spend time mapping columns that QBO or OFX would have avoided entirely. CSV is the format to reach for when nothing else fits, not the default.

Does QuickBooks Online ever need IIF?

No — IIF is specific to Desktop. Online works with QBO and OFX.

What does Skyline Convert output by default?

Skyline Convert supports QBO, OFX, IIF, and CSV as output formats, so you choose the one your version of QuickBooks — or another tool entirely — actually expects, rather than being locked into one option.

Why does the wrong format cause a rejected import instead of just an error message?

QuickBooks validates the structure of the file against what that import screen expects. A mismatched format often fails silently or partially, which is part of why picking the right one upfront matters more than it seems like it should.

Does the same logic apply beyond bank statements?

Yes. The same format mismatch causes the same rejected-import problem whether the source is a bank statement, a credit card export, or a historical file from another system — the fix is always to match the output to what the destination expects, not to the format the source happened to arrive in.

Is one format ever objectively better than the others?

Not in the abstract — each one exists because a specific version of QuickBooks expects it. "Better" here just means "the one your import screen will actually accept," which is a question about your setup, not about the formats themselves.

The bottom line

There's no universal answer to which format you should export — it depends entirely on which QuickBooks you're running. Match the format to the version once, and you stop rejected imports before they happen instead of troubleshooting them after.

Try Skyline Convert →