Razorpay
This screen has two parts. The top part says how a Razorpay payment is recorded in the books of this business unit. The part below, Collect payments online, lets customers pay your invoices through your own Razorpay account.
Video coming soon: Razorpay set-up in 4 minutesWhere to find it
Configuration › Finance › RazorpayThe row appears only for administrators of your own organisation. Platform staff acting inside your organisation do not see it.
Quick set-up
- Open Configuration › Finance › Razorpay. If you see "Razorpay is not enabled for this business unit", the platform team must turn it on first; you can read the page but not change it.
- Tick Record Razorpay payments in these books, pick the Service item on the invoice and Deposit to, then click Save.
- In Collect payments online, pick the three ledgers and click Save and connect.
- Copy the Webhook URL into your Razorpay Dashboard, then save the Webhook secret.
- Enter your Key id, Key secret and Razorpay account id and click Save keys. New keys take effect after the delay shown.
Done. Both sections show a saved message, and the Online payments line reads On.
Full guide
Record Razorpay payments
Each payment becomes an invoice and a receipt in this business unit.
Fields in this section
| Field | Default | What it changes |
|---|---|---|
| Record Razorpay payments in these books | Off | Off keeps your choices saved without using them yet. |
| Service item on the invoice | None | Required when on. One of your active Services items; a search box narrows the list. |
| Deposit to | None | Required when on. The bank or cash ledger the receipt records the money in. |
| Department | Admin (default) | The department the invoice is raised under. |
| Name in the email | Blank (uses the business unit's trade name) | Sender name the payer sees, up to 80 characters. |
| Email the invoice and receipt to the payer | On | Off still records both but emails nobody. |
Collect payments online: where payments are booked
Fields in this section
| Field | Default | What it changes |
|---|---|---|
| Razorpay clearing ledger | None | A Bank ledger holding the money between the customer's payment and Razorpay's settlement. |
| Bank ledger | None | The bank account Razorpay settles into. Must differ from the clearing ledger. |
| Fee expense ledger | None | The expense ledger Razorpay's fee is booked to. |
| How Razorpay's fee is booked | Book the fee from each settlement | The other choice is "Book the fee from Razorpay's monthly invoice". With per settlement, do not also enter the monthly invoice as a Bill, or the fee is counted twice. With monthly invoice, enter Razorpay's tax invoice as a supplier Bill and pay it through the fees-payable ledger. |
| GST on Razorpay's fee | Automatic (from this business unit's state) | Shown for per settlement. Choose Automatic, CGST + SGST or IGST. Check it against Razorpay's invoice. |
| Razorpay fees payable ledger | None | Shown for monthly invoice. A Bank ledger holding the fee until you pay the invoice. |
| Payment links expire after (days) | 15 | Whole days from 1 to 30. The default offered when a link is sent. |
| Let customers pay part of the amount | Off | The default for new links; changeable on each link. |
The save button reads Save and connect the first time, then Save.
Connection, keys and webhook
Shown once the business unit is connected.
Fields in this section
| Item | What it does |
|---|---|
| Online payments On or Paused | Pause stops new payment links; links already sent stay payable until they expire and are still recorded. Every admin is emailed. Switch on resumes. |
| Webhook URL and Copy | Paste into Razorpay Dashboard, Webhooks, with the events payment_link.paid, payment_link.partially_paid, settlement.processed, refund.created and payment.dispute.created. |
| Payment events | The last payment event received, with any error or a bad-signature warning. |
| Delay before new keys take effect (hours) | Default 48, from 24 to 168. Every admin is emailed when keys change and can Block them during this time. Save delay saves it. |
| Key id, Key secret, Razorpay account id | From Razorpay Dashboard, Account and Settings, API keys. Checked with Razorpay when you click Save keys and never shown again. Each key set shows as Waiting, In use, Blocked or Retired, with Block or Retire where allowed. |
| Webhook secret | The secret you set on the Razorpay webhook. It works as soon as saved. Revoke removes one. |
| Posting key | Reissuable from the page; the notes say whether receipts are posted with the server's key. |
What changes for your team
Customers can pay a sent link; the payment arrives as a receipt against the invoice, and settlements are booked to your bank. Finance sees the fee as an expense, per settlement or from the monthly invoice.
When changes take effect
Settings apply to payments received after saving. New keys wait for the delay you set and can be blocked meanwhile. Webhook secrets work immediately. Earlier payments are not rewritten.
What is not on this screen
No export, import or payment list: payments appear in your normal receipts and invoices. Razorpay account keys are never displayed after saving.
On mobile
There is no Razorpay screen on the phone. Set it up in the admin portal in a web browser; receipts from online payments then show on the phone like any other receipt. The Android app is on Google Play. The iPhone app is coming soon to the App Store. Same on iPhone and Android.
Problems and fixes
"Razorpay is not enabled for this business unit."
The platform team turns Razorpay on for a business unit. Until then the settings are visible but cannot be changed.
"The clearing ledger and the bank ledger must be different accounts."
Pick two different Bank ledgers.
"Only this organisation's own admins can change this."
Platform staff cannot change another organisation's Razorpay settings. A tenant administrator of the organisation must do it.
The webhook shows a bad-signature warning
The webhook secret in Razorpay does not match the one saved here. Save the same secret in both places.
Related
- Chart of Accounts for the ledgers
- Role permissions