TMC Contract Negotiation in India: Clauses, SLAs and Commercial Terms to Insist On
The TMC contract is the enforcement mechanism for everything your procurement process has established — the SLAs agreed during the RFP, the GST invoice commitments, the account management standards, and the commercial model. A poorly drafted contract transforms binding commitments into unenforceable aspirations. This guide identifies the clauses and terms that Indian enterprises must insist on, and the common drafting traps that consistently disadvantage buyers.
Key Contract Clauses for Indian Enterprises
Define with specificity every service included in the contract: booking channels (online, agent-assisted, mobile), categories covered (hotel, domestic air, international air, ground transport), invoicing obligations, reporting deliverables, and account management. Anything not listed in the scope clause may be treated as out of scope and subject to additional fees. Avoid scope definitions that reference "standard services" without further specification.
This is the single most commercially significant clause in any Indian TMC contract. The clause must specify: (a) the TMC's obligation to deliver GST-compliant invoices within 48 hours of check-out for all hotel bookings, (b) the correction obligation for defective invoices within 72 hours of client notification, (c) the TMC's responsibility for ensuring GSTIN capture at the booking stage, and (d) a financial remedy for any ITC loss attributable to late or defective invoices. The remedy mechanism should be unambiguous — fee credit against the current billing cycle, or direct reimbursement, calculated based on the applicable tax rate on the invoice value.
SLAs must appear in a separate, numbered schedule attached to the contract — not embedded in general terms where they can be obscured. The schedule should specify the metric, the measurement method, the target, the measurement period, and the penalty for breach. Penalties should be proportionate: a minor SLA miss (monthly MIS delivered on the 6th instead of the 5th) warrants a small credit; a critical failure (traveller stranded without support for four hours) warrants a significantly higher penalty. Ensure SLAs are measured on objective data from the TMC's own system, with the client retaining the right to audit.
The fee schedule must itemise every charge. Common fee categories to negotiate and define: per-booking transaction fee (hotel, air, ground separately), amendment fee, cancellation fee, after-hours support surcharge (if applicable), implementation and onboarding fee, and any minimum monthly or annual commitment. Fees that are not listed in the schedule should not be payable. Include a provision for annual fee review with a defined mechanism (e.g., CPI-linked escalation with a cap of 5% per annum) to avoid mid-contract surprises.
Require the TMC to disclose all supplier commissions, override agreements, and incentive arrangements that influence the rates or inventory presented to travellers. This is a common source of misaligned interests: a TMC receiving a volume-based override from a specific hotel chain has a financial incentive to present that chain's properties preferentially, even when a better-value alternative exists. Full disclosure does not eliminate this conflict, but it allows the client to monitor and challenge anomalous booking patterns.
All travel data generated on your account belongs to your organisation, not the TMC. The contract must confirm this explicitly and specify: the formats in which data will be provided on request, the timeline for delivering a complete data export on contract termination (recommend 30 days), and the TMC's data retention and deletion obligations post-contract. Indian enterprises increasingly need this data for GST reconciliation, audits, and spend analysis — loss of data on TMC termination is a significant operational risk.
SLA Benchmarks: Reference Standards
| SLA Category | Metric | Recommended Target | Measurement Basis |
|---|---|---|---|
| Online Booking | Booking confirmation time | ≤30 minutes | System timestamp |
| Agent-Assisted Booking | Confirmation time (business hours) | ≤4 hours | Ticket open/close time |
| Emergency Booking | Response time (after hours) | ≤30 minutes | Call/chat log |
| GST Invoice | Delivery after check-out | ≤48 hours | Invoice timestamp |
| Invoice Correction | Reissue after client notification | ≤72 hours | Reissue timestamp |
| Monthly MIS | Delivery date | By 5th of following month | Delivery date |
| Critical Incident | Acknowledgment time | ≤30 minutes | Incident log |
| Critical Incident | Resolution time | ≤2 hours | Incident log |
| QBR Delivery | Quarterly business review scheduling | Within 30 days of quarter end | Meeting date |
Exit Clause and Data Portability
A TMC contract without a robust exit clause is a contract that favours the vendor. The exit clause should address three scenarios: (1) end of contract term (standard notice), (2) termination for cause — defined as persistent SLA failure — and (3) termination for convenience.
For end of term: Require a minimum 90-day notice from both parties, with the TMC obligated to continue full service during the notice period and to cooperate with transition to the successor TMC.
For termination for cause: Define "cause" with objective criteria — for example, three consecutive months of GST invoice accuracy below 97%, or two critical SLA failures in any rolling 30-day period. Cause-based termination should allow a shorter notice period (30 days) and should not trigger any early termination penalty.
For data portability: Require a complete data export within 30 days of contract end, including all historical transaction data, GST invoice records, and traveller profile data, in a machine-readable format (CSV or structured XML).
Performance Review Cadence in Contract
Specify in the contract that quarterly business reviews are a contractual obligation, not an optional courtesy. Include in the contract: the minimum agenda items for each QBR (SLA performance report, spend analysis, top-10 issues log, coming-quarter priorities), the TMC's obligation to prepare and circulate materials five business days in advance, and a named senior TMC contact required to attend. A TMC that resists contractualising QBR obligations is signalling that it does not intend to maintain account management standards throughout the contract term.
Pricing Model Negotiation: Transaction vs. Subscription
Two pricing models dominate the Indian TMC market:
Transaction-based: A per-booking fee charged on each hotel, air, and ground booking. This model aligns TMC revenue with usage and is transparent, but can create perverse incentives — some TMCs may favour assisted bookings over self-service to maximise transaction count, or may resist automation investments that reduce booking volumes.
Subscription-based: A fixed monthly or annual fee covering an agreed service scope. This model provides cost predictability and aligns TMC interests with efficiency. However, it requires careful scope definition to prevent the TMC from treating scope ambiguity as a fee-generating opportunity.
For most large Indian enterprises with predictable travel patterns, a hybrid model — subscription covering the core platform and account management, with per-transaction charges for air and ground (high-variable-cost services) and no separate charge for hotel bookings — typically produces the best total cost of ownership.
Common TMC Contract Traps to Avoid
- Automatic renewal without notice: Contracts that renew automatically for a full term unless notice is given 90 days before expiry can lock an organisation into a substandard TMC relationship for an additional year. Cap automatic renewal to a 30-day rolling extension pending renegotiation.
- Unilateral fee revision clauses: Some contracts allow the TMC to revise transaction fees with 30 days' notice. Require that any fee revision above the agreed CPI escalation cap requires mutual written agreement.
- Force majeure overreach: Broad force majeure clauses have been used by TMCs to excuse GST invoice failures, service outages, and account management lapses. Negotiate force majeure scope to cover only genuine external events (natural disasters, government-mandated shutdowns) and exclude technology failures, staffing issues, or hotel non-cooperation.
- Liability caps at one month's fees: A liability cap equal to one month's fees is inadequate for large enterprises. For a programme with ₹50 crore in annual spend, a one-month fee cap may be ₹2–3 lakh — covering only a trivial fraction of the ITC loss that could result from a systematic GST invoice failure. Negotiate liability caps commensurate with the financial risk.
- Vague "best efforts" language: Any contractual commitment described as "best efforts" or "reasonable endeavours" is unenforceable as an SLA. Require specific, measurable commitments throughout the contract.