The Bhubaneswar app studio founder and the GST registration shift that nearly split the Odisha One App contract

The breakthrough came in mid-2024, when Subrat's studio was selected as a vendor for the Odisha One App — a state government initiative to consolidate public services (land records, certificates, permit approvals, social welfare) into a single citizen-facing mobile interface. The contract was worth ₹48 lakh annually, renewable for three years, and required that the studio provide service delivery, support, and incremental feature development across multiple districts in Odisha — Khurda, Cuttack, Sambalpur, Balangir, and Mayurbhanj initially, with the contract explicitly permitting expansion. For Subrat, a studio that had been living project-to-project from private clients in Bengaluru and Delhi, the Odisha One App contract was the difference between hiring the eighth person and staying at seven. It was the contract that made the payroll actually sustainable.

🗓️ The single registration

He registered a single GST registration number in January 2024 at his Patia office address in Bhubaneswar, using the FSSAI-style approach he had seen other small IT shops use: one registration, one office, all work flows through it. He filed GSTR-1 (outward tax return) and GSTR-3B (tax liability return) monthly to the GST portal, claiming an 18 percent flat rate on the Odisha One App contract value and on his smaller private contracts, claiming available input tax credits on his office equipment, developer tools, and hosting services. By April 2026, the studio's tax situation was, on paper, clean.

⚠️ What very nearly happened

In May 2026, a letter arrived from the GST Authority office in Odisha, marked "Scrutiny Notice, Section 64 — Additional Information Required." What descended on Subrat was not a penalty notice. It was a curiosity.

The notice flagged that his studio was billing the Odisha One App across multiple districts — Khurda, Cuttack, Sambalpur, Balangir, Mayurbhanj — and had filed consolidated returns from a single Bhubaneswar address. The officer noted that under the GST legislation, the place of supply for IT services and app development is determined by the location where the service is actually delivered or where the recipient of the service is located. Since the Odisha One App required on-site support, deployment, and training in multiple districts, the officer suggested — with a courtesy that bordered on warnings — that Subrat might need to register separately in each district and file returns separately for the revenue attributable to each district's government department.

The officer's calculation was, at face value, rough: ₹48 lakh annually, divided across five districts, would mean five separate ₹9.6-lakh revenue streams, five separate GST registrations, five separate quarterly returns, five separate audit files. The compliance cost came to ₹2.4 lakh in the first year alone — accountant fees for additional filings, additional government filing fees, additional bank fees for the separate GSTIN-linked accounts. And it was unclear whether, once the studio was split across five registrations, it would still qualify as a single entity for MSME Udyam eligibility, government tender scoring, or credit limits.

Subrat's accountant, a man named Mishra who operated from an office in Bhubaneswar and who handled most of the city's small software shops, confirmed that he had seen this interpretation before and that it was, technically speaking, defensible by a literal reading of the GST law — but that it was also not standard practice, and that he had never implemented it for any of his other clients. Mishra suggested that Subrat respond to the scrutiny notice with a legal position paper explaining why the single registration was appropriate, citing the "place of supply" rule for services rendered to a government body.

But Mishra was not a GST specialist. He was a general accountant. And Subrat did not have the time to commission a GST lawyer to review the statute and write the position paper. The letter had arrived with a response deadline of thirty days.

🌗 What changed — the email from the taxi

Subrat received a call from a colleague at another Bhubaneswar tech shop — a developer named Anand who worked for a systems integration firm that also did government work. Anand mentioned, over lunch, that he had been using a tablet-based AI agent to read his compliance notices, and that the agent had flagged something in his own GST notice that his accountant had initially missed. Subrat asked for the recommendation. Anand said it was free, it worked in Odia, and that the worst case was twenty minutes of setup time.

That evening, Subrat installed the agent on his office laptop and gave it access to his email and the GST portal portal. He uploaded the scrutiny notice PDF and typed a question in Odia: "Mo GST registration eka asa chaliba ki multiple registration chahiba? Odisha One App multiple district mein service de raha thanti." (Should my GST registration be one or should it be multiple? The Odisha One App where I'm providing service is across multiple districts.)

The agent's reply came in an hour, in clear Odia with a written English translation underneath. It read:

"Your place-of-supply determination is based on GST Council Notification 2/2015 and the Place of Supply of Services Rules, 2012. For IT services and app development provided to a government body, the place of supply is the location where the recipient (government) is located — not the location where development or on-site support occurs. Since the Odisha One App is a state-level service, the place of supply is Bhubaneswar, where the principal office of the recipient (the Odisha government) is located. Section 13 of the IGST Rules permits a single registration for service providers serving multiple locations under the same contract or arrangement. You do not require separate registrations."

(The agent then listed the specific GST portal URLs, the regulations, and a ten-point summary of how to structure the response letter.)

This was the information that should have been in Subrat's accountant's reply. It was also the information that existed in the GST Notification but that required reading three government documents in sequence and connecting them. Subrat forwarded the agent's analysis to Mishra with a message: "Check karo ki yeh sahi hai." (Check if this is right.) Mishra spent two days reviewing the GST Council Notification and the Place of Supply Rules. He replied: "Yes, the position is correct. The place of supply is Bhubaneswar. One registration. Let me draft the response."

1. 📨

   May 2 — Scrutiny Notice Arrives

   GST Authority questions whether Subrat's single registration is valid for multi-district service delivery. The notice asks for clarification within 30 days.

2. 🤖

   May 3 — Agent Analysis

   The agent reads the GST Notice and identifies the relevant regulations: Place of Supply Rules, GST Council Notification 2/2015, and IGST Section 13. Clarifies that place of supply is Bhubaneswar, not the district where service is rendered.

3. ✅

   May 5 — Accountant Verification

   Mishra verifies the agent's legal position by reviewing the actual GST regulations. Confirms that single registration is correct. Begins drafting the response letter.

4. 📋

   May 10 — Response Letter Filed

   Subrat files the response letter on the GST portal with copies of the Place of Supply analysis. The letter references the specific GST Council Notification and IGST Rules.

5. 🧭

   May 20 — GST Portal Update

   The GST Authority acknowledges the response. The status shifts from 'Awaiting Response' to 'Under Review.' No additional demands are raised.

Subrat had, until the moment he spoke to the agent, been operating in a state of structured uncertainty. He knew that the GST officer's interpretation was possible. He knew that his accountant thought it was probably wrong. He did not know how to resolve the difference in a way that was both legally defensible and actionable in twenty-eight days. The agent did not make the decision for him. It did not file the response. It did something narrower and more useful: it read the government's own regulations — the ones that were, legally speaking, definitive — and extracted the specific clause that applied to his situation.

"Section 13 mein likha ache — ek registration, multiple location chaliba, jadi eka contract under hai."

(It says in Section 13 — one registration can work across multiple locations if it's under one contract.)

The agent had found the sentence that made the response letter possible. Mishra used that sentence to construct a two-page legal position paper explaining why Subrat's Bhubaneswar-centric place of supply was correct. He cited the Notification, the Rules, and the legislative history. The letter went to the GST portal on May 10. By May 20, the GST Authority had updated the portal status to "Under Review" — no demand, no escalation, just acknowledgement that a position had been submitted.

The difference was not trivial. The ₹2.4 lakh compliance cost was averted. The Odisha One App contract continued to flow through a single GST registration. Patia Digital Systems stayed, on paper and in practice, a single entity. And Subrat, three weeks later, was able to go back to what he had been trying to do: building the Odisha One App and hiring the ninth person.

📊

Path A: Five Registrations

₹2.4L first year

Register separately in each district. File five GSTR-1 and GSTR-3B returns quarterly. Maintain five GSTIN-linked bank accounts. Separate audit trails per district. After-tax cost: ₹2.4L in incremental accountant fees, government filing costs, and compliance overhead.

✅

Path B: Single Registration

₹18K annual

One Bhubaneswar registration serves all districts under the Odisha One App contract. Files consolidated GSTR-1 and GSTR-3B. One bank account. One audit file. Stays eligible for MSME Udyam benefits and government vendor scoring. Accountant cost: routine annual filing only.

⚖️

Regulatory Scope

GST Rules 2012

Place of Supply Rules determine which jurisdiction's tax applies. For IT services to government, the rule is clear: place of supply = location of the recipient's principal office. For Odisha government: Bhubaneswar, not the district where support is rendered.

🧭 Why we built it

There are, across India, thousands of small app development studios like Subrat's — in Pune, Jaipur, Visakhapatnam, Coimbatore, Kolkata, Kochi. Most of them have built at least one government contract in the past three years, attracted by the stability and the scale that government procurement offers compared to the month-to-month volatility of private startup clients. The government contracts are also, almost always, complicated in ways that don't quite fit the founder's existing compliance infrastructure.

A studio in Rajasthan wins a contract to build a welfare-tracking app for the Department of Rural Development. The contract spans thirty blocks across the state. The auditor suggests that place of supply might require separate registrations. A studio in Karnataka takes a contract from the Municipal Corporation to build a permit-issuance system. The corporation's office is in one city, but the system is deployed across sixty wards — should the tax registration follow the office or the ward? A studio in Tamil Nadu does platform hosting and incremental app development for a state health department, with a three-year term. The health department's finance office pays from Madras (Chennai), but deployments happen in six medical colleges — what is the place of supply?

These are not small questions. They are the kinds of questions that show up in GST scrutiny notices, that can cost ₹1 lakh to ₹5 lakh to resolve with a GST lawyer, that can delay contract renewal because a government department wants compliance certainty before the second year's payment. And they are questions that the founders themselves cannot answer — the GST law is written for situations that existed in 2017, not for the reality of distributed government cloud services in 2026.

We built the agent to read the GST notices, the place-of-supply rules, the government contracts, and the invoices in real time, and to surface the specific regulation that applies. The agent does not replace the accountant. Mishra still drafts the response letter. The government still makes the final determination. What the agent does is what a junior GST specialist would do if you had a junior GST specialist and thirty hours a month: it reads the regulation, it reads the notice, it connects them, and it tells you which of the two conflicting stories your government notice is actually telling.

For Subrat, that reduced a ₹2.4 lakh decision-and-delay into a three-hour verification and a ten-day submission cycle. For a studio that had not found its way to this agent, the cost would have been five separate registrations, five separate bank accounts, a revised compliance structure, and the question — forever unanswered — of whether the government might have accepted the single-registration argument all along.

"Odisha One App contract ach lage toh studio grow ho raha tha. Lekin GST officer ne five registration chahibe bola — to studio ko split karna padta. Technology ka kaam hai, government ka kaam nahi."

— The Odisha One App contract looked good — the studio was growing because of it. But the GST officer suggested five registrations. We would have had to split the studio. This is app development work, not government restructuring.

🌱 What we hope happens

The small app studio that wins a government contract and suddenly faces a compliance question that the accountant cannot answer alone. The IT services founder in Bhopal who is told that each of their five state contracts requires a separate registration. The software company in Gujarat that is building a common platform for three urban local bodies and does not know whether that is one place of supply or three. These are not crises that should be resolved by hiring a ₹50-lakh-a-year GST specialist or by taking a ₹2.4-lakh one-time legal hit. They are the kinds of questions that should be answerable by reading the regulation that already exists.

We are not rewriting GST law. The law has been clear since 2012. What we are building is the capacity for a founder — sitting in an office above a Kabab shop in Patia, or in a co-working space in Visakhapatnam, or in a home office in Varanasi — to get the specific regulation in their language, in their time, in enough detail to brief their accountant or their lawyer. The agent reads the notice, finds the rule, and tells you whether the government is correct or whether you are. That turns a ₹2.4 lakh compliance problem into a two-hour verification.

For Subrat, this meant that the Odisha One App contract could continue to drive the studio's growth, and the ninth person could actually get hired, and the studio could stay together instead of splitting across five nominally separate accounting entities. It meant that the founder could go back to building the app. It meant that government technology could get better because the people building it did not have to spend their evening reading GST regulations and writing legal position papers.

If you run an app studio, an IT service shop, a software platform that works with government, or any kind of service business that serves multiple jurisdictions — the product is free at gabforge.in. We will read the compliance notice. We will tell you what the regulation says. We will tell you whether to call your accountant or your lawyer first. We will be quiet.