What Mercury data does Well pull into QuickBooks?

Mercury streams transactions, wires, ACH transfers, card payments, and counterparty records to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to QuickBooks as bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks, with the Mercury event ID preserved on the entry for audit.

How often does Mercury data sync to QuickBooks?

Mercury pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches QuickBooks within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

Will every Mercury record post to QuickBooks automatically?

Not always. Within seconds of Mercury firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your QuickBooks email-in address and QuickBooks drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.

How does Well prevent duplicates when posting Mercury records to QuickBooks?

Mercury sends each event with a stable resource ID that Well tracks against the QuickBooks ledger. Webhook replays (which Mercury can issue for delivery retries) are recognised by ID and either skipped or used to update the existing QuickBooks entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.

Can I customise which Mercury fields are sent to QuickBooks?

The default mapping covers every Mercury field your QuickBooks chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields QuickBooks does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in QuickBooks is left exactly as it stands.

How does Well authenticate with Mercury and QuickBooks?

Mercury's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your QuickBooks email-in address once it clears the matching threshold; QuickBooks creates the draft record from it and you confirm and post it. Well holds no write credential to QuickBooks. Tokens are encrypted at rest and in transit under TLS 1.3. Mercury and QuickBooks together cover multiple regions; Well's storage region is configured per workspace.

Mercury to QuickBooks

AvailableNative · MercuryNative · QuickBooks

Connect Mercury to QuickBooks with Well

Mercury statement lines collapse onto their counterparties inside Well; resulting documents arrive at QuickBooks as drafts pre-filled by QuickBooks's own OCR.

Connect both toolsView all integrations

Mercury

Source

The Mercury integration connects your startup banking to Well via MCP, pulling transactions, balances, and counterparty data into your workspace.

QuickBooks

Target

The QuickBooks connection delivers documents into QuickBooks Online through its @qbodocs.

Clean entries, not bank lines

Mercury runs on US banking rails in USD; QuickBooks Online accepts emailed PDFs at @qbodocs.

com and creates bills or receipts from them. Connecting Mercury to QuickBooks through Well matches each Mercury transaction inside its own ledger with the vendor resolved and the source reference preserved, then forwards the matched document to QuickBooks' email-in. QuickBooks creates a bill or receipt with vendor, date, and amount populated; your team confirms in the For Review tab and reconciles the bank line.

What Well does between Mercury and QuickBooks

One-way: Mercury into Well into QuickBooks
Sync mode: Real-time MCP push
Events arrive in seconds

Trigger from Mercury

6 events · pick one

Well engine·recipe·When a new transaction posts on your Mercury account

Source

from bank line · live webhook

Twilio Ireland

via Mercury

Transaction

When a new transaction posts on your Mercury account

INV-1024 · 22 Apr 2026$1,284.00

Extract

5 fields read from Mercury

5 fields read

CounterpartyTwilio Ireland
Booking date22 Apr 2026
Amount$1,284.00
CurrencyUSD
ReferenceINV-1024

Enrich

against your historical record graph

4 fields added

CounterpartyTwilio Ireland
Tax idIE3251428LH
Ledger account6156 · Communications
Match1 candidate invoice

Confidence97%

<55% refused55–85% review≥85% auto-posts

Post

post as bills and receipts

Route the record to the For Review tab

auto-posted

posted

TypeReview
VendorTwilio Ireland
Amount$1,284.00
Ledger6156 · Communications
Source docattached
Confidence97%

audit linkto QuickBooks

Action in QuickBooks

1 compatible with this trigger

Route the record to the For Review tab

Reconcile Mercury transactions to QuickBooks ledger lines.

01Featured

Forward a resolved Mercury payment to QuickBooks

Well reads each Mercury transaction, resolves the vendor, and forwards a document to your QuickBooks email-in address with the company and amount already attached.

Turn a bank descriptor into a named vendor

Well matches the Mercury counterparty to its company record so the payment reaches QuickBooks naming a real supplier.

Keep the Mercury source on the entry

The original Mercury transaction stays linked to the document sent to QuickBooks, so every entry traces back to the cleared payment.

12 signals and actions across Mercury and QuickBooks

When a wire transfer arrives in Mercury
Pulls from the Mercury transactions API. Captures incoming wires with originator, reference, and value date. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a new transaction posts on your Mercury account
Pulls from the Mercury transactions API. Triggers on every debit or credit posting in a Mercury account. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a Mercury card charge posts
Pulls from the Mercury transactions API. Captures debit card transactions with merchant and MCC code. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a check is deposited to Mercury
Pulls from the Mercury transactions API. Tracks check deposits with the payer, amount, and clearing date. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When an ACH payment clears in Mercury
Pulls from the Mercury transactions API. Picks up cleared ACH credits and debits with the company id reference. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a wire transfer is sent from Mercury
Pulls from the Mercury transactions API. Tracks outbound wires with beneficiary detail and instruction. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a Mercury account's payment details are read
Pulls from the Mercury transactions API. Resolves the account and routing numbers from the Mercury account so a payment instrument can be matched. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Payment method
When a Mercury account is read
Pulls from the Mercury transactions API. Pulls each Mercury account the workspace holds with its balance, currency, and routing details. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Account
Create a bill or receipt in QuickBooks
Driven by Mercury transaction events. Well forwards the PDF to your @qbodocs.com address; QuickBooks creates a bill or receipt with vendor, date, and amount populated. QuickBooks picks the record type per document.
Action·Invoice

Reference

Field mapping for Mercury → QuickBooks

5 fields across 1 record type, open to see the full table.

Transaction fields

5 fields flow from Mercury into QuickBooks.

Mercury field	Label		QuickBooks field	Label
transaction.amount	Amount	→	Amount	Amount
transaction.currency	Currency	→	CurrencyRef	Currency
transaction.posted_at	Posted date	→	TxnDate	Transaction date
transaction.bank_description	Description	→	Memo	Memo
transaction.id	Transaction id	→	PrivateNote	Source id

Connect Mercury and QuickBooks in three steps.

1
Connect Mercury
Click Connect with Mercury; Mercury's MCP server handles authorisation through Dynamic Client Registration. Mercury's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
- AuthConnect
2
Map your accounts
Well discovers Mercury's transactions, wires, ACH transfers, card payments, and counterparty records and the the QuickBooks For Review inbox. Counterparty proximity, amount, date, and reference drive the match score; lines above 85% post automatically and the rest queue for a one-click sign-off.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect QuickBooks
Click Connect with QuickBooks; you approve the connection inside QuickBooks Online and authorise read-only discovery of your existing records so Well can match against them when forwarding documents. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your QuickBooks Online.
- AuthOAuth 2.0
- First syncup to an hour

How Mercury and QuickBooks stay secure with Well

Well connects to Mercury through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Mercury secret; the server refreshes its own tokens on each session. Well's storage region is configured per workspace regardless of where Mercury and QuickBooks host theirs.

MCP server authStorage region per workspaceGDPR-aligned

Scopes Well requestsmcp.mercury.com/mcp

Read Mercury records
Scoped to transactions, wires, ACH transfers, card payments, and related records. No access to anything else in your Mercury account.
granted
Deliver documents to your QuickBooks inbox
Well forwards the extracted document to your QuickBooks email-in address; QuickBooks reads bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks from it and you review and post. No write credential to QuickBooks is requested.
granted
Modify or delete Mercury records
Not granted. Mercury is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
refused

Disconnect any time from Well settings or Mercury’s admin panel.

Frequently asked questions about Mercury and QuickBooks on Well

01What Mercury data does Well pull into QuickBooks?: Mercury streams transactions, wires, ACH transfers, card payments, and counterparty records to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to QuickBooks as bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks, with the Mercury event ID preserved on the entry for audit.
02How often does Mercury data sync to QuickBooks?: Mercury pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches QuickBooks within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
03Will every Mercury record post to QuickBooks automatically?: Not always. Within seconds of Mercury firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your QuickBooks email-in address and QuickBooks drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.
04How does Well prevent duplicates when posting Mercury records to QuickBooks?: Mercury sends each event with a stable resource ID that Well tracks against the QuickBooks ledger. Webhook replays (which Mercury can issue for delivery retries) are recognised by ID and either skipped or used to update the existing QuickBooks entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
05Can I customise which Mercury fields are sent to QuickBooks?: The default mapping covers every Mercury field your QuickBooks chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields QuickBooks does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in QuickBooks is left exactly as it stands.
06How does Well authenticate with Mercury and QuickBooks?: Mercury's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your QuickBooks email-in address once it clears the matching threshold; QuickBooks creates the draft record from it and you confirm and post it. Well holds no write credential to QuickBooks. Tokens are encrypted at rest and in transit under TLS 1.3. Mercury and QuickBooks together cover multiple regions; Well's storage region is configured per workspace.