What Mercury data does Well pull into Bill.com?

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 Bill.com as bills via email-in inbox, with vendor, invoice number, amount, and due date populated by Bill.com's IVA OCR, with the Mercury event ID preserved on the entry for audit.

How often does Mercury data sync to Bill.com?

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 Bill.com 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 Bill.com?

Each Mercury debit is checked against the bills scheduled in Bill.com. Well scores on payee, amount, scheduled date, and currency; above 85% the bank line is auto-matched to the bill, the payment status updates in Bill.com, and the receipt is attached. Between 55% and 85% the candidate bills are surfaced for sign-off so you can confirm which bill the debit actually covers.

Does Well handle multi-currency records between Mercury and Bill.com?

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

How does Well prevent duplicates when posting Mercury records to Bill.com?

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

How does Well authenticate with Mercury and Bill.com?

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

Mercury to Bill.com

AvailableNative · MercuryNative · Bill.com

Connect Mercury to Bill.com with Well

A Mercury debit links to the matching context inside Well the moment it clears; the bill arrives in Bill.com reflecting the real state, including manual transfers reconciled retroactively.

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.

Bill.com

Target

The Bill.

Why this pair

Connect Mercury to Bill.com through Well so records flow without manual rework.

What Well does between Mercury and Bill.com

One-way: Mercury into Well into Bill.com
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

WeWork France

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

CounterpartyWeWork France
Booking date22 Apr 2026
Amount$1,284.00
CurrencyUSD
ReferenceINV-1024

Enrich

against your historical record graph

4 fields added

CounterpartyWeWork France
Tax idFR48818717128
Ledger account6132 · Co-working
Match1 candidate invoice

Confidence97%

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

Post

schedule as bills

Create a bill in Bill.com inbox

auto-posted

posted

TypeBill
VendorWeWork France
Amount$1,284.00
Ledger6132 · Co-working
Source docattached
Confidence97%

audit linkto Bill.com

Action in Bill.com

1 compatible with this trigger

Create a bill in Bill.com inbox

Match Mercury debits to Bill.com scheduled payments.

01Featured

Match debits to bills you have in flight

Each Mercury debit is checked against your bill records inside Well on payee, amount, scheduled date, and currency. Above the auto-link threshold the bank line is linked inside Well; AP sees the link in the document Well forwards to Bill.com, with the receipt attached for the next vendor audit.

Flag unauthorised vendor payments

If a Mercury debit appears for a vendor not on your approved list inside Well, the match is stopped and the workspace owner is paged. The debit sits on a review queue with the proposed new vendor alongside; once confirmed, Well treats the next debit from the same counterparty consistently before forwarding to Bill.com.

Close the loop on returned payments

When a Mercury payment is returned (insufficient funds, account closure, fraud claim), Well flags the reversal inside its own ledger, reopens the bill for rescheduling, and routes a notification to the AP owner so the reschedule decision in Bill.com has the original reason in context.

Confirm bills paid outside of Bill.com

Vendors sometimes get paid directly from Mercury without going through Bill.com (manual transfers, wire requests). Well detects these by counterparty plus amount and surfaces them in its own queue so AP can close the loop in Bill.com without recreating the payment.

12 signals and actions across Mercury and Bill.com

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.
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.
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.
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.
Trigger·Payment method
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.
Trigger·Transaction
When a Mercury card charge posts
Pulls from the Mercury transactions API. Captures debit card transactions with merchant and MCC code.
Trigger·Transaction
When a wire transfer arrives in Mercury
Pulls from the Mercury transactions API. Captures incoming wires with originator, reference, and value date.
Trigger·Transaction
When a wire transfer is sent from Mercury
Pulls from the Mercury transactions API. Tracks outbound wires with beneficiary detail and instruction.
Trigger·Transaction
Attach the source PDF to the Bill.com bill
Driven by Mercury transaction events. The forwarded PDF is the bill record itself in Bill.com's inbox.
Action·Document

Reference

Field mapping for Mercury → Bill.com

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

Transaction fields

5 fields flow from Mercury into Bill.com.

Mercury field	Label		Bill.com field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency	Currency	→	currency	Currency
transaction.posted_at	Posted date	→	process_date	Process date
transaction.bank_description	Description	→	memo	Memo
transaction.id	Transaction id	→	payment_id	Payment id

Connect Mercury and Bill.com 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 Bill.com inbox awaiting approval. The first batch of bank lines flows into the review queue alongside candidate scheduled payments; once you confirm the rule, Mercury debits auto-link above 85% confidence.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Bill.com
In Bill.com, open Settings > Developer > API keys and create a key paired with your developer ID. Paste the key into Well; Bill.com's discovery endpoints are reached over TLS 1.3 and the secret is never echoed in the UI.
- AuthConnect
- First sync~10 min

How Mercury and Bill.com 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 Bill.com 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 Bill.com inbox
Well forwards the extracted document to your Bill.com email-in address; Bill.com reads bills via email-in inbox, with vendor, invoice number, amount, and related records from it and you review and post. No write credential to Bill.com 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 Bill.com on Well

01What Mercury data does Well pull into Bill.com?: 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 Bill.com as bills via email-in inbox, with vendor, invoice number, amount, and due date populated by Bill.com's IVA OCR, with the Mercury event ID preserved on the entry for audit.
02How often does Mercury data sync to Bill.com?: 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 Bill.com 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 Bill.com?: Each Mercury debit is checked against the bills scheduled in Bill.com. Well scores on payee, amount, scheduled date, and currency; above 85% the bank line is auto-matched to the bill, the payment status updates in Bill.com, and the receipt is attached. Between 55% and 85% the candidate bills are surfaced for sign-off so you can confirm which bill the debit actually covers.
04Does Well handle multi-currency records between Mercury and Bill.com?: Mercury reports a single base currency; Well stores the value verbatim and tags the record so your Bill.com ledger can apply its own conversion rule at posting time. Exchange-rate fields are not synthesised, so the Bill.com entry carries the unchanged Mercury amount and the conversion is owned by the Bill.com accounting policy.
05How does Well prevent duplicates when posting Mercury records to Bill.com?: Mercury sends each event with a stable resource ID that Well tracks against the Bill.com ledger. Webhook replays (which Mercury can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Bill.com entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
06How does Well authenticate with Mercury and Bill.com?: 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 Bill.com email-in address once it clears the matching threshold; Bill.com creates the draft record from it and you confirm and post it. Well holds no write credential to Bill.com. Tokens are encrypted at rest and in transit under TLS 1.3. Mercury and Bill.com together cover multiple regions; Well's storage region is configured per workspace.