Statutory compliance calendar India: how to build one that stays true

Why most compliance calendars decay

Almost every firm has a compliance calendar. Most of them are a spreadsheet of dates copied from last year, and they fail in three predictable ways.

The first is no provenance. A row says "AOC-4 — 29 October" with nothing recording where that date came from. Nobody can tell whether it is the statutory computation, a date that applied to a different company, or an internal buffer someone added and never labelled.

The second is frozen dates. Several Indian due dates are not calendar dates at all. They are computed from an event, most often the annual general meeting. Copying last year's date forward produces a deadline that has no legal basis this year.

The third is no review loop. Extensions, revised forms and changed thresholds are notified through the year by MCA, CBDT and CBIC. A calendar built in April and untouched until March will be wrong somewhere, and nobody will notice until a filing fails.

Step 1: scope the calendar to your entity

Start by deciding what does not apply. A generic "India compliance calendar" is worse than a short accurate one, because a row that never applied trains people to ignore rows. Work through the applicability questions first.

• Entity type: private limited, public, listed, OPC, LLP, partnership or sole proprietorship. Company law obligations differ sharply, and an LLP does not file the company annual return forms.
• Listed or unlisted: a listed entity adds the SEBI LODR disclosure layer on top of everything below.
• Registrations held: GST, TAN, PF, ESI, professional tax, shops and establishment. No registration, no row.
• Turnover and threshold tests: these decide audit applicability, GST filing frequency, e-invoicing, and the annual return and reconciliation obligations.
• Sector regulators: an NBFC, insurer or intermediary has an RBI or SEBI reporting calendar that a trading company does not.

Write the applicability answer next to each obligation you keep. When turnover crosses a threshold next year, the calendar tells you which rows need revisiting.

Step 2: separate fixed dates from event-linked dates

This is the distinction that keeps a calendar honest. A fixed date is set by the calendar itself and can be scheduled years ahead. An event-linked date has to be recomputed from something that happens in the year.

Keep event-linked rows visibly incomplete until the trigger happens. A blank date with a note saying "AGM + statutory period" is safer than a guessed date that looks authoritative. The moment the AGM is held, the row gets its real date and a reference to the meeting.

Step 3: lay out the recurring spine

Most of the year is the same shape. Build the repeating pattern once, then overlay the annual and event-linked items. The pattern below is the common skeleton for a company with GST and TAN registration; confirm each date against the rule that applies to you.

Resist putting exact dates in the shared template. Put the rule in the template and let each entity's calendar carry the computed date. Templates with hardcoded dates are how a wrong date spreads across a client base.

Step 4: record the provision, not just the date

For each row, store the section or rule, the form or challan, and a link to the official source. It takes a few extra minutes per row once, and it changes what happens when a date is questioned.

1. Obligation: plain description of what has to be done.
2. Authority: the section, rule or regulation that creates the obligation, and the provision that sets the timing if it is different.
3. Instrument: the form number, challan or return type.
4. Source link:the regulator's own page or PDF, not a summary.
5. Date basis: fixed, event-linked with the trigger named, or conditional with the threshold named.
6. Consequence of delay: interest, late fee, additional fee or penalty, at least in outline.

The consequence column earns its place during a crunch week. When three deadlines collide, a row carrying per-day additional fees is a different decision from one carrying a fixed late fee.

Step 5: build the review loop

A calendar is a living document. The review loop has two speeds, and both are needed.

Monthly, forward-looking:before each month starts, read the coming month's rows. Confirm each date against the regulator's current position, check that event-linked rows have their triggers, and assign an owner to anything unassigned.

Continuous, change-driven: when a regulator notifies something, ask whether it touches a tracked row. Three questions settle it: which obligation does this change, does it change the date or the form or the applicability, and from when does it apply. Then amend the row and keep the source link with the amendment.

Who owns each row

A calendar with no named owner per row is a list of things everyone assumed someone else was doing. Assign at the row level, not the regulator level.

• Company secretary or compliance officer: company law filings, board and general meeting process, registers, and the listed entity disclosure calendar.
• Finance or accounts: TDS deposits and statements, advance tax, GST returns and reconciliations, payroll statutory payments.
• Auditor and tax advisor: audit reports and the positions behind the returns, not the filing mechanics.
• A single reviewer: one person who runs the monthly review across all rows, so a gap between owners does not become a missed filing.

Common compliance calendar mistakes

• Copying last year's dates forward, including AGM-linked dates that have no basis this year.
• Building one generic calendar for every client instead of scoping by entity type, registrations and thresholds.
• Storing dates without the section, rule or form that produced them.
• Mixing internal buffer dates with statutory dates in the same column with no label.
• Acting on an extension that has no notification number and no official PDF.
• Reviewing only at year start, so mid-year form and threshold changes never reach the calendar.
• Leaving rows unassigned, so a deadline sits between two functions.

Where Complied AI fits

The maintenance problem, not the construction problem, is what breaks a compliance calendar. Complied AI puts MCA, CBDT, CBIC, RBI and SEBI updates into one feed with the official document behind each change, so the monthly review starts from what actually changed rather than from five regulator websites. When a change touches a provision, you can read the source law next to the update instead of trusting a summary.