What Stripe data does Well pull into Bill.com?

Stripe streams charges, refunds, payouts, customers, disputes, and subscription events 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 Stripe event ID preserved on the entry for audit.

How does Well match Stripe records to entries in Bill.com?

Well scores every candidate match between Stripe records and existing Bill.com entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Bill.com updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.

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

Stripe carries the original transaction currency on every record and Bill.com natively ledgers in multiple currencies. Well preserves the original amount, applies your Bill.com chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Bill.com, so the Bill.com entry you post keeps both sides of the trade.

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

Stripe sends each event with a stable resource ID that Well tracks against the Bill.com ledger. Webhook replays (which Stripe 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.

What happens if I disconnect Stripe or Bill.com?

Disconnecting Stripe stops the flow at the source. Well asks the Stripe MCP server to revoke the access token; Stripe returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Bill.com is Bill.com'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 Stripe and Bill.com?

Stripe'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. Stripe and Bill.com together cover multiple regions; Well's storage region is configured per workspace.

Stripe to Bill.com

AvailableNative · StripeNative · Bill.com

Connect Stripe to Bill.com with Well

Forward Stripe charges, payouts, and refunds as documents into Bill.com's bill inbox, with vendor matches resolved inside Well before the next payment run.

Connect both toolsView all integrations

Stripe

Source

The Stripe integration connects your payment infrastructure to Well via MCP, pulling charges, invoices, subscriptions, refunds, and payout data into your workspace automatically.

Bill.com

Target

The Bill.

Why this pair

Stripe handles customer revenue; Bill.

com handles vendor payments. Each side runs on different rails and rarely sees the other. Connecting Stripe to Bill. com through Well surfaces Stripe payout activity alongside the Bill. com scheduled-payment queue, so treasury sees revenue collected and bills due in the same view. Stripe pushes events to Well over its MCP server; Bill.com receives the forwarded PDF via email-in and creates the bill for your configured approval workflow.

What Well does between Stripe and Bill.com

One-way: Stripe into Well into Bill.com
Sync mode: Real-time MCP push
Events arrive in seconds

Trigger from Stripe

14 events · pick one

Well engine·recipe·When a Stripe charge succeeds

Source

from payment · live webhook

Quantica Energy

via Stripe

Charge

When a Stripe charge succeeds

ch_1q5nk · 22 Apr 2026€1,284.00

Extract

6 fields read from Stripe

6 fields read

CustomerQuantica Energy
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordQuantica Energy
Domainquantica.energy
Tax idES45612378900
Sales journalVE · 2026

Confidence97%

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

Post

schedule as bills

Create a bill in Bill.com inbox

auto-posted

posted

TypeBill
VendorQuantica Energy
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Bill.com

Action in Bill.com

2 compatible with this trigger

Create a bill in Bill.com inboxResolve a Bill.com vendor from the bill

Bridge Stripe payouts to Bill.com reimbursements.

01Featured

Bridge merchant payouts to vendor reimbursements

Stripe payout batches are joined to the reimbursement records inside Well by date and total. The per-line breakdown becomes individual documents forwarded to Bill.com, so a payout that covers 30 reimbursements arrives as 30 entries you can confirm one by one, not one lump sum to chase down later.

Detect failed disbursements

A failed Stripe disbursement triggers a flag inside Well: the linked vendor payment is marked needs reschedule, the Stripe failure code is attached, and the workspace owner is notified with the candidate next-payment date based on your standard reschedule policy.

Tie chargebacks to the originating vendor bill

Chargebacks landing in Stripe are traced back to the originating vendor bill inside Well by reference and amount. The chargeback context is forwarded to Bill.com on the affected document, so AP can decide whether to reschedule a corrected payment or write off the loss with the original Stripe reason in hand.

Settle expense reimbursements weekly

Approved expense reimbursements are batched inside Well into a weekly Stripe disbursement run, paid in a single ACH window, and matched on settlement. The per-claim audit trail stays intact inside Well and on the matched documents forwarded to Bill.com.

18 signals and actions across Stripe and Bill.com

When a Stripe payout lands in your bank
Pulls from the Stripe events feed. Detects the bank arrival of a Stripe payout to anchor the deposit.
Trigger·Transaction
When a Stripe invoice is finalised
Pulls from the Stripe events feed. Captures the finalised invoice before payment, with totals and due date.
Trigger·Invoice
When the processing fee on a Stripe charge is recorded
Pulls from the Stripe events feed. Pulls the fee from the charge's balance transaction so net revenue is correct.
Trigger·Transaction
When a Stripe invoice is marked paid
Pulls from the Stripe events feed. Pulls the paid invoice with its line items, customer, and applied tax.
Trigger·Invoice
When a Stripe customer is created
Pulls from the Stripe events feed. Pulls new customer records with name, email, and tax id where set.
Trigger·Company
When a Stripe dispute is opened
Pulls from the Stripe events feed. Captures the dispute with the contested charge and dispute reason.
Trigger·Transaction
When a Stripe customer is updated
Pulls from the Stripe events feed. Detects changes to customer name, billing address, or tax id.
Trigger·Company
When a Stripe subscription starts
Pulls from the Stripe events feed. Tracks new subscription records with cadence, amount, and customer.
Trigger·Invoice
When a Stripe charge fails
Pulls from the Stripe events feed. Captures failed charges so you can chase the customer or retry.
Trigger·Transaction

Reference

Field mapping for Stripe → Bill.com

15 fields across 3 record types, open to see the full table.

Transaction fields

5 fields flow from Stripe into Bill.com.

Stripe field	Label		Bill.com field	Label
charge.amount	Charge amount	→	amount	Amount
charge.currency	Currency	→	currency	Currency
charge.created	Charge date	→	process_date	Process date
charge.description	Description	→	memo	Memo
charge.id	Charge id	→	payment_id	Payment id

Invoice fields

6 fields flow from Stripe into Bill.com.

Stripe field	Label		Bill.com field	Label
invoice.currency	Currency	→	currency	Currency
invoice.number	Invoice number	→	invoice_number	Invoice number
invoice.issue_date	Issue date	→	invoice_date	Invoice date
invoice.due_date	Due date	→	due_date	Due date
invoice.subtotal	Subtotal	→	subtotal	Subtotal
invoice.customer	Customer reference	→	external_id	External id

Company fields

4 fields flow from Stripe into Bill.com.

Stripe field	Label		Bill.com field	Label
customer.name	Customer name	→	vendor_name	Vendor name
customer.email	Email	→	email	Email
customer.tax_id	Tax id	→	tax_id	Tax id
customer.id	Customer id	→	vendor_id	Vendor id

Connect Stripe and Bill.com in three steps.

1
Connect Stripe
Click Connect with Stripe; Stripe's MCP server handles authorisation. Stripe's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
2
Map your accounts
Well discovers Stripe's charges, refunds, payouts, customers, disputes, and subscription events and the the Bill.com inbox awaiting approval. Each payout is paired to its scheduled vendor payment by date and total; failed transfers reverse the linked payment automatically so the schedule self-corrects.
- 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 Stripe and Bill.com stay secure with Well

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

MCP server authStorage region per workspaceGDPR-aligned

Scopes Well requestsmcp.stripe.com

Read Stripe records
Scoped to charges, refunds, payouts, customers, and related records. No access to anything else in your Stripe 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 Stripe records
Not granted. Stripe 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 Stripe’s admin panel.

Frequently asked questions about Stripe and Bill.com on Well

01What Stripe data does Well pull into Bill.com?: Stripe streams charges, refunds, payouts, customers, disputes, and subscription events 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 Stripe event ID preserved on the entry for audit.
02How does Well match Stripe records to entries in Bill.com?: Well scores every candidate match between Stripe records and existing Bill.com entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Bill.com updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
03Does Well handle multi-currency records between Stripe and Bill.com?: Stripe carries the original transaction currency on every record and Bill.com natively ledgers in multiple currencies. Well preserves the original amount, applies your Bill.com chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Bill.com, so the Bill.com entry you post keeps both sides of the trade.
04How does Well prevent duplicates when posting Stripe records to Bill.com?: Stripe sends each event with a stable resource ID that Well tracks against the Bill.com ledger. Webhook replays (which Stripe 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.
05What happens if I disconnect Stripe or Bill.com?: Disconnecting Stripe stops the flow at the source. Well asks the Stripe MCP server to revoke the access token; Stripe returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Bill.com is Bill.com'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 Stripe and Bill.com?: Stripe'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. Stripe and Bill.com together cover multiple regions; Well's storage region is configured per workspace.