What Pennylane data does Well pull into Ramp?

Pennylane streams supplier and customer invoices, contacts, and VAT detail read over Pennylane's MCP server to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Ramp as draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and line items pre-filled by Ramp's OCR, with the Pennylane event ID preserved on the entry for audit.

Will every Pennylane record post to Ramp automatically?

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

Well scores every candidate match between Pennylane records and existing Ramp entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Ramp updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.

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

Pennylane carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.

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

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

Pennylane'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 Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. 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.

Pennylane to Ramp

AvailableNative · PennylaneNative · Ramp

Connect Pennylane to Ramp with Well

Move Pennylane invoices and contacts through Well and into Ramp as draft bills, with the audit trail kept on every record.

Connect both toolsView all integrations

Pennylane

Source

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

Ramp

Target

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

Why this pair

Connect Pennylane to Ramp through Well so records flow without manual rework.

What Well does between Pennylane and Ramp

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

Trigger from Pennylane

4 events · pick one

Well engine·recipe·When a Pennylane customer invoice is read

Source

from payment · live webhook

Northpoint Logistics

via Pennylane

Invoice

When a Pennylane customer invoice is read

INV-1284 · 22 Apr 2026€1,284.00

Extract

5 fields read from Pennylane

5 fields read

CustomerNorthpoint Logistics
Invoice numberINV-1284
Issue date22 Apr 2026
Total€1,284.00
CurrencyEUR

Enrich

against your historical record graph

4 fields added

Customer recordNorthpoint Logistics
Domainnorthpoint.io
Tax idNL876543219B01
Sales journalVE · 2026

Confidence97%

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

Post

reconcile as draft bills

Create a draft bill in Ramp Bill Pay

auto-posted

posted

TypeBill
VendorNorthpoint Logistics
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Ramp

Action in Ramp

1 compatible with this trigger

Create a draft bill in Ramp Bill Pay

12 signals and actions across Pennylane and Ramp

When a Pennylane customer is read
Pulls Pennylane company customers with name, registration number, and billing detail.
Trigger·Company
When a Pennylane bank account is read
Pulls the bank accounts linked in Pennylane with currency and holder detail.
Trigger·Account
When a Pennylane customer invoice is read
Pulls Pennylane customer invoices with line items, customer, totals, and VAT.
Trigger·Invoice
When a Pennylane payment is read
Reads the payment recorded against a Pennylane invoice with method and amount.
Trigger·Payment method
When a Pennylane credit note is read
Captures Pennylane credit notes with the linked invoice, totals, and VAT so refunds reconcile correctly.
Trigger·Invoice
When a Pennylane supplier invoice is read
Pulls Pennylane supplier invoices with the supplier, amount, due date, and VAT.
Trigger·Invoice
When a Pennylane invoice attachment is read
Picks up the source PDF attached to a Pennylane invoice as a document.
Trigger·Document
When a Pennylane transaction is read
Captures the bank transactions Pennylane holds with amount, date, and counterparty.
Trigger·Transaction
Create a draft bill in Ramp Bill Pay
Well forwards the PDF to your company's @ap.ramp.com address; Ramp OCR creates a draft bill with invoice number, vendor, payment details, and line items pre-filled.
Action·Invoice

Reference

Field mapping for Pennylane → Ramp

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

Invoice fields

4 fields flow from Pennylane into Ramp.

Pennylane field	Label		Ramp field	Label
invoice.amount.total	Total amount	→	matched_record.amount	Matched amount
invoice.currency	Currency	→	matched_record.currency	Currency
invoice.invoice_number	Reference	→	matched_record.reference	Reference
invoice.id	Pennylane id	→	matched_record.id	Source id

Transaction fields

5 fields flow from Pennylane into Ramp.

Pennylane field	Label		Ramp field	Label
transaction.amount	Amount	→	transaction.amount	Transaction amount
transaction.currency	Currency	→	transaction.currency_code	Currency
transaction.date.created	Execution date	→	transaction.user_transaction_time	Transaction time
transaction.label.description	Label	→	transaction.merchant_name	Merchant
transaction.id	Transaction id	→	transaction.id	Ramp transaction id

Connect Pennylane and Ramp in three steps.

1
Connect Pennylane
Click Connect with Pennylane; Well's OAuth proxy handles Pennylane authorisation through Dynamic Client Registration. Pennylane'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 Pennylane's supplier and customer invoices, contacts, and VAT detail read over Pennylane's MCP server and the the Ramp Bill Pay drafts queue awaiting approval. Match candidates are scored on counterparty, amount, date, and reference; above 85% confidence the link posts automatically, below it the candidate set queues for sign-off.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Ramp
Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First sync~30 min

How Pennylane and Ramp stay secure with Well

Well connects to Pennylane through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Pennylane 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 requestswellapp.ai/v1/mcps/pennylane/mcp

Read Pennylane records
Scoped to supplier and customer invoices, contacts, and VAT detail read over Pennylane's MCP server. No access to anything else in your Pennylane account.
granted
Deliver documents to your Ramp inbox
Well forwards the extracted document to your Ramp email-in address; Ramp reads draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and related records from it and you review and post. No write credential to Ramp is requested.
granted
Modify or delete Pennylane records
Not granted. Pennylane 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 Pennylane’s admin panel.

Frequently asked questions about Pennylane and Ramp on Well

01What Pennylane data does Well pull into Ramp?: Pennylane streams supplier and customer invoices, contacts, and VAT detail read over Pennylane's MCP server to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Ramp as draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and line items pre-filled by Ramp's OCR, with the Pennylane event ID preserved on the entry for audit.
02Will every Pennylane record post to Ramp automatically?: Not always. Within seconds of Pennylane 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 Ramp email-in address and Ramp 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 match Pennylane records to entries in Ramp?: Well scores every candidate match between Pennylane records and existing Ramp entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Ramp updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
04Does Well handle multi-currency records between Pennylane and Ramp?: Pennylane carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.
05How does Well prevent duplicates when posting Pennylane records to Ramp?: Pennylane sends each event with a stable resource ID that Well tracks against the Ramp ledger. Webhook replays (which Pennylane can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Ramp 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 Pennylane and Ramp?: Pennylane'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 Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. 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.