Choose the right file format
QuickBooks Desktop reads several formats, and picking the correct one saves time. QBO (also called Web Connect) is the standard for importing bank and credit card activity. It maps directly into a bank feed, so transactions arrive with dates, amounts, and descriptions ready to match.
IIF (Intuit Interchange Format) is a tab-delimited text format used for importing lists like customers, vendors, and the chart of accounts, and for bulk journal entries or transactions. It is powerful but unforgiving about column order, so it suits users comfortable with structured data.
QFX is the Quicken variant of the same underlying OFX standard and behaves like QBO in most cases. If your bank only offers a plain CSV or PDF statement, you will need to convert it to QBO or format it for import before QuickBooks Desktop can read it.
Import a QBO (Web Connect) bank file
This is the most common path for bank and credit card transactions. First, confirm the account exists in your chart of accounts and, if you use bank feeds, that it is set up for Web Connect rather than Direct Connect.
In QuickBooks Desktop, go to File, then Utilities, then Import, and choose Web Connect Files. Select your .qbo file. QuickBooks will ask which account to link it to. Pick the matching bank or credit card account, or create a new one if prompted.
After import, the transactions appear in the Bank Feeds center for review. You match each one to an existing entry or add it as new, assigning a payee and category. Nothing posts to your registers until you accept it, which gives you a chance to catch mistakes before they hit your books.
Import lists and journal entries with IIF
Use IIF when you need to bring in structured data such as a chart of accounts, customer or vendor lists, items, or batches of transactions. Go to File, then Utilities, then Import, and select IIF Files.
IIF files are plain text with header rows that define the record type and column layout. The header must exactly match the fields QuickBooks expects, and accounts or names referenced in the file should already exist in your company file or be defined within the import. A single misplaced column can cause the whole import to fail or post to the wrong place.
Because IIF bypasses many of the checks a normal entry goes through, always back up your company file first. Test with a small sample before importing a large batch, and review the results in the relevant registers and reports.
Convert statements and avoid duplicates
If you only have a PDF statement or a CSV export, QuickBooks Desktop cannot read those directly for bank activity. You need to convert them into a QBO file that maps to your account, or format the data into an IIF for transaction import. Converting to QBO is usually the cleaner route because it flows through the bank feed review process.
When you convert, keep the field mapping consistent: date, amount, and description at minimum. Watch the sign on amounts so debits and credits land correctly, and make sure the date format matches what QuickBooks expects for your region.
To prevent duplicates, import each statement period only once and note the last transaction date you brought in. If a transaction already exists from a prior import or manual entry, use the match option in bank feeds instead of adding it again. After importing, run a reconciliation against the paper or PDF statement so your ending balance ties out.