Goibibo (MMT-owned) and Yatra each issue distinct settlement files on different cadences with different commission ranges and dispute windows — and any property listed on multiple OTAs must reconcile each settlement to PMS folios while keeping inventory parity intact to avoid double-sold rooms and parity-SLA penalties.
Per OTA, ingest the settlement file at the contract cadence (Goibibo weekly, Yatra fortnightly or monthly), match each booking to a PMS folio, derive room GST at the correct slab, claim 18% ITC on commission GST, log disputes within the contractual window, and cross-check inventory pushes against the channel manager log to identify parity breaches that may carry penalty deductions.
Per-OTA settlement file connectors with cadence calendars; PMS folio adapter; channel manager log connector for parity events; dispute-window timer per contract; commission rate master per OTA per inventory class.
A reconciled multi-OTA revenue ledger with each booking matched to its PMS folio, ITC claimed against each OTA's tax invoice, disputes raised within window, and parity breaches flagged before they become commercial penalties.
A 120-room business hotel in Pune lists inventory across MakeMyTrip, Goibibo, Yatra, Booking.com, and its direct booking engine. In a typical month it receives a Goibibo settlement weekly, a Yatra settlement fortnightly, and an MMT settlement weekly — alongside a monthly Booking.com B.V. invoice. The finance team must reconcile each separately, identify dispute candidates within each OTA’s window, and cross-reference the channel manager log to confirm no two OTAs sold the same room. This article is for hotel controllers reconciling Goibibo and Yatra settlements in India in a multi-OTA environment.
What Goibibo and Yatra Settlement Reconciliation Involves
Goibibo and Yatra reconciliation follows the same structural shape as MakeMyTrip — match settlement file to PMS folio, derive room GST at 12% or 18% by tariff slab, capture 18% commission GST as ITC, and apply the appropriate TDS section (194-O for e-commerce gross deduction, 194H for commission-agent flow). What differs is cadence, commission range, dispute window, and the multi-OTA dimension — a property reconciled in isolation per OTA cannot detect inventory-parity issues that cross OTAs.
Goibibo, despite operating under MMT Group ownership since 2017, still issues its own settlement files with distinct identifiers, commission contracts, and tax invoices. Yatra is independent of MMT Group and operates its own technology and finance stack. Treating Goibibo as if it were MMT — or aggregating Yatra into a single monthly OTA bucket — collapses the audit trail and obscures dispute candidates.
How Goibibo and Yatra Settlement Reconciliation Works
Per-OTA Settlement File Cadence
Goibibo settlements typically run weekly with payout landing 7 to 10 days after cycle close. Yatra settlements vary — fortnightly is common for B2C, monthly for some pay-at-hotel arrangements. The reconciliation cadence calendar must mirror the contract cadence. Aggregating to monthly to align with the GSTR-3B filing date is convenient but obscures intra-month dispute candidates that may fall outside the dispute window by the time the monthly close runs.
Booking-Level Match to PMS Folios
Each settlement-file row carries an OTA booking ID (Goibibo or Yatra reference), check-in date, room nights, gross room amount, commission, and net payout. The reconciliation matches these to PMS folios using the OTA reference number stored on the folio. Mismatches surface as un-matched OTA settlement rows (PMS folio missing or cancelled), un-matched PMS folios (booking flowed in but settlement absent), or amount disagreements (rate revision, no-show retention, commission rate change between booking and stay).
Dispute Window Discipline
Each OTA contract specifies a dispute window — typically 30 to 45 days from settlement date — within which the hotel may dispute individual bookings. Once breached, the OTA’s standard contract treats the settlement as final. Disputes commonly cover commission rate misapplication, GST slab errors on the commission tax invoice, missing TDS credit reflection in Form 26AS, and no-show retention disagreements. The reconciliation must surface candidates well before the deadline so the property’s account manager has time to engage the OTA’s billing team.
Multi-OTA Inventory Parity Cross-Check
Inventory parity is the operational obligation that the same room not be sold twice across OTAs. The channel manager enforces this in real time, but settlement reconciliation can detect after-the-fact parity breaches — most often when a guest who arrived from one OTA was reaccommodated and the original booking refunded, but the commercial impact (refund timing, reaccommodation cost, OTA penalty) was not booked. Cross-referencing all OTA settlements for the same date range and room category surfaces these events.
Goibibo vs Yatra Settlement Reference
| Element | Goibibo | Yatra |
|---|---|---|
| Ownership | MMT Group | Independent (Yatra Online) |
| Typical commission range | 15% to 22% | 12% to 20% |
| Settlement cadence | Weekly | Fortnightly to monthly |
| Dispute window (typical) | 30 to 45 days | 30 to 45 days |
| Commission GST treatment | 18% domestic forward charge | 18% domestic forward charge |
| Corporate arm | Through MMT MyBiz | Yatra for Business |
India Compliance Angle: Multi-OTA GSTR-2B Reconciliation
For a property reconciling Goibibo, Yatra, and MMT in the same month, three separate commission tax invoices appear in GSTR-2B from three suppliers. Each must be matched and the 18% IGST or CGST + SGST claimed as ITC. A common error is rolling all three into a single “OTA commission” line in books while three distinct GSTINs are visible in GSTR-2B — the line-level mismatch causes ITC denial under Rule 36(4) and Section 16(2)(aa) when the matching tool cannot reconcile a consolidated line against three separate vendor invoices. The reconciliation logic must keep the supplier dimension intact down to the GSTR-2B match.
Hotel finance teams using payment gateway reconciliation tooling can run multi-OTA settlement reconciliation on a single timeline with per-OTA cadence rules. Broader reconciliation software India platforms add channel-manager log ingestion for parity detection and dispute-window timers per OTA contract. Industry guidance from FHRAI on OTA contracts and inventory parity expectations is the policy reference for hospitality controllers managing multi-OTA distribution.
For the broader hotel industry reconciliation surface, see the Hotels & Hospitality industry guide.
The following questions address the Goibibo and Yatra reconciliation issues hotel finance teams encounter most frequently.