· 4 min read · Updated 31 Aug 2026
By Correct Editorial — Compliance Research Desk
One Company or a CA Practice: Running Indian Compliance
Published on: August 15, 2026
Indian compliance software has a habit of picking a side. Tools built for CA firms talk about portfolios and staff utilisation. Tools built for founders talk about a single GSTIN and a mobile reminder. The work underneath is the same: know what is due, hold the proof, run the numbers, match them, catch what is missing.
A private limited company in Pune and a CS practice in Mumbai with forty clients both live under the Companies Act, 2013, GST, TDS, PF/ESI and, increasingly, DPDP. The founder needs the calendar for one entity. The practice needs that calendar multiplied, with walls between clients. If the product only speaks "24 client companies", the owner leaves. If it only speaks "your GSTIN", the firm cannot operate.
This article is the operating model: same job, two doors.
What Is the Job, Regardless of Who Buys?
Five systems have to talk:
- Calendars. ROC/MCA, GST, TDS, PF/ESI, DPDP: owner, due date, penalty if it slips. See Annual Compliance Calendar for Companies (2025-26) and GSTR-3B Due Date and Late Fee in India.
- Vault. Documents and passwords, company-owned. See Who Should Hold GST and MCA Logins and Challans?.
- Finance ops. Invoices, vendors, books: the numbers filings are built from.
- Reconciliation. GSTR-2B against the purchase register before the portal does it. See GSTR-2B vs Purchase Register: How to Reconcile ITC.
- A layer that sees all four. The invoice with no matching entry, the filing marked done with no evidence, the obligation nobody owns.
That sequence is how you stay audit-ready by default. It does not change because the buyer is a firm.
What Changes for a Practice?
- Isolation. Client A's challans never appear in Client B's vault.
- Owners inside each company. "I thought you were handling it" is a firm-failure mode. Every obligation still needs a name at the client.
- Portfolio view without mixing evidence. The managing partner sees what is due this week across the book. The evidence pack for a notice is still per company.
- Commercial honesty. Price per company, so one GSTIN is a complete product, not a discounted slice of a firm SKU.
A practice that registers every client portal under the firm's email recreates the custody problem in Who Should Hold GST and MCA Logins and Challans?. Do not scale that.
What Changes for a Founder?
- You do not need a 24-company workspace to understand the product
- You need the penalty on the GSTR-3B line, not only the date
- You need to log in to your own GSTIN after the CA engagement ends
- You need the evidence pack before the first notice, not after
If a homepage only shows a firm ledger, owners correctly conclude the product is not for them. The dual model is: your company, or a practice, same underlying entity.
How Should You Start?
Running one company. Add the entity. Upload one thing you have lost before. See what is already due. Free to start.
Running a practice. Pilot calendars, vault, finance ops, reconciliation and copilots on a small set of real client companies. Keep the cohort small on purpose.
Correct is built as one product with two doors, not two products glued together. The AI is not a fifth module. It is the reason the other four sit in one system. Open the app at Correct.
The Third Case: A Group, Not a Practice
The two-door framing covers the common cases and leaves out a third that is increasingly ordinary — one owner running several of their own companies. A holding entity with an operating subsidiary and an LLP is not a practice, because there is no client relationship and no wall to maintain between them. It is also not a single company, because the obligations multiply.
This case behaves like a practice structurally and like a founder commercially. The work needs multi-entity handling, records scoped per company, and one view across all of them. What it does not need is client isolation, staff utilisation or engagement management, because there is only one principal.
The practical test is simple: do the entities have different owners? If yes, you need walls. If no, you need scope. Pricing that treats every multi-entity account as a firm gets this wrong, and charges a group for isolation machinery it will never use.
What Happens at Handover
The moment that exposes how a compliance setup was actually built is the moment it changes hands — a new CA is appointed, a finance hire replaces an outsourced arrangement, or a practice loses a client.
If records live in the company's own account, handover is an access change. The obligations, evidence and history stay where they are; who can see them changes. If records live in the advisor's system, handover is a migration — and a migration performed under time pressure, usually with an open filing deadline somewhere in it.
That difference is invisible while nothing changes, which is why it is rarely a purchase criterion and frequently a regret. The question worth asking before an engagement starts, rather than as it ends, is where the statutory record will live and who can retrieve it without anyone's cooperation.
For practices, the same logic runs the other way: a firm that keeps client records inside client-owned accounts has less to migrate when a client leaves, and a cleaner story when a client asks what happens if they do.
References
- Companies Act, 2013 — ROC/MCA obligations for every company
- CGST Act, 2017 — GST returns and records for every GSTIN
- EPFO Unified Portal — PF for covered establishments
- ESIC — ESI for covered establishments
- DPDP Act, 2023 — Data protection duties for data fiduciaries
- ICAI — Practice management and client records
- ICSI — Secretarial practice across client companies
Frequently asked questions
- Is compliance software in India built only for CA firms?
- No. A growing company has the same GST, ROC, TDS and PF/ESI calendar as a client of a firm. The difference is volume: one GSTIN versus dozens. The work is the same job. The system should work for one entity without forcing a portfolio mental model.
- What does a CA or CS firm need that a single company does not?
- A practice needs isolation between client companies, per-company evidence, named owners inside each entity, and the ability to see what is due across the book without mixing records. Price per company, not a vague "firm seat", keeps that isolation honest.
- Can one product serve both without watering down either?
- Yes, if the unit of work is the company. The owner runs one company. The firm runs many copies of the same company workspace. AI that reads calendar, vault, books and returns only works if those four sit in one product per entity.
- Where should a founder start versus a managing partner?
- A founder should add the entity, upload one document that has been lost before, and see what is already due. A practice should pilot the full suite on a small set of real client companies and keep the cohort small until the operating rhythm is proven.