What PayPal data does Well pull into Bill.com?

PayPal streams completed payments, refunds, disputes, holds, and currency-conversion 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 PayPal event ID preserved on the entry for audit.

Will every PayPal record post to Bill.com automatically?

Not always. Within seconds of PayPal firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Bill.com email-in address and Bill.com drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.

What happens to historical PayPal data when I first connect to Bill.com?

PayPal exposes the last full year 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 Bill.com ledger, and re-running the backfill is safe because Well tracks the PayPal record IDs and updates existing Bill.com entries instead of duplicating them.

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

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

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

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

PayPal to Bill.com

AvailableNative · PayPalNative · Bill.com

Connect PayPal to Bill.com with Well

Pair PayPal disbursements with Bill.com bills; failed transfers surface inside Well so the next manual schedule reflects the real state.

Connect both toolsView all integrations

PayPal

Source

The PayPal integration connects your payment account to Well via MCP, importing transactions, fees, settlements, and refund data.

Bill.com

Target

The Bill.

Why this pair

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

What Well does between PayPal and Bill.com

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

Trigger from PayPal

11 events · pick one

Well engine·recipe·When a PayPal payment is captured

Source

from payment · live webhook

Brightline Analytics

via PayPal

Payment

When a PayPal payment is captured

ch_1q5nk · 22 Apr 2026€1,284.00

Extract

6 fields read from PayPal

6 fields read

CustomerBrightline Analytics
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordBrightline Analytics
Domainbrightline.ai
Tax idGB876543210
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
VendorBrightline Analytics
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Bill.com

Action in Bill.com

1 compatible with this trigger

Create a bill in Bill.com inbox

Bridge PayPal payouts to Bill.com reimbursements.

01Featured

Bridge merchant payouts to vendor reimbursements

PayPal 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 PayPal disbursement triggers a flag inside Well: the linked vendor payment is marked needs reschedule, the PayPal 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 PayPal 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 PayPal reason in hand.

Settle expense reimbursements weekly

Approved expense reimbursements are batched inside Well into a weekly PayPal 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.

16 signals and actions across PayPal and Bill.com

When a PayPal payment is captured
Pulls from PayPal transaction events. Captures completed PayPal payments with buyer, amount, and order id.
Trigger·Transaction
When a new buyer's first PayPal capture is recorded
Pulls from PayPal transaction events. Recognises a first-time buyer from the capture and prepares a customer record.
Trigger·Company
When a PayPal capture is denied
Pulls from PayPal transaction events. Surfaces denied captures with the denial reason for follow-up.
Trigger·Transaction
When a PayPal chargeback is filed
Pulls from PayPal transaction events. Flags the contested transaction and preserves the dispute trail.
Trigger·Transaction
When a PayPal payout settles
Pulls from PayPal transaction events. Tracks settlement batches with the covered captures and processing fees.
Trigger·Transaction
When a PayPal payment is held pending review
Pulls from PayPal transaction events. Detects pending captures and waits for the resolution before posting.
Trigger·Transaction
When a PayPal capture is recorded with its merchant fee
Pulls from PayPal transaction events. Pulls the merchant fee out of the capture so net revenue is correct.
Trigger·Transaction
When a PayPal capture includes a currency conversion
Pulls from PayPal transaction events. Pulls the FX rate and conversion fee from the capture.
Trigger·Transaction
When a PayPal checkout completes
Pulls from PayPal transaction events. Picks up the moment a buyer finishes checkout, before the bank settlement.
Trigger·Transaction

Reference

Field mapping for PayPal → Bill.com

7 fields across 2 record types, open to see the full table.

Transaction fields

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

Invoice fields

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

Connect PayPal and Bill.com in three steps.

1
Connect PayPal
Click 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.
- AuthOAuth 2.0
2
Map your accounts
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.
- 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 PayPal and Bill.com stay secure with Well

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.

MCP server authStorage region per workspaceGDPR-aligned

Scopes Well requestsmcp.paypal.com/mcp

Read PayPal records
Scoped to completed payments, refunds, disputes, holds, and related records. No access to anything else in your PayPal 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 PayPal records
Not granted. PayPal 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 PayPal’s admin panel.

Frequently asked questions about PayPal and Bill.com on Well

01What PayPal data does Well pull into Bill.com?: PayPal streams completed payments, refunds, disputes, holds, and currency-conversion 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 PayPal event ID preserved on the entry for audit.
02Will every PayPal record post to Bill.com automatically?: Not always. Within seconds of PayPal firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Bill.com email-in address and Bill.com drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.
03What happens to historical PayPal data when I first connect to Bill.com?: PayPal exposes the last full year 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 Bill.com ledger, and re-running the backfill is safe because Well tracks the PayPal record IDs and updates existing Bill.com entries instead of duplicating them.
04Does Well handle multi-currency records between PayPal and Bill.com?: PayPal 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.
05How does Well prevent duplicates when posting PayPal records to Bill.com?: PayPal sends each event with a stable resource ID that Well tracks against the Bill.com ledger. Webhook replays (which PayPal 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 PayPal and Bill.com?: PayPal'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. PayPal and Bill.com together cover multiple regions; Well's storage region is configured per workspace.