What Ramp data does Well pull into Pennylane?

Ramp streams card transactions, approved bills, reimbursements, vendor records, and policy events to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Pennylane as supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR, with the Ramp event ID preserved on the entry for audit.

Will every Ramp record post to Pennylane automatically?

Not always. Within seconds of Ramp 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 Pennylane email-in address and Pennylane 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.

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

Ramp sends each event with a stable resource ID that Well tracks against the Pennylane ledger. Webhook replays (which Ramp 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.

Can I customise which Ramp fields are sent to Pennylane?

The default mapping covers every Ramp field your Pennylane 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 Pennylane 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 Pennylane is left exactly as it stands.

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

How does Well authenticate with Ramp and Pennylane?

Ramp'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 Ramp hosts outside the EU; Well processes records per the storage region configured for your workspace.

Ramp to Pennylane

AvailableNative · RampNative · Pennylane

Connect Ramp to Pennylane with Well

Ramp statement lines collapse onto their counterparties inside Well; resulting documents arrive at Pennylane as drafts pre-filled by Pennylane's own OCR.

Connect both toolsView all integrations

Ramp

Source

The Ramp integration connects your corporate card and expense management platform to Well.

Pennylane

Target

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

Why this pair

Ramp issues corporate cards primarily for US companies; Pennylane runs on French SMB accounting in EUR.

The two systems rarely sit on the same model. Connecting Ramp to Pennylane through Well matches each Ramp card transaction inside its own ledger with the FX-converted amount on the booking date, the policy classification preserved, and the receipt attached, then forwards the matched document to Pennylane's email-in. Ramp's MCP server pushes card-transaction events to Well; Pennylane's OCR creates the invoice from the forwarded PDF with the French ledger context attached.

What Well does between Ramp and Pennylane

One-way: Ramp into Well into Pennylane
Sync mode: Real-time MCP push
Events arrive in seconds

Trigger from Ramp

4 events · pick one

Well engine·recipe·When a Ramp card is swiped

Source

from card · live webhook

OpenAI Ireland

via Ramp

Card

When a Ramp card is swiped

INV-1024 · 22 Apr 2026€1,284.00

Extract

5 fields read from Ramp

5 fields read

CounterpartyOpenAI Ireland
Booking date22 Apr 2026
Amount€1,284.00
CurrencyEUR
ReferenceINV-1024

Enrich

against your historical record graph

4 fields added

CounterpartyOpenAI Ireland
Tax idIE3893540LH
Ledger account6156 · AI services
Match1 candidate invoice

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
VendorOpenAI Ireland
Amount€1,284.00
Ledger6156 · AI services
Source docattached
Confidence97%

audit linkto Pennylane

Action in Pennylane

1 compatible with this trigger

Create a supplier invoice in Pennylane

Reconcile Ramp transactions to Pennylane entries with EU residency intact.

01Featured

Resolve the merchant behind a charge

Well reads spend from Ramp and matches each merchant against the companies already in Pennylane, then forwards the matched document to the email-in address with the vendor resolved.

Collapse look-alike merchants

Merchant strings that resolve to one company are treated as the same vendor inside Well before the forward, so Pennylane keeps one clean supplier.

Carry the spend context onward

Each forwarded document keeps the Ramp charge and its resolved company attached, so Pennylane sees the vendor and the spend together.

Keep the accountant's ledger untouched

Well forwards resolved documents to Pennylane's email-in and never writes journal entries through its API, so the ledger stays your accountant's.

11 signals and actions across Ramp and Pennylane

When a Ramp card is swiped
Captures every card transaction with merchant, amount, currency, and category. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Ramp reimbursement is filed
Pulls employee reimbursement requests with their amount and category as a transaction. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Ramp vendor record appears in your account
Well discovers new Ramp vendors via the read-only ETL load and mirrors them as company records. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Company
When a Ramp transaction is coded by a Ramp rule
Picks up Ramp transactions that arrive with an automated coding rule already applied. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Ramp transaction trips a spend policy
Pulls the policy_violations field on the transaction so non-compliant lines surface for review. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Transaction
When a Ramp card account is read
Pulls each Ramp card account the workspace holds with its limit and the cards bound to it. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Account
Create a supplier invoice in Pennylane
Well forwards the extracted PDF to Pennylane's supplier inbox; Pennylane creates the supplier invoice with amount, VAT, and date pre-filled.
Action·Invoice
Attach the source document to the Pennylane record
The PDF Well forwards is stored as the source attachment on whichever invoice Pennylane creates from it.
Action·Document
Resolve a Pennylane supplier from the document
Pennylane's OCR resolves the supplier name from the PDF. You confirm or correct the match on first sight.
Action·Company

Reference

Field mapping for Ramp → Pennylane

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

Transaction fields

3 fields flow from Ramp into Pennylane.

Ramp field	Label		Pennylane field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency_code	Currency	→	currency	Currency
transaction.id	Transaction id	→	external_reference	Source id

Invoice fields

4 fields flow from Ramp into Pennylane.

Ramp field	Label		Pennylane field	Label
bill.invoice_number	Invoice number	→	label	Reference
bill.invoice_date	Issue date	→	date	Invoice date
bill.due_date	Due date	→	deadline	Due date
bill.currency_code	Currency	→	currency	Currency

Connect Ramp and Pennylane in three steps.

1
Connect Ramp
Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp'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 Ramp's card transactions, approved bills, reimbursements, vendor records, and policy events and the the Pennylane Purchases tab and the customer-invoice collections list. Counterparty proximity, amount, date, and reference drive the match score; lines above 85% post automatically and the rest queue for a one-click sign-off.
- 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 Ramp and Pennylane stay secure with Well

Well connects to Ramp through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Ramp 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 requestsramp-mcp-remote.ramp.com/mcp

Read Ramp records
Scoped to card transactions, approved bills, reimbursements, vendor records, and related records. No access to anything else in your Ramp 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 Ramp records
Not granted. Ramp 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 Ramp’s admin panel.

Frequently asked questions about Ramp and Pennylane on Well

01What Ramp data does Well pull into Pennylane?: Ramp streams card transactions, approved bills, reimbursements, vendor records, and policy events to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Pennylane as supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR, with the Ramp event ID preserved on the entry for audit.
02Will every Ramp record post to Pennylane automatically?: Not always. Within seconds of Ramp 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 Pennylane email-in address and Pennylane 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.
03How does Well prevent duplicates when posting Ramp records to Pennylane?: Ramp sends each event with a stable resource ID that Well tracks against the Pennylane ledger. Webhook replays (which Ramp 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.
04Can I customise which Ramp fields are sent to Pennylane?: The default mapping covers every Ramp field your Pennylane 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 Pennylane 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 Pennylane is left exactly as it stands.
05What happens if a Ramp 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 Ramp record. Nothing silently drops.
06How does Well authenticate with Ramp and Pennylane?: Ramp'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 Ramp hosts outside the EU; Well processes records per the storage region configured for your workspace.