What Xero data does Well pull into Ramp?

Xero streams bills, contacts, tracking categories, and tax types read over Xero'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 Xero event ID preserved on the entry for audit.

Will every Xero record post to Ramp automatically?

Not always. Within seconds of Xero 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.

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

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

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

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

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

When a record fails to post to Ramp (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 Xero record. Nothing silently drops.

How does Well authenticate with Xero and Ramp?

Xero'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. Xero and Ramp together cover multiple regions; Well's storage region is configured per workspace.

Xero to Ramp

AvailableNative · XeroNative · Ramp

Connect Xero to Ramp with Well

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

Connect both toolsView all integrations

Xero

Source

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

Ramp

Target

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

Why this pair

This is the reverse of the usual Ramp-to-Xero close.

Here Xero is the source of accounting truth and Ramp is the spend surface that needs context. Xero exposes its bills, contacts, and tracking categories through Well's OAuth-proxy MCP server; Ramp tracks card transactions and policy in real time over its own MCP. Connecting Xero to Ramp through Well means each Ramp card charge is matched inside Well against the corresponding Xero bill or contact, the Xero tracking category and tax type are carried across, and the reconciled record is surfaced against the Ramp transaction so the spend ledger and the books agree without anyone re-keying a line.

What Well does between Xero and Ramp

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

Trigger from Xero

4 events · pick one

Well engine·recipe·When a Xero invoice is read

Source

from upload · live webhook

Slack Technologies

via Xero

Invoice

When a Xero invoice is read

INV-2026-04-100 · 22 Apr 2026€1,284.00

Extract

6 fields read from Xero

6 fields read

VendorSlack Technologies
Invoice numberINV-2026-04-100
Issue date22 Apr 2026
Total€1,284.00
Tax€256.80

Enrich

against your historical record graph

5 fields added

Legal entitySlack Technologies
Tax idEU372014983
Domainslack.com
Ledger account6064 · SaaS

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
VendorSlack Technologies
Amount€1,284.00
Ledger6064 · SaaS
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 Xero and Ramp

When a Xero invoice attachment is read
Picks up the source PDF attached to a Xero invoice as a document.
Trigger·Document
When a Xero bank account is read
Pulls the bank-type accounts from the Xero chart of accounts with currency and account number.
Trigger·Account
When a Xero purchase order is read
Pulls Xero purchase orders with supplier, line items, and totals to match against the arriving bill.
Trigger·Invoice
When a Xero payment is read
Reads the payment applied to a Xero invoice or bill with method, account, and amount.
Trigger·Payment method
When a Xero bank transaction is read
Captures spent and received money transactions reconciled in Xero with amount and account code.
Trigger·Transaction
When a Xero contact is read
Pulls Xero contacts with name, trading address, and tax number to match against your companies.
Trigger·Company
When a Xero invoice is read
Pulls Xero sales and purchase invoices with contact, line items, totals, and tax.
Trigger·Invoice
When a Xero credit note is read
Captures Xero credit notes with contact, totals, and tax so refunds reconcile against the original invoice.
Trigger·Invoice
Attach the source document to the Ramp bill
The forwarded PDF is stored on the Ramp draft bill as the source document.
Action·Document

Reference

Field mapping for Xero → Ramp

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

Invoice fields

4 fields flow from Xero into Ramp.

Xero field	Label		Ramp field	Label
Invoice.Total.total	Total	→	matched_record.amount	Matched amount
Invoice.CurrencyCode.currency	Currency	→	matched_record.currency	Currency
Invoice.InvoiceNumber.invoice_number	Invoice number	→	matched_record.reference	Reference
Invoice.InvoiceID.id	Xero id	→	matched_record.id	Source id

Transaction fields

5 fields flow from Xero into Ramp.

Xero field	Label		Ramp field	Label
BankTransaction.Total.amount	Amount	→	transaction.amount	Transaction amount
BankTransaction.CurrencyCode.currency	Currency	→	transaction.currency_code	Currency
BankTransaction.Date.created	Transaction date	→	transaction.user_transaction_time	Transaction time
BankTransaction.Reference.description	Reference	→	transaction.merchant_name	Merchant
BankTransaction.BankTransactionID.transaction_id	Transaction id	→	transaction.id	Ramp transaction id

Connect Xero and Ramp in three steps.

1
Connect Xero
Click Connect with Xero; Well's OAuth proxy handles Xero authorisation through Dynamic Client Registration. Xero'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 Xero's bills, contacts, tracking categories, and tax types read over Xero'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 Xero and Ramp stay secure with Well

Well connects to Xero through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Xero secret; the server refreshes its own tokens on each session. Well's storage region is configured per workspace regardless of where Xero and Ramp host theirs.

MCP server authStorage region per workspaceGDPR-aligned

Scopes Well requestswellapp.ai/v1/mcps/xero/mcp

Read Xero records
Scoped to bills, contacts, tracking categories, and tax types read over Xero's MCP server. No access to anything else in your Xero 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 Xero records
Not granted. Xero 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 Xero’s admin panel.

Frequently asked questions about Xero and Ramp on Well

01What Xero data does Well pull into Ramp?: Xero streams bills, contacts, tracking categories, and tax types read over Xero'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 Xero event ID preserved on the entry for audit.
02Will every Xero record post to Ramp automatically?: Not always. Within seconds of Xero 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.
03What happens to historical Xero data when I first connect to Ramp?: Xero exposes seven years of accounting history 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 Ramp ledger, and re-running the backfill is safe because Well tracks the Xero record IDs and updates existing Ramp entries instead of duplicating them.
04How does Well prevent duplicates when posting Xero records to Ramp?: Xero sends each event with a stable resource ID that Well tracks against the Ramp ledger. Webhook replays (which Xero 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.
05What happens if a Xero record fails to post to Ramp?: When a record fails to post to Ramp (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 Xero record. Nothing silently drops.
06How does Well authenticate with Xero and Ramp?: Xero'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. Xero and Ramp together cover multiple regions; Well's storage region is configured per workspace.