Will every PayPal record post to Freshbooks 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 Freshbooks email-in address and Freshbooks 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 Freshbooks?

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

Can I customise which PayPal fields are sent to Freshbooks?

The default mapping covers every PayPal field your Freshbooks chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields Freshbooks does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in Freshbooks is left exactly as it stands.

What happens if a PayPal 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 PayPal record. Nothing silently drops.

What happens if I disconnect PayPal or Freshbooks?

Disconnecting PayPal stops the flow at the source. Well asks the PayPal MCP server to revoke the access token; PayPal 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 PayPal and Freshbooks?

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

PayPal to Freshbooks

AvailableNative · PayPalNative · Freshbooks

Connect PayPal to Freshbooks with Well

Replace the monthly payout-to-ledger spreadsheet: Well watches PayPal, matches it against your existing records, and forwards the resulting documents to Freshbooks as soon as the funds clear.

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.

Freshbooks

Target

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

Why this pair

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

What Well does between PayPal and Freshbooks

One-way: PayPal into Well into Freshbooks
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

Pixel Foundry

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

CustomerPixel Foundry
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordPixel Foundry
Domainpixelfoundry.studio
Tax idFR98765432101
Sales journalVE · 2026

Confidence97%

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

Post

post as expenses and bills

Create an expense in FreshBooks

auto-posted

posted

TypeExpense
VendorPixel Foundry
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Freshbooks

Action in Freshbooks

2 compatible with this trigger

Create an expense in FreshBooksCreate a bill in FreshBooks (Select plan)

Reconcile PayPal multi-currency charges to Freshbooks entries.

01Featured

Match payouts to the bank deposit

PayPal payouts are reconciled against the bank deposit they generate by amount, date, and currency, then the matched deposit document is forwarded to Freshbooks with the underlying charge breakdown attached, ready for your team to post. The fee line is split out automatically so the Freshbooks P&L sees gross revenue and processor fees as separate accounts.

Bring multi-currency charges into one ledger

Each PayPal charge keeps its original transaction currency on the matched document. Well stamps the FX rate at the timestamp of the event and attaches both the source and converted amounts to the document forwarded to Freshbooks, so the draft your team confirms stands up to audit.

Surface jurisdiction for tax-code routing

PayPal charges carry the customer billing country in their metadata; Well stamps the jurisdiction (EU / US / AU / etc.) on the document forwarded to Freshbooks, with reverse-charge context on cross-border charges so your team can apply the right tax code in Freshbooks in one click.

Decompose fees from a card payment

Every PayPal card charge is split inside Well into the gross amount, the processor fee, and the net deposit. The fee context is broken out on the document forwarded to Freshbooks, ready for your team to route it onto the processor-fee account on confirmation.

16 signals and actions across PayPal and Freshbooks

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 PayPal payout settles
Pulls from PayPal transaction events. Tracks settlement batches with the covered captures and processing fees.
Trigger·Transaction
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 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 includes a currency conversion
Pulls from PayPal transaction events. Pulls the FX rate and conversion fee from the capture.
Trigger·Transaction
When a PayPal-issued invoice is paid
Pulls from PayPal transaction events. Captures invoices issued through PayPal with line items and tax.
Trigger·Invoice
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 subscription renews
Pulls from PayPal transaction events. Detects recurring billing cycles and matches the new charge to the contract.
Trigger·Invoice
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

Reference

Field mapping for PayPal → Freshbooks

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

Transaction fields

4 fields flow from PayPal into Freshbooks.

PayPal field	Label		Freshbooks field	Label
capture.amount.currency_code	Currency	→	currency_code	Currency
capture.create_time	Capture date	→	date	Transaction date
capture.id	Capture id	→	external_id	External id
capture.seller_receivable.fee	PayPal fee	→	amount	Amount

Invoice fields

3 fields flow from PayPal into Freshbooks.

PayPal field	Label		Freshbooks field	Label
invoice.detail.invoice_number	Invoice number	→	invoice_number	Invoice number
invoice.detail.invoice_date	Issue date	→	create_date	Issue date
invoice.amount.currency_code	Currency	→	currency_code	Currency

Connect PayPal and Freshbooks 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 FreshBooks expense or bill queue. Match candidates are scored on counterparty name, amount, currency, and reference; you approve any that need a human eye and Well saves the rule for the next batch.
- 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 PayPal and Freshbooks 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 Freshbooks 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 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 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 Freshbooks on Well

01Will every PayPal record post to Freshbooks 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 Freshbooks email-in address and Freshbooks 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.
02What happens to historical PayPal data when I first connect to Freshbooks?: 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 Freshbooks ledger, and re-running the backfill is safe because Well tracks the PayPal record IDs and updates existing Freshbooks entries instead of duplicating them.
03Can I customise which PayPal fields are sent to Freshbooks?: The default mapping covers every PayPal field your Freshbooks chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields Freshbooks does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in Freshbooks is left exactly as it stands.
04What happens if a PayPal 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 PayPal record. Nothing silently drops.
05What happens if I disconnect PayPal or Freshbooks?: Disconnecting PayPal stops the flow at the source. Well asks the PayPal MCP server to revoke the access token; PayPal 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 PayPal and Freshbooks?: 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 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. PayPal and Freshbooks together cover multiple regions; Well's storage region is configured per workspace.