Will every Razorpay record post to Xero automatically?

Not always. Within seconds of Razorpay 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 Xero email-in address and Xero 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.

How does Well match Razorpay records to entries in Xero?

Every Razorpay charge is scored against your open Xero sales invoices and existing customer records on customer name, amount, currency, and reference. Above 85% the charge collapses onto the right invoice and Xero reconciliation builds the matched journal entry in Well's ledger, the ledger accounts mapped and the matched customer and payment pre-filled, ready for you to post to Xero. Between 55% and 85% the candidate list is queued for review with the alternative customers ranked.

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

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

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

Razorpay carries the original transaction currency on every record and Xero natively ledgers in multiple currencies. Well preserves the original amount, applies your Xero chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Xero, so the Xero entry you post keeps both sides of the trade.

What happens if a Razorpay 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 Razorpay record. Nothing silently drops.

How does Well authenticate with Razorpay and Xero?

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

Razorpay to Xero

AvailableNative · RazorpayNative · Xero

Connect Razorpay to Xero with Well

Razorpay settles in batches; Well decomposes each payout into its component charges and forwards a clean per-customer document to Xero's inbox, with VAT and fee context attached.

Connect both toolsView all integrations

Razorpay

Source

The Razorpay integration imports payment data from India's leading payment gateway into Well.

Xero

Target

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

Why this pair

Connect Razorpay to Xero through Well so records flow without manual rework.

What Well does between Razorpay and Xero

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

Trigger from Razorpay

8 events · pick one

Well engine·recipe·When a Razorpay payment is captured

Source

from payment · live webhook

Aldercroft Trading

via Razorpay

Payment

When a Razorpay payment is captured

ch_1q5nk · 22 Apr 2026€1,284.00

Extract

6 fields read from Razorpay

6 fields read

CustomerAldercroft Trading
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordAldercroft Trading
Domainaldercroft.co.uk
Tax idGB987604123
Sales journalVE · 2026

Confidence97%

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

Post

post as draft bills

Create a draft bill in Xero

auto-posted

posted

TypeBill
VendorAldercroft Trading
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Xero

Action in Xero

1 compatible with this trigger

Create a draft bill in Xero

Reconcile Razorpay multi-currency charges to Xero entries.

01Featured

Resolve refund and dispute writebacks

Refunds and chargebacks from Razorpay land as reversing entries in Xero the moment the dispute is opened, with the original charge auto-linked so the audit trail keeps both sides of the trade. The reversal carries the dispute reason so the accounting team does not have to dig through Razorpay to write the note.

Match payouts to the bank deposit

Razorpay payouts are reconciled against the bank deposit they generate by amount, date, and currency, then the matched deposit document is forwarded to Xero with the underlying charge breakdown attached, ready for your team to post. The fee line is split out automatically so the Xero P&L sees gross revenue and processor fees as separate accounts.

Bring multi-currency charges into one ledger

Each Razorpay charge keeps its original transaction currency on the matched document. Well stamps the FX rate at the timestamp of the event and attaches both the source and converted amounts to the document forwarded to Xero, so the draft your team confirms stands up to audit.

Surface subscription renewals as recurring invoices

Recurring Razorpay charges from a subscription cycle are recognised as renewals and posted to Xero against the customer's open recurring invoice, not as a fresh sales line. The cycle start and end dates ride along on the entry so revenue recognition reports show the right service period.

12 signals and actions across Razorpay and Xero

When a Razorpay subscription cycle renews
Detects renewal cycles and links the new invoice to the recurring contract. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Invoice
When a Razorpay order is fully paid
Detects when an order is fully captured and links the underlying payments to the order reference. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a Razorpay payment is captured
Captures successful Razorpay payments with currency, fees, and order linkage. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a Razorpay invoice is paid
Pulls the paid invoice with its line items, customer, and applied tax. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Invoice
When a Razorpay payout is processed
Detects payout batches as Razorpay processes them toward your bank. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a Razorpay payment fails
Captures failed payment attempts with the error code so you can chase the customer or retry. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a Razorpay refund is processed
Detects refunds against captured payments and links back to the order. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a Razorpay dispute is created
Captures chargebacks with the contested payment and merchant response window. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
Create a draft bill in Xero
Well forwards the PDF to your Xero email-in address; Xero creates a draft bill via Hubdoc with contact, dates, totals, line items, and tax type pre-filled. You review and post.
Action·Invoice

Reference

Field mapping for Razorpay → Xero

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

Transaction fields

4 fields flow from Razorpay into Xero.

Razorpay field	Label		Xero field	Label
payment.amount	Captured amount	→	Total	Amount
payment.currency	Currency	→	CurrencyCode	Currency
payment.created_at	Capture date	→	Date	Transaction date
payment.id	Charge id	→	BankTransactionID	Bank line id

Invoice fields

4 fields flow from Razorpay into Xero.

Razorpay field	Label		Xero field	Label
invoice.number	Invoice number	→	InvoiceNumber	Invoice number
invoice.date	Issue date	→	Date	Bill date
invoice.currency	Currency	→	CurrencyCode	Currency
invoice.customer_id	Customer	→	Reference	Reference

Connect Razorpay and Xero in three steps.

1
Connect Razorpay
Click Connect with Razorpay; Razorpay's MCP server handles authorisation. Razorpay'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 Razorpay's captured payments, refunds, settlements, disputes, subscription cycles, and paid invoices and the the Xero draft bills queue populated by Hubdoc. Match candidates are scored on counterparty name, amount, currency, and reference; you approve any that need a human eye and Well saves the rule for the next batch.
- 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 Razorpay and Xero stay secure with Well

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

MCP server authStorage region per workspaceGDPR-aligned

Scopes Well requestsmcp.razorpay.com/mcp

Read Razorpay records
Scoped to captured payments, refunds, settlements, disputes, and related records. No access to anything else in your Razorpay 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 Razorpay records
Not granted. Razorpay 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 Razorpay’s admin panel.

Frequently asked questions about Razorpay and Xero on Well

01Will every Razorpay record post to Xero automatically?: Not always. Within seconds of Razorpay 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 Xero email-in address and Xero 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.
02How does Well match Razorpay records to entries in Xero?: Every Razorpay charge is scored against your open Xero sales invoices and existing customer records on customer name, amount, currency, and reference. Above 85% the charge collapses onto the right invoice and Xero reconciliation builds the matched journal entry in Well's ledger, the ledger accounts mapped and the matched customer and payment pre-filled, ready for you to post to Xero. Between 55% and 85% the candidate list is queued for review with the alternative customers ranked.
03What happens to historical Razorpay data when I first connect to Xero?: Razorpay exposes the last two 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 Xero ledger, and re-running the backfill is safe because Well tracks the Razorpay record IDs and updates existing Xero entries instead of duplicating them.
04Does Well handle multi-currency records between Razorpay and Xero?: Razorpay carries the original transaction currency on every record and Xero natively ledgers in multiple currencies. Well preserves the original amount, applies your Xero chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Xero, so the Xero entry you post keeps both sides of the trade.
05What happens if a Razorpay 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 Razorpay record. Nothing silently drops.
06How does Well authenticate with Razorpay and Xero?: Razorpay'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. Razorpay and Xero together cover multiple regions; Well's storage region is configured per workspace.