How often does PayPal data sync to Pennylane?

PayPal pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Pennylane within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

What happens to historical PayPal data when I first connect to Pennylane?

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

Does Well handle multi-currency records between PayPal and Pennylane?

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

How does Well prevent duplicates when posting PayPal records to Pennylane?

PayPal sends each event with a stable resource ID that Well tracks against the Pennylane ledger. Webhook replays (which PayPal can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Pennylane 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 a PayPal record fails to post to Pennylane?

When a record fails to post to Pennylane (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.

How does Well authenticate with PayPal and Pennylane?

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 Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and PayPal hosts outside the EU; Well processes records per the storage region configured for your workspace.

PayPal to Pennylane

AvailableNative · PayPalNative · Pennylane

Connect PayPal to Pennylane with Well

Skip the spreadsheet middle step: PayPal payments and refunds are matched in Well, then the matched PDFs land in Pennylane as supplier and customer invoices ready for your review.

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.

Pennylane

Target

The Pennylane integration creates a bidirectional bridge between Well and your accounting workspace.

Why this pair

PayPal generates more accounting work per transaction than most payment processors.

Refunds, holds, dispute reserves, and currency conversions all land on different value dates. Pennylane wants all of that landed in clean records with VAT lines that match. Connecting them through Well unwinds the PayPal activity inside Well's own ledger, then forwards each matched document to Pennylane's email-in so disputes and refunds chain back to the original sale instead of floating as orphan rows.

What Well does between PayPal and Pennylane

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

Aldercroft Trading

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

CustomerAldercroft Trading
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordAldercroft Trading
Domainaldercroft.co.uk
Tax idGB987604123
Sales journalVE · 2026

Confidence97%

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

Post

post as supplier and customer invoices

Create a supplier invoice in Pennylane

auto-posted

posted

TypeSupplier invoice
VendorAldercroft Trading
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Pennylane

Action in Pennylane

1 compatible with this trigger

Create a supplier invoice in Pennylane

Reconcile PayPal multi-currency charges to Pennylane entries.

01Featured

Open the black box

Stop booking PayPal as a single net line and surface every underlying component.

Drafts your accountant trusts

Gross sales and fees arrive in Pennylane as pre-filled drafts on the accounts your accountant expects, ready for one-click confirmation.

Settlements matched fast

Reconcile each PayPal settlement against your bank in minutes instead of hours.

Charge to batch, traced

Follow every PayPal charge through to its customer invoice and payout batch.

17 signals and actions across PayPal and Pennylane

When a PayPal subscription renews
Pulls from PayPal transaction events. Detects recurring billing cycles and matches the new charge to the contract. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When a PayPal checkout completes
Pulls from PayPal transaction events. Picks up the moment a buyer finishes checkout, before the bank settlement. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a PayPal capture is denied
Pulls from PayPal transaction events. Surfaces denied captures with the denial reason for follow-up. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
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. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
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. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
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. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a PayPal payment is refunded
Pulls from PayPal transaction events. Detects refunds against captured payments and links back to the order. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a PayPal payout settles
Pulls from PayPal transaction events. Tracks settlement batches with the covered captures and processing fees. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a PayPal chargeback is filed
Pulls from PayPal transaction events. Flags the contested transaction and preserves the dispute trail. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction

Reference

Field mapping for PayPal → Pennylane

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

Transaction fields

4 fields flow from PayPal into Pennylane.

PayPal field	Label		Pennylane field	Label
capture.amount.currency_code	Currency	→	currency	Currency
capture.create_time	Capture date	→	date	Execution date
capture.id	Capture id	→	external_reference	Source id
capture.seller_receivable.fee	PayPal fee	→	amount	Amount

Invoice fields

3 fields flow from PayPal into Pennylane.

PayPal field	Label		Pennylane field	Label
invoice.detail.invoice_number	Invoice number	→	label	Reference
invoice.detail.invoice_date	Issue date	→	date	Invoice date
invoice.amount.currency_code	Currency	→	currency	Currency

Connect PayPal and Pennylane 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 Pennylane Purchases tab and the customer-invoice collections list. 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 Pennylane
Click Connect with Pennylane; Well's OAuth proxy handles Pennylane authorisation through Dynamic Client Registration. Pennylane's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First syncup to an hour

How PayPal and Pennylane 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 processes records per the storage region configured for your workspace; only fields strictly required by the write surface are ferried across regions.

MCP server authEU residency optionGDPR-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 Pennylane inbox
Well forwards the extracted document to your Pennylane email-in address; Pennylane reads supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR from it and you review and post. No write credential to Pennylane 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 Pennylane on Well

01How often does PayPal data sync to Pennylane?: PayPal pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Pennylane within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
02What happens to historical PayPal data when I first connect to Pennylane?: 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 Pennylane ledger, and re-running the backfill is safe because Well tracks the PayPal record IDs and updates existing Pennylane entries instead of duplicating them.
03Does Well handle multi-currency records between PayPal and Pennylane?: PayPal carries the original transaction currency on every record and Pennylane natively ledgers in multiple currencies. Well preserves the original amount, applies your Pennylane chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Pennylane, so the Pennylane entry you post keeps both sides of the trade.
04How does Well prevent duplicates when posting PayPal records to Pennylane?: PayPal sends each event with a stable resource ID that Well tracks against the Pennylane ledger. Webhook replays (which PayPal can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Pennylane 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 a PayPal record fails to post to Pennylane?: When a record fails to post to Pennylane (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.
06How does Well authenticate with PayPal and Pennylane?: 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 Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and PayPal hosts outside the EU; Well processes records per the storage region configured for your workspace.