How to Import Mercury Transactions into QuickBooks (Including the Months the Sync Skips)

Short answer: Connect Mercury to QuickBooks Online through Mercury's free integration and it will sync transactions several times a day, forward from the start date you choose. It will not fill in the past. QuickBooks does not download transactions older than 90 days through any bank connection, so for earlier months you download the Mercury statement PDFs, convert them to QBO files, and upload them under Transactions, Bank transactions, Upload from file.

That second half is where most of the work actually lives. Mercury is where a very large share of US startups park their operating cash, and startups have a habit of running for a year on a spreadsheet before anyone hires a bookkeeper. By the time QuickBooks gets set up, the interesting history is already behind the wall.

Does Mercury integrate with QuickBooks?

Yes, and it is genuinely good. Mercury's QuickBooks Online integration is free, syncs several times a day, and lets you assign GL codes to transactions inside the Mercury dashboard so they arrive in QuickBooks already coded. If you have an active account and you care about current activity, turn it on and stop reading. Nothing below competes with that.

The catch is direction. The integration runs forward from the start date you pick during setup. It does not reach behind that date and rebuild what came before. On top of that sits Intuit's own rule, which applies to every bank connection in QuickBooks, not just Mercury's: transactions older than 90 days cannot be downloaded through a feed and have to be added from a file. A first connection typically brings in somewhere between 30 and 90 days depending on the institution, and that is the end of it.

Why is QuickBooks only showing 90 days of Mercury transactions?

Because that is the ceiling QuickBooks enforces, not something Mercury chose. Intuit states that transactions older than 90 days cannot be downloaded and must be added manually from a supported file. This is the single most common thing people get wrong here: they assume the short history is a bug in the Mercury connection, so they disconnect and reconnect it. Reconnecting does not reach backward. It starts a fresh 90-day window and you end up exactly where you were, sometimes with duplicates for your trouble.

The file import path exists precisely for this. QuickBooks Online accepts QBO, QFX, OFX, and CSV files on the upload path, and QuickBooks Desktop Web Connect accepts .qbo. None of them accept a PDF, which is the one format Mercury hands you for a historical statement. Converting the statement is the bridge.

What each path to QuickBooks actually reaches

Read that as a division of labor. The integration owns everything from today forward. Converted statements own everything behind it.

How to import older Mercury transactions into QuickBooks, step by step

1. Download the statements

In Mercury, click your org name in the top left and open Documents & Data, or open a specific account and choose View Statements. Select every month you need. Mercury lets you tick several statements and download them together, which matters when you are rebuilding a full year rather than patching one gap. If you are the bookkeeper and a founder forwarded you a PDF, that file is just as good.

2. Convert the PDFs to QBO

Upload them to the Mercury statement to QBO converter and pick QBO as the output format. You get back a Web Connect file with the OFX structure QuickBooks expects, debits negative, credits positive, posting dates intact. Several months can go in at once. If you would rather work in a spreadsheet first, the same upload produces XLSX or CSV through the Mercury statement to Excel converter.

3. Upload into QuickBooks

In QuickBooks Online, go to Transactions, then Bank transactions, choose the Mercury account, and pick Upload from file under the Link account dropdown. Select the QBO file, confirm which account it maps to, and the transactions land in the For review tab. In QuickBooks Desktop, use File, Utilities, Import, Web Connect Files.

Two limits to respect: one Mercury account per file, because QuickBooks maps a single QBO to a single account, and each upload has to stay under 1,000 transactions and 350 KB. A busy startup month can brush against that, so split by month if an upload gets rejected.

4. Categorize and reconcile

Everything arrives in For review uncategorized. Set up bank rules before you start accepting, not after, or you will hand-code the same Stripe payout forty times. Then reconcile each month against the closing balance printed on the Mercury statement. If a month reconciles to the penny, that month is done and you never have to look at it again.

My Mercury account moved off Evolve. Where did my history go?

Mercury migrated customers off Evolve Bank & Trust to its other partner banks, Choice Financial Group and Column N.A. Accounts that moved were effectively re-established, and the QuickBooks connection had to be set up again against the new account. A new connection starts at zero and reaches back 90 days at most, so pre-migration activity does not reappear on the other side.

If your Mercury account moved and QuickBooks suddenly shows a suspiciously short history, that is the explanation, and no amount of reconnecting will change it. The statements from before the move still exist in Mercury, and each one converts to a QBO file that imports exactly like a bank download.

How do I avoid duplicate Mercury transactions?

Load history behind the feed, never on top of it. Open the bank register in QuickBooks, find the oldest transaction the sync brought in, and end your converted file the day before it. Mercury gives the same advice in reverse for its Treasury connection: pick a start date later than the last posted transaction so the two sources cannot overlap.

QuickBooks does try to catch duplicates on a Web Connect import, but it matches on amount, date, and reference. A reworded merchant description or a posting date that shifted by a day will slip straight past it, and a duplicated payroll run is not a fun thing to find during a reconciliation. If you are importing a long stretch, it is cleaner to pause the integration, import, review, and switch the sync back on.

Can QuickBooks import a Mercury PDF statement directly?

No. QuickBooks Online accepts QBO, QFX, OFX, and CSV on the upload path, and QuickBooks Desktop Web Connect accepts only .qbo. A PDF is a document, not a data file, and no version of QuickBooks reads one. This is why the conversion step exists at all: it turns the record you have into the file QuickBooks will take.

Is Mercury a bank?

Mercury is a financial technology company, not a bank. Banking services are provided by its partner banks, Choice Financial Group and Column N.A., Members FDIC. In April 2026 Mercury received conditional approval from the OCC to establish Mercury Bank, N.A. For bookkeeping purposes none of this changes anything: Mercury statements are ordinary account statements with an opening balance, a closing balance, and a transaction list, and they convert to QBO like any other.

The startup catch-up case

This is the situation the whole article is really about. A company incorporates, opens Mercury, raises a seed round, and runs for fourteen months on founder intuition and a Google Sheet. Then a tax deadline or a diligence request arrives and someone has to produce a real set of books.

The bank feed gives you 90 days of that. The other eleven months are sitting in the statement archive, and the fastest route is to bulk download every statement from month one, convert them in a single pass, and import them month by month, reconciling as you go. While you are in there, the receipts and vendor bills behind that spend need to become data too, and it is worth pulling the line items off your vendor invoices at the same time so the expense side of the ledger is not just a list of merchant names. The full sequence is laid out in catch-up bookkeeping in QuickBooks.

Related reading

If the 90-day wall is the thing blocking you, why QuickBooks only imports 90 days of transactions explains the rule and what each connection type reaches. For the bank-side version of the same question, see how far back you can download bank transactions. Before uploading a heavy year, check how many transactions QuickBooks accepts at once. And if your company also runs a corporate card program, Brex statements convert to QBO the same way, with a 90-day sync limit Brex documents itself.