PG owners get told two contradictory things: that residential accommodation is outside GST, and that their PG business definitely needs to register. Both are sometimes right, which is why this is one of the more genuinely confusing tax questions in the sector.
Quick answer (for the impatient)
The treatment turns on the nature of the supply, not on what you call the business.
A room plus meals plus services is not obviously the same supply as a room, and that distinction is where the analysis happens.
This area has seen changes and litigation. Get a current answer for your specific setup rather than relying on any article, including this one.
Why "residential accommodation is exempt" isn't the end of it
The exemption concept relating to residential dwellings is what PG owners latch onto, reasonably. The complication is whether what you're providing is a residential dwelling used as a residence, or a bundled commercial service that happens to include somewhere to sleep.
A PG providing a bed, three meals, housekeeping, laundry, Wi-Fi and security looks materially different from a landlord letting a flat. How much different, and with what consequence, is exactly the question — and it's been contested, considered by authorities, and revisited more than once.
What actually drives the analysis
The factors that tend to matter, which are the ones to be ready to describe to your CA:
What's bundled. Accommodation only, versus accommodation plus meals and services.
How you charge. A single inclusive figure, versus separately identified rent and service charges.
Duration and nature of stay. Long-term residents versus short-stay occupants.
The property's character and use. How the premises are classified and how they're actually used.
Your aggregate turnover, which drives registration obligations independently of the exemption analysis.
The charging structure point is worth dwelling on, because it's the one under your control. How you present rent versus services on your bills can matter to the analysis — which means this is a decision to make deliberately with advice, not one to stumble into through billing convenience.
The turnover question is separate
Two independent questions get conflated constantly. Whether your supply is taxable is one. Whether you're required to register is another, driven by aggregate turnover computed across your PAN.
The trap that catches PG owners specifically: an owner running a PG plus another business — a shop, a second property, consultancy income — is assessed on aggregate turnover across all of it. Each business looks small; the aggregate may not be.
If you're in scope, what changes
Registration brings invoicing obligations, returns, and the input tax credit question. That last one is worth modelling rather than assuming: a PG with significant input costs may be better or worse off depending on the position taken, and the arithmetic isn't obvious.
It also affects how you present bills to residents. A tenant who has been paying ₹9,000 all-in and starts receiving a tax-broken invoice will ask questions, and having a clear answer prepared is worth more than the awkwardness of improvising one.
A practical operating workflow for this PG
The useful way to apply Does GST Apply to Your PG? The Question That Depends on What You're Actually Selling is to turn the idea into a repeatable operating rhythm. Start with the current process, not the software screen. Write down who begins the task, what information they need, where the record is kept, who checks an exception, and what the resident is told. That prevents a common PG mistake: digitising an unclear process and discovering that the same argument now happens faster.
Step 1 — establish the starting record. The treatment turns on the nature of the supply , not on what you call the business. The owner or warden should decide which field, document or confirmation is the source of truth. Existing residents, rooms, balances or requests should be checked before a new workflow is switched on. If the starting record is incomplete, note the gap openly instead of filling it with an assumption.
Step 2 — define responsibility. A room plus meals plus services is not obviously the same supply as a room , and that distinction is where the analysis happens. Name the person who enters the record, the person who can approve a change, and the person who follows up when something is overdue. In a small PG those roles may belong to one person, but writing them down still matters. It stops a cook, caretaker, accountant and owner from each believing that somebody else handled the same exception.
Step 3 — test one real case end to end. This area has seen changes and litigation. Get a current answer for your specific setup rather than relying on any article, including this one. Use one room, one resident or one billing cycle first. Follow the record from the first action to the final acknowledgement. Check the owner view, staff view and resident-facing result separately. A backend record or internal screen is not enough if the person expected to act cannot reach it.
Step 4 — keep an exception path. Decide what happens when information is late, a resident disputes the record, a staff member lacks permission, or the usual approver is absent. Record the reason for any manual correction. Do not quietly overwrite history simply to make a dashboard look tidy.
What the weekly review should cover
Fifteen focused minutes is enough when the team brings the same evidence each week. Review what was completed, what remains open, which cases needed manual intervention, and whether residents received the message or document they were meant to receive. The objective is not a perfect-looking count. It is to find repeated friction while it is still small enough to fix.
Review question Evidence to check Action if it fails
Did the process start with a complete record? The original entry, document or resident confirmation Correct the source and note who verified it
Did the right person act? User, timestamp and permission trail where available Clarify responsibility or access before the next cycle
Did the resident receive a clear outcome? Receipt, message, portal view or signed acknowledgement Send the missing confirmation and repair the template
Did an exception repeat? Open cases and manual corrections from the week Change the process; do not keep relying on memory
For Why "residential accommodation is exempt" isn't the end of it, ask whether staff explain the process consistently. For What actually drives the analysis, compare the operating record with what the resident experienced. For The turnover question is separate, look for cases handled outside the agreed path. These checks do not assume an automated report, alert or capability that the article has not established.
A safe rollout checklist
Confirm the property, room and resident scope before changing any record.
Check that only the intended role can create, approve, reverse or view the relevant information.
Run a real test with the people who perform the work, not only an administrator.
Keep the previous record available until the new result has been checked.
Tell residents what changes, what does not, and where they can raise a dispute.
Review the first week and document every manual workaround.
This checklist protects both sides. Residents get a process they can understand and question. Owners get a record that can be checked later instead of an argument reconstructed from memory. It also respects the boundary between guidance and capability: use only screens, permissions and resident surfaces actually reachable in your Hotel/Hospitality tenant.
One more question operators ask
Should we move every existing case into the new process at once?
No. Start with a controlled group or the next clean cycle, reconcile the result, and then expand. A staged rollout is slower for a few days and far safer than correcting every resident record after a rushed migration.
Where we're honest about the limits of this post
No rates, thresholds, notification numbers or exemption entries are quoted here, and no conclusion is offered about whether your PG is taxable. That's deliberate. The treatment of PG and hostel accommodation has changed, has been the subject of advance rulings that don't all point the same way, and depends on facts specific to your operation. An article that gave you a confident answer would be doing you harm.
What to do: take your actual setup — what you bundle, how you charge, your turnover across all businesses — to a CA and get a written position. If your situation is genuinely borderline, that written position is what protects you later.
FAQ
My PG is small — am I automatically out of scope?
Turnover thresholds exist, but they're computed across your PAN, not per business. Check the aggregate.
Should I split rent and services on my bills?
Possibly relevant to the analysis — which is exactly why it should be a decision made with advice rather than for convenience.
What about the mess specifically?
Food supply raises its own questions, alongside your FSSAI obligations. Raise it explicitly with your CA rather than assuming it follows the accommodation treatment.
The bottom line
PG GST isn't a question with a general answer, and the confident answers circulating in owner groups are the most dangerous thing in this area. Get a written position on your own facts, once.
See what PG accounting handles and doesn't, TDS obligations, or pricing.
Bills that hold up. Start free →
Comments