Razorpay settles one net number into your bank. Your GST invoices were never written in net.
A Razorpay, PayU or Cashfree settlement is net of processing fees, GST on those fees, and refunds already deducted — so the bank credit never equals the gross invoice amount you booked, and summing several invoices into one T+2 batch makes a one-to-one bank match impossible. Reconcile instead by pulling the gateway's settlement recon export, keyed to the order reference you set at order creation, and matching each row's gross amount, fee and tax back to the specific invoice it funds.
A customer pays the full invoice amount — taxable value plus GST — straight into Razorpay, PayU or Cashfree. What lands in your bank account two days later is neither that number nor the sum of several of them. It's a single net figure, after the gateway's own fee, the GST on that fee, and any refunds already netted out of the same batch. The payout is correct. It just isn't written in the same units as your invoice register, and the gap is where reconciliation breaks.
The netted-payout problem
Say a customer pays an invoice for ₹11,800 — ₹10,000 taxable value plus ₹1,800 GST — through a Razorpay checkout. That invoice is already final: it carries a specific invoice number, a specific gross amount, and the output tax on it is set by that invoice, not by the settlement. What arrives in your bank account roughly two working days later is not ₹11,800. It's that amount minus Razorpay's processing fee, minus the GST charged on that fee, netted together with every other payment captured in the same settlement window and reduced further by any refunds that cleared in the same batch. One bank line, one UTR (Unique Transaction Reference — the bank reference number the transfer carries across banks), funding dozens or hundreds of invoices at once.
Nothing here is wrong. The gateway settled exactly what it owes you. The problem is that your invoice register speaks in gross, invoice-by-invoice numbers, and the bank statement speaks in one net, batch-level number — and a reconciliation built on "does the bank amount match an invoice amount" will never find a match, because it's comparing two numbers that were never supposed to be equal.
What actually lands in your bank account
Per Razorpay's own settlement documentation, the standard settlement cycle is T+2 working days from the date a payment is captured — subject to bank approval, and Razorpay notes explicitly that the cycle "can vary based on your business vertical, risk factor, and other factors," so treat T+2 as the default, not a guarantee for every account. Each settlement is its own object, with an amount (what's being settled) and the utr you'll see land in your bank statement. It also carries fees and tax fields, but Razorpay's own entity documentation says both are 0 for a normal settlement, so don't read the gateway's fee off the settlement object — on a standard account it sits on each row of the recon export below, where fee and tax (GST, in practice, though Razorpay's own field documentation there just says "tax") are populated per transaction. None of those fields name an invoice. They describe the batch, not its contents.
The join key is the order reference, not the UTR
To get from one batch total to the individual invoices funding it, you need the gateway's reconciliation export, not the settlement object. Razorpay's Settlement Recon API (GET /v1/settlements/recon/combined, queried by year and month, optionally narrowed to a day) returns one row per settled transaction — payment, refund, transfer or adjustment — each carrying entity_id (the payment ID itself, for a payment row), order_id, order_receipt, settlement_id, settlement_utr, fee and tax. There is no invoice field. The closest thing to one is order_receipt — the value you supplied when you created the Razorpay order — while a refund or transfer row points back to its original payment through payment_id (null on payment rows). Each row also returns any notes you attached.
That makes the join key a decision you have to make before the sale happens, not after. When you create an order through Razorpay's Orders API, set its receipt (optional, unique, max 40 characters) to your own invoice or order number; the recon export returns it as order_receipt. Not every flow goes through the Orders API: Payment Links take a reference_id, not a receipt, and Razorpay's recon documentation doesn't say whether that value surfaces as order_receipt. For those flows, also write the invoice number into notes, which the recon export returns on every row, and confirm against your own export. A row that comes back with neither is matched by amount and timestamp instead — exactly the manual, error-prone step the receipt field exists to avoid. Cashfree's equivalent is the order_id you pass at order creation, surfaced nested inside order_details in its /settlement/recon response; PayU's equivalent is merchantTransactionId, your own reference, returned per transaction by its Settlement Detail Range API — set deliberately on all three, rather than assuming a default field does the job.
Refunds inside a settlement aren't your GST credit note
A settlement recon row typed refund tells you money moved back to a customer and reduced a payout. It does not tell you whether you issued a GST credit note for that sale. The two are governed by entirely different rules: Section 34(1), CGST Act, lets a supplier issue "one or more credit notes" for supplies made in a financial year — the provision is deliberately written at the level of the financial year's supplies, not tied one-for-one to a single invoice or a single payment event. A refund that clears through Razorpay, PayU or Cashfree is a cash-flow fact on the gateway's side; a credit note that reduces your output tax is a document you issue and declare in your own return. Treating a settlement's refund row as proof a credit note exists — or skipping the credit note because the cash already moved — breaks that link in either direction: the first reduces output tax without the document; the second over-pays it.
Net settlement is not your output tax base
The output GST on a sale is set by the supply and the invoice you issue for it (its taxable value and the tax on it), not by when, or in what net figure, the gateway settles it. Booking "bank receipt" as revenue, or netting the gateway's fee straight into the sales line instead of recording it as a separate purchase, understates both your outward turnover and an input-side expense you're entitled to claim credit on. The outward-supply figures that feed GST reconciliation and GSTR-3B's Table 3.1 need to trace back to gross invoice value, invoice by invoice — the settlement batch is a cash-matching exercise that sits downstream of that, never a substitute for it.
The gateway's fee is a separate purchase, with its own ITC
The fee and tax fields in a settlement aren't a deduction you just absorb — they're the gateway's own taxable supply to you, for processing the payment, and it comes with a tax invoice for those fees. That invoice only reaches your GSTR-2B if the gateway has your GSTIN on file (on Razorpay: Account & Settings → GST Details) — worth confirming once, since it's easy to set up and forget. From there it runs through the exact same credit pipeline as any other vendor bill: it has to actually reach your GSTR-2B before the credit is yours to claim, and ITC on it is subject to the Section 16 conditions — a tax invoice (s.16(2)(a)); the supplier reporting it and it being communicated in your GSTR-2B (s.16(2)(aa), applied through Rule 36(4)); receipt of the service (s.16(2)(b)); the tax actually paid to the government (s.16(2)(c)); and your own return filed (s.16(2)(d)) — claimed no later than 30 November following the end of the financial year (s.16(4)). If the payment gateway's own fee invoice goes missing from a monthly reconciliation because it got silently netted out of the settlement arithmetic instead of booked and tracked as a purchase, that's real, recoverable credit quietly left unclaimed.
PayU and Cashfree: same mechanics, different field names
The structural problem is identical across gateways; the vocabulary isn't. PayU India's Settlement Detail Range API (/settlement/range, up to a 3-day window, paginated) returns each UTR's gross amount and transaction count, then one row per transaction carrying your own merchantTransactionId, PayU's payuId, the gross amount, merchantServiceFee, merchantServiceTax (broken into SGST/CGST/IGST) and merchantNetAmount. Cashfree's POST /pg/settlement/recon endpoint returns event-level records — PAYMENT, REFUND, DISPUTE, CHARGEBACK and their reversals, plus OTHER_ADJUSTMENT — each nesting your order_id (inside order_details), cf_payment_id (inside payment_details) and cf_settlement_id/settlement_utr (inside settlement_details). The per-transaction fee and tax are payment_service_charge/payment_service_tax, not Razorpay's fee/tax; the plain service_charge/service_tax fields are settlement-level totals, not per-transaction. Cashfree's own API reference also varies these field names across API versions, so match the response you're parsing to the x-api-version you actually called, not to whichever version a blog post or your own memory assumes.
Building the reconciliation, step by step
- Fix the join key before go-live, not after. Set Razorpay's Orders-API
receipt(andnoteson flows like Payment Links), Cashfree'sorder_id, or PayU'smerchantTransactionIdto your invoice or order number. - Pull the recon export for the period — Razorpay's
/v1/settlements/recon/combinedby year/month/day, PayU's Settlement Detail Range API by date, or Cashfree's/settlement/reconby settlement ID, UTR or date range. - Match each payment row to its invoice on the join key, and reconcile gross amount, fee and tax against the taxable value and GST you booked at invoice issuance — not against the net settlement total.
- Hold refund rows separately. Confirm a Section 34 credit note was actually issued and reported in GSTR-1 for the refunded supply before treating output tax as reduced.
- Book the gateway's own fee-and-tax invoice as a purchase, and track it through GSTR-2B and IMS like any other vendor bill — don't let it disappear into the settlement netting.
- Flag unmatched UTRs and stray settlement amounts for manual review rather than writing them off against the nearest invoice by amount alone.
Doing this by hand works at a few dozen invoices a batch. It stops working the moment a growing business is running several hundred orders through a T+2 cycle every working day — matching net settlement UTRs back to gross invoice amounts, batch by batch, invoice by invoice, is exactly the kind of continuous, reference-by-reference check that's painful to do by hand once the batches outrun the hours anyone has to sit and do it.
How Recoup fits
Recoup doesn't touch the settlement side — Razorpay, PayU and Cashfree own that layer, and getting the join key right at order creation is still the first thing that has to happen. What Recoup does is sit on the reconciliation side of the same chain: matching your purchase register against what actually lands in GSTR-2B, continuously, invoice by invoice — including the gateway's own fee invoices, and the vendor credit that quietly goes missing when any upstream reconciliation, settlement or otherwise, nets something out instead of tracking it.
A netted settlement number isn't a reconciled one.
Recoup reconciles your purchase register against GSTR-2B continuously and names the exact invoice behind credit that never arrived.
Book a demo →Related guides
GST reconciliation: the 2026 guide for finance teams
The four reconciliations that decide your input tax credit, and why matching the bank is only one of them.
Auto-categorising bank transactions in Zoho Books
The rule pattern that silently breaks your Rule 37 evidence chain when a bank feed is matched by amount alone.
GST reconciliation for retail, e-commerce & FMCG
Why high invoice volume turns every reconciliation gap, including a netted settlement, into a volume problem first.
Input Tax Credit (ITC)
The Section 16 conditions a gateway's own fee invoice has to clear before you can claim credit on it.