Hotel owners tend to think about tax on what comes in. The obligations that actually trip people up sit on what goes out — the rent on the building, the housekeeping contractor, the commission an OTA deducted before you ever saw the money.
Quick answer (for the impatient)
TDS is your obligation as a payer, not something your vendor handles for you.
The usual hotel exposures are rent, contractors and professional fees — and commission, which is the sneaky one.
OTA commission netted off before payout is still a payment you made. Money you never touched can still carry an obligation.
The commission trap
This is the one worth reading even if you skip the rest. When a booking platform remits your payout net of its commission, it is intuitive to treat only the amount received as your revenue and forget the rest. But commercially the transaction is two flows: the guest paid the gross, and you paid a commission out of it. That commission is a payment you made to the platform.
Whether and how TDS applies to that depends on the nature of the arrangement and the platform's status, including whether it's a non-resident — which brings a different and more complicated set of rules. That's a question for your CA, but the trap is not knowing to ask it, because the money never appeared in your bank account as an expense.
Rent, if you don't own the building
A large number of independent hotels operate from leased premises, and rent above a threshold attracts TDS. Two things go wrong here regularly. Rent paid to co-owners is often assessed per co-owner rather than in aggregate, which people get backwards in both directions. And rent that includes furniture, fittings or equipment can be treated differently from rent for the premises alone — so a single monthly payment may not be a single category.
If your lease bundles the building and the furnishings into one figure, that's worth unpacking with your accountant rather than assuming one rate covers it.
Contractors and the housekeeping question
Outsourced housekeeping, security, laundry and maintenance are contractor payments. The distinction that matters — and that hotels get wrong — is between a contractor and an employee. If you've engaged people described as contractors but who work fixed shifts under your supervision using your equipment, the substance of that relationship may not match the label, which changes both your TDS position and your labour obligations.
The label on the invoice does not settle this. The working arrangement does.
Where we're honest about the limits of this post
No rates, thresholds or section numbers here, deliberately. They change, they differ by payee status, and several depend on whether the recipient is a resident. What this post is for is identifying which of your outgoing payments deserve a conversation — the rest is genuinely your CA's work, and the specifics are exactly the part where general articles do damage.
A realistic hotel example: what the team sees during a working shift
Picture Lakeview Residency, an independent property where the same manager may answer a booking query, approve a rate, settle a guest account and help a new employee before lunch. The question behind The TDS a Hotel Owes Without Realising: Rent, Contractors and Commission does not arrive as a neat software task. It arrives while somebody is waiting, another department needs an answer and the record must still make sense at the end of the day.
The first useful observation is this: TDS is your obligation as a payer , not something your vendor handles for you. The manager should translate that statement into a visible hand-off. Who starts the action? Which record do they open? What information must already be present? Who checks the result? If any answer depends on one experienced employee remembering an exception, the process is not yet reliable.
The second observation is equally practical: The usual hotel exposures are rent, contractors and professional fees — and commission, which is the sneaky one. At Lakeview Residency, the team would test this with one ordinary case and one awkward case. The ordinary case confirms the expected path. The awkward case exposes missing permissions, incomplete data, unclear ownership or a decision that still happens in a private message. Both tests matter because hotel operations rarely fail on the clean example shown in a demonstration.
The third observation is about the downstream record: OTA commission netted off before payout is still a payment you made. Money you never touched can still carry an obligation. A completed action should leave enough context for the next person to understand what happened without reconstructing the story from calls and chat messages. That does not mean collecting every possible field. It means keeping the few facts that change the decision, the status, the responsible role and the next action together.
Rollout checklist: move from a good idea to a repeatable process
Use this checklist before the team treats the workflow as normal operating procedure. It deliberately separates product reachability from management discipline: software can make a record available, but the property still decides who owns it and how exceptions are handled.
Name the owner. Choose the role responsible for starting and completing the process. "The office" or "the front desk" is too vague when several people share a shift.
Confirm access. Test with the real role and tenant configuration, not an unrestricted demonstration account. Check enabled modules, feature permissions and the property or outlet context.
Define the minimum input. Agree which guest, room, date, amount, document or operational detail must be present before somebody can act.
Run the normal case. Complete one realistic example from beginning to end and ask the next team member to explain the result using only the saved record.
Run the exception. Try a correction, cancellation, missing value, late change or disputed instruction that genuinely occurs at the property. Record the fallback if the product path does not cover it.
Check the hand-off. Make sure the relevant people in front desk, reservations, housekeeping and accounts can see the status they need without receiving unnecessary access to unrelated records.
Write the fallback. If the system is unavailable or the case sits outside the verified path, state who records the temporary decision and who reconciles it later.
Review after live use. Ask staff where they paused, duplicated work or returned to a spreadsheet. Fix the process before adding more fields or automation.
Decision table: evidence to collect before you approve the workflow
A manager does not need a large transformation project to evaluate this topic. A short evidence review is enough to distinguish a reachable workflow from an attractive claim. Use the table during a property review and write the answer in plain language.
Review point What to verify Evidence to keep Decision if it fails
Reachability The responsible role can open and complete the path in the correct tenant and property context. A completed test record and the role used. Do not announce the workflow; check provisioning and permissions.
Data quality The minimum information needed for the decision is present, understandable and current. The input checklist and one reviewed example. Fix the collection step before adding automation.
Ownership One role owns the next action and another can review where separation is appropriate. The operating owner and escalation path. Assign responsibility before rollout.
Exception handling A correction, cancellation or disputed case has a documented path. The tested exception and fallback note. Keep the process in controlled trial use.
Downstream hand-off The next department sees the status it needs without manual re-entry or excessive access. A hand-off check by the receiving role. Use a documented interim hand-off and reconcile it.
The honest AXOIX limit and what to review after the first live cycle
The first review should focus on behaviour, not vanity metrics. Ask the people who performed the work where they hesitated, what they entered twice and which decision still escaped into a phone call or personal message. Compare the saved record with what actually happened. If they differ, find the earliest point where context was lost.
Then separate a training problem from a product boundary. A training problem means the verified path exists but the team did not understand the trigger, required input or next action. A configuration problem means the module, property context or permission is not available to that role. A product boundary means the audited path does not support the case. Those three diagnoses require different responses; calling all of them "user error" guarantees a repeat.
Keep the limitation visible while reviewing this article: Verify the workflow and its applicability before relying on it. That boundary is part of the buying and rollout decision, not a footnote to remove from the sales conversation. Where the workflow is usable, test it honestly. Where it is partial, keep the manual control explicit. Where applicability depends on law, policy or professional judgement, confirm it with the appropriate adviser.
FAQ
Do I deduct TDS on guest payments?
Generally your guest-facing concern is GST, not TDS. TDS mostly attaches to what you pay out. Corporate clients may deduct TDS on payments to you, which is a separate thing to track.
What if a corporate client deducted TDS on my invoice?
That's credit available to you — reconcile it against your Form 26AS rather than treating it as a shortfall in payment.
Does this apply to a small hotel?
Obligations turn on thresholds and on your audit status, not on how small you feel. Check rather than assume.
How should a hotel test this before rolling it out?
Use the real tenant, property context and staff role. Complete one ordinary case and one exception from start to finish, then ask the receiving role to verify the saved result without relying on a private message.
What should the team do if the verified product path does not cover its case?
Keep a documented manual control, name the person responsible for reconciliation and avoid describing the unsupported step as automated. Recheck module provisioning and permissions before concluding that a capability is absent.
The bottom line
The TDS conversation for a hotel is a conversation about the payments ledger, not the guest bill. Sit down with your outgoing payments for one quarter and ask which ones deserve a second look — commission first.
See how hotel GST slabs work, how operations reach the books, or pricing.
Know what you owe. Start free →
Comments