Financial compliance
Startup Compliance Calendar in India: Configure Applicability and Ownership
A startup-specific workflow for identifying applicable compliance work, assigning accountable owners, recording event triggers, and handing evidence to qualified reviewers without inventing universal dates.
10 min read
Short answer
A startup compliance calendar should begin with facts and ownership, not a list of internet dates. Record the legal entity, registrations, tax and accounting period, locations, workforce, directors or partners, funding and capital events, borrowing, suppliers, customers, and schemes that can change applicability. For every possible obligation, assign one accountable internal role, the person or adviser who prepares or reviews it, the records owner, an escalation route, and close evidence. Mark whether the item is applicable, not applicable with reasons, unresolved, or awaiting evidence. Then link it to a maintained official source and either a supported recurring rule, an event-relative formula, a review-only trigger, or a withheld state. There is no universal startup deadline set: entity type, period, jurisdiction, registration, event, scheme, notification, relief, and source freshness can change the result. If evidence is stale, inaccessible, conflicting, or incomplete, show Recheck required and withhold the exact date until a qualified owner resolves it.
Configure the startup before configuring its calendar
| Fact group | Capture | Why it matters | Owner evidence |
|---|---|---|---|
| Entity and period | Legal form, incorporation date, financial year, tax or assessment period, OPC or small-company facts, and current status. | ROC, income-tax, and governance branches depend on entity and period-specific law. | Controlled entity profile and dated reviewer confirmation. |
| Registrations and schemes | GST registration and return period, TAN or deductor state, Udyam status, state registrations, and scheme elections. | Registration does not make every form, cadence, or date applicable in the same way. | Registration references and official portal status kept in the restricted repository. |
| People and governance | Directors or partners, employees, payroll start, auditor, actual meetings, resolutions, and changes in personal particulars. | Annual and event-based duties use different anchors and may change when facts change. | Board, employment, and adviser records referenced by internal IDs only. |
| Transactions and counterparties | Capital, borrowing, office, contract, cross-border, marketplace, and micro or small supplier facts. | Transaction and supplier characteristics can create a review or reporting branch. | Finance or operations owner confirms the category without publishing counterparty data. |
Build an applicability and ownership register
- 01
Freeze the entity profile
Create a versioned intake with the entity category, period, registrations, locations, workforce, governance roles, schemes, and known transaction classes. Record an effective date and profile owner so later changes do not silently rewrite the earlier decision.
- 02
List candidate obligations by source domain
Start with ROC, income tax, GST, TDS, payroll, Udyam or MSME, state registration, contract, and finance-close domains relevant to known facts. Candidate means review required; it does not mean applicable or due.
- 03
Resolve applicability explicitly
For each candidate, record applicable, not applicable, unresolved, or awaiting evidence; name the controlling facts and effective period; link the exact official source; and preserve who reviewed the conclusion and when.
- 04
Assign accountable and supporting roles
Give one internal role accountability for the outcome. Separately name the preparer, specialist reviewer, records owner, approver, substitute, and escalation role. Hiring an accountant or company secretary does not transfer founder or company accountability automatically.
- 05
Classify the schedule safely
Use fixed recurring only when a supported cadence and day rule exists; event relative when a verified anchor and offset control; review only when facts or sources need periodic inspection; and withheld when evidence cannot support an exact public date.
- 06
Define evidence handoff and closure
State what records the specialist needs, where restricted records remain, when readiness is checked, what approval closes the task, and which acknowledgement, challan, filing, minutes, register update, or reviewed decision proves completion.
Make ownership visible without confusing roles
| Role | Owns | Does not imply | Escalation trigger |
|---|---|---|---|
| Accountable founder, finance, or operations role | Applicability review occurs, inputs arrive, decisions are assigned, and closure evidence is recorded. | Technical authority to decide every tax, legal, secretarial, or payroll question. | Unresolved applicability, missing owner, withheld date near an operating decision, or overdue evidence handoff. |
| Internal preparer | Controlled data collection, checklist progress, draft preparation, and status updates. | Approval of specialist judgments or silent changes to source rules. | Records do not reconcile, required facts conflict, or source scope is unclear. |
| Qualified specialist | Fact-specific interpretation, form or computation review, current relief checks, and filing advice within the agreed scope. | Custody of every business record or ownership of unrelated calendar items. | Source conflict, law transition, entity change, event branch, or material uncertainty. |
| Records owner | Restricted source records, permissions, version history, and approved evidence handoff. | Permission to place personal, counterparty, financial, or credential data in a public tool. | Missing, stale, inaccessible, or inconsistent evidence. |
Route dates through fail-closed source controls
| State | Meaning | Public display | Owner action |
|---|---|---|---|
| Stale | The controlling source review-by date or required notice-index scan has expired. | Recheck required; exact actionable date withheld. | Reopen the official source, check current notices or relief, record the review, and rerun applicability. |
| Conflict | Two sources or instructions support incompatible outcomes and precedence is unresolved. | Conflict explained; no averaged, guessed, or preferred date shown. | Escalate to the qualified reviewer and preserve both source IDs and resolution evidence. |
| Withheld | Facts, effective period, source access, or legal chain cannot support an exact occurrence. | Recurring rule context may appear, but no actionable date. | Collect missing facts or controlling authority before changing status. |
| Current and applicable | Applicability, effective period, source freshness, notice scan, and formula inputs are resolved. | Exact date may appear with source, last checked, review state, and owner. | Recheck within the action window and preserve closure evidence. |
Direct answer
Do not publish one universal GST, ROC, income-tax, TDS, director, Udyam, or MSME date for every startup. For example, ROC annual-return timing depends on AGM facts; income-tax law depends on the relevant period and taxpayer branch; TDS depends on deductor, month, payment method, form, and permission facts; GST depends on registration, return period, notification, and relief; Udyam has review and update triggers rather than a universal renewal date. The current DIR-3 KYC amendment and legacy instruction kit conflict for transition purposes, so exact action stays withheld until director facts and current live instructions resolve it. Disputed quarterly GST dates also stay withheld.
Review changes before they become missed handoffs
- 01
Run a monthly ownership review
Check new hires, registrations, customers, suppliers, borrowing, funding, offices, directors, contracts, thresholds, and unresolved items. Monthly is an operating review rhythm, not a claim that every legal obligation is monthly.
- 02
Open event reviews when facts change
Do not wait for month-end after a director, capital, office, auditor, registration, payroll, borrowing, or material supplier event. Record the event date, fact owner, candidate obligations, and specialist handoff.
- 03
Check official sources on their risk cadence
Review acts, rules, and event formulas within the controlled ceiling; mutable portals and instruction kits more often; exact upcoming actions within seven days; and relevant official notice indexes daily when an actionable occurrence is inside fourteen days.
- 04
Close the evidence loop
After preparation or filing, reconcile the approved result, acknowledgement, payment, minutes, register, specialist decision, and resulting next trigger. An email saying done is not enough when the required close evidence is missing.
Sources and review
Published by ThynkBored. Published 16 July 2026. Content review completed 16 July 2026.
- Companies Act, 2013
India Code, Government of India. Accessed 16 July 2026.
Supports: Authoritative Act context for company and event-based compliance review; Need to resolve the applicable section, entity facts, and event anchor before deriving an occurrence.
- Section 92 of the Companies Act, 2013
India Code, Government of India. Accessed 16 July 2026.
Supports: Annual-return timing relative to the actual AGM or required AGM where no AGM is held; Why a startup register must capture AGM facts instead of copying a universal MGT-7 date.
- Central Tax notifications
Central Board of Indirect Taxes and Customs. Accessed 16 July 2026.
Supports: Official notification-discovery step for GST schedule and relief review; Need to recheck mutable notification state before exposing an actionable date.
- QRMP advisory
Goods and Services Tax Network. Accessed 16 July 2026.
Supports: One official operational statement for quarterly GSTR-1 timing; Need to preserve the disputed quarterly date as withheld when read with conflicting GSTN help copy.
- GSTR-1 contextual help
Goods and Services Tax Network. Accessed 16 July 2026.
Supports: Opposing mutable operational context for monthly and quarterly GSTR-1 filing; Need to reconcile current notification evidence before exposing a quarterly occurrence.
- G.S.R. 943(E), 31 December 2025
Ministry of Corporate Affairs. Accessed 16 July 2026.
Supports: Current substituted DIR-3 KYC rule and transition context; Need to reconcile the amendment with legacy public instructions and director-specific facts.
- Legacy DIR-3 KYC instruction kit
Ministry of Corporate Affairs. Accessed 16 July 2026.
Supports: Legacy annual and date-specific DIR-3 KYC public instructions retained as conflict evidence; Need to withhold exact action while the live route and transition evidence remain unresolved.
- Objective and scope of the new Income-tax Act
Income Tax Department, Government of India. Accessed 16 July 2026.
Supports: Period transition between the Income-tax Act, 1961 and Income-tax Act, 2025; Need to attach the correct period law before resolving a startup tax-calendar item.
- Income-tax Rules, 2026
Income Tax Department, Government of India. Accessed 16 July 2026.
Supports: TDS timing branches by deductor, period, payment class, statement, certificate, and permission; Need to attach the correct period rule before resolving a startup TDS occurrence.
- Udyam Registration important information
Ministry of Micro, Small and Medium Enterprises. Accessed 16 July 2026.
Supports: Mutable official workflow and update context for Udyam registration; Use of review and fact triggers rather than an invented universal renewal date.
- Micro, Small and Medium Enterprises Development Act, 2006 - sections 2 and 15 to 24
India Code, Government of India. Accessed 16 July 2026.
Supports: Micro-or-small supplier, acceptance, deemed-acceptance, payment-period, interest, and disclosure foundations; Need to keep payment duty separate from company Form I reporting applicability.
- S.O. 1376(E), 25 March 2025
Gazette of India, Ministry of Micro, Small and Medium Enterprises. Accessed 16 July 2026.
Supports: Current company, micro-or-small supplier, pending-over-45-days, and half-year scope direction; Need to resolve buyer and supplier status before treating Form I as a candidate occurrence.
- Specified Companies Order, S.O. 368(E), 22 January 2019
Ministry of Corporate Affairs. Accessed 16 July 2026.
Supports: Recurring April-to-September and October-to-March Form I reporting periods; Why the startup calendar must not convert the half-year rule into a monthly filing claim.
- Specified Companies Amendment Order, S.O. 2751(E), 15 July 2024
Ministry of Corporate Affairs. Accessed 16 July 2026.
Supports: Current pending-over-45-days trigger and amended MSME Form I categories; Need to resolve acceptance, pending state, amount population, and period before creating an occurrence.
This article provides an educational operating-control model, not legal, tax, secretarial, accounting, audit, payroll, labour, regulatory, or filing advice. It does not determine whether any obligation applies, calculate a tax or fee, choose a form, interpret a notification, create a statutory date, or replace a chartered accountant, company secretary, lawyer, payroll specialist, or authority portal. The composite scenario is synthetic. Official sources can change, become inaccessible, conflict, be superseded, carry period-specific transition rules, or require facts not available in a public guide. A monthly ownership review is an internal control rhythm, not a universal legal cadence. Confirm entity, period, jurisdiction, registration, event, scheme, threshold, relief, source precedence, and exact occurrence with the appropriate qualified owner. Keep identity, registration, financial, employee, counterparty, credential, filing, and document evidence in a restricted system.
Name the unresolved obligation and owner gap
Share only the entity category, broad registration state, obligation domain, applicability state, schedule state, source-review state, internal owner status, event category, and evidence-readiness status. ThynkBored can help structure the register, RACI-style handoffs, and escalation controls before a qualified review.
Use controlled categories and status only. Do not send PAN, GSTIN, CIN, DIN, Aadhaar, employee or director details, supplier or customer identities, invoices, payroll, bank or transaction data, tax computations, filings, notices, contracts, credentials, passwords, OTPs, documents, files, or free-text evidence through the public form. Agree a secure handoff before any restricted record review.
Diagnose this issueQuestions owners ask
What should a startup compliance calendar include?
Include a versioned entity and period profile, registrations, locations, workforce and governance facts, transaction and event triggers, candidate obligations, explicit applicability state, official source IDs, schedule state, one accountable internal role, preparer and reviewer roles, required records, escalation condition, readiness checkpoint, close evidence, and next review. Withhold an exact date when facts or sources are unresolved.
How often should startup compliance be reviewed?
Run an operating ownership review at least monthly and reopen applicability whenever an entity, registration, employee, director, office, capital, borrowing, contract, supplier, customer, threshold, scheme, or law fact changes. Source review follows risk: mutable portals need tighter review, upcoming exact actions need a seven-day recheck, and relevant notice indexes need daily scans inside the fourteen-day action window.
Who should own the compliance calendar?
Assign one accountable internal founder, finance, or operations role for completeness, handoffs, escalation, and closure. Preparers, records owners, approvers, accountants, company secretaries, lawyers, and other specialists can own defined steps, but their involvement does not remove the need for an internal accountable role or authorize unsupervised changes to applicability and source rules.
Useful context for this decision
Follow the records, definitions, comparisons, and next actions connected to this page.