Free OFX to QBO Converter for QuickBooks
Convert supported Open Financial Exchange (OFX) bank or credit-card transactions into a QuickBooks Web Connect (.QBO) file for review and import into QuickBooks Desktop Bank Feeds.
OFX vs QBO: OFX is the Open Financial Exchange standard used for financial-data exchange. QBO is the Web Connect file type QuickBooks Desktop Bank Feeds reads. The two are related, but Web Connect expects a .QBO carrying compatible statement and financial-institution metadata rather than a generic .OFX.
Choose your file
Drop your .OFX, .QFX or .QBO file here
Your file is never uploaded. We never receive it or store it.
Same File, Different Label
An OFX to QuickBooks converter re-labels a file rather than rebuilding it. OFX, QFX and QBO are all Open Financial Exchange, and what separates them sits in the sign-on block: a .qbo carries the Intuit Bank ID that Web Connect checks before it reads a single transaction. Your bank's export never carried that tag, so the transactions in it are almost certainly fine and only the label is missing.
All three extensions describe the same standard. A .ofx is plain Open Financial Exchange, a .qfx is the same file carrying Quicken's identifiers, and a .qbo is the same file carrying Intuit's. Neither of the first two reads through Web Connect and the third does, which is why taking Open Financial Exchange to QuickBooks is mostly a re-tag rather than a re-parse.
So the conversion copies your transactions across untouched and adds the Intuit Bank ID. Nothing is re-dated, re-signed or re-derived on the way through. What QuickBooks reads is your bank's own statement under a label Web Connect will accept, which is what the drawing beside this sets out tag by tag.
| From the .OFX — the file you have | ||
|---|---|---|
| <SONRQ> | Quicken, or none | The sign-on block |
| <FITID> | 2026030400471 | The bank's own id |
| <DTPOSTED> | 20260304 | Posted date |
| <TRNAMT> | -84.25 | Amount |
| <NAME> | Example Merchant | Payee |
| Into the .QBO — the file QuickBooks reads | ||
| <INTU.BID> | 2430 | Rewritten |
| <FITID> | 2026030400471 | Unchanged |
| <DTPOSTED> | 20260304 | Unchanged |
| <TRNAMT> | -84.25 | Unchanged |
| <NAME> | Example Merchant | Unchanged |
One tag is added and the rest is copied. The transaction id surviving is what lets QuickBooks recognise a period it has already imported.
Your Bank's Transaction Ids Are Kept
The ids are what make a second import safe, and a conversion can quietly discard them.
QuickBooks Skips What It Has Seen
Every transaction in a Web Connect file carries an identifier. QuickBooks skips any identifier it has already imported, and that is what stops an overlapping date range posting twice. The protection is real, but it belongs to the ids rather than to the import.
The Bank's Own Id Travels
Each FITID is read out of the source file and written into the .qbo unchanged, so the protection your bank's own ids give you survives the conversion. A converter that regenerates those ids destroys that protection silently, and nothing in QuickBooks will tell you it happened.
A Missing Id Gets a Stable One
Where a transaction arrived without an identifier, ours is derived from its own date, amount and payee rather than from a counter or the clock, so converting the same file twice produces the same ids. Genuinely identical rows carry an occurrence number, which keeps two matching charges on one day as two transactions.
What an OFX File Is
A statement in a standard format, written by a system that was not writing for QuickBooks.
One Standard, Two Dialects
OFX 1.x is SGML, where a value simply runs until the next tag opens, and OFX 2.x is real XML. Both wrap each transaction in a STMTTRN block, so the reader handles them on one path rather than asking you which dialect your bank wrote.
It Was Never Labelled for QuickBooks
Banks, treasury tools and finance applications export the plain standard because the plain standard is what it is. The Intuit identifiers are added only when a file is written specifically for QuickBooks, so a .ofx is not a damaged .qbo. It is a correct file with a different audience.
It Describes One Account's Activity
A statement block names the account, the period and the closing balance, then lists transactions: a date, an amount, a payee, a memo, a check number and an identifier. No category sits on any of them, because the format carries bank activity rather than coded entries.
How to Convert OFX to QBO
It takes four steps to convert OFX to QBO, and only the sign-on block is rewritten.
Drop Your .OFX
A bank, credit-card or finance-application export, and a .qfx or an existing .qbo works here too. The file is read in your browser, so nothing is uploaded and there is no sign-up.
.ofx · .qfx · .qbo
Set the Intuit Bank ID
The account number comes out of the file you dropped in when you leave it blank. The account type and currency are settings you choose, and they start at Checking and USD whatever the file says. The Intuit Bank ID is the one value the file cannot supply, because it identifies your bank to QuickBooks rather than describing your transactions. Upload a .qbo your bank has already sent and the value is read out of it. The CSV to QBO Converter page covers where it comes from.
INTU.BID required
Read the Count and the Warnings
How many transactions came across is on screen before anything is written, and any transaction the reader could not use is named by its own identifier rather than dropped in silence. A missing Bank ID is raised as an error here instead of as a rejection in QuickBooks later.
counts and warnings on screen
Download the .QBO
The Web Connect file is built in your browser and downloaded from there. Import it into a backed-up company file through Bank Feeds and review the transactions before you accept them.
Bank Feeds import
One Re-tag, or a Feed That Keeps Itself
The re-tag takes a minute. Doing it every month is a different question.
| Need | Free converter | Autymate |
|---|---|---|
| One download QuickBooks would not take | The quickest route there is | Too much machinery for a single file |
| A download from the same bank every period | The Bank ID and account details re-entered each time | Confirmed once and reused |
| Several accounts, each exporting its own file | A separate pass for every account | Each account carried on its own agreed path |
| The month a file does not arrive | Nothing says so until you go looking | The gap is raised as part of the run |
| Data that starts somewhere other than the bank | Out of scope; this reads one bank file at a time | The source is connected where authorized access exists |
The Second Import
Moving OFX to QuickBooks Desktop a second time is the case that decides whether a converter was careful.
An Overlapping Period Is Normal
Re-downloading a month you already have is routine: a period gets re-run, a date range is widened, two people import the same file a week apart. That is the ordinary case rather than the unusual one, and it is the case a conversion has to survive.
What the Overlap Looks Like
Because your bank's identifiers came across unchanged, QuickBooks recognises the transactions it has already taken and passes over them. The count waiting in Bank Feeds is then smaller than the count in the file, and that difference is the protection working rather than transactions going astray.
A Bank ID QuickBooks Does Not Recognise
The value has to match QuickBooks' own list of Web Connect institutions. One lifted out of a .qbo your bank sent has already been accepted once, which is why that is the reliable source. A guessed value produces a generic rejection that explains very little about the real cause.
An OFX That Is Genuinely Damaged
Where the file's own structure is incomplete, a converter reading the same bytes meets the same limit. The warnings say which case it is before you download: no statement block it recognises, or no transaction records in the file at all.
More Than One Account, More Than One Company File
One download is one file, and the re-tag is a minute of work. What multiplies is everything around it once every account exports its own file, every period, into its own company file.
- A separate download per account, each written by a different bank's exporter
- The Bank ID, account type and currency held as approved settings rather than retyped per file
- Separate QuickBooks companies, with the right file reaching the right one
- A period that closes before every account has sent its file
- A new account or location brought on without repeating the setup from scratch
- Back years loaded once, with the overlap decided in advance rather than discovered in Bank Feeds
Common Questions
What people ask before they trust a converter with their accounting system.
Because Web Connect checks for INTU.BID, an Intuit-specific tag identifying your bank, and a plain OFX file does not carry one. QuickBooks refuses the file before it reads the transactions, with an error that says nothing about the real cause. Converting an OFX file to QBO adds that tag and leaves the transactions as they were.
Only in its tags. Both are Open Financial Exchange; a .qfx carries Quicken's identifiers and a .qbo carries Intuit's. The transactions inside are structured identically, which is why this conversion preserves them exactly and why the same converter takes either one.
Not while the identifiers survive, and here they do. Your bank's own FITID is kept on every transaction, so QuickBooks can skip what it has already imported from any route. QuickBooks may still refuse a Web Connect file for other reasons, but a period you have imported before is not one of them.
From any .qbo your bank has sent you before. Upload it in step two and the value is read out of it, along with the routing number and account details. If you have none, ask your bank for a single month of Web Connect download. Guessing does not work, because the value has to match QuickBooks' own list, and the CSV to QBO Converter page covers why.
No. It is read on your own computer and never sent to us, so there is nothing for anyone to store or delete. That applies to the .qbo you upload for its Bank ID as well: the identifiers are read out of it and nothing else.
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
A Monthly Download Is a Workflow, Not a File
Re-tagging one file is a minute of work and the converter above does it for nothing. When the same export arrives from the same bank every period, tell us where the data starts, which company file has to receive it, and how many accounts are involved.
Exact source access, fields, permissions, QuickBooks behaviour and service scope are confirmed during discovery.