Secretarial Compliance Operating Model for Indian Companies

Law and applicability

Companies Act sections 88, 92, 117, 118, 134 and 137; relevant rules, Secretarial Standards and sectoral overlays.

A functional system links the law to business events and accountable people. It must distinguish a transaction being approved, actioned, filed, registered and evidenced. Company secretarial compliance is not only a calendar: new contracts, appointments, funding events and company-class transitions generate their own obligations.

Key statutory decision tests

• Keep a maintained legal universe: entity class, thresholds, exemptions, foreign investment and listing status.
• Assign each event one accountable owner and independent checker; record precise source and jurisdiction.
• Track planned date, triggering date, calculated legal due date, actual filing date, SRN and regulator response as separate fields.
• Store signed source documents, rather than draft PDF copies, with an immutable version trail.
• Escalate unresolved defaults to the Board with likelihood and consequences, not only an overdue counter.

Practical step-by-step workflow

1. Create a master event-and-periodic compliance register for each legal entity.
2. Require transaction teams to register new financing, issue, sale, appointment and RPT events before execution.
3. Conduct monthly exception meetings and quarterly legal change checks.
4. Evidence each closure with filed form, acknowledgement and updated books/registers.

Important exceptions and higher-risk transactions

Use a three-layer register: periodic obligations, event-triggered obligations and legal change monitoring. For each entry, store entity class, statute/rule, controlling trigger, maker, checker, documentary input, due-date calculation, action, SRN/reference, regulator result and the final statutory-record update. A missed input should be escalated promptly rather than recorded as compliant simply because no filing has yet been attempted. Link open items to the Board exception report with owner and remedy.

Effective change monitoring is not a weekly copy of newspaper headlines. Track the Gazette, MCA official circulars, ICSI standard changes and SEBI regulatory amendments according to entity type; distinguish consultation paper from operative amendment. Capture enactment, publication, commencement, prospective/transitional provisions and impact on outstanding events. A dated source matrix prevents a newly published form instruction from being applied retrospectively to a prior completed filing without justification.

A practical escalation framework uses three levels. Routine low-risk filings are reviewed by the secretarial operations team, material capital and governance actions receive a legal/finance review before execution, and matters creating director disqualification, securities invalidity, lender priority or public-disclosure risk go to the Board or appropriate committee promptly. Evidence of a missed filing should include the original event document, date the omission was detected, legal consequence and proposed cure. Monthly reports should state overdue age, corrected actions and unresolved authority responses. This approach distinguishes meaningful legal compliance from completion of internal tick boxes.

Worked professional example

How the rule works in real companies

A functioning compliance system links each event to a legally responsible person, due date, source document and proof of closure. Keep a master calendar by company and financial year, but separately maintain event-driven triggers: issue, director change, charge, office shift, related-party arrangement and statutory notices. The evidence log should distinguish drafted, approved, filed, acknowledged and finally recorded states.

A director resigns on 18 August. Rather than entering only a calendar reminder, the team opens an event record: resignation letter, Board noting, director register update, DIR-12 assessment, bank mandate change, committee composition impact and any stock-exchange disclosure for a listed company.

RACI matrix, signed board authorities, event register, filing checklists, portal SRNs/challans, proof of ROC status, exception escalation tickets, yearly reviewer sampling and retention schedule.

Documents to retain and reconcile

• Law-to-control matrix with dated sources
• Calendar, risk log, evidence-file index
• Sign-off and exception escalation trail
• Versioned filings, resolutions and regulatory acknowledgements

Common mistakes to avoid

• Using last year’s statutory threshold without testing a new definition
• Treating SRN upload as final approval
• Storing legal source as an undated screenshot

Practical questions and answers

Statutory provisions and official references

• Companies Act, 2013 — MCA Act text (read with subsequent amendments)
• ICSI — revised SS-1 and SS-2 applicable from 1 April 2024
• MCA small-company classification revised from 1 December 2025
• MCA — live circulars, forms and filing updates

Use the applicable amended provision and actual effective date for the transaction. Current MCA portal instructions and valid circulars govern web-form fields, fees and approved extensions.