How often does Ramp data sync to Xero?

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

How does Well match Ramp records to entries in Xero?

Ramp transactions are scored against open Xero entries on counterparty, amount, date proximity, and reference; above 85% the bank line reconciles automatically and posts to the right account, between 55% and 85% the candidate Xero entries are surfaced for sign-off, below 55% the line stays open and is added to a review queue.

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

Ramp reports a single base currency; Well stores the value verbatim and tags the record so your Xero ledger can apply its own conversion rule at posting time. Exchange-rate fields are not synthesised, so the Xero entry carries the unchanged Ramp amount and the conversion is owned by the Xero accounting policy.

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

Ramp sends each event with a stable resource ID that Well tracks against the Xero ledger. Webhook replays (which Ramp can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Xero entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.

What happens if a Ramp record fails to post to Xero?

When a record fails to post to Xero (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 Xero?

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 Xero email-in address once it clears the matching threshold; Xero creates the draft record from it and you confirm and post it. Well holds no write credential to Xero. Tokens are encrypted at rest and in transit under TLS 1.3. Ramp and Xero together cover multiple regions; Well's storage region is configured per workspace.

Ramp to Xero

AvailableNative · RampNative · Xero

Connect Ramp to Xero with Well

Inter-company transfers and multi-currency settlements decompose correctly inside Well, then arrive in Xero as per-vendor documents with the source breakdown attached.

Connect both toolsView all integrations

Ramp

Source

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

Xero

Target

The Xero integration connects Well to your accounting platform for bidirectional data flow.

Why this pair

Ramp tracks card spend and policy in real time; Xero accepts emailed PDFs and creates draft bills via Hubdoc.

Connecting Ramp to Xero through Well matches each Ramp card transaction inside its own ledger with Ramp policy classification, the receipt, and the FX rate (when needed) attached, then forwards the matched document to Xero's email-in. Ramp's MCP server pushes card-transaction events to Well; Hubdoc creates the draft bill from the forwarded PDF with the Ramp policy classification surfaced for your team to route to the matching tracking category in Xero.

What Well does between Ramp and Xero

One-way: Ramp into Well into Xero
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

Linear Orbit Inc.

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

CounterpartyLinear Orbit Inc.
Booking date22 Apr 2026
Amount€1,284.00
CurrencyEUR
ReferenceINV-1024

Enrich

against your historical record graph

4 fields added

CounterpartyLinear Orbit Inc.
Tax idEU826112334
Ledger account6064 · SaaS
Match1 candidate invoice

Confidence97%

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

Post

post as draft bills

Create a draft bill in Xero

auto-posted

posted

TypeBill
VendorLinear Orbit Inc.
Amount€1,284.00
Ledger6064 · SaaS
Source docattached
Confidence97%

audit linkto Xero

Action in Xero

1 compatible with this trigger

Create a draft bill in Xero

Reconcile Ramp transactions to Xero ledger lines.

01Featured

Resolve the merchant behind a charge

Well reads spend from Ramp and matches each merchant against the contacts already in Xero, 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 Xero keeps one clean contact.

Carry the spend context onward

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

Keep the accountant's ledger untouched

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

10 signals and actions across Ramp and Xero

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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Account
When a Ramp card is swiped
Captures every card transaction with merchant, amount, currency, and category. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a Ramp reimbursement is filed
Pulls employee reimbursement requests with their amount and category as a transaction. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
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 Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
Resolve a Xero contact from the document
Hubdoc reads the contact name and trading address off the PDF to match the vendor. You confirm or merge on first sight.
Action·Company
Pre-fill the Xero tax rate from the document
Hubdoc extracts the tax type and applies it on the draft bill. You confirm before posting.
Action·Invoice
Attach the file to the Xero record
Hubdoc stores the original PDF on the draft bill as the source attachment.
Action·Document

Reference

Field mapping for Ramp → Xero

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

Transaction fields

3 fields flow from Ramp into Xero.

Ramp field	Label		Xero field	Label
transaction.amount	Amount	→	Total	Amount
transaction.currency_code	Currency	→	CurrencyCode	Currency
transaction.id	Transaction id	→	BankTransactionID	Bank line id

Invoice fields

4 fields flow from Ramp into Xero.

Ramp field	Label		Xero field	Label
bill.invoice_number	Invoice number	→	InvoiceNumber	Invoice number
bill.invoice_date	Issue date	→	Date	Bill date
bill.due_date	Due date	→	DueDate	Due date
bill.currency_code	Currency	→	CurrencyCode	Currency

Connect Ramp and Xero 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 Xero draft bills queue populated by Hubdoc. 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 Xero
Click Connect with Xero; Well's OAuth proxy handles Xero authorisation through Dynamic Client Registration. Xero'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 Xero 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 Xero 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 Xero inbox
Well forwards the extracted document to your Xero email-in address; Xero reads draft bills via email-in, with contact, dates, totals, and related records from it and you review and post. No write credential to Xero 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 Xero on Well

01How often does Ramp data sync to Xero?: Ramp 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 Xero within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
02How does Well match Ramp records to entries in Xero?: Ramp transactions are scored against open Xero entries on counterparty, amount, date proximity, and reference; above 85% the bank line reconciles automatically and posts to the right account, between 55% and 85% the candidate Xero entries are surfaced for sign-off, below 55% the line stays open and is added to a review queue.
03Does Well handle multi-currency records between Ramp and Xero?: Ramp reports a single base currency; Well stores the value verbatim and tags the record so your Xero ledger can apply its own conversion rule at posting time. Exchange-rate fields are not synthesised, so the Xero entry carries the unchanged Ramp amount and the conversion is owned by the Xero accounting policy.
04How does Well prevent duplicates when posting Ramp records to Xero?: Ramp sends each event with a stable resource ID that Well tracks against the Xero ledger. Webhook replays (which Ramp can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Xero entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
05What happens if a Ramp record fails to post to Xero?: When a record fails to post to Xero (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 Xero?: 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 Xero email-in address once it clears the matching threshold; Xero creates the draft record from it and you confirm and post it. Well holds no write credential to Xero. Tokens are encrypted at rest and in transit under TLS 1.3. Ramp and Xero together cover multiple regions; Well's storage region is configured per workspace.