The right choice when
- One bank credit covers hundreds of payments and nobody can say which.
- Fees and GST on fees are booked as one rough entry.
- Refunds and chargebacks make month end slow.
Integration · Razorpay + Tally / Zoho Books
Razorpay settlements, matched. Payments, fees and GST, split.
Each Razorpay settlement is split into the payments it contains, the fees and the GST on them, and matched to your invoices in Tally or Zoho Books, so the bank entry finally explains itself.
- Razorpay
A settlement lands in your bank.
- Connector
Fetches its payments, fees, refunds and GST, and matches each to an invoice.
- Your books
Entries wait for review; anything unmatched is listed.
Unmatched money is listed, never guessed.
01 / Is this the one
Is this the connection you need?
It suits a business taking many payments through Razorpay.
Look elsewhere when
- You take a few payments a month.
- Your invoices are not in Tally or Zoho Books, or not raised at all.
- Your accountant already gets this from a tool you pay for.
02 / What the work covers
What the work covers.
Settlement splits first, then invoice matching.
- 01
Rules with your accountant
How fees, GST on fees, refunds and disputes are booked.
- 02
Razorpay access
A read-only API key, and webhooks for settlements.
- 03
Matching
Each payment matched to an invoice by its reference, with clear rules for partial and missing ones.
- 04
Review and handover
Entries held for review, an exceptions list, and the code handed to you.
03 / Limits and risks
Where it can go wrong.
Matching needs a reference
A payment with no invoice reference can only be matched by amount and date, which is a guess. We list those for a person instead.
Two systems will disagree sometimes
A product renamed in one, an invoice deleted in the other, a tax rate changed mid-year. We agree with you which system wins, and a sync that fails is logged and retried, never skipped quietly.
Tally has to be reachable
Tally's data interface runs on the computer or server where Tally runs. That machine has to be on and connected, or a small agent beside it copies the data out on a schedule.
04 / What we can show
The same checking, in our hotel product.
Reconciliation^, our product for hotels, checks bookings against what booking sites charged and billed and flags each difference. It only reports, and lists a check it could not run as not checked.
What this does not show
Results. Reconciliation^ is in early access, and we have no published figure for what it has found.
05 / What to do next
Price it or talk it through.
The first step is a free scoping call about your payment volume and how settlements are booked today. A written estimate follows.
01
Estimate the cost
02A price range for your build in four steps.
Custom software development
03Software built around how you work.
Website forms into HubSpot
04Every enquiry saved, sent to HubSpot and retried.
Shopify orders into Tally
05Shopify sales, taxes and payouts posted to Tally.
All integrations
Every connection we build.
A little clarity
Before matching Razorpay to your books.
Can we see it working?
Yes. This connection is built and tested by our team, and we can demo it for you on a free call before you decide anything.
Does it work with other gateways?
Yes. Stripe, PayU, Cashfree and others publish settlement data in a similar way; the rules are the same.
Does it change anything in Razorpay?
No. It reads with a read-only key.
Is there not an app for this already?
Sometimes there is, and if a vendor's own app or a no-code tool does what you need, use it: it is cheaper. A built connection earns its place when the rules are yours, such as which records go, who sees what, what happens when the two systems disagree, or when the volume makes per-task pricing expensive.
What does it cost?
It depends on volume and how many gateways and books are involved. First releases at NSDBytes start from $5,000. The project cost estimator gives a range, and a fixed quote follows a free scoping call. Charges from the services themselves, such as WhatsApp messages, API plans and hosting, are billed by those providers and are separate.
Who owns the connection once it is built?
You do. The code, the server it runs on and the accounts with each provider are yours once the final invoice is paid. We can run and maintain it afterwards if you want, but you are never locked in.
Start wherever you are
Bring last month's settlements.
We'll show you how each one would split and match.
Want certainty before you commit? Start with a scoping project, $500