Free QIF to QBO Converter for QuickBooks
Convert supported QIF banking or credit-card transactions into a QuickBooks Web Connect (.QBO) file for review and import into QuickBooks Desktop Bank Feeds.
QIF vs QBO: QIF is a financial interchange format used by Quicken and other finance tools. QBO is the Web Connect file type used by QuickBooks Desktop Bank Feeds. QuickBooks Desktop Web Connect does not directly accept QIF files.
Choose your file
Drop your .QIF file here
Your file is never uploaded. We never receive it or store it.
What Crosses, and What Does Not
A QIF to QuickBooks converter can only carry one side of each entry. A QIF record has two sides: the account the money moved through, and the category that balances it. A .QBO file is one account's statement, so only the account side can travel. Date, amount, payee, memo and check number all cross; the category on the other side of the entry does not.
What lands in QuickBooks Desktop is therefore a bank statement rather than a coded set of entries. The transactions arrive in Bank Feeds for review, which is the same place a file downloaded straight from your bank arrives.
That is a property of the target format rather than a shortcoming of the conversion. Anything writing a .QBO from a double-entry source meets the same limit, and the honest version of the answer is to say which half arrives before you convert rather than after.
| D | 08/04/2026 | Date | Crosses |
|---|---|---|---|
| T | -84.25 | Amount | Crosses |
| P | Example Merchant | Payee | Crosses |
| M | Store purchase | Memo | Crosses |
| N | 1042 | Number | Crosses |
| L | Meals:Staff | Category | Stays behind |
| ^ | End of record |
A QBO file is one account’s statement, so it has nowhere to put the category on the other side of the entry. That is the destination format, not the conversion.
What a QIF File Is
Quicken's plain-text export format, and what it takes to convert Quicken QIF to QuickBooks.
One Letter per Line
A single prefix letter starts every line and says what the rest of it means: D for the date, T for the amount, P for the payee. A lone caret closes the record and the next one begins.
It Names No Account
A QIF account carries a name and nothing else: no routing number, no account number. A file that names no account at all puts its transactions in “Unspecified Account” and tells you so rather than guessing a name for you.
Web Connect Does Not Take It
Intuit's current guidance is that QuickBooks Desktop Web Connect works with .QBO files. QIF is not part of that workflow, which is the gap this converter exists to close.
How to Convert QIF to QBO
Four steps, and the file is read in your browser rather than uploaded anywhere.
Drop Your .QIF
A Quicken, GnuCash or Moneydance export holding bank or credit-card records. The file is read in your browser, so nothing is uploaded and there is no sign-up.
.qif · .txt
Set the Account and Bank ID
A QIF account has a name and nothing else, so the account number, account type, currency and Intuit Bank ID come from you. The Bank ID can be lifted out of a .qbo your bank already sent.
INTU.BID required
Check the Dates
Quicken's apostrophe form, D01/02'03, is normalised on the way in. Genuinely ambiguous dates are resolved by the day-first setting rather than a guess.
day-first setting
Review and Download
Transaction count, date range and every warning are listed before the file is written, not after.
issues shown before download
When to Convert, and When Not To
The conversion is worth doing in some cases, and in others the file you already have is better.
Worth Converting
- Legacy export
- A legacy tool exports nothing else, so moving that QIF to QuickBooks Desktop is the only route those transactions have.
- Older records
- You are migrating older banking records and want to review them through a bank-feed import rather than key them in.
- No .QBO left
- Your bank no longer offers a direct .QBO download for the period you need, but the data survives as QIF.
Use Something Else
- Bank .QBO
- Your bank still gives you a .QBO. Use that one; it already carries the identifiers QuickBooks checks, and nothing needs converting.
- Investments
- The QIF holds only lists or investment records, which have no bank-feed equivalent to arrive as.
- Coded import
- You want fully coded transactions rather than bank-feed activity. That is a different import path, not a different converter.
The Second Time You Do This, and the Twelfth
The section above settles whether to convert. This one is about doing it again.
| Need | Free converter | Autymate |
|---|---|---|
| A one-time migration | The whole job, in a single pass | Nothing recurring to manage |
| The same export every month | Account name, Bank ID and date format re-entered | Set once and reused |
| Categories to re-code after each import | By hand in Bank Feeds, every period | Coded before it reaches QuickBooks |
| Several accounts or entities | One file at a time | Routed per account where the source allows |
| A QIF that stops arriving | You find out when the numbers look wrong | Monitored, with someone named to chase it |
What Arrives, and What You Will Re-code
You get back less than you put in, and these are the places it shows.
The Categories Did Not Travel
Every transaction arrives. The category on it does not, so each one is coded in QuickBooks as you accept it from Bank Feeds. That work is proportional to the number of transactions, which makes a long date range cost more of it than a short one.
Splits Are Not Flattened Quietly
Where a split's amounts do not sum to the transaction total, the transaction is named in the warnings along with the amount it is out by, rather than being forced to balance on the way through.
Some QIF Has No Bank-Feed Equivalent
Investment sections, memorised payees and price blocks hold nothing a bank feed can carry. A file with only categories or memorised payees in it has nothing to convert, and the converter says so in the warnings rather than leaving you to find out in QuickBooks.
Duplicate Identifiers Are Skipped
Each transaction carries an identifier derived from its own content rather than from a counter, so converting the same records twice produces the same identifiers and QuickBooks can skip the ones it has already imported.
Converting Files for Several Accounts
One file at a time is what the converter is built for. These are the parts that repeat once every account exports its own QIF, every period, into its own company file.
- A separate export per account, each with its own layout
- The same re-coding after every import, by hand
- Separate QuickBooks company files, each needing the right one
- Different date conventions, and files that arrive late
- A new account or location, set up from scratch each time
Common Questions
What people ask before they trust a converter with their accounting system.
QIF stands for Quicken Interchange Format. It is a plain-text financial format where one letter at the start of each line says what the rest of the line holds, and a lone caret closes each record. A QIF can carry accounts, transactions, categories and memorised payees.
A QBO file is a QuickBooks Web Connect file, used by QuickBooks Desktop Bank Feeds to bring bank or credit-card transactions into a company file. It describes one account's activity, which is why it is not the same thing as a coded accounting import.
No. Intuit's current QuickBooks Desktop guidance is that Web Connect works with .QBO files; QIF and QFX files do not work directly in that Web Connect workflow, which is the gap a conversion closes.
No. Converting a QIF file to QBO works for banking and credit-card records. Investment sections, list-only files such as categories or memorised payees, and splits whose meaning would change if they were flattened are reported rather than forced into a format that cannot hold them.
From a .qbo your bank has already sent you. QuickBooks checks the Intuit Bank ID in the file header against its own list of Web Connect institutions, so the reliable value is one your own QuickBooks has already accepted. The CSV to QBO Converter page covers where to find it and how to lift it out of an existing file.
No. QuickBooks can refuse a Web Connect file over its structure, financial-institution verification, account configuration, duplicate identifiers or other conditions at the destination. No converter can promise otherwise.
No. The conversion carries the transaction data across and makes no accounting classification on your behalf. Each transaction is categorised in QuickBooks when you accept it from Bank Feeds.
Use the converter for occasional files. When the same export arrives from the same system every period, Autymate can scope a managed QuickBooks workflow where authorized source access and destination behavior are available.
Written and maintained by The Autymate integrations team. We build and run accounting integrations for multi-location franchises, ISVs and bookkeeping firms: QuickBooks Desktop and Online, POS, payroll and ERP. These converters exist because we kept writing the same ones for customers, and there was no reason to keep them to ourselves.
Last reviewed
Stop Converting the Same Export Every Month
The converter is the right tool when one file has to move. If the same system produces the same QIF every period, tell us where it starts, which company file receives it, and how many accounts are involved.
Exact source access, fields, permissions, QuickBooks behaviour and service scope are confirmed during discovery.