PayPal to Bill.comPair PayPal disbursements with Bill.com bills; failed transfers surface inside Well so the next manual schedule reflects the real state.
The PayPal integration connects your payment account to Well via MCP, importing transactions, fees, settlements, and refund data.
The Bill.
A PayPal transaction lands as an amount and a counterparty, with little to tell a real supplier from a one-off or a duplicate.
Well reads the invoices, transactions, and companies behind your PayPal activity, resolves each counterparty to a company record, and forwards the matched document to your Bill. com email-in address. The bill that arrives for approval already carries a resolved vendor and its context, so your team is not keying the same supplier twice or approving a payment to a name it cannot place. Well reads from PayPal and forwards the matched document; approval stays in Bill. com with your team.
Well matches the counterparty on a PayPal transaction to a company record and forwards the document to your Bill.com email-in address, so approvers see a resolved supplier rather than a bare name.
Two PayPal payees that share one web domain resolve to the same company inside Well before the document is forwarded, so Bill.com does not accumulate near-duplicate vendors for one business.
Each forwarded document keeps the PayPal invoice and transaction detail Well read, giving the approver the amount and history behind the bill without leaving Bill.com to look it up.
The PayPal record Well resolved stays linked to the document forwarded to your Bill.com email-in address, so the audit trail traces each bill back to the transaction it came from.
Pulls from PayPal transaction events. Captures completed PayPal payments with buyer, amount, and order id.
Pulls from PayPal transaction events. Recognises a first-time buyer from the capture and prepares a customer record.
Pulls from PayPal transaction events. Surfaces denied captures with the denial reason for follow-up.
Pulls from PayPal transaction events. Flags the contested transaction and preserves the dispute trail.
Pulls from PayPal transaction events. Tracks settlement batches with the covered captures and processing fees.
Pulls from PayPal transaction events. Detects pending captures and waits for the resolution before posting.
Pulls from PayPal transaction events. Pulls the merchant fee out of the capture so net revenue is correct.
Pulls from PayPal transaction events. Pulls the FX rate and conversion fee from the capture.
Pulls from PayPal transaction events. Picks up the moment a buyer finishes checkout, before the bank settlement.
4 fields flow from PayPal into Bill.com.
| PayPal field | Label | Bill.com field | Label | |
|---|---|---|---|---|
| capture.amount.currency_code | Currency | currency | Currency | |
| capture.create_time | Capture date | process_date | Process date | |
| capture.id | Capture id | payment_id | Payment id | |
| capture.seller_receivable.fee | PayPal fee | amount | Amount |
3 fields flow from PayPal into Bill.com.
| PayPal field | Label | Bill.com field | Label | |
|---|---|---|---|---|
| invoice.detail.invoice_number | Invoice number | invoice_number | Invoice number | |
| invoice.detail.invoice_date | Issue date | invoice_date | Invoice date | |
| invoice.amount.currency_code | Currency | currency | Currency |
1Click Connect with PayPal; the PayPal MCP server registers a Well client automatically. PayPal's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
Well discovers PayPal's completed payments, refunds, disputes, holds, and currency-conversion 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.
3In 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.
Well connects to PayPal through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived PayPal secret; the server refreshes its own tokens on each session. Well's storage region is configured per workspace regardless of where PayPal and Bill.com host theirs.
Read PayPal records
Scoped to completed payments, refunds, disputes, holds, and related records. No access to anything else in your PayPal 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 PayPal records
Not granted. PayPal is read-only on Well's side; the source of truth never moves.
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
Link both tools to Well so each PayPal bill arrives at Bill.com with its vendor already resolved.
Other ways to connect PayPal or Bill.com through Well.
PayPal
See the PayPal connector
Bill.com
See the Bill.com connector
PayPal → Pennylane
Match PayPal sales and fees inside Well, then forward matche…
PayPal → Xero
Match PayPal sales, refunds, and disputes inside Well with t…
Square → Bill.com
Reconcile Square supplier-side activity inside Well, forward…
Melio
See the Melio connector
Razorpay
See the Razorpay connector
Square
See the Square connector
