What Razorpay data does Well pull into Bill.com?

Razorpay streams captured payments, refunds, settlements, disputes, subscription cycles, and paid invoices to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Bill.com as bills via email-in inbox, with vendor, invoice number, amount, and due date populated by Bill.com's IVA OCR, with the Razorpay event ID preserved on the entry for audit.

How often does Razorpay data sync to Bill.com?

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

How does Well match Razorpay records to entries in Bill.com?

Well scores every candidate match between Razorpay records and existing Bill.com entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Bill.com updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.

Does Well handle multi-currency records between Razorpay and Bill.com?

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

Can I customise which Razorpay fields are sent to Bill.com?

The default mapping connects each Razorpay record to the Bill.com bill shape (vendor, amount, due date, approval policy). Settings let you override the vendor source, swap default approvers, attach a different document on the bill, or pull GL codes from your connected data. Mapping versions are immutable for already-paid bills so audit traces stay intact.

How does Well authenticate with Razorpay and Bill.com?

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

Razorpay to Bill.com

AvailableNative · RazorpayNative · Bill.com

Connect Razorpay to Bill.com with Well

Stop chasing reimbursements: Razorpay outbound payments arrive in Bill.com pre-matched to the originating context inside Well, with the source receipt attached on every bill.

Connect both toolsView all integrations

Razorpay

Source

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

Bill.com

Target

The Bill.

Why this pair

Razorpay handles inbound revenue collection from customers; Bill.

com handles outbound vendor payments. Both sit on opposite ends of the SMB AP/AR workflow and rarely talk. Connecting Razorpay to Bill. com through Well surfaces the Razorpay settlement balance alongside the Bill. com payment queue, with revenue concentration and vendor disbursement on one reconciled view. Razorpay's MCP server pushes settlement events to Well; Bill. com structures the bill for the configured approval chain before scheduling payment.

What Well does between Razorpay and Bill.com

One-way: Razorpay into Well into Bill.com
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

Tessellate Design

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

CustomerTessellate Design
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordTessellate Design
Domaintessellate.studio
Tax idGB432109876
Sales journalVE · 2026

Confidence97%

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

Post

schedule as bills

Create a bill in Bill.com inbox

auto-posted

posted

TypeBill
VendorTessellate Design
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Bill.com

Action in Bill.com

1 compatible with this trigger

Create a bill in Bill.com inbox

Bridge Razorpay payouts to Bill.com reimbursements.

01Featured

Match a payment to the invoice it settled

Well reads payments and invoices from Razorpay, matches each payment to the invoice it settled, and forwards the reconciled document to Bill.com's email-in address.

Resolve the customer behind a payment

Well matches the company on a Razorpay payment against your prior history and carries the resolved customer onto the document forwarded to Bill.com.

Surface payments with no matching invoice

A Razorpay payment that finds no invoice is held in Well's queue with its customer and amount, so nothing reaches Bill.com without a match behind it.

Keep the payment attached

The Razorpay payment Well matched stays linked to the document sent to Bill.com, so each record traces back to the settlement behind it.

12 signals and actions across Razorpay and Bill.com

When a Razorpay payment is captured
Captures successful Razorpay payments with currency, fees, and order linkage.
Trigger·Transaction
When a Razorpay payout is processed
Detects payout batches as Razorpay processes them toward your bank.
Trigger·Transaction
When a Razorpay subscription cycle renews
Detects renewal cycles and links the new invoice to the recurring contract.
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.
Trigger·Transaction
When a Razorpay invoice is paid
Pulls the paid invoice with its line items, customer, and applied tax.
Trigger·Invoice
When a Razorpay refund is processed
Detects refunds against captured payments and links back to the order.
Trigger·Transaction
When a Razorpay payment fails
Captures failed payment attempts with the error code so you can chase the customer or retry.
Trigger·Transaction
When a Razorpay dispute is created
Captures chargebacks with the contested payment and merchant response window.
Trigger·Transaction
Attach the source PDF to the Bill.com bill
The forwarded PDF is the bill record itself in Bill.com's inbox.
Action·Document

Reference

Field mapping for Razorpay → Bill.com

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

Transaction fields

4 fields flow from Razorpay into Bill.com.

Razorpay field	Label		Bill.com field	Label
payment.amount	Captured amount	→	amount	Amount
payment.currency	Currency	→	currency	Currency
payment.created_at	Capture date	→	process_date	Process date
payment.id	Charge id	→	payment_id	Payment id

Invoice fields

4 fields flow from Razorpay into Bill.com.

Razorpay field	Label		Bill.com field	Label
invoice.number	Invoice number	→	invoice_number	Invoice number
invoice.date	Issue date	→	invoice_date	Invoice date
invoice.currency	Currency	→	currency	Currency
invoice.customer_id	Customer	→	external_id	External id

Company fields

3 fields flow from Razorpay into Bill.com.

Razorpay field	Label		Bill.com field	Label
customer.name	Customer name	→	vendor_name	Vendor name
customer.email	Email	→	email	Email
customer.id	Customer id	→	vendor_id	Vendor id

Connect Razorpay and Bill.com 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 Bill.com inbox awaiting approval. Each payout is paired to its scheduled vendor payment by date and total; failed transfers reverse the linked payment automatically so the schedule self-corrects.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Bill.com
In Bill.com, open Settings > Developer > API keys and create a key paired with your developer ID. Paste the key into Well; Bill.com's discovery endpoints are reached over TLS 1.3 and the secret is never echoed in the UI.
- AuthConnect
- First sync~10 min

How Razorpay and Bill.com 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 Bill.com 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 Bill.com inbox
Well forwards the extracted document to your Bill.com email-in address; Bill.com reads bills via email-in inbox, with vendor, invoice number, amount, and related records from it and you review and post. No write credential to Bill.com 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 Bill.com on Well

01What Razorpay data does Well pull into Bill.com?: Razorpay streams captured payments, refunds, settlements, disputes, subscription cycles, and paid invoices to Well over its MCP server. After Well resolves the counterparty and assigns a confidence score, the matched record posts to Bill.com as bills via email-in inbox, with vendor, invoice number, amount, and due date populated by Bill.com's IVA OCR, with the Razorpay event ID preserved on the entry for audit.
02How often does Razorpay data sync to Bill.com?: Razorpay 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 Bill.com within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
03How does Well match Razorpay records to entries in Bill.com?: Well scores every candidate match between Razorpay records and existing Bill.com entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Bill.com 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 Razorpay and Bill.com?: Razorpay carries the original transaction currency on every record and Bill.com natively ledgers in multiple currencies. Well preserves the original amount, applies your Bill.com chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Bill.com, so the Bill.com entry you post keeps both sides of the trade.
05Can I customise which Razorpay fields are sent to Bill.com?: The default mapping connects each Razorpay record to the Bill.com bill shape (vendor, amount, due date, approval policy). Settings let you override the vendor source, swap default approvers, attach a different document on the bill, or pull GL codes from your connected data. Mapping versions are immutable for already-paid bills so audit traces stay intact.
06How does Well authenticate with Razorpay and Bill.com?: 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 Bill.com email-in address once it clears the matching threshold; Bill.com creates the draft record from it and you confirm and post it. Well holds no write credential to Bill.com. Tokens are encrypted at rest and in transit under TLS 1.3. Razorpay and Bill.com together cover multiple regions; Well's storage region is configured per workspace.