When to Use a Compliance Calendar (AGM & Audit Season)
When to use a compliance calendar (AGM and audit season)
A compliance calendar is not only for September AGM week. These are the moments when a regulatory-pack calendar tied to live books saves the most committee time and risk.
1. Co-operative year close (March–April)
When your financial year ends (typically 31 March for Maharashtra CHS), FY_CLOSE and ACCOUNTS_FINALIZE tasks activate. Start readiness checks now — not in May when the 45-day finalization deadline (15 May under MCS Rule 61) is already tight.
Plinth action: Review readiness on ACCOUNTS_FINALIZE; issue pending billing cycles; generate Form N pack when score hits 100%.
2. Member inspection window (May)
Rule 61 opens accounts for member inspection from 16–31 May. Societies that publish the inspection pack to the document vault reduce member challenges at AGM.
Plinth action: Generate member inspection pack; optionally publish to document vault with member notice.
3. Audit handover (June)
Hand books to the panel auditor by 1 June (Maharashtra). A complete handover ZIP — Form N, Tally export, billing summary, expense entries — cuts auditor queries and speeds audit completion.
Plinth action: Generate audit handover pack; upload auditor engagement letter; mark AUDIT_HANDOVER submitted.
4. Audit completion and report upload (July–August)
Target audit completion by 31 July; upload signed audit report and Form N-1 before AGM notice goes out (by 31 August or 15 September depending on your pack).
Plinth action: Upload auditor Form N-1 as external artifact; link to AUDIT_REPORT_UPLOAD.
5. AGM season (August–September)
AGM must conclude by 30 September for Maharashtra CHS — no extension. Use AGM notice pack for statutory notice period; link the meeting record; publish minutes after conclusion.
Plinth action: Generate AGM notice pack → hold AGM in Meetings → generate minutes pack → mark AGM_HOLD completed → annual returns and auditor appointment return due dates auto-recompute.
6. Annual returns filing (by 30 September)
Mahasahakar requires six return categories. Generate the export from Plinth, upload manually, record ack reference.
Plinth action: Generate Mahasahakar annual returns export; submit with portal reference number.
7. Audit rectification season (November–January)
Three months from audit report receipt to file Form O rectification (MCS Act §82). Track objections as they arrive — not in a last-week scramble.
Plinth action: Enter objections in Form O tracker; mark rectifications; generate Form O draft; upload signed Form O.
8. Election year (90 days before term end)
ELECTION_DUE appears 90 days before committee_term_end. Start a GBE election early enough for Registrar timelines.
Plinth action: Deep link to GBE create flow; on results declared, election artifact links to compliance task and annual returns.
9. New committee onboarding
When office-bearers change, the calendar and audit trail stay in Plinth — not in a departing secretary's phone. New admins see full task history, generated packs, and submission records.
Plinth action: Assign task owners; review compliance hub on day one.
10. Member transparency requests
When members ask "when is AGM?" or "can I inspect accounts?", enable member transparency for read-only key dates and published artifacts — without exposing draft packs or objection details.