Match a payment to its invoice
Well reads Stripe transactions and invoices and reconciles each payment to the invoice it settles inside Well, then forwards the matched document to Bill.com's email-in address.



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.

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

The Bill.
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.




Well reads Stripe transactions and invoices and reconciles each payment to the invoice it settles inside Well, then forwards the matched document to Bill.com's email-in address.
Well resolves the company and people on a Stripe record and attaches them to the forwarded document, so Bill.com carries a verified business, not a bare name.
Records that resolve to the same company are treated as one business inside Well before the document is forwarded, so Bill.com does not accumulate near-duplicates.
The Stripe transaction Well reconciled stays linked to the document sent to Bill.com, so the trail traces each bill back to the payment it matched.

Pulls from the Stripe events feed. Detects the bank arrival of a Stripe payout to anchor the deposit.

Pulls from the Stripe events feed. Captures the finalised invoice before payment, with totals and due date.

Pulls from the Stripe events feed. Pulls the fee from the charge's balance transaction so net revenue is correct.

Pulls from the Stripe events feed. Pulls the paid invoice with its line items, customer, and applied tax.

Pulls from the Stripe events feed. Pulls new customer records with name, email, and tax id where set.

Pulls from the Stripe events feed. Captures the dispute with the contested charge and dispute reason.

Pulls from the Stripe events feed. Detects changes to customer name, billing address, or tax id.

Pulls from the Stripe events feed. Tracks new subscription records with cadence, amount, and customer.

Pulls from the Stripe events feed. Captures failed charges so you can chase the customer or retry.
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 |
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 |
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 | → | |||
| customer.tax_id | Tax id | → | tax_id | Tax id |
| customer.id | Customer id | → | vendor_id | Vendor id |

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.
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.

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.
Each one answers a question from the data this pair brings in. The required ones return nothing until a source like it is connected.
Needs a source like these
Know how many months of cash you have at your current burn, with both sides of the division shown.
See how long your cash lasts if a customer pays late, leaves, or you hire.
Know how much cash you hold right now, with the accounts counted and the ones left out both stated.
See a company's or household's spend by category, supplier and trend; not for savings: use Subscription spend.
Find the double charges and price rises in your bank debits, each with the dates and amounts your bank shows.
Get a prioritized list of who to chase for payment, with their contact info and a message already drafted.
Know if payroll is safe, and which vendor bills to push if it is not.
Rank your most valuable customers by lifetime value, over a year you name or their whole life.
See how much of your revenue rides on a few customers, and what a late or lost one does to your cash.
Everything you know about one company, in one view.
Find what payment settled an invoice, or catch every payment that never got one.
Find the bills with no paperwork attached, before an auditor does.
Know which invoices are missing a legal line before your customer or the tax office does.
Know what you spend in an average month over a window you can see, with the months that carried no spend counted.
See the monthly run-rate of live subscriptions, or an invoice average when no typed subscriptions are present.
See the settled month-end cash series and where the line goes from the last complete month.
See how the month moved from opening cash to closing cash, with whatever does not reconcile named as its own step.
See which suppliers owe you paperwork, in each of your files, for a month, a quarter or this week.
Put a name on every settled expense that still has no invoice.
Walk the whole month-end sweep in one prompt.
Drive the month-end close from open to sent to your accounting tool.
Work through your open accounting items by category.
Close the category gaps behind your spend before you close a month.
The board numbers in one pass, each with its scope and its window stated.
See what you paid a supplier, how its price moved, and get the negotiation email drafted.
See what each scheduled supplier costs a month and a year, how it moved, and where your workspaces can save.
Act on a subscription you name or pick by number from a list: cancel, renegotiate or contest a double debit.
See what you spent on one category, such as groceries, this month and how that compares to a usual month.
See who cancelled, which payments failed and what was refunded, read live from Stripe, Paddle or Lago.
See what in a month has not reached the ledger, and which pile each item sits in.
Compare your bank with your books, list the gaps, and re-run what missed rows.
Answers better with these connected
See which customers still owe you money: the unpaid and overdue invoices, how late each is, and the total.
See what you owe and when, ordered by due date with a running total.
See how much of your cash and receivables sit outside your reporting currency.
See exactly which agents would run, before any of them does.
Turn mixed currencies into one number you can actually audit.
See what you owe your suppliers, and how long each bill has been past due.
The measures you name, arranged on one board that stores the question rather than the answer.
See how much each customer billed in a period, ranked by revenue, with the part you could not place named.
See what each supplier invoiced you over a year, ranked, with unplaced invoices counted.
Claim a refund or a compensation with the evidence in hand, and know what to say when you call.
See the VAT position your data suggests for a quarter, and which invoices to fix first.
Find money owed back to you: refunds, credit notes, VAT credits, double debits, then unpaid customer invoices.
Read a month of payslips, or each of several months, and state, per person, gross pay plus the employee deductions and the employer charges the payslip printed, then list the payroll related bills paid from the bank that no payslip carries.
For each supplier that looks like a freelancer, read the purchase invoices, the payment rail and any contract Well holds, and state the facts a requalification question turns on, next to the papers your country expects you to keep.
Uses them when they are there
Connects and checks them
See what is connected, what is syncing, and what is missing.
Connect your AI apps and your tools, then see your business as one context graph.
Get the bank feed in, and confirm it is really live.
The companies you deal with that carry no tax identifier, listed before year end.
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. Anything Well holds between Stripe and Bill.com is encrypted at rest and handled in line with GDPR.
Read Stripe records
Scoped to charges, refunds, payouts, customers, and related records. No access to anything else in your Stripe account.
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.
Modify or delete Stripe records
Not granted. Stripe is read-only on Well's side; the source of truth never moves.
Read other workspaces' data
Not granted. A session resolves only to the workspaces your account belongs to, and Well checks that membership before it returns any record.


Connect both sides. Stripe purchases queue cleanly in Bill.com.
Other ways to connect Stripe or Bill.com through Well.

Stripe
See the Stripe connector

Bill.com
See the Bill.com connector


Stripe → Pennylane
Match every Stripe charge and payout inside Well, then forwa…


Stripe → Qonto
Reconcile Stripe payouts against Qonto bank deposits. Well d…


Square → Bill.com
Reconcile Square supplier-side activity inside Well, forward…

Melio
See the Melio connector

PayPal
See the PayPal connector

Razorpay
See the Razorpay connector