Bring Pennylane bills into Melio

About Pennylane and Melio

Pennylane

Source

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

Melio

Target

The Melio connection delivers extracted bills into Melio through its Pay Bills email address.

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 Melio Bills Inbox awaiting payment scheduling. 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 Melio

   In Melio, open Settings > Integrations and generate an API token with payment-write scope. Paste the key into Well; Melio's discovery endpoints are reached over TLS 1.3 and the secret is never echoed in the UI.

   • AuthConnect
   • First sync~10 min

01What Pennylane data does Well pull into Melio?

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 Melio as bills via email-in at @invoicesmelio.com, with vendor, amount, and due date populated by Smart Bill Capture, with the Pennylane event ID preserved on the entry for audit.

02How often does Pennylane data sync to Melio?

Pennylane 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 Melio within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

03How does Well match Pennylane records to entries in Melio?

Well scores every candidate match between Pennylane records and existing Melio entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Melio 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 Melio?

Pennylane carries the original transaction currency on every record, but Melio 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 Melio, so both sides of the trade are visible when you post.

05How does Well prevent duplicates when posting Pennylane records to Melio?

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

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 Melio email-in address once it clears the matching threshold; Melio creates the draft record from it and you confirm and post it. Well holds no write credential to Melio. Tokens are encrypted in transit under TLS 1.3. Anything Well holds between Pennylane and Melio is encrypted at rest and handled in line with GDPR.