How many compliances does a company in India actually track?

Why is there no single number?

Vendors and consultants quote figures in the thousands or tens of thousands. Those numbers are not wrong so much as unanswerable: they count every obligation in every Act a company could conceivably be subject to, across every state. No company is subject to all of them, and a figure that applies to everyone describes no one.

The useful question is narrower: how many obligations apply to this entity, at these locations, with these registrations and licences, this year. That number is driven by five multipliers, and once you see them you can estimate your own register in an afternoon.

• Central law — applies once per legal entity, with some filings repeated per registration.
• States — labour, shops, professional tax and stamp duty are state subjects, so each new state adds a parallel set.
• Registrations — GST is registered per state, so returns multiply by the number of GSTINs.
• Licences — each licence carries a renewal date and conditions, and every condition is an obligation.
• Events — appointing a director, opening a location or crossing a headcount threshold creates a filing with its own clock.

What does the central layer look like for one entity?

Take an illustrative private limited company: a manufacturing plant in one state, sales offices in two others, about 400 employees, and GST registered in all three states because it supplies from each. Assume it files GST monthly. This is the recurring central layer, counted per year:

• GST: an outward-supplies statement (GSTR-1) and a summary return with payment (GSTR-3B) every month, plus an annual return, for each registration. Three registrations × (12 + 12 + 1) = 75 returns. A business with aggregate turnover up to ₹5 crore may opt for quarterly returns with monthly payment under the QRMP scheme; this company is above that threshold.
• TDS: quarterly statements for salary and for non-salary payments. 2 × 4 = 8. The Income-tax Act, 2025 replaced the 1961 Act from 1 April 2026 and the statement forms were renumbered, so the form names your team uses may have changed while the quarterly rhythm has not.
• Provident fund: contributions and the electronic challan-cum-return within fifteen days of the close of each month under paragraph 38 of the EPF Scheme. 12.
• ESI: monthly contributions for covered employees. 12.
• Companies Act: at least four board meetings a year with no more than 120 days between two (section 173), the AGM, financial statements on AOC-4 within thirty days of the AGM and the annual return on MGT-7 within sixty days (sections 137 and 92). At least 7.

So what does that add up to?

75 + 8 + 12 + 12 + 7 = 114 dated filings and meetings a year, from a deliberately short list of central obligations, for a company that is not listed, not RBI-regulated and not in a licensed sector. A listed company adds the recurring disclosures under SEBI's LODR Regulations; a bank or NBFC adds RBI returns. Those are covered in our separate piece on building a compliance calendar.

Notice what drove the number. Most of it is GST, and GST is large only because it is multiplied by three registrations. Open a fourth state and the company adds twenty-five returns before anything else changes. This is the pattern throughout Indian compliance: the count is set less by how many laws exist than by how many places and registrations the business has.

What does each additional state add?

Labour, shops and establishments, professional tax and stamp duty are administered by states, so each location brings its own set. For the illustrative company, each of the three states contributes some or all of these:

• Shops and establishments registration for each office, under that state's own Act, with renewal and record-keeping rules that differ by state.
• Professional tax, where the state levies it. The Constitution caps it at ₹2,500 per person per year (Article 276), but registration, deduction and return periodicity are set by each state, and some states do not levy it at all.
• Labour welfare fund contributions, in states that have such a fund, at intervals set by the state.
• State rules under the four labour codes. The Codes were made effective from 21 November 2025, replacing 29 central labour laws, but for most private establishments the state is the appropriate government and states are notifying their rules on different dates. Until a state's rules are in force, the transition provisions keep parts of the older regime alive.

Why do licences add more than one row each?

A licence looks like a single obligation with a renewal date. It is usually a dozen. The plant in the example needs, at minimum, a factory licence and consent from the state pollution control board to operate — consents are required under section 25 of the Water (Prevention and Control of Pollution) Act, 1974 and section 21 of the Air (Prevention and Control of Pollution) Act, 1981. Depending on the operation it may also need fire safety clearance, registration for engaging contract labour above the statutory threshold, and sector licences such as food safety.

Each consent order or licence is issued with conditions: monitoring, returns, display requirements, limits, periodic reports. Every condition is an obligation with an owner and evidence, and conditions are where inspections find gaps, because they live in a PDF that nobody re-reads after the licence is filed away. A company that tracks only licence expiry dates is tracking a fraction of what its licences actually require.

What is the event-driven layer?

Some obligations have no calendar date at all. They start when something happens, and they are the ones most often missed because no recurring reminder exists for them.

• A director is appointed or resigns: the change must be filed with the Registrar, on DIR-12, within thirty days.
• A new office or warehouse opens: a shops registration in that state and, where it changes the place of business, an amendment to the GST registration.
• Headcount crosses a threshold: thresholds in the labour codes switch on registers, committees, standing orders and contribution schemes.
• A contract is signed: obligations inside customer, vendor and lease agreements — insurance certificates, audit rights, data protection duties, notice periods — are compliance obligations too, even though no regulator tracks them.

How do you count your own number?

The method matters more than the total, because the total changes every time the business does. Build it from the multipliers up:

• List legal entities, then every location of each entity with its state.
• List registrations per entity: GSTINs, PF and ESI codes, shops registrations, professional tax registrations.
• List licences and consents per location, and break each one into its conditions.
• Apply the central layer once per entity and the recurring returns once per registration.
• Add the events your business actually generates — appointments, openings, hiring thresholds, material contracts — as triggers rather than dates.
• Record, for every row, the provision it comes from, so it can be retired when the law changes.

What should software do with that number?

A tool that hands you a library of thousands of obligations has done the easy half. The hard half is applicability: which of those rows bind this entity at this location, and which have been switched off by a change in law. That is why applicability should be mapped from the entity, location, registration and licence structure above, not by scrolling a master list.

For reference, IntelloComply ships with 300+ cited statutory obligations and 340+ controls, and 43 business-event triggers, and the register for each customer is built from their own entities, locations and licences at onboarding. Whatever tool you use, the test is the same: pick any row and ask which provision it comes from, why it applies to you, and when it was last checked.