Blog · Payments
Razorpay and ERPNext: a sane integration checklist
22 April 2026 · Shivanand Banahatti
India teams often start with manual Payment Entry creation after checking the Razorpay dashboard. That works until volume grows. A durable integration ties each settlement to sales documents, handles partial failures and refunds, and gives finance a daily reconciliation they can defend in audit — without re-keying.
1. Map the money path
Clarify whether you collect against Sales Orders, Invoices, or standalone payment links. Decide the GL accounts for gateway clearing, charges, and TDS if applicable. If this mapping is fuzzy, automation will amplify mistakes.
2. Webhooks and idempotency
Razorpay sends asynchronous events. Your ERPNext side should treat webhook delivery as the trigger to create or update payment records — and be idempotent so retries do not duplicate entries. Log raw payloads for the first weeks in production.
3. Reconciliation rhythm
Align settlement batches with bank credits. ERPNext should show unmatched payments, gateway fees, and rounding differences in one place. Finance signs off on a weekly template before you add more channels.
4. Refunds and chargebacks
Define how a refund in Razorpay updates the invoice or credit note in ERPNext. Leaving refunds dashboard-only guarantees period-end surprises.
5. Scope integrations realistically
Payment work is often bundled into a larger go-live. For how integrations affect overall effort in India, see implementation cost drivers. I take integration-heavy programmes through services with explicit UAT — contact if you want a review of your current flow.