QIF to QBO Conversion Field Mapping and When PDF Is Faster

Convert a PDF bank statement to a QuickBooks file

Drop in a PDF statement and get a QBO (Web Connect) or IIF file you can import into QuickBooks Online or Desktop.

QIF to QBO conversion is possible in principle but rarely worth doing. A QIF file has no bank ID, account ID or unique transaction ID, and a QBO file needs all three, so a converter has to invent them. If the QIF came from a bank PDF in the first place, it is faster and safer to convert the PDF straight to QBO and let the closing balance check prove the rows are complete.

People land on this question from two directions. Some have a QIF export from Quicken, Money or an old bank download and want it inside QuickBooks. Others have a stack of PDF statements and assume QIF is the stepping stone. This article covers both, shows exactly how the two formats differ, and gives a rule for choosing the route. If your starting point is PDF, the PDF to QuickBooks automation page shows the shorter path.

Why QuickBooks will not take your QIF directly

QuickBooks Online accepts CSV, QBO, QFX and OFX files for bank uploads. QIF is not on that list. QuickBooks Desktop builds its bank import around the Web Connect format, which is what a .qbo file is. So a QIF has to become a QBO (or a CSV mapped by hand) before QuickBooks will read it. The format itself is documented informally, and the Quicken Interchange Format overview is a fair reference for the field codes below.

The same transaction in both formats

Here is one debit as it appears in each file, followed by what is missing on the QIF side.

ItemQIFQBO (OFX body)Gap when converting
DateD03/14/2026DTPOSTED 20260314QIF date style varies by region, so a day and month can swap
AmountT-412.50TRNAMT -412.50Thousands separators in QIF break some converters
PayeePHILLIPS SUPPLY CONAME PHILLIPS SUPPLY CONone, but long memos get cut
Check numberN1042CHECKNUM 1042None
Unique IDNot presentFITID, requiredThe converter must generate one per row
Bank and accountNot presentBANKID and ACCTID, requiredYou type them or the file imports to the wrong account
Statement balanceNot presentLEDGERBALNothing to check the rows against

The last row matters most. A QIF carries no ending balance, so after conversion you have no way to know whether a row was dropped. You find out at reconciliation, one statement at a time.

The three ways a QIF conversion goes wrong

Duplicate or unstable transaction IDs

QuickBooks uses FITID to decide whether a downloaded transaction is new. If a converter derives it from the row position, a second run with a slightly different file produces fresh IDs and QuickBooks imports everything again. Duplicates then have to be deleted one at a time. The fix is a converter that builds the ID from date, amount and description, and that you run once per period, never twice over an overlapping range.

Wrong account on import

Because a QIF has no account identity, the generated QBO carries whatever bank and account numbers the converter was given. If those match a different account already connected in QuickBooks, the file offers to import into the wrong one. Always pick the destination account yourself on the upload screen and check the first three rows before accepting.

Date and sign errors

A QIF written on a machine with day first settings reads 03/04/2026 as 3 April, while US QuickBooks reads 4 March. Check one transaction with a day above 12. Credit card QIF files also flip signs in some exports, so a payment shows as a charge. Compare the total of the first ten rows with the PDF statement before importing anything.

A worked comparison with real numbers

Take a client with 18 months of checking history, 18 statements of about 55 lines each, 990 rows in total. Assume the QIF exists and was exported from old Quicken software.

StepQIF routePDF route
SourceOne QIF covering 18 months18 statement PDFs
ConversionQIF to QBO tool, then split by monthOne .qbo per statement
Balance proofNone, reconcile 18 timesEach file checked against its printed closing balance
Typical failureA dropped row found at month 11The failing month is named before download
Fits whenQIF is the only record that existsThe bank PDFs exist, which is almost always

The QIF route wins in one case: the PDFs are gone and the QIF is the only copy. In every other case the PDF is the primary document, the one an auditor or a client's bank will ask for, and converting from it removes a lossy middle step. A year of statements is about $49 for a Starter month, or $149 on Plus when you have several clients, as listed on the pricing page.

How to decide in one minute

  1. Do you still have the bank's PDF statements? If yes, convert those. Start with one month on the PDFQBO converter and compare the rows with the page.
  2. Is the QIF the only record? Convert it, import one month into a test company file first, then reconcile that month before loading the rest.
  3. Is the history long and spread over several accounts? Work month by month with the closing balance as your check. The routine in batch converting PDF bank statements to QuickBooks applies to either source.

If you are still choosing between formats for a PDF source, PDF to CSV versus QBO for QuickBooks explains why the QBO file avoids the column mapping step. Bookkeepers chasing missing PDFs from slow clients sometimes send a quick reminder text through a tool like a bulk texting service for client follow ups instead of a third email.

Frequently asked questions

Can QuickBooks Online import a QIF file?

No. QuickBooks Online accepts CSV, QBO, QFX and OFX files for bank uploads. A QIF has to be converted to one of those first, and QBO is the cleanest target because it carries account identity and transaction IDs.

Is QIF the same as QBO?

No. QIF is an older Quicken text format with no bank ID, account ID or transaction ID. QBO is Web Connect, built on OFX, and requires all three plus an optional ledger balance. They hold similar transaction data in very different wrappers.

What is the best way to get bank history into QuickBooks without a QIF?

Convert the bank's PDF statements to QBO. Each statement becomes one file, checked against its closing balance, and you import them through the normal bank upload screen. It works for closed accounts and for history older than a bank feed.

Why did my QIF import create duplicate transactions?

The converter probably generated new transaction IDs on the second run, so QuickBooks treated every row as new. Delete the duplicates, then re-import only the date range that is missing, once.

Skip the manual entry

Upload a PDF bank statement and get a QBO or IIF file ready to import into QuickBooks.

Convert a Statement