Platform Settlement Reconciliation for D2C and E-Commerce
Marketplaces and payment gateways settle net of MDR, GST on MDR, TCS, commissions, and platform fees — aggregated across days and stripped of order-level detail. This cluster covers every major Indian gateway and marketplace.
Platform settlements are the hardest reconciliation surface most Indian finance teams encounter. A single daily Razorpay deposit represents 2,400 customer payments, each net of MDR, each with GST on the MDR deducted separately, each potentially held for T+1 or T+2, each subject to chargebacks or refunds that net against future settlements. Amazon and Flipkart pile on: seller-side commission bands, storage fees, advertising cross-charges, returns, and TCS under Section 52.
Generic reconciliation tools match rows. Platform settlement reconciliation needs batch disaggregation (one bank credit → N orders), fee unpacking (MDR + GST on MDR + TCS + platform fee), timing lag handling (T+1 to T+30), and chargeback netting. Without those primitives, reconciliation collapses into Excel and the team ends up reconciling a rolling 90-day window manually.
This cluster covers every major Indian gateway (Razorpay, PayU, Cashfree, Amazon Pay, Stripe India, UPI) and every major marketplace (Amazon, Flipkart, Meesho), plus the cross-cutting surfaces — chargebacks, MDR audit, marketplace fee reconciliation, refund flows, and TCS on e-commerce operators under GST Section 52.
Chargeback Dispute Won: Recovery Reconciliation Label Gap
When a streaming merchant wins a chargeback dispute, the acquirer returns the funds — but most reconciliation systems have no distinct label for a chargeback-reversed credit. It gets bucketed as a refund reversal or a settlement adjustment, and the ledger loses the audit trail. This guide walks the full chargeback lifecycle for OTT and subscription businesses under the RBI Chargeback Framework 2018, with the GL entries and reconciliation controls each state needs.
Mid-Month MDR Rate Renegotiation: Two Rates Both Correct
When an MDR renegotiation lands on 15 July, the July settlement file legitimately contains two rates: the old 2.4% for transactions captured 1–14 July and the new 2.0% from 15 July onward. Applying one flat rate across the month produces a phantom variance in either direction. Correct reconciliation requires a rate-schedule table, per-transaction timestamp lookup, and a tolerance-based match that accepts both rates as valid within their effective windows.
Premium Card Fee Hidden in UPI Appearance: Fee-Schedule Extraction
Zero MDR on UPI and RuPay Debit is fixed by the 30/12/2019 notification. But a 'Pay via UPI' tile in an OTT subscription checkout can route a premium credit card through UPI-on-cards rails at 1.5–2.4% MDR. Fee reconciliation that treats the tile label as the fee driver — instead of extracting network, card type, and BIN from the settlement line — under-books gateway costs and under-recovers input tax credit on the merchant discount rate.
Refund Landing After PG Settlement: Negative-Net Cycle Reconciliation
For streaming and OTT subscription businesses in India, refund reconciliation gets messy when the refund is initiated days or weeks after the original transaction has already settled. The refund becomes a negative adjustment in a later settlement cycle, and finance teams must reconcile that cycle-shifted deduction against the merchant refund ledger, the customer credit, the Section 34 CGST credit note, and the proportional GST reversal — all while keeping the original cycle's revenue and ITC positions clean.
One PG Settlement Arriving as Two Bank Credits: Split Reconciliation
A payment gateway confirms a single settlement, but two bank credits land in the merchant's HDFC or ICICI account on the same day. Rules-based reconciliation must sum the two credits back to one PG settlement expected line — not flag a duplicate credit, not raise a missing-second alarm, and not confuse this with an intentional marketplace split settlement. This guide covers the India-specific split logic, worked example, breakages, and platform handling for streaming, subscription, and PG-heavy businesses.
Subscription vs Ad Revenue Reconciliation: Two Ind AS 115 Streams
Streaming and OTT platforms in India carry two economically distinct revenue streams that flow through the same payment gateway rail: subscription (recognised over the subscription period under Ind AS 115.35 as an over-time performance obligation) and advertising (recognised on impression or view under Ind AS 115.32 as a point-in-time obligation). Both attract GST at 18% but under different SAC codes (998431 for OIDAR/subscription vs 998365 for advertising). Reconciling PG settlement lines back to two separate GL revenue schedules — and forward to a split GSTR-1 SAC declaration — is the core multi-stream reconciliation problem for hybrid streaming platforms.
Test Transaction Ghost: The ₹1 Transaction That Leaves 98 Paise in Production
A single ₹1 test transaction accidentally executed against production Razorpay, PayU, or Cashfree keys creates a 98-paise ghost in the settlement file — no invoice, no customer, no subscription. Over months, hundreds of such ghosts accumulate into an unexplained variance that finance teams either write off or absorb silently into month-end. This guide covers detection logic, quarantine workflow, and why absorption is the wrong answer under GST audit conditions.
Weekend and Holiday Settlement Stretch: 4-Day Cycle Reconciliation
Payment gateways in India settle on T+1 or T+2 bank working days. A long weekend, national holiday, or RBI clearing house holiday can stretch the cycle to T+4 or T+5, and a naive reconciliation flags the missing days as failed settlements. This guide covers the expected-settlement-cycle table, the RBI clearing calendar overlay, and the settlement-arrival trigger that keeps streaming and OTT platforms compliant when the calendar breaks the standard cadence.
Marketplace Fee Audit: Identifying Revenue Leakage in E-Commerce Settlement Reports
E-commerce sellers lose 2-3% of gross payment volume to fee errors that never get audited. Commission category misclassification, volumetric weight overcharges, incomplete return reversals, and incorrect TCS calculations compound silently across thousands of orders. For a seller processing ₹5 crore GMV per month, that translates to ₹10-15 lakh in annual leakage from settlement report discrepancies alone.
Amazon Pay Settlement Reconciliation: Marketplace TCS, MDR, and Weekly Payouts
Amazon Pay settlement reconciliation differs depending on whether you are a third-party seller on Amazon's marketplace or a merchant using Amazon Pay as a checkout method on an external website. For marketplace sellers, the TCS deduction under GST Section 52 — applied at 1% on the taxable value of each transaction — creates a compliance reconciliation step that pure payment gateway settlements do not have. Both modes require reconciling a net settlement credit to transaction-level detail, but the data sources and compliance steps are materially different.
Cashfree Settlement Reconciliation: T+1 Payouts and Exception Handling
Cashfree settlement reconciliation is the process of matching Cashfree's NEFT payouts — which arrive on a T+1 cycle as a standard feature — to individual orders in the settlement report. The faster settlement cycle creates a specific challenge: finance teams running day-old order exports against same-day bank credits find themselves reconciling against data that has not yet been consolidated. Cashfree also offers a separate Payouts product for bulk disbursements, which requires its own reconciliation track distinct from collection settlements.
Chargeback reconciliation in India — matching disputes, deductions, and representment
Chargeback reconciliation in India requires matching each negative line item in a payment gateway settlement report to the original transaction, classifying it as a chargeback versus a refund or MDR adjustment, and tracking the dispute window and representment result. Finance teams at merchants operating across Razorpay, PayU, and Cashfree face this challenge every settlement cycle. Without order-level matching, chargeback deductions are routinely written off as unexplained variances.
Flipkart Seller Settlement Reconciliation: TCS, Fees, and Returns
Flipkart seller settlement reconciliation requires unpacking a single weekly bank credit into four separate deduction categories before any ITC or TCS adjustment can be claimed. Each category — marketplace commission, TCS under Section 52, return adjustments, and shipping charges — maps to a different ledger entry and a different compliance obligation.
MDR fee reconciliation — verifying gateway charges against contracted rates
MDR fee reconciliation in India is the process of verifying that every Merchant Discount Rate deduction in a payment gateway settlement matches the contracted rate for that specific transaction type — credit card, debit card, UPI, net banking, or international card. MDR is not a single flat rate, and billing errors where the wrong rate is applied to a transaction type are a consistent source of recoverable cost. This guide covers the reconciliation workflow and the ITC implications of GST on MDR.
Meesho Seller Reconciliation: Handling High Return Rates and TCS Deductions
Meesho seller reconciliation is complicated by two factors that operate independently of each other: high return rates in fashion and lifestyle categories that can reduce weekly settlements to near-zero, and TCS deducted on forward sales that still appears in GSTR-2B even when the underlying order is returned. Tracking these two flows separately is the core of the reconciliation task.
PayU Settlement Reconciliation: Matching Nodal Bank Credits to Transaction-Level Payouts
PayU settlement reconciliation is the process of reconciling NEFT credits from PayU's nodal bank account to individual transaction records in the PayU settlement report. Every PayU settlement credit in your bank account represents a batch of captured transactions, net of MDR and GST on MDR — and the 18% GST charged on MDR is recoverable as ITC for registered businesses, but only if the settlement report is reconciled to the GST invoice PayU issues.
Razorpay Settlement Reconciliation: Unpacking Net Payouts to Individual Orders
Razorpay settlement reconciliation is the process of matching a single NEFT bank credit — the net payout Razorpay sends every settlement cycle — back to the individual orders, fee deductions, and refund adjustments that constitute it. The settlement report, exported from the Razorpay Dashboard, is the primary document for this work. Without it, the bank credit is an opaque lump sum that cannot be posted to the correct revenue and expense accounts.
Refund reconciliation for payment gateways — matching deductions to credit notes
Refund reconciliation for payment gateways in India requires matching three simultaneous obligations: the negative deduction in the settlement report, the credit note issued to the customer under Section 34 of the CGST Act, and the proportional ITC reversal in GSTR-3B. Finance teams that treat gateway refunds as simple settlement adjustments miss the GST liability embedded in each refund. This guide covers the full matching workflow for full, partial, and gateway-initiated refunds.
Stripe India Settlement Reconciliation: Forex, FIRC, and Inward Remittance Matching
Stripe India settlement reconciliation involves three distinct tasks that standard accounts receivable workflows do not address: matching each Stripe payout_id to a bank SWIFT credit, reconciling the forex rate difference between invoice date and settlement date, and obtaining FIRC documentation for FEMA compliance on export proceeds. Each task requires a separate data source and a different reconciliation method.
TCS reconciliation for e-commerce sellers — GSTR-8 to GSTR-2B to GSTR-3B
TCS ecommerce reconciliation in India is a seller-side obligation that arises from Section 52 of the CGST Act: every rupee of Tax Collected at Source deducted by an e-commerce operator in the settlement report must reconcile against the GSTR-2B credit auto-populated from the operator's GSTR-8 filing. Sellers on Amazon, Flipkart, and Meesho cannot claim TCS credit in GSTR-3B without first confirming that the operator has filed and the correct amount appears in GSTR-2B. This guide covers the full three-source reconciliation workflow.
UPI Settlement Reconciliation — Matching High-Volume T+0 Transactions to Books
UPI settlement reconciliation India requires a different approach from batch gateway reconciliation: each transaction settles individually at T+0, generating its own bank credit line with a 12-digit UPI Reference ID. At scale, the volume of individual credits — not the complexity of any single transaction — is what makes manual matching unworkable and automated reconciliation necessary.
See how TransactIG handles reconciliation for your industry
TransactIG is configurable for your ERP, your bank feeds, and your compliance requirements. Most implementations complete in 2–4 weeks without code development.