Convert Mercury CSV to QuickBooks (.QBO)
Works with Mercury CSV and Excel exports Nothing uploaded
Mercury is a popular banking platform for startups, and its dashboard gives you a few export choices: a plain CSV, a QuickBooks-flavored CSV, and a NetSuite CSV (found under the three-dot menu on the transactions table, or in Settings → Statements & data). What it does not hand you is a .QBO / Web Connect file you can import straight into QuickBooks Desktop. That gap is exactly where things get annoying.
Even Mercury's "QuickBooks CSV" is still a CSV, QuickBooks Online may accept it after column-mapping, but QuickBooks Desktop won't take any CSV at all, and Mercury's downloaded statements often shorten dates (showing 03/15 instead of 03/15/2025), which trips up reconciliation. QBO Maker bridges the gap: drop your Mercury CSV in, and it produces a clean .QBO (or .QFX / .OFX) with the right account and routing metadata baked in. Everything happens in your browser, your transaction data never leaves your machine. Convert your Mercury export now.
.QBO QuickBooks accepts. For Mercury, its dates are usually MM/DD/YYYY (statements may omit the year, e.g. 03/15), and amounts arrive as a single signed column (positive credits, negative debits), both detected automatically.A typical Mercury export has columns like Date, Description, Amount, Status, Source Account, Bank Description, Reference, Note and uses MM/DD/YYYY (statements may omit the year, e.g. 03/15) dates. QBO Maker auto-detects these, just confirm the mapping.
How to import Mercury statements into QuickBooks
- Export your transactions from Mercury online banking as CSV or Excel.
- Open the QBO Maker converter and drop the file in.
- Confirm the auto-detected date, amount (or separate debit/credit) and description columns.
- Choose .QBO as the output and click download.
- In QuickBooks Online: Transactions → Bank transactions → Upload from file, then select the .QBO. In Desktop: Banking → Bank Feeds → Import Web Connect File.
Mercury-specific things to watch for
- Multiple export flavors. Mercury offers plain CSV, a QuickBooks CSV, and a NetSuite CSV, but none of them is a true .QBO file, so QuickBooks Desktop still rejects them.
- Year sometimes dropped. Downloaded statements can show dates like
03/15without the year, which breaks sorting and reconciliation if pasted in raw. - Two routing numbers. Depending on when you opened your account, Mercury sits on Choice Financial (084106768) or Column N.A. (091311229). Pick the one matching your account so the .QBO maps to the right register.
- Treasury vs checking. Mercury Treasury accounts export separately, convert each account's CSV into its own .QBO file rather than mixing them.
QuickBooks Online vs Desktop
QuickBooks Online: Transactions → Bank transactions → Upload from file → choose your .QBO. QuickBooks Desktop: Banking → Bank Feeds → Import Web Connect File. Desktop is stricter about the bank ID.
Frequently asked questions
Does Mercury export a .QBO or Web Connect file for QuickBooks?
No. Mercury offers CSV exports, including a QuickBooks-formatted CSV, but not a native .QBO / Web Connect download. QuickBooks Desktop can only import .QBO, so you'll need to convert Mercury's CSV first. Paste or upload it at the converter and you'll get a ready-to-import .QBO.
Mercury already has a QuickBooks CSV option, why convert?
That option is still a CSV, which only works with QuickBooks Online's manual upload (and even then needs column mapping). QuickBooks Desktop won't accept any CSV. Converting to .QBO gives you a one-click Web Connect import in Desktop and a cleaner Banking-feed match in Online.
Why do my Mercury dates look wrong after import?
Mercury statements sometimes drop the year (showing 03/15 instead of 03/15/2025). When you convert, make sure the date format and statement year are set correctly so transactions land in the right period. QBO Maker lets you confirm the format before generating the file.
Is my Mercury financial data uploaded anywhere?
No. The conversion runs entirely in your browser using JavaScript, your CSV is parsed locally and the .QBO is generated on your device. Nothing is sent to a server. You can confirm by checking your output file offline.