What Mercury data does Well pull into Freshbooks?

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 Freshbooks as expenses (or bills on the Select plan) via email-in, with merchant, total, and tax populated, with the Mercury event ID preserved on the entry for audit.

What happens to historical Mercury data when I first connect to Freshbooks?

Mercury exposes the last three years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Freshbooks ledger, and re-running the backfill is safe because Well tracks the Mercury record IDs and updates existing Freshbooks entries instead of duplicating them.

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

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

What happens if a Mercury record fails to post to Freshbooks?

When a record fails to post to Freshbooks (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Mercury record. Nothing silently drops.

What happens if I disconnect Mercury or Freshbooks?

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 Freshbooks is Freshbooks'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 Freshbooks?

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

Mercury to Freshbooks

AvailableNative · MercuryNative · Freshbooks

Connect Mercury to FreshBooks with Well

Stop reconciling by hand: Mercury bank lines reach Freshbooks 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.

Freshbooks

Target

The FreshBooks connection delivers extracted documents into FreshBooks through its email-in address.

Why this pair

Mercury runs on US banking rails in USD; FreshBooks handles SMB books with customer invoices, expenses, and bank reconciliation.

Connecting Mercury to FreshBooks through Well matches each Mercury transaction inside its own ledger and forwards the matched document as the matching FreshBooks document with the vendor resolved, the bank line reconciled against the corresponding bill, and the source reference preserved on the entry. Mercury's MCP server pushes transaction events to Well; FreshBooks creates the matching record from the PDF Well forwards, with the source reference and category preserved.

What Well does between Mercury and Freshbooks

One-way: Mercury into Well into Freshbooks
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 expenses and bills

Create an expense in FreshBooks

auto-posted

posted

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

audit linkto Freshbooks

Action in Freshbooks

1 compatible with this trigger

Create an expense in FreshBooks

Reconcile Mercury transactions to Freshbooks ledger lines.

01Featured

Reconcile transactions to existing invoices

Every Mercury debit is scored against your open invoices inside Well on counterparty, amount, scheduled date, and currency. Above the auto-link threshold the bank line is linked to the right invoice; the matched document is then forwarded to Freshbooks's email-in inbox with the receipt attached for your one-click confirmation.

Reconcile deposits to expected receivables

Mercury deposits are checked against your open sales invoices inside Well. The match runs on amount and date proximity inside the same customer, so a partial payment or an aggregated weekly deposit still resolves to the right invoices before the matched document reaches Freshbooks.

Tag inter-company transfers

Transfers between your own Mercury accounts and other entities you own are detected by counterparty and reciprocal-amount checks inside Well. The pair is tagged as inter-company so the matched documents reach Freshbooks with the inter-company label rather than as two separate ordinary transactions.

Capture FX impact on cross-border transfers

Cross-currency Mercury transfers carry the source and converted amounts; Well records the FX rate at the timestamp of settlement and includes it in the document forwarded to Freshbooks, so the FX delta is visible alongside the operational entry when you review the draft.

12 signals and actions across Mercury and Freshbooks

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 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 wire transfer is sent from Mercury
Pulls from the Mercury transactions API. Tracks outbound wires with beneficiary detail and instruction.
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 wire transfer arrives in Mercury
Pulls from the Mercury transactions API. Captures incoming wires with originator, reference, and value 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 a Mercury card charge posts
Pulls from the Mercury transactions API. Captures debit card transactions with merchant and MCC code.
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.
Trigger·Transaction
Resolve a FreshBooks merchant from the receipt
Driven by Mercury transaction events. FreshBooks reads the merchant name off the forwarded receipt and matches it on the expense (or bill). You confirm or correct the merchant on first sight.
Action·Company

Reference

Field mapping for Mercury → Freshbooks

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

Transaction fields

5 fields flow from Mercury into Freshbooks.

Mercury field	Label		Freshbooks field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency	Currency	→	currency_code	Currency
transaction.posted_at	Posted date	→	date	Transaction date
transaction.bank_description	Description	→	note	Description
transaction.id	Transaction id	→	external_id	External id

Connect Mercury and Freshbooks 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 FreshBooks expense or bill queue. 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 Freshbooks
Click Connect with FreshBooks; FreshBooks asks for the account to authorise and returns a refresh token 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 FreshBooks.
- AuthConnect
- First syncup to an hour

How Mercury and Freshbooks 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 Freshbooks 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 Freshbooks inbox
Well forwards the extracted document to your Freshbooks email-in address; Freshbooks reads expenses (or bills on the Select plan) via email-in, with merchant, total, and tax populated from it and you review and post. No write credential to Freshbooks 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 Freshbooks on Well

01What Mercury data does Well pull into Freshbooks?: 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 Freshbooks as expenses (or bills on the Select plan) via email-in, with merchant, total, and tax populated, with the Mercury event ID preserved on the entry for audit.
02What happens to historical Mercury data when I first connect to Freshbooks?: Mercury exposes the last three years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Freshbooks ledger, and re-running the backfill is safe because Well tracks the Mercury record IDs and updates existing Freshbooks entries instead of duplicating them.
03Does Well handle multi-currency records between Mercury and Freshbooks?: Mercury reports a single base currency; Well stores the value verbatim and tags the record so your Freshbooks ledger can apply its own conversion rule at posting time. Exchange-rate fields are not synthesised, so the Freshbooks entry carries the unchanged Mercury amount and the conversion is owned by the Freshbooks accounting policy.
04What happens if a Mercury record fails to post to Freshbooks?: When a record fails to post to Freshbooks (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Mercury record. Nothing silently drops.
05What happens if I disconnect Mercury or Freshbooks?: 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 Freshbooks is Freshbooks'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 Freshbooks?: 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 Freshbooks email-in address once it clears the matching threshold; Freshbooks creates the draft record from it and you confirm and post it. Well holds no write credential to Freshbooks. Tokens are encrypted at rest and in transit under TLS 1.3. Mercury and Freshbooks together cover multiple regions; Well's storage region is configured per workspace.