How do I convert a bank statement to a QBO file for QuickBooks?

Upload the statement PDF to the converter above, confirm the transactions in the preview, choose QBO, and download the .qbo file. In QuickBooks Online go to Transactions, Bank transactions, pick the account, and upload the file, no column mapping is needed. Five pages each month are free with no account.

Why use QBO instead of importing a CSV into QuickBooks?

A QBO (Web Connect) file is read natively, so QuickBooks already knows where the date, description, and amount are and posts debits and credits with the correct sign. A CSV import forces you through a column-mapping screen where reversed signs are an easy and costly mistake.

Why do I need a QBO file for older transactions?

QuickBooks' live bank feed only backfills roughly 90 days of history when you connect an account, so anything older never arrives automatically. Converting your statements to QBO and uploading them is the standard way to bring in last quarter, last year, or several years for a catch-up.

Where do I upload a QBO file in QuickBooks Online?

Go to Transactions, then Bank transactions, select the account the statement belongs to, choose Link account or the Upload option, and pick your .qbo file. QuickBooks reads it directly and places the transactions in the For review tab.

Will QuickBooks create duplicates if dates overlap?

Each transaction in the QBO file carries a unique FITID that QuickBooks uses to recognize entries it already has, so an overlapping range is flagged rather than imported twice.

Is converting a bank statement to QBO free?

Yes, the first five pages every month are free with no signup or card. Larger multi-year catch-ups are covered by affordable credit packs, and the PDF is processed in memory and not stored.

Bank Statement to QBO Converter, Free for QuickBooks

A bank statement PDF becomes a QBO file by extracting every transaction and writing it in QuickBooks' native Web Connect format, the same structure QuickBooks downloads when you connect a bank directly. Because the file already carries each transaction's date, description, amount, and type in fields QuickBooks understands, importing it skips the column-mapping screen entirely: no telling QuickBooks which column is the date, no fixing reversed signs. Upload the PDF above, choose QBO, download, and upload the file in QuickBooks. Your first five pages each month are free with no account.

No column mapping: a QBO file is read natively, so unlike a CSV import you never map Date / Description / Amount or correct debit/credit signs.
Built for backfilling history: QuickBooks' direct bank feed only reaches back about 90 days, so older transactions have to come in by file, QBO is the format for it.
Works with Online and Desktop: QBO (Web Connect) is accepted by QuickBooks Online and by Desktop Pro, Premier, and Enterprise.
Coverage: tested against 500+ bank layouts across the US, UK, Canada, India, and the EU.
Cost and privacy: 5 pages/month free, then credit packs; the PDF is parsed in memory and not stored.

Why a QBO file imports without a mapping screen

QBO is QuickBooks' own bank-feed format. It is built on OFX, the Open Financial Exchange standard banks use for direct connections, with QuickBooks-specific tags layered on top. When you upload one, QuickBooks already knows where the date, payee, amount, and transaction type live, so it drops the rows straight into the For review tab.

A CSV import is the opposite experience. QuickBooks cannot know your column order, so it shows a three-step mapping wizard where you point it at the date column, the description column, and the amount column, choose a date format so 03/04 is not read as the wrong month, and decide whether a single signed amount or separate debit and credit columns are in play. Get the sign convention wrong and every deposit posts as a withdrawal, quietly doubling the size of the cleanup. Get the date format wrong on a statement that crosses a month boundary and transactions scatter across the wrong periods. The QBO file removes that entire wizard and the whole class of errors that rides along with it, because every one of those decisions is already encoded in the file's tags. That is why bookkeepers convert to QBO rather than CSV when QuickBooks is the destination, the import becomes a non-event instead of a careful, error-prone chore repeated for every statement.

The reason historical transactions need a file at all

If you only ever needed the last few weeks, you would let QuickBooks pull them from the connected bank feed. The catch is the lookback window: a freshly connected bank typically backfills only around 90 days of history, and anything older never arrives through the live feed.

That gap is exactly what file import exists to close. To bring in last quarter, last year, or several years for a catch-up or a clean migration, you download the PDF statements covering that span, convert them to QBO, and upload each one. The bank feed handles "now," the QBO file handles "everything before now." A practical rhythm is one .qbo file per statement period, convert January, February, March as three files rather than trying to merge them, because it keeps the review queue manageable and makes any re-import surgical. This is the standard play for three situations: a bookkeeper taking on a client mid-year, a business switching from spreadsheets or another package to QuickBooks, and anyone whose live feed connected late and missed the opening months of the year. For a full walkthrough of the import side, see how to import bank statements into QuickBooks.

Uploading the QBO file in QuickBooks Online

The import lives under the banking area, and the file is recognized the moment you point QuickBooks at the right account. The path is short.

Step	Where in QuickBooks Online	What to expect
1. Open banking	Transactions > Bank transactions	Your list of connected accounts
2. Pick the account	Select the account the statement belongs to	The account's review queue
3. Start an upload	Link account > Upload from file (or the Upload option in the account menu)	A file picker
4. Choose the .qbo file	Select your converted file and confirm the account	No column-mapping screen, QBO is read directly
5. Review	For review tab	Transactions ready to categorize and accept

QuickBooks de-duplicates against transactions already present using each entry's unique ID, so if a few days overlap with the live feed you are warned rather than landing double entries. This makes it safe to slightly overlap your file's date range with the feed instead of guessing the exact cutoff, which removes the risk of leaving a one-day gap between the imported history and the live data.

QBO or OFX, which file does your software take?

Use QBO when QuickBooks is the destination; use OFX for nearly everything else. They share a foundation, but QuickBooks treats its own QBO format as the first-class citizen.

Aspect	QBO (Web Connect)	OFX
Best destination	QuickBooks Online and Desktop	Xero, Sage, GnuCash, MoneyWiz, most finance apps
Underlying standard	OFX plus QuickBooks-specific tags	Open Financial Exchange
Column mapping	None, read natively	None, read natively
Bank-identity tags	Carries an FID/INTU.BID that QuickBooks may check	Carries an FID; some apps are stricter than others
Use it when	You import into QuickBooks	Your app rejects QBO or you are not on QuickBooks

The reason the distinction matters is that QuickBooks treats QBO as its trusted native format and validates the Intuit-specific tags inside it, while a generic finance app simply wants the OFX transaction data and ignores the QuickBooks extras. Feeding QuickBooks a plain OFX file sometimes works and sometimes triggers an "unsupported file" message, whereas QBO is the format it never argues with. Going the other direction, handing QuickBooks-flavored QBO to a non-Intuit app can confuse it for the same reason. Match the file to the destination and the import is boring, which is what you want. If you are not on QuickBooks at all, the OFX converter targets the broader ecosystem. If you want a spreadsheet rather than an accounting import, the CSV converter is the flexible choice.

What is actually inside the QBO file

OFX-based Web Connect structure. The file uses QuickBooks' Web Connect (.qbo) format, OFX with Intuit's tags, so QuickBooks accepts it through the same path as a bank's own download.
A unique ID per transaction. Each entry carries its own FITID, the field QuickBooks uses to recognize and de-duplicate transactions, so re-importing an overlapping range does not double up your books.
Account and routing context. Bank-identity fields are populated so QuickBooks can match the file to the correct account on upload.
Signed amounts, no mapping. Debits and credits are encoded with the correct sign in the transaction type, so deposits and withdrawals post the right way without you touching a settings screen.
Date normalization. Posting dates are written in the format QuickBooks expects, so transactions land on the correct day regardless of how the statement printed them.

What we see across 500+ bank layouts feeding QuickBooks

From converting statements destined for QuickBooks across hundreds of bank templates, the friction almost never comes from QuickBooks itself, it comes from how the source statement is structured, and three patterns recur:

Separate withdrawal and deposit columns. Many banks print two amount columns rather than one signed figure. Encoded carelessly, half the transactions post backwards in QuickBooks. We resolve the sign before writing the file so deposits and withdrawals always land correctly.
The 90-day surprise. The most common reason people reach for a converter is discovering the live bank feed will not reach the older months they need for a year-end catch-up, file import via QBO is the only route to that history.
Bank-identity strictness. QuickBooks occasionally checks the FID/INTU.BID tags. We populate sensible identity fields so the file is accepted, and where a bank is unusually strict, the OFX route is the fallback.

Converting to QBO turns a stack of PDF statements into clean QuickBooks bank feeds that import in a couple of clicks, with no mapping and no reversed signs, the practical way to backfill the history the live feed cannot reach. Upload your statement above, choose QBO, download, and upload it in QuickBooks. Start free with five pages a month at the free converter, and use credit packs for a multi-year catch-up.

Convert a Bank Statement PDF to QBO

Drop your bank statement PDF here