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.
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.