What Mercury data does Well pull into Xero?

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 Xero as draft bills via email-in, with contact, dates, totals, line items, and tax type extracted by Hubdoc, with the Mercury event ID preserved on the entry for audit.

How often does Mercury data sync to Xero?

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 Xero within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

How does Well match Mercury records to entries in Xero?

Mercury transactions are scored against open Xero entries on counterparty, amount, date proximity, and reference; above 85% the bank line reconciles automatically and posts to the right account, between 55% and 85% the candidate Xero entries are surfaced for sign-off, below 55% the line stays open and is added to a review queue.

Does Well handle multi-currency records between Mercury and Xero?

Mercury reports a single base currency; Well stores the value verbatim and tags the record so your Xero ledger can apply its own conversion rule at posting time. Exchange-rate fields are not synthesised, so the Xero entry carries the unchanged Mercury amount and the conversion is owned by the Xero accounting policy.

What happens if I disconnect Mercury or Xero?

Disconnecting Mercury stops the flow at the source. Well asks the Mercury MCP server to revoke the access token; Mercury returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Xero is Xero's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.

How does Well authenticate with Mercury and Xero?

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 Xero email-in address once it clears the matching threshold; Xero creates the draft record from it and you confirm and post it. Well holds no write credential to Xero. Tokens are encrypted at rest and in transit under TLS 1.3. Mercury and Xero together cover multiple regions; Well's storage region is configured per workspace.

Mercury to Xero

AvailableNative · MercuryNative · Xero

Connect Mercury to Xero with Well

Stop reconciling by hand: Mercury bank lines reach Xero as drafts with the counterparty resolved and the receipt attached. You confirm and post in seconds.

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.

Xero

Target

The Xero integration connects Well to your accounting platform for bidirectional data flow.

Why this pair

Mercury runs on US banking rails in USD; Xero closes books in GBP, AUD, NZD, or EUR depending on where the entity is registered.

Connecting them through Well handles the currency conversion, the counterparty resolution, and the matching inside its own ledger. Every Mercury transaction is reconciled against your invoices with the FX rate of the booking date and the original Mercury reference preserved; the matched document is then forwarded to Xero's email-in. Hubdoc reads the PDF and creates a draft bill with contact, dates, totals, and tax type extracted.

What Well does between Mercury and Xero

One-way: Mercury into Well into Xero
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

Stripe Payments Europe

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

CounterpartyStripe Payments Europe
Booking date22 Apr 2026
Amount$1,284.00
CurrencyUSD
ReferenceINV-1024

Enrich

against your historical record graph

4 fields added

CounterpartyStripe Payments Europe
Tax idIE3206488LH
Ledger account627 · Bank fees
Match1 candidate invoice

Confidence97%

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

Post

post as draft bills

Create a draft bill in Xero

auto-posted

posted

TypeBill
VendorStripe Payments Europe
Amount$1,284.00
Ledger627 · Bank fees
Source docattached
Confidence97%

audit linkto Xero

Action in Xero

1 compatible with this trigger

Create a draft bill in Xero

Reconcile Mercury transactions to Xero ledger lines.

01Featured

Match a Mercury payment to a Xero invoice

Well reads the invoices in Xero and the transactions in Mercury and pairs a payment with the invoice it settles before forwarding the document to Xero's email-in address.

Read the Xero ledger before forwarding

Well reads Xero's own ledger and invoice records so the document it forwards reflects what Xero already holds for the counterparty.

Resolve the counterparty across both

Well ties the Mercury company and payment means to the matching Xero contact, so a supplier reads the same on both sides.

Keep the bank line on the entry

The Mercury transaction stays linked to the document forwarded to Xero, so the entry traces back to the cleared payment.

12 signals and actions across Mercury and Xero

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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Account
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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a wire transfer arrives in Mercury
Pulls from the Mercury transactions API. Captures incoming wires with originator, reference, and value date. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
Create a draft bill in Xero
Driven by Mercury transaction events. Well forwards the PDF to your Xero email-in address; Xero creates a draft bill via Hubdoc with contact, dates, totals, line items, and tax type pre-filled. You review and post.
Action·Invoice

Reference

Field mapping for Mercury → Xero

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

Transaction fields

5 fields flow from Mercury into Xero.

Mercury field	Label		Xero field	Label
transaction.amount	Amount	→	Total	Amount
transaction.currency	Currency	→	CurrencyCode	Currency
transaction.posted_at	Posted date	→	Date	Transaction date
transaction.bank_description	Description	→	Reference	Reference
transaction.id	Transaction id	→	BankTransactionID	Bank line id

Connect Mercury and Xero 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 Xero draft bills queue populated by Hubdoc. 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 Xero
Click Connect with Xero; Well's OAuth proxy handles Xero authorisation through Dynamic Client Registration. Xero's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First syncup to an hour

How Mercury and Xero 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 Xero 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 Xero inbox
Well forwards the extracted document to your Xero email-in address; Xero reads draft bills via email-in, with contact, dates, totals, and related records from it and you review and post. No write credential to Xero 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 Xero on Well

01What Mercury data does Well pull into Xero?: 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 Xero as draft bills via email-in, with contact, dates, totals, line items, and tax type extracted by Hubdoc, with the Mercury event ID preserved on the entry for audit.
02How often does Mercury data sync to Xero?: 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 Xero within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
03How does Well match Mercury records to entries in Xero?: Mercury transactions are scored against open Xero entries on counterparty, amount, date proximity, and reference; above 85% the bank line reconciles automatically and posts to the right account, between 55% and 85% the candidate Xero entries are surfaced for sign-off, below 55% the line stays open and is added to a review queue.
04Does Well handle multi-currency records between Mercury and Xero?: Mercury reports a single base currency; Well stores the value verbatim and tags the record so your Xero ledger can apply its own conversion rule at posting time. Exchange-rate fields are not synthesised, so the Xero entry carries the unchanged Mercury amount and the conversion is owned by the Xero accounting policy.
05What happens if I disconnect Mercury or Xero?: Disconnecting Mercury stops the flow at the source. Well asks the Mercury MCP server to revoke the access token; Mercury returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Xero is Xero's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.
06How does Well authenticate with Mercury and Xero?: 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 Xero email-in address once it clears the matching threshold; Xero creates the draft record from it and you confirm and post it. Well holds no write credential to Xero. Tokens are encrypted at rest and in transit under TLS 1.3. Mercury and Xero together cover multiple regions; Well's storage region is configured per workspace.