Bring Pennylane invoices into Ramp

About Pennylane and Ramp

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.

1. 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. 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. 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

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 in transit under TLS 1.3. Anything Well holds between Pennylane and Ramp is encrypted at rest and handled in line with GDPR.