Unclip
Sign in

Convert Excel to QBO for QuickBooks

Drop an .xlsx of bank transactions and get a QuickBooks Web Connect file, in your browser. Any column order; real dates or text dates.

  • Runs in your browser. The file is never uploaded.
  • Free for 10 files a day. No account.
  • Also writes CSV, Excel, QFX, OFX, QIF, IIF, PDF.
  • Nothing is uploaded: the file stays on your computer
  • Free for 10 files a day, no account
  • Every output format from the same screen

Why Excel to QBO

Bookkeepers often end up with transactions in a spreadsheet: typed in from paper, copied from a portal, or exported by a system QuickBooks doesn't talk to. QuickBooks won't import the .xlsx, and its CSV import is picky about columns. A QBO file sidesteps all of that: it imports like a bank download, no column mapping, no lost rows.

Preparing the spreadsheet, then importing

  1. One row per transaction on the first sheet, with a header row. Needed: a date column and either a signed amount column or debit and credit columns. Optional: description, memo, check number.
  2. Dates can be Excel dates or text like 01/31/2026. Day-first dates are detected when a day above 12 appears; you can override the order under Options.
  3. In QuickBooks Online, open Transactions, then Bank transactions, and pick the account's tile.
  4. Open the Link account dropdown and choose Upload from file, then select the .qbo file you just downloaded.
  5. Choose the QuickBooks account the transactions belong to and confirm. They land in the For review tab.

How the conversion works

1. Read

Columns are detected from the header, or from the content when there is no header: a date column, an amount column or a debit and credit pair, and the longest text column as the description. Day-first dates are recognised.

2. Check

Rows without a readable date and amount are counted and reported, never silently dropped. Totals in and out and the period are shown so you can compare them with the source before importing.

3. Write

A valid OFX 1.02 file with the Intuit header tags the target program expects, escaped special characters (the usual cause of error OL-222) and a stable FITID per transaction so re-imports don't duplicate.

Starting from a PDF statement? The statement converter reads it and checks every row against the printed balance.

Related converters

  • CSV to QBOTurn a bank's CSV export into a QuickBooks Web Connect (.qbo) file in your browser. The file never leaves your computer.
  • CSV to IIFCreate a QuickBooks Desktop IIF import file from a CSV or Excel file of bank transactions. Pick the bank and offset accounts; download; import.
  • QBO to ExcelOpen a QuickBooks Web Connect (.qbo) file as a real spreadsheet: dates as dates, amounts as numbers, one row per transaction.
  • CSV to OFXMake an Open Financial Exchange (.ofx) file from a CSV or Excel export, for Xero, Sage, Quicken, GnuCash, MoneyWorks and anything else that imports bank feeds.

All file converters

Questions

Which sheet is used?

The first worksheet. Move your data there, or save that sheet as its own file.

Old .xls files?

Not supported. Save as .xlsx or CSV in Excel first.

What should I put as the bank ID (INTU.BID)?

It only sets the bank label QuickBooks shows during import; you still pick the real account yourself. The default, 3000, works for every account type. If QuickBooks complains that the bank isn't supported, try the ID your bank's own Web Connect files use: open one in a text editor and look for INTU.BID.

QuickBooks says the file has an invalid format or shows error OL-222

That's almost always an unescaped & or < in a payee name, or a missing bank ID. Unclip escapes these characters and always writes INTU.BID. If it still fails, send us the first ten lines of the file (no account numbers needed) and we'll look at it.

Will importing twice create duplicates?

Each transaction gets a stable FITID based on its date, amount and payee, so QuickBooks recognises a file it has already seen. New transactions in a later file still come through.