OTA Short Payouts: Why Bus Operators Lose 2-5% Revenue and How to Recover It
Published by Team GaadiKharcha | Category: OTA & Collections
Disclaimer: This article is intended for general informational purposes only and does not constitute legal, tax, or financial advice. figures and percentages mentioned are illustrative estimates based on general industry observations and do not represent guaranteed outcomes. OTA contract terms, commission structures, and dispute policies vary by platform and are subject to change. Always consult a qualified Chartered Accountant or legal advisor before taking action on financial discrepancies. GaadiKharcha is a software platform and is not a licensed financial or legal advisory firm.
You're Probably Being Underpaid. You Just Can't Prove It Yet.
If you operate buses on RedBus, AbhiBus, or Paytm Bus, there's a good chance your OTA payouts are consistently lower than they should be - not by a dramatic amount, but by 2–5% every single settlement cycle.
That might sound small. On ₹10 lakh of monthly OTA revenue, that's ₹20,000–₹50,000 disappearing every month. Over a year: ₹2.4–6 lakh. Quietly. Without a single dispute being raised.
The reason most operators never catch it: the loss doesn't come from one big error. It comes from four or five small, systematic leakages that compound over time.
The 5 Sources of OTA Short Payouts
1. Commission Rate Drift
Your OTA contract specifies a commission percentage. But contracts get renegotiated, platform tiers change, and sometimes the rate in the system simply doesn't get updated.
Most operators verify their payout amount - they don't verify the effective rate. A 0.5% commission overcharge on ₹5 lakh monthly OTA revenue is ₹2,500/month you're overpaying silently.
How to catch it: Divide commission deducted by gross booking amount every cycle. Compare to your contract rate. Flag any variance immediately.
2. Cancellation Deductions That Don't Match Reality
When a passenger cancels, the OTA refunds them and deducts the equivalent from your payout. That's expected. What's not expected:
Deductions for cancellations that happened in a previous settlement cycle (double-deducted)
Deductions for bookings that were cancelled after the passenger travelled (system error)
Deductions for cancellations initiated by the OTA due to their own operational issues
These don't show up as obvious errors - they just make the cancellation total slightly higher than your actual cancellation list.
How to catch it: Export your full cancelled booking list for the period. Match every cancellation deduction in the Payment Advice to an actual booking ID. Any deduction without a match is disputable.
3. Settled Bookings Missing from Payout
OTAs settle bookings based on travel date, not booking date. Settlement windows vary - typically 2–5 days post-travel depending on the platform and your contract tier.
What sometimes happens: bookings fall into a gap between settlement cycles and simply don't appear in either cycle's payout. They're not in the current Payment Advice, and they're not in the next one either.
If you're not tracking expected settlements against actual payouts at booking level, these just disappear.
How to catch it: Maintain a running log of bookings by travel date. Cross-reference each settlement cycle against travel dates that should have settled. Identify any booking IDs that haven't appeared in any payout after the expected settlement window.
4. Convenience Fee Not Credited
Some operator contracts include a share of the convenience fee that OTAs charge passengers. This is a relatively small amount per booking but accumulates meaningfully at volume.
Many operators don't even know this is in their contract - and even those who do often don't verify whether it's being credited correctly each cycle.
How to catch it: Re-read your OTA contract's fee-sharing clause. Calculate expected convenience fee credit based on booking volume. Compare to what's appearing (or not appearing) in your Payment Advice.
5. GST Invoice Not Raised by OTA
OTAs charge GST on their commission and are supposed to issue a proper tax invoice for it. If they don't - or if the invoice is delayed - you can't claim that GST as Input Tax Credit in your GSTR-2B.
This isn't technically a "short payout" in cash terms, but it increases your effective net cost per booking because you're paying GST that you can't recover.
⚠️ ITC eligibility depends on your GST registration type and compliance status. Confirm with your CA before claiming.
How to catch it: Check that every settlement cycle comes with a proper GST invoice from the OTA. If it's missing, follow up immediately - delays in receiving invoices push your ITC into later months.
Why Operators Don't Dispute These
The honest reason: it's too hard.
Raising a dispute with an OTA requires:
Identifying the specific booking IDs in question
Pulling the Payment Advice, booking report, and cancellation log
Cross-referencing them manually
Writing a formal dispute with evidence
Following up through the OTA's support system
Doing all of this within the dispute window (usually 30 days)
Most operators don't have the bandwidth. So the disputes don't get raised. The OTA keeps the money. And the operator assumes it's just "how the system works."
How to Recover Underpayments
Step 1: Audit the last 3 months
Pull Payment Advice and booking reports for the last 3 settlement cycles across all OTAs. Run the commission rate check and cancellation match for each. Quantify the gap.
Step 2: Raise disputes with evidence
Most OTAs have a finance helpdesk or a dispute ticket system in the operator portal. Submit:
The specific booking IDs in question
The Payment Advice showing the deduction
Your booking export showing the discrepancy
A clear statement of the amount in dispute
Step 3: Escalate if unresolved
If the support ticket doesn't move within 7–10 business days, escalate to your OTA account manager. Large-volume operators typically have a dedicated contact - use it.
Step 4: Fix the process going forward
Past underpayments are recoverable up to a point. What matters more is ensuring every future cycle is verified before the dispute window closes.
The Scale Problem
Doing this manually for one OTA is hard. Doing it for three - RedBus, AbhiBus, Paytm Bus - running staggered settlement cycles every few days, across a fleet of 10–30 buses, is operationally unsustainable without a system.
This is what GaadiKharcha's OTA Reconciliation module is designed for: tracking expected vs. actual settlements at booking level, flagging commission rate variances automatically, and surfacing dispute candidates before the window closes.
See how GaadiKharcha helps Daily Intercity Bus operators recover OTA revenue →
Quick Audit Checklist
[ ] Calculate effective commission rate for each OTA this cycle - does it match your contract?
[ ] List all cancellation deductions - does each one match an actual cancelled booking?
[ ] Identify any bookings by travel date that should have settled but haven't appeared in any payout
[ ] Check whether convenience fee credit appears if your contract includes it
[ ] Confirm GST invoice received from each OTA for this settlement period
[ ] Raise dispute tickets for any identified discrepancies before the dispute window closes
Summary
OTA short payouts aren't usually the result of fraud - they're the result of systematic gaps in how settlements are processed, combined with operators who don't have the time or tools to verify every cycle.
The operators who recover this revenue are the ones who treat reconciliation as a weekly process, not a month-end task. Even catching one commission rate discrepancy or one batch of unmatched cancellations can recover more than the cost of the time spent checking.
Verify every cycle. Dispute within the window. Or automate both.
GaadiKharcha is a fleet finance management platform built for Indian bus operators. If OTA reconciliation is eating into your team's time every month, talk to us.
RedBus, AbhiBus, and Paytm Bus are trademarks of their respective owners. GaadiKharcha is not affiliated with, endorsed by, or officially partnered with any of these platforms. All platform names are referenced solely for descriptive and educational purposes.
Revenue recovery figures mentioned in this article are illustrative estimates based on general industry patterns. Actual results will vary based on your OTA contracts, booking volumes, and specific discrepancies present in your settlements.
Tags: ota-reconciliation bus-operator redbus abhibus paytm-bus short-payout fleet-finance revenue-recovery payment-advice