Will every Razorpay record post to QuickBooks 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 QuickBooks email-in address and QuickBooks 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 Razorpay data when I first connect to QuickBooks?

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

How does Well prevent duplicates when posting Razorpay records to QuickBooks?

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

Can I customise which Razorpay fields are sent to QuickBooks?

The default mapping covers every Razorpay field your QuickBooks chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields QuickBooks does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in QuickBooks is left exactly as it stands.

What happens if I disconnect Razorpay or QuickBooks?

Disconnecting Razorpay stops the flow at the source. Well asks the Razorpay MCP server to revoke the access token; Razorpay returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in QuickBooks is QuickBooks's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.

How does Well authenticate with Razorpay and QuickBooks?

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

Razorpay to QuickBooks

AvailableNative · RazorpayNative · QuickBooks

Connect Razorpay to QuickBooks with Well

Replace the monthly payout-to-ledger spreadsheet: Well watches Razorpay, matches it against your existing records, and forwards the resulting documents to QuickBooks as soon as the funds clear.

Connect both toolsView all integrations

Razorpay

Source

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

QuickBooks

Target

The QuickBooks connection delivers documents into QuickBooks Online through its @qbodocs.

Why this pair

Razorpay handles inbound payments primarily for Indian merchants; QuickBooks Online accepts emailed PDFs at @qbodocs.

com and creates bills or receipts from them. Connecting Razorpay to QuickBooks through Well matches each Razorpay capture inside its own ledger with FX context on the value date and GST broken out per state, then forwards the matched document to QuickBooks' email-in. Razorpay's MCP server pushes settlement events to Well; QuickBooks creates the bill or receipt and your team confirms tax codes and bank reconciliation in the For Review tab.

What Well does between Razorpay and QuickBooks

One-way: Razorpay into Well into QuickBooks
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

Sunrise Coffee Co.

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

CustomerSunrise Coffee Co.
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordSunrise Coffee Co.
Domainsunrisecoffee.com
Tax idUS12-3456789
Sales journalVE · 2026

Confidence97%

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

Post

post as bills and receipts

Route the record to the For Review tab

auto-posted

posted

TypeReview
VendorSunrise Coffee Co.
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto QuickBooks

Action in QuickBooks

2 compatible with this trigger

Route the record to the For Review tabCreate a bill or receipt in QuickBooks

Reconcile Razorpay multi-currency charges to QuickBooks entries.

01Featured

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 QuickBooks with the underlying charge breakdown attached, ready for your team to post. The fee line is split out automatically so the QuickBooks 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 QuickBooks, so the draft your team confirms stands up to audit.

Surface jurisdiction for tax-code routing

Razorpay charges carry the customer billing country in their metadata; Well stamps the jurisdiction (EU / US / AU / etc.) on the document forwarded to QuickBooks, with reverse-charge context on cross-border charges so your team can apply the right tax code in QuickBooks in one click.

Decompose fees from a card payment

Every Razorpay card charge is split inside Well into the gross amount, the processor fee, and the net deposit. The fee context is broken out on the document forwarded to QuickBooks, ready for your team to route it onto the processor-fee account on confirmation.

12 signals and actions across Razorpay and QuickBooks

When a Razorpay payout is processed
Detects payout batches as Razorpay processes them toward your bank. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
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 QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a Razorpay refund is processed
Detects refunds against captured payments and links back to the order. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a Razorpay invoice is paid
Pulls the paid invoice with its line items, customer, and applied tax. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Invoice
When a Razorpay dispute is created
Captures chargebacks with the contested payment and merchant response window. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
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 QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a Razorpay payment is captured
Captures successful Razorpay payments with currency, fees, and order linkage. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Transaction
When a Razorpay subscription cycle renews
Detects renewal cycles and links the new invoice to the recurring contract. Forwarded to QuickBooks' @qbodocs.com email-in; QuickBooks creates a bill or receipt with vendor, date, and amount populated.
Trigger·Invoice
Attach the source document to the QuickBooks record
The forwarded PDF is stored on the QuickBooks bill or receipt as the source.
Action·Document

Reference

Field mapping for Razorpay → QuickBooks

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

Transaction fields

4 fields flow from Razorpay into QuickBooks.

Razorpay field	Label		QuickBooks field	Label
payment.amount	Captured amount	→	Amount	Amount
payment.currency	Currency	→	CurrencyRef	Currency
payment.created_at	Capture date	→	TxnDate	Transaction date
payment.id	Charge id	→	PrivateNote	Source id

Invoice fields

4 fields flow from Razorpay into QuickBooks.

Razorpay field	Label		QuickBooks field	Label
invoice.number	Invoice number	→	DocNumber	Doc number
invoice.date	Issue date	→	TxnDate	Bill date
invoice.currency	Currency	→	CurrencyRef	Currency
invoice.customer_id	Customer	→	PrivateNote	Source id

Connect Razorpay and QuickBooks 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 QuickBooks For Review inbox. 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 QuickBooks
Click Connect with QuickBooks; you approve the connection inside QuickBooks Online and authorise read-only discovery of your existing records so Well can match against them when forwarding documents. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your QuickBooks Online.
- AuthConnect
- First syncup to an hour

How Razorpay and QuickBooks 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 QuickBooks 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 QuickBooks inbox
Well forwards the extracted document to your QuickBooks email-in address; QuickBooks reads bills or receipts via email-in at the @qbodocs.com address, with vendor, date, and amount populated by QuickBooks from it and you review and post. No write credential to QuickBooks 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 QuickBooks on Well

01Will every Razorpay record post to QuickBooks 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 QuickBooks email-in address and QuickBooks 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.
02What happens to historical Razorpay data when I first connect to QuickBooks?: 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 QuickBooks ledger, and re-running the backfill is safe because Well tracks the Razorpay record IDs and updates existing QuickBooks entries instead of duplicating them.
03How does Well prevent duplicates when posting Razorpay records to QuickBooks?: Razorpay sends each event with a stable resource ID that Well tracks against the QuickBooks ledger. Webhook replays (which Razorpay can issue for delivery retries) are recognised by ID and either skipped or used to update the existing QuickBooks entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
04Can I customise which Razorpay fields are sent to QuickBooks?: The default mapping covers every Razorpay field your QuickBooks chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields QuickBooks does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in QuickBooks is left exactly as it stands.
05What happens if I disconnect Razorpay or QuickBooks?: Disconnecting Razorpay stops the flow at the source. Well asks the Razorpay MCP server to revoke the access token; Razorpay returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in QuickBooks is QuickBooks's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.
06How does Well authenticate with Razorpay and QuickBooks?: 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 QuickBooks email-in address once it clears the matching threshold; QuickBooks creates the draft record from it and you confirm and post it. Well holds no write credential to QuickBooks. Tokens are encrypted at rest and in transit under TLS 1.3. Razorpay and QuickBooks together cover multiple regions; Well's storage region is configured per workspace.