Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
OYO operates revenue-share or minimum-guarantee contracts where OYO owns the customer relationship, sets rates, and applies SLA-based deductions — making the property's settlement file structurally different from a commission-only OTA payout, with the GST liability flowing to either OYO or the property depending on the contract structure under sub-brands like Townhouse, Capital O, or OYO Wizard.
Per settlement cycle, classify each booking under the property's contract type (revenue-share, minimum-guarantee, hybrid), match to PMS folio, apply the contracted revenue-share split, compute minimum-guarantee top-up if applicable, layer in SLA-based deductions with reason codes, separate operational settlement from capex-recovery deductions on Townhouse or Capital O properties, and apply the GST treatment that matches the contract's supplier identification.
OYO settlement file connector with sub-brand and contract identifiers; PMS folio adapter; revenue-share split rule per property; minimum-guarantee floor per month; SLA deduction reason-code master; capex recovery schedule on Townhouse or Capital O contracts; GST supplier-identification rule per contract.
A reconciled OYO ledger where each cycle's payout is built up from revenue share or minimum guarantee, SLA deductions are itemised with reason codes for dispute, capex recovery is segregated, and the GST treatment matches the contract — supporting accurate revenue recognition under Ind AS 115.
A 40-room property branded as OYO Townhouse in Hyderabad receives monthly settlements from OYO comprising revenue share on actual occupancy, an applied minimum-guarantee top-up for the months below the guarantee floor, deductions for two SLA breaches in the period, and a recovery instalment against the original Townhouse capex. The owner’s finance team must reconcile each component against the contract terms, the property management system folio data, and the bank credit. This article is for hotel finance teams reconciling OYO settlements in India.
What OYO Hotel Settlement Reconciliation Involves
OYO settlement reconciliation differs structurally from commission-only OTA reconciliation because OYO is not just a booking channel — under most partner contracts OYO is the brand-facing supplier or co-supplier of the accommodation experience. The property cedes rate-setting, customer relationship, and brand presentation to OYO in exchange for a contracted revenue share, often with a minimum-guarantee floor. The settlement file therefore reflects a revenue-sharing agreement rather than a commission deduction on a hotel-set rate.
The reconciliation outputs are: a folio-level revenue map matched to the OYO settlement, a build-up of the revenue-share calculation versus minimum-guarantee floor, an itemised SLA deduction register with reason codes for dispute, a capex recovery schedule for Townhouse or Capital O properties, and a GST treatment that follows the contractual supplier identification.
How OYO Settlement Reconciliation Works
Classifying the Contract Type
The first reconciliation input is the contract type. OYO operates several models: pure revenue-share where the property gets a fixed percentage of OYO-collected revenue net of OYO’s share, minimum-guarantee where the property is paid a baseline regardless of occupancy with revenue-share applying above the floor, and hybrid models where capex contribution from OYO is recovered through revenue-share over a tenure. The reconciliation logic loads the contract terms per property and applies the right calculation each cycle.
Building the Revenue-Share Calculation
For a revenue-share contract, the cycle’s gross revenue is OYO’s collected room revenue (the rate OYO charged the guest, which the property typically does not control). OYO’s share is taken as per the contract — say, 30% of net revenue after taxes and platform fees. The property’s share is 70%. The PMS folio data confirms occupancy, room nights, and any incidentals charged at the property — these incidentals usually belong entirely to the property and are settled separately or paid by the guest at check-out without going through OYO.
Applying the Minimum-Guarantee Top-Up
If the cycle’s revenue-share calculation produces a property payout below the minimum guarantee, OYO tops up to the floor. The reconciliation must compute both: the revenue-share figure and the minimum-guarantee figure, identify which leg paid, and verify the top-up is correct. A common dispute is whether SLA deductions are applied to the revenue-share calculation before the guarantee comparison or after — contracts vary, and the wrong sequence can swing the payout materially.
Itemising SLA Deductions
OYO settlements list SLA-based deductions with reason codes — cleanliness audit failure, response-time SLA breach, rating below contracted threshold, channel parity violation, walkthrough audit finding. Each deduction needs a reason code logged in the reconciliation register so the property can dispute incorrect applications. The dispute window is typically 30 to 45 days from settlement date. Repeated SLA deductions that go unchallenged can compound and eat into multiple subsequent settlements.
Segregating Capex Recovery on Townhouse / Capital O
For OYO Townhouse, Capital O, or OYO Wizard properties where OYO funded a capex programme — branding, room refurbishment, amenity build-out — the contract amortises that capex against the property’s revenue share over a contracted tenure. The recovery instalments appear in the settlement file as a separate deduction. The reconciliation must segregate this from operational settlement because in the property owner’s books, capex recovery is a financing-type cash outflow against an asset or contractual obligation, not an operating expense.
OYO Settlement Component Reference
| Component | Operational Treatment | Recovery / Adjustment Treatment |
|---|---|---|
| Revenue share | Operating revenue at contracted percentage | n/a |
| Minimum-guarantee top-up | Operating revenue at guaranteed floor | n/a |
| SLA deduction | Reduction of operating revenue or operating expense per contract | Disputable within window |
| Capex recovery instalment | n/a | Reduction of capex obligation, not operating expense |
| OYO Wizard programme fee | Marketing or platform service expense | n/a |
| Channel parity violation deduction | Reduction of operating revenue | Disputable within window |
India Compliance Angle: GST Supplier Identification
The most consequential reconciliation decision on an OYO contract is identifying the GST supplier of the accommodation service. If OYO is the supplier under its brand, OYO raises the tax invoice on the guest with OYO’s GSTIN, pays output GST at the applicable slab (12% up to ₹7,500 tariff, 18% above), and the property invoices OYO under SAC 996311 (services in support of accommodation) at 18%. If the property is the supplier, the property invoices the guest with its GSTIN and OYO bills its revenue share separately, also at 18%. The two structures produce materially different GSTR-1 schedules and ITC chains. Reading the partner agreement before configuring the reconciliation is essential — a misconfiguration can trigger a GSTR-1 amendment exercise across an entire financial year.
Hotel finance teams using payment gateway reconciliation tooling can ingest OYO settlement files alongside direct booking and OTA payouts on a single timeline. Broader reconciliation software India platforms add the contract-rule engine for revenue-share calculation, minimum-guarantee comparison, SLA deduction reason codes, and capex recovery segregation. Industry guidance from FHRAI on revenue-share contracts and SLA practices is a useful reference for property owners evaluating or operating under OYO partner agreements.
For the broader hotel industry reconciliation surface, see the Hotels & Hospitality industry guide.
The following questions address the OYO settlement reconciliation issues hotel finance teams encounter most frequently.