Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An Indian merchant selling through Zomato and Swiggy for delivery, Amazon for e-commerce, and MakeMyTrip for hotel inventory receives a monthly stack of settlement files that each carry between one and three variances against the merchant's own decomposition workbook. A Zomato payout lands 22 per cent short of the expected commission because a promotional discount was routed through the commission line rather than through a separate discount line. A Swiggy payout applies Section 194O TDS on gross including customer packaging fees the merchant never booked to revenue. An Amazon disbursement carries an FBA long-term storage fee on inventory that cleared out ninety days ago. A MakeMyTrip payment holds a hotel reservation payout across a cancellation policy invocation the front desk has evidence to dispute. Each variance has a different dispute window — Amazon seven days from settlement, Zomato fifteen, Swiggy twenty-one, MakeMyTrip thirty — and each requires a specifically phrased letter that names the platform's own portal ticket path, the right escalation ladder, and the right statutory anchor. Without a standardised letter pack, the dispute either misses the window or fails at the first support-ticket level and rolls forward as a permanent settlement loss.
Build one dispute letter template per platform, calibrated to the platform's specific dispute window, portal path, escalation ladder, and statutory anchor set. Each template carries a Level 1 body for the portal support officer ticket, a Level 2 escalation to the single point of contact citing the Section 194O and Section 52 anchors for tax variances or the platform's own SLA for gateway variances, a Level 3 escalation to the operations manager citing Rule 5 of the Consumer Protection (E-Commerce) Rules 2020 as the operator's own grievance duty, and a Level 4 escalation to the key account director cited only when the dispute value is material and the operations manager has not resolved within the platform's stated escalation window. Every letter carries the dispute-window countdown as the opening line — Amazon Day 5 of 7, Zomato Day 8 of 15, Swiggy Day 12 of 21, MakeMyTrip Day 18 of 30 — so the recipient can see the clock at first read. Every letter carries an illustrative rupee figure with a worked decomposition. Every letter carries a customise-before-sending note that names the fields the merchant's finance team must replace before dispatch.
One Word document per platform, saved in the letter pack folder as `zomato-dispute-letter-template.docx`, `swiggy-dispute-letter-template.docx`, `amazon-dispute-letter-template.docx`, and `makemytrip-dispute-letter-template.docx`. Each document carries four escalation-level sections in-line, a merchant-details header block that the finance team fills in once and reuses across every future dispute, a variance-classification table that maps the six common variance types (commission overcharge, TDS misapplied on wrong base, TCS not passed through in GSTR-2B, SLA penalty overreach, FBA or storage fee dispute, cancellation policy invocation) to the specific paragraph within the template, and an escalation-ladder appendix with the platform's own contact taxonomy — portal support officer ticket path, single point of contact name field, operations manager escalation email, key account director escalation email — that the merchant fills in from the merchant agreement on first use and refreshes at every quarterly account review. The pack is stored in the finance team's shared drive alongside the Day 4 platform settlement decomposition workbook so the two open together on the dispute morning.
By the end of the dispute window, every variance the Day 4 decomposition workbook flagged has either been recovered (settlement adjusted and the corrected credit received in the next payout cycle) or has been documented on the ticket log with the escalation ladder run to the level appropriate to the dispute value. The ticket reference numbers are archived in the monthly working paper folder against the settlement date. The Level 2 letters citing Section 194O and Section 52 have been filed with the platform's tax team and the corrected settlement or the corrected GSTR-8 filing has flowed through to the next month's GSTR-2B Table 6 credit. The unresolved cases have been logged in the exception queue with the platform's stated next-review date, and where the operator's grievance officer under Rule 5 has been formally invoked, the acknowledgement reference is preserved for the eventual Consumer Protection escalation. The finance team's aggregator settlement recovery rate for the quarter is measured on the closed disputes, and the recurring variance categories are logged in the reconciliation process design register so the Day 4 decomposition catches the class earlier next month.
The Zomato settlement for the week landed at Rs 3,74,000 against the Day 4 decomposition workbook’s expected Rs 4,80,000 — a Rs 1,06,000 gap the workbook attributed to a promotional discount routed through the commission line rather than through a separate discount line. The clock on the Restaurant Partner Portal dispute path began on the settlement date; fifteen days from that date, the dispute window closed and any recovery moved from a routine settlement adjustment to a commercial recovery via the platform’s account director. This is the four-letter pack the finance team keeps ready for exactly that morning — one letter per platform, calibrated to that platform’s dispute window and its escalation ladder, with the Day 4 platform settlement decomposition workbook as the evidence base and the invoice-to-bank failure modes brief as the design layer above it.
Why the letter pack exists
Every mid-market merchant running on more than two aggregator platforms discovers within a quarter that platform disputes are their own operational stream. The Day 4 decomposition workbook in the monthly close playbook catches the variance; the dispute letter is what turns the caught variance into a recovered settlement. The finance teams that run this loop cleanly hold a folder of four Word documents — one per major platform — that they open on the Day 4 morning and dispatch by the end of Day 5. The finance teams that do not either miss the dispute window and roll the variance forward as a permanent loss, or file an ad-hoc ticket that gets bounced back at the first portal support officer level and never escalates.
The pack is not a substitute for good decomposition. The workbook still has to run every week the settlement files land, and the variance still has to be caught within the platform’s dispute window. What the pack does is standardise the recovery step so that the letter that goes out on the dispute morning names the right portal path, the right escalation ladder, the right statutory anchor, and the right illustrative rupee figure — the four fields that determine whether the ticket clears at the portal support officer level or has to escalate through single point of contact and operations manager to key account director.
The dispute-window arithmetic
The four platforms in this pack have four dispute windows, and the arithmetic of each window is what determines when the letter has to go out.
- Zomato — 15 days from settlement date. The Restaurant Partner Portal dispute path opens on the settlement date shown on the payout statement. A dispute filed after Day 15 is auto-closed as time-barred on the portal.
- Swiggy — 21 days from settlement date. The Partner App dispute path opens on the settlement date shown on the Merchant Payout Statement. The window is longer than Zomato’s because Swiggy’s payout cycle is fortnightly for parts of the merchant base rather than weekly.
- Amazon — 7 days from settlement date. The Seller Central Contact Us case log is the primary path, and the window is the tightest in this pack because Amazon’s dispute lifecycle is calibrated to the fortnightly disbursement cadence and the SPN case-management framework.
- MakeMyTrip — 30 days from settlement date. The Hotel Extranet dispute path opens on the settlement date shown on the Reservation Manager payout view. The window is the most forgiving but it is not a licence to delay — the reservation manager’s evidence base (booking record, cancellation timestamp, guest communication log) starts degrading against the platform’s internal thirty-day evidence retention rule at around Day 21.
The workbook catches the variance on Day 4 of the monthly close. The letter has to land inside the platform’s window, which for Amazon means Day 5 of the settlement is Day 5 of the dispute window and there is essentially no operational buffer. For Zomato and Swiggy the buffer is comfortable; for MakeMyTrip the buffer is generous. The Amazon letter is therefore the one the finance team keeps at the front of the pack.
The four-level escalation ladder
Every letter in this pack is written for a four-level escalation ladder that is common across the platforms in shape even though the specific contact taxonomy differs.
- Level 1 — portal support officer (POC). The ticket auto-routes to whoever the portal’s first-level support desk assigns. Response is a scripted acknowledgement within one to two business days. The Level 1 letter is the ticket body — factual, specific, and short.
- Level 2 — single point of contact (SPOC). The named account owner the merchant onboarded with. Escalated to when the POC ticket has been open beyond the platform’s published SLA — typically five business days. The Level 2 letter cites the Section 194O and Section 52 anchors for tax-related variances and the platform’s own SLA for gateway-related variances.
- Level 3 — operations manager. Sits above the SPOC. Escalated to when the SPOC response has been unsatisfactory — usually the seventh to tenth business day. The Level 3 letter cites Rule 5 of the Consumer Protection (E-Commerce) Rules 2020 as the operator’s own grievance duty and requests a written response within the timeline the operator has published to the regulator.
- Level 4 — key account director. The platform’s most senior merchant-facing escalation. Invoked only when the dispute value is material (illustratively above Rs 50,000 per settlement or above Rs 2 lakh cumulative), the operations manager has not resolved within the platform’s stated escalation window, and the dispute window is close to expiry. The Level 4 letter names the Payment and Settlement Systems Act 2007 and the RBI Master Direction on Payment Aggregators and Payment Gateways where the settlement error falls under the payment-aggregator settlement SLA — three working days for a mis-collected amount to be refunded to the merchant escrow account.
Each letter template in this pack contains all four levels in one document, with the level headers as separate sections. The finance team escalates by opening the same document, updating the addressee block, and dispatching to the next level.
Letter 1 — Zomato dispute letter template
Platform. Zomato Restaurant Partner Portal. Dispute window. 15 days from settlement date. Common variance categories. Commission overcharge (promotional discount routed through commission line); Section 194O TDS applied on wrong base (including customer packaging fees); Section 52 TCS not passed through to merchant GSTR-2B Table 6; SLA penalty overreach on delivery cancellations. Statute anchors. Section 194O 1 per cent TDS; Section 52 1 per cent TCS; Rule 46 tax invoice compliance for commission GST; Rule 5 Consumer Protection (E-Commerce) Rules 2020.
Level 1 — Restaurant Partner Portal ticket body.
Subject: Dispute on Restaurant Partner Payout — Settlement ID [SETTLEMENT ID] — Restaurant [RESTAURANT NAME] GSTIN [MERCHANT GSTIN]
This is to raise a dispute against the payout statement received on [SETTLEMENT DATE] for the week ending [WEEK ENDING DATE]. The expected payout as per our internal decomposition against orders received in the week is Rs 4,80,000. The actual credit to our bank account was Rs 3,74,000. The variance of Rs 1,06,000 traces to a promotional discount amount that appears to have been routed through the commission line on the settlement report rather than through the promotional support line for which we have documented invoice-level entitlement under the current commercial arrangement.
Order-level detail is attached for the eleven orders where the discount routing is disputed. Please confirm the correct commission calculation and process the differential in the next payout cycle. Dispute window: fifteen days from settlement date, closing on [DISPUTE WINDOW CLOSE DATE].
Level 2 — SPOC escalation citing statute anchors.
Following the Level 1 ticket [TICKET REFERENCE] opened on [DATE], and in the absence of a resolution within the Restaurant Partner Portal’s five-business-day SLA, this is to escalate the Rs 1,06,000 disputed settlement to the account single point of contact.
The disputed amount includes an illustrative Section 194O deduction at 1 per cent on the gross order value including the disputed commission base. Under Section 194O of the Income-tax Act 1961 (Section 393 payment code 1011 from 1 April 2026), the deduction is on the gross amount of sales, and where the deduction has been applied on a base that includes amounts not attributable to the merchant’s supply, the deduction is excess to the extent of that base. Please confirm the base against which the TDS at Rs 4,800 has been computed and issue a corrected settlement, or a corrected quarterly TDS return under Section 200 where the corrected figure changes the deposit already made.
Level 3 — operations manager escalation citing Rule 5 duty.
Following the Level 2 escalation [ESCALATION REFERENCE] and the absence of a substantive response from the single point of contact within seven business days, this is to escalate to the operations manager under the platform’s own grievance framework published in accordance with Rule 5 of the Consumer Protection (E-Commerce) Rules 2020 issued under the Consumer Protection Act 2019.
The disputed amount of Rs 1,06,000 remains outstanding. Under Rule 5, the platform is required to publish the grievance officer’s name and contact details and to resolve complaints within one month. The complaint reference is [COMPLAINT REFERENCE], filed on [DATE], and the resolution deadline under the platform’s own published policy is [DATE].
Level 4 — key account director escalation.
Following the escalation ladder run through Level 1 (portal ticket), Level 2 (single point of contact), and Level 3 (operations manager) without resolution, and with the dispute window closing on [DATE], this is to escalate to the key account director. The disputed amount of Rs 1,06,000 is material to the merchant’s settlement cycle. We request a resolution by [DATE] or the case will be escalated to the platform’s grievance officer under Rule 5 with a copy to the consumer commission with appropriate jurisdiction.
Customise before sending. Replace [SETTLEMENT ID], [RESTAURANT NAME], [MERCHANT GSTIN], [SETTLEMENT DATE], [WEEK ENDING DATE], [DISPUTE WINDOW CLOSE DATE], [TICKET REFERENCE], [ESCALATION REFERENCE], [COMPLAINT REFERENCE], and every illustrative rupee figure before dispatch. The Zomato commission overcharge scenario is illustrative — the same template body applies to a TCS pass-through dispute or an SLA penalty overreach with the specific paragraph adjusted. See the Zomato restaurant settlement reconciliation article for the variance-category detail the letter body draws from.
Letter 2 — Swiggy dispute letter template
Platform. Swiggy Partner App. Dispute window. 21 days from settlement date. Common variance categories. Commission-TCS-TDS split discrepancy (collection fee and platform fee treated inconsistently between the operator’s tax filing and the merchant’s decomposition); Section 194O TDS on gross including customer packaging fees the merchant did not book to revenue; delivery partner incentive claw-back applied to merchant payout instead of to the delivery-partner ledger. Statute anchors. Section 194O; Section 52; Rule 46; Rule 5 Consumer Protection (E-Commerce) Rules 2020.
Level 1 — Partner App ticket body.
Subject: Dispute on Merchant Payout Statement — Payout ID [PAYOUT ID] — Restaurant [RESTAURANT NAME] GSTIN [MERCHANT GSTIN]
This is to raise a dispute against the Merchant Payout Statement for the settlement period ending [SETTLEMENT PERIOD END DATE], received on [SETTLEMENT DATE]. Our decomposition against the order log for the settlement period computes an expected net payout of Rs 5,62,000. The actual credit was Rs 5,08,400. The variance of Rs 53,600 traces to a Section 194O TDS applied on an order-value base that included customer packaging fees (Rs 8 per order across 1,340 orders = Rs 10,720 additional base) that our books have not recognised as merchant revenue.
The order-level extract with the TDS base per order is attached. Please confirm the TDS calculation and process the differential in the next payout cycle. Dispute window: twenty-one days from settlement date, closing on [DISPUTE WINDOW CLOSE DATE].
Level 2 — SPOC escalation citing Section 194O base.
Following the Level 1 ticket [TICKET REFERENCE] and the absence of resolution within seven business days, this is to escalate to the account single point of contact.
Under Section 194O of the Income-tax Act 1961, the TDS at 1 per cent is on the gross amount of sale of goods or provision of services by the e-commerce participant. The customer packaging fee is a separately recognised head under the merchant’s own supply invoice structure and is not part of the merchant’s gross sale for which the platform is the operator. The illustrative TDS excess on the disputed base is Rs 10,720 multiplied by 1 per cent = Rs 107.20 — a small figure per order, but accumulating to Rs 53,600 across the merchant’s monthly volume. Please issue a corrected settlement and, where the deposit has been made, a corrected quarterly TDS return under Section 200 so the excess is credited to the merchant’s Form 168 (or Form 26AS for pre-2026-27 residuals).
Level 3 — operations manager escalation. Same Rule 5 framing as Letter 1, adjusted for the Swiggy Partner App grievance mechanism.
Level 4 — key account director escalation. Same closing paragraph as Letter 1, adjusted for the Swiggy account taxonomy.
Customise before sending. Replace [PAYOUT ID], [RESTAURANT NAME], [MERCHANT GSTIN], [SETTLEMENT PERIOD END DATE], [SETTLEMENT DATE], [DISPUTE WINDOW CLOSE DATE], [TICKET REFERENCE], and every illustrative rupee figure before dispatch. See the Swiggy restaurant settlement reconciliation article for the Swiggy-specific payout column conventions the letter body draws from.
Letter 3 — Amazon dispute letter template (highest urgency)
Platform. Amazon Seller Central. Dispute window. 7 days from settlement date (shortest of the four). Common variance categories. Commission variance by SKU category (books, electronics, apparel, grocery — 8 to 25 per cent range); Fulfilment by Amazon fee applied against inventory that cleared out prior to the fee cycle; long-term storage fee on inventory that was removed within the exemption window; Section 194O TDS on gross including MDR retention by the payment gateway. Statute anchors. Section 194O; Section 52; Rule 46; Rule 5. Portal path. Seller Central Contact Us → Seller Support Case Log → Amazon SPN grievance officer escalation. The Amazon SPN grievance officer contact is published under Rule 5 of the Consumer Protection (E-Commerce) Rules 2020 and is the escalation of last resort inside the platform.
Level 1 — Seller Central Contact Us case body (dispatch within 3 business days of settlement).
Subject: Dispute on Seller Disbursement — Disbursement ID [DISBURSEMENT ID] — Seller [SELLER NAME] GSTIN [MERCHANT GSTIN] — Seller Account [MERCHANT ACCOUNT ID]
This is to raise a dispute against the seller disbursement for the settlement period ending [SETTLEMENT PERIOD END DATE], credited on [SETTLEMENT DATE]. The disbursement includes an illustrative Fulfilment by Amazon long-term storage fee of Rs 42,300 charged against ASIN [ASIN LIST] for the storage cycle ending [STORAGE CYCLE END DATE]. Our warehouse removal log confirms that the disputed inventory was removed from FBA warehouses on [REMOVAL DATE], which falls before the storage-fee assessment date. Please review the removal log against the assessment, refund the disputed Rs 42,300, and confirm resolution in the next disbursement cycle. Dispute window: seven days from settlement date, closing on [DISPUTE WINDOW CLOSE DATE].
Level 2 — Seller Support Case Log escalation to Amazon SPN.
Following the Level 1 case [CASE ID] opened on [DATE] and the absence of a substantive resolution within three business days of the seven-day dispute window, this is to escalate to Amazon Services Network. The disputed amount of Rs 42,300 remains outstanding. Under the Amazon Services Business Solutions Agreement and the fee schedules published for the FBA long-term storage program, storage fees are assessed on inventory held in FBA facilities on the assessment date. The attached warehouse removal manifest confirms the inventory was withdrawn from Amazon fulfilment on [REMOVAL DATE], prior to the assessment date of [ASSESSMENT DATE]. Please process the refund and confirm.
Level 3 — Amazon SPN grievance officer escalation under Rule 5.
Following the Level 2 escalation on Case ID [CASE ID] and the absence of resolution with the dispute window closing on [DATE], this is to escalate to the Amazon SPN grievance officer under Rule 5 of the Consumer Protection (E-Commerce) Rules 2020. The disputed amount is Rs 42,300. The escalation path from portal support officer through Seller Support to SPN has been documented and is attached.
Level 4 — key account director escalation. Reserved for cases where the cumulative dispute value across the settlement cycle exceeds Rs 2 lakh and the Level 3 SPN grievance officer has not resolved within seven days of escalation.
Customise before sending. Replace [DISBURSEMENT ID], [SELLER NAME], [MERCHANT GSTIN], [MERCHANT ACCOUNT ID], [SETTLEMENT PERIOD END DATE], [SETTLEMENT DATE], [ASIN LIST], [STORAGE CYCLE END DATE], [REMOVAL DATE], [ASSESSMENT DATE], [DISPUTE WINDOW CLOSE DATE], [CASE ID], and every illustrative rupee figure before dispatch. See the Amazon SPN GST reconciliation article for the Amazon-specific SPN dispute framework the letter body draws from.
Letter 4 — MakeMyTrip dispute letter template
Platform. MakeMyTrip Hotel Extranet. Dispute window. 30 days from settlement date. Common variance categories. Commission variance (net-of-tax versus gross-of-tax split with the hotel’s own tax invoice under Rule 46); cancellation policy invocation without documented guest cancellation timestamp; payment lag beyond the merchant agreement settlement cycle; no-show penalty attributed to the hotel where the OTA guest actually checked in. Statute anchors. Section 194O; Section 52; Rule 46; Rule 5; Payment and Settlement Systems Act 2007 for the payment-aggregator embedded in the OTA settlement stack.
Level 1 — Hotel Extranet dispute ticket body.
Subject: Dispute on Hotel Payout Statement — Reservation ID [RESERVATION ID] — Hotel [HOTEL NAME] GSTIN [MERCHANT GSTIN]
This is to raise a dispute against the hotel payout statement for the reservation cycle ending [RESERVATION CYCLE END DATE], credited on [SETTLEMENT DATE]. The disputed reservation is [RESERVATION ID], guest name [GUEST NAME], check-in [CHECK-IN DATE], check-out [CHECK-OUT DATE]. Our front desk records confirm the guest checked in on [CHECK-IN DATE] and completed the stay. The payout statement records a cancellation policy invocation dated [CLAIMED CANCELLATION DATE] and has withheld Rs 18,400 against a no-show penalty. The attached check-in register and folio confirm the stay was completed. Please review the reservation status, release the withheld Rs 18,400, and process it in the next payout cycle. Dispute window: thirty days from settlement date, closing on [DISPUTE WINDOW CLOSE DATE].
Level 2 — Reservation Manager escalation.
Following the Level 1 ticket [TICKET REFERENCE] and the absence of substantive resolution within seven business days, this is to escalate to the Reservation Manager for [HOTEL NAME]. The withheld amount of Rs 18,400 remains disputed. Under the hotel-OTA merchant agreement, the cancellation policy invocation requires a documented guest cancellation timestamp raised through the OTA’s own booking interface prior to the check-in cutoff. The attached check-in register, guest folio, and photo-ID sign-in confirm the stay was completed. Please process the release within three working days.
Level 3 — operations manager escalation citing Rule 5.
Following the Reservation Manager escalation [ESCALATION REFERENCE] without resolution, this is to escalate to the OTA operations manager under Rule 5 of the Consumer Protection (E-Commerce) Rules 2020. The disputed amount is Rs 18,400. The platform’s own grievance framework published under Rule 5 requires resolution within the platform’s stated timeline. The complaint reference is [COMPLAINT REFERENCE], filed on [DATE].
Level 4 — key account director escalation.
Following the escalation ladder run through Level 1, 2, and 3, and with the dispute window closing on [DATE], this is to escalate to the key account director for the hotel account. The withheld amount of Rs 18,400 is disputed on documented evidence. We request resolution by [DATE] or the case will be escalated to the platform’s grievance officer with a copy to the consumer commission with appropriate jurisdiction.
Customise before sending. Replace [RESERVATION ID], [HOTEL NAME], [MERCHANT GSTIN], [RESERVATION CYCLE END DATE], [SETTLEMENT DATE], [GUEST NAME], [CHECK-IN DATE], [CHECK-OUT DATE], [CLAIMED CANCELLATION DATE], [DISPUTE WINDOW CLOSE DATE], [TICKET REFERENCE], [ESCALATION REFERENCE], [COMPLAINT REFERENCE], and every illustrative rupee figure before dispatch. See the MakeMyTrip hotel settlement reconciliation article for the OTA payout structure the letter body draws from.
Download the four-letter Word pack
The four dispute letter templates above are available as a bundled Word pack — zomato-dispute-letter-template.docx, swiggy-dispute-letter-template.docx, amazon-dispute-letter-template.docx, and makemytrip-dispute-letter-template.docx — from the aggregator settlement dispute letter pack landing page. The landing page carries a short lead form that captures the merchant’s platform mix and industry so the pack can be updated when the platform account structures change; the pack itself is emailed on submission. Every template ships with the customise-before-sending markers already highlighted and the escalation-ladder appendix ready for the finance team to fill in from the merchant agreement on first use.
When the manual escalation ladder outgrows itself
The letter pack is designed for a finance team running against two to four aggregator platforms with a monthly settlement volume of a few hundred to a few thousand orders per platform. Above roughly four active platforms, or above roughly ten thousand monthly transactions per platform, the manual dispute cadence stops holding cleanly. Three specific breakages surface.
Dispute-window enforcement across four platforms with four windows. The finance team has to hold the seven-day Amazon window in the same working memory as the fifteen-day Zomato window, the twenty-one-day Swiggy window, and the thirty-day MakeMyTrip window. A missed Amazon window is silently a permanent loss; a missed Zomato window is a commercial recovery through the account director rather than a routine settlement adjustment. The tracker that keeps four windows straight is not a spreadsheet the analyst can maintain without prompting.
Variance-detection scaling above ten thousand monthly transactions per platform. The Day 4 decomposition workbook holds the variance surface up to a few thousand transactions per platform. Above ten thousand, the ARRAYFORMULA and REGEXEXTRACT patterns start missing edge cases (a new SKU category on Amazon, a new commission-fee split on Swiggy, a new promotional discount routing on Zomato), and the letters that would have gone out on the Day 5 morning are not going out because the variance was not detected.
Escalation-ladder tracking across four platforms across four levels. Each dispute that escalates carries a POC ticket, a SPOC email, an operations manager email, and potentially a key account director email — sixteen possible contact touch-points per platform. The finance team’s follow-up cadence has to hold each thread against the platform’s published SLA and the dispute window countdown, and above roughly twenty simultaneously open disputes, the manual follow-up cadence starts producing silent misses.
The response is not to abandon the letter pack — the pack is what makes the dispute discipline defensible. The response is to move the variance-detection surface off the analyst’s screen and onto a continuously refreshed reconciliation surface that catches the variance on the day the settlement lands rather than on the Day 4 workbook refresh, and to hold the dispute ladder in a workflow tracker that shows every open ticket against every window and every escalation level. The reconciliation playbook pillar documents the operational cadence, and TransactIG reconciliation infrastructure is where the manual dispute pattern moves when the four-window arithmetic and the sixteen-touchpoint tracking stop being sustainable.
Where this fits
- TransactIG — reconciliation infrastructure
- Reconciliation software India — pillar guide
- GST reconciliation software India
- TDS reconciliation software India
Related reading
- The reconciliation playbook — monthly close pillar
- Platform settlement decomposition in Google Sheets — the Day 4 workbook that feeds the dispute pack
- Invoice-to-bank reconciliation failure modes — the design layer for aggregator credit failures
- Bank reconciliation runbook — Days 1 to 5, where the aggregator credit lands
- Zomato restaurant settlement reconciliation
- Swiggy restaurant settlement reconciliation
- Amazon SPN GST reconciliation
- MakeMyTrip hotel settlement reconciliation
- Vendor GSTR-1 follow-up letter templates — the sibling six-letter pack for supplier ITC recovery
- Deductor Form 168 query letter templates — the sibling five-letter pack for TDS credit recovery
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ Section 194O, Income-tax Act 1961 — Section 393 payment code 1011 — An e-commerce operator paying an e-commerce participant for the sale of goods or provision of services must deduct tax at 1 per cent of the gross amount of such sales or services or both at the time of credit to the participant or at the time of payment, whichever is earlier. From FY 2026-27 the deduction is filed under Section 393 payment code 1011. The deduction is on the gross order value, not on the merchant's net payout, which means the TDS-net calculation on a Zomato or Swiggy payout must be reconstructed from the settlement file rather than inferred from the bank credit. A Section 194O deduction applied on a wrong base (customer packaging fees or delivery charges that the merchant did not book to revenue) is a common dispute category and the anchor for the Level 2 escalation letter in this pack.
- ▸ Section 52, Central Goods and Services Tax Act 2017 — e-commerce operator TCS — Every electronic commerce operator, not being an agent, shall collect an amount at the notified rate on the net value of taxable supplies made through it by other suppliers where the consideration is to be collected by the operator. The notified rate is 0.5 per cent CGST plus 0.5 per cent SGST for intra-state supplies and 1 per cent IGST for inter-state supplies. Where the operator has collected TCS at the wrong rate, on a wrong base, or has failed to pass the credit through in the merchant's GSTR-2B Table 6, the merchant's dispute letter cites Section 52 and requests either a corrected settlement or a corrected GSTR-8 filing by the operator.
- ▸ Consumer Protection Act 2019 and Consumer Protection (E-Commerce) Rules 2020 — The Consumer Protection (E-Commerce) Rules 2020 issued under the Consumer Protection Act 2019 impose specific duties on e-commerce entities. Rule 5 requires every e-commerce entity to appoint a grievance officer, publish the officer's name and contact details on the platform, resolve consumer complaints within one month, and maintain a grievance redressal mechanism accessible to the merchant. A merchant disputing a settlement error is a first-level participant under the platform's own grievance framework, and the Level 3 escalation letter in this pack cites Rule 5 as the operator's own duty basis for a written response within the timeline the operator has published to the regulator.
- ▸ Payment and Settlement Systems Act 2007 and RBI Master Direction on Payment Aggregators and Payment Gateways (RBI/DPSS/2020-21/113 as amended) — The Payment and Settlement Systems Act 2007 governs the settlement of payments in India. The RBI Master Direction on Payment Aggregators and Payment Gateways issued under the Act requires an authorised payment aggregator to credit the merchant's escrow account within the settlement cycle notified in the merchant agreement — typically T+1 for card and net banking and T+0 for UPI — and to refund a mis-collected amount within three working days of the merchant's written dispute. Where the aggregator holding the settlement is an authorised PA or PG (Razorpay, PayU, Cashfree, and the payment stacks embedded inside Zomato Pay, Swiggy Money, and Amazon Pay), the three-day SLA is the anchor for the escalation clock in the Level 2 letter.
- ▸ Rule 46, Central Goods and Services Tax Rules 2017 — tax invoice content — A tax invoice issued by a registered person shall contain the name, address, and GSTIN of the supplier and the recipient; a consecutive serial number; the date of issue; the description of goods or services; the total value of supply; the taxable value; the rate of tax; and the amount of tax charged. The commission invoice raised by Zomato, Swiggy, Amazon, or MakeMyTrip against the merchant must satisfy Rule 46 in full for the commission GST at 18 per cent to be ITC-eligible in the merchant's GSTR-3B Table 4. Where the operator's commission invoice is short of Rule 46 particulars — missing GSTIN, wrong merchant name, ambiguous SAC, or a serial number that resets mid-year — the merchant's dispute letter cites Rule 46 and requests a corrected invoice before the Section 16(4) time bar of 30 November of the following financial year forecloses the ITC.