Admin: Annual Returns & Mahasahakar Export

Admin: annual returns and Mahasahakar export

Requires: Maharashtra CHS society; AGM_HOLD completed or AGM date recorded; audit report uploaded.

Task code: ANNUAL_RETURNS (due 30 September for Maharashtra CHS).

What Mahasahakar requires

Six online return categories per Maharashtra Dept of Co-operation:

1. Annual Activity Return
2. Audited Balance Sheet
3. Audited Profit & Loss / Income & Expenditure
4. Plan for Surplus Distribution
5. List of Amendments to Bye-laws
6. AGM date, election details, auditor name and consent

Plinth maps society profile, GL, AGM meeting, linked GBE election, and auditor profile into these fields.

Steps

1. Open ANNUAL_RETURNS on the compliance timeline.
2. Confirm prerequisites: AGM completed, audit report artifact linked, auditor profile current.
3. Tap Generate filing pack → mh_annual_returns_export.
4. Download outputs:
   • Mahasahakar_Annual_Returns_{fy}.json — field-mapped export for manual portal entry or upload
   • Annual_Returns_Summary.pdf — human-readable checklist for secretary review
5. Log in to Mahasahakar and complete each return module manually.
6. Return to Plinth → mark task submitted.
7. Enter portal acknowledgment reference (ack number or transaction ID).
8. Optionally upload Registrar acknowledgment PDF as external artifact.

Election data in export

If a GBE election was linked to ELECTION_DUE, results (nominations, turnout, declared officers) appear in category 6. Link election before generating if not already attached.

FAQ

Does Plinth auto-submit to Mahasahakar? No — export only. Manual upload and ack recording in v1.

What if AGM was after 30 September? Task will show overdue; waive only with documented Registrar order (rare). Fix governance process — §75 has no extension.

Non-Maharashtra CHS? State-labelled annual returns task uses generic export until L1 portal maps ship for that state.

Can we regenerate after AGM date correction? Yes — regenerate with reason; prior artifact retained in history.