What Ramp data does Well pull into Melio?

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

How does Well match Ramp records to entries in Melio?

Each Ramp debit is checked against the bills scheduled in Melio. Well scores on payee, amount, scheduled date, and currency; above 85% the bank line is auto-matched to the bill, the payment status updates in Melio, and the receipt is attached. Between 55% and 85% the candidate bills are surfaced for sign-off so you can confirm which bill the debit actually covers.

What happens to historical Ramp data when I first connect to Melio?

Ramp exposes the last three years 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 Melio ledger, and re-running the backfill is safe because Well tracks the Ramp record IDs and updates existing Melio entries instead of duplicating them.

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

Ramp reports a single base currency and Melio ledgers in a single base currency, so Well stores the value verbatim and posts the record without any conversion step. If you start trading in another currency, switch the connector behaviour in settings and Well begins tagging records with the source currency for conversion at posting time.

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

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

How does Well authenticate with Ramp and Melio?

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 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 at rest and in transit under TLS 1.3. Ramp and Melio together cover multiple regions; Well's storage region is configured per workspace.

Ramp to Melio

AvailableNative · RampNative · Melio

Connect Ramp to Melio with Well

Match Ramp debits against your bills inside Well, then forward the matched bill PDFs to Melio's inbox so AP sees only items needing action.

Connect both toolsView all integrations

Ramp

Source

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

Melio

Target

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

Why this pair

Ramp tracks card spend and reimbursement requests; Melio schedules vendor payments on US rails.

Connecting Ramp to Melio through Well promotes Ramp reimbursement requests and recurring vendor charges into Melio scheduled payments with the vendor record resolved, the PDF receipt attached on the payment record, and the policy classification preserved. Ramp's MCP server handles authorisation through Dynamic Client Registration; Melio's Smart Bill Capture creates the bill from the PDF Well forwards to @invoicesmelio. com.

What Well does between Ramp and Melio

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

Trigger from Ramp

5 events · pick one

Well engine·recipe·When a Ramp card is swiped

Source

from card · live webhook

Twilio 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

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

Enrich

against your historical record graph

4 fields added

CounterpartyTwilio Ireland
Tax idIE3251428LH
Ledger account6156 · Communications
Match1 candidate invoice

Confidence97%

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

Post

schedule as bills

Create a bill in your Melio inbox

auto-posted

posted

TypeBill
VendorTwilio Ireland
Amount€1,284.00
Ledger6156 · Communications
Source docattached
Confidence97%

audit linkto Melio

Action in Melio

2 compatible with this trigger

Create a bill in your Melio inboxResolve a Melio vendor from the bill

Match Ramp debits to Melio scheduled payments.

01Featured

Resolve the merchant behind a charge

Well reads spend from Ramp and matches each merchant to a company record, then forwards the matched document to Melio's 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 Melio does not accumulate near-duplicates.

Carry the spend context onward

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

Keep the source charge attached

The Ramp transaction Well matched stays linked to the document sent to Melio, so each entry traces back to the charge it came from.

10 signals and actions across Ramp and Melio

When a Ramp reimbursement is filed
Pulls employee reimbursement requests with their amount and category as a transaction.
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.
Trigger·Account
When a Ramp transaction is coded by a Ramp rule
Picks up Ramp transactions that arrive with an automated coding rule already applied.
Trigger·Transaction
When a Ramp card is swiped
Captures every card transaction with merchant, amount, currency, and category.
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.
Trigger·Company
When a Ramp transaction trips a spend policy
Pulls the policy_violations field on the transaction so non-compliant lines surface for review.
Trigger·Transaction
Create a bill in your Melio inbox
Well forwards the PDF to your @invoicesmelio.com address; Melio's Smart Bill Capture lifts the vendor, amount, and due date into a Bills Inbox entry that waits for you to schedule a payment date and funding method.
Action·Invoice
Resolve a Melio vendor from the bill
Melio's OCR resolves the vendor name from the PDF; banking details for the payment route are set up separately.
Action·Company
Park the Melio bill in the Bills Inbox for payment scheduling
The created bill waits in your Melio Bills Inbox until you pick a pay date, choose a funding source (bank transfer or card), and set how the vendor gets paid (ACH deposit or mailed check). Well never sets a pay date, chooses funding, or sends the payment.
Action·Invoice

Reference

Field mapping for Ramp → Melio

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

Transaction fields

3 fields flow from Ramp into Melio.

Ramp field	Label		Melio field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency_code	Currency	→	currency	Currency
transaction.id	Transaction id	→	payment_id	Payment id

Invoice fields

3 fields flow from Ramp into Melio.

Ramp field	Label		Melio field	Label
bill.invoice_number	Invoice number	→	bill_number	Bill number
bill.due_date	Due date	→	due_date	Due date
bill.currency_code	Currency	→	currency	Currency

Company fields

3 fields flow from Ramp into Melio.

Ramp field	Label		Melio field	Label
vendor.name	Vendor name	→	vendor_name	Vendor name
vendor.email	Email	→	email	Email
vendor.id	Vendor id	→	vendor_id	Vendor id

Connect Ramp and Melio 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 Melio Bills Inbox awaiting payment scheduling. The first batch of bank lines flows into the review queue alongside candidate scheduled payments; once you confirm the rule, Ramp debits auto-link above 85% confidence.
- Auto-post above85% confidence
- Overridemanual anytime
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

How Ramp and Melio 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's storage region is configured per workspace regardless of where Ramp and Melio host theirs.

MCP server authStorage region per workspaceGDPR-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 Melio inbox
Well forwards the extracted document to your Melio email-in address; Melio reads bills via email-in at @invoicesmelio.com, with vendor, amount, and due date populated by Smart Bill Capture from it and you review and post. No write credential to Melio 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 Melio on Well

01What Ramp data does Well pull into Melio?: 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 Melio as bills via email-in at @invoicesmelio.com, with vendor, amount, and due date populated by Smart Bill Capture, with the Ramp event ID preserved on the entry for audit.
02How does Well match Ramp records to entries in Melio?: Each Ramp debit is checked against the bills scheduled in Melio. Well scores on payee, amount, scheduled date, and currency; above 85% the bank line is auto-matched to the bill, the payment status updates in Melio, and the receipt is attached. Between 55% and 85% the candidate bills are surfaced for sign-off so you can confirm which bill the debit actually covers.
03What happens to historical Ramp data when I first connect to Melio?: Ramp exposes the last three years 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 Melio ledger, and re-running the backfill is safe because Well tracks the Ramp record IDs and updates existing Melio entries instead of duplicating them.
04Does Well handle multi-currency records between Ramp and Melio?: Ramp reports a single base currency and Melio ledgers in a single base currency, so Well stores the value verbatim and posts the record without any conversion step. If you start trading in another currency, switch the connector behaviour in settings and Well begins tagging records with the source currency for conversion at posting time.
05How does Well prevent duplicates when posting Ramp records to Melio?: Ramp sends each event with a stable resource ID that Well tracks against the Melio ledger. Webhook replays (which Ramp 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 Ramp and Melio?: 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 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 at rest and in transit under TLS 1.3. Ramp and Melio together cover multiple regions; Well's storage region is configured per workspace.