Electronic storage must preserve the statutory record
Rule 27 of the Companies (Management and Administration) Rules, 2014 permits the listed-company or stated thousand-holder population to maintain records electronically. Its operative word is may, not shall. Adoption does not authorise replacement of statutory particulars with an incomplete spreadsheet or silent alteration of a digitally signed record. ICSI’s legal e-book reproduces the rule and its amendment note.
Avoid a fresh six-month deadline invented from historical wording
The amendment dated 24 July 2014 replaced shall with may. The explanation concerning conversion within six months of notification of section 120 refers to that historical notification, not each future software installation. Confirm the applicable company population before asserting a universal mandate. Conversely, do not infer that every smaller company is barred from all electronic recordkeeping; examine its applicable record-specific framework.
Test the required capabilities
The Board determines the manner subject to the safeguards: statutory formats and other requirements, adequate information for future reference, readable retrieval and printed reproduction, dating and digital signing where required, resistance to editing or alteration once dated and digitally signed, and lawful updates whose dates are recorded. Records include registers, indexes, agreements, memoranda, minutes and other documents required by the Act or rules.
Migration is more than copying rows
Inventory sources by stable identifiers, dates and quantities. Match substantive fields and attachments, test retrieval and inspect printable output. Equal row counts can conceal duplicate entries and omissions. Preserve signed originals and link lawful later updates rather than overwriting evidence. The rule specifies no vendor or hash algorithm; a product’s audit-trail claim does not prove the required capabilities. Applicable inspection rights, privacy limits and record-specific retention requirements remain separate checks. The examples are migration-control models, not statutory tolerances for missing records.
Six worked illustrations
All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.
Illustrative example 1: Threshold equality
Assume the properly established Rule 27 holder population is 1,000. This meets not less than 1,000. A population of 999 is one below the threshold. The permission remains optional, and this example does not prescribe an unsupported method of counting overlapping holder categories.
Illustrative example 2: Listed-company route
A listed company’s verified population is 700, which is 300 below 1,000. It is nevertheless separately within the listed-company wording. Do not turn the numerical test into an exclusion of listed entities below that number.
Illustrative example 3: Incomplete migration
Source inventory contains 240 required records; only 232 matching records are migrated. Eight remain missing. Completion is 96.67%, rounded to two decimals. This is a status figure, not legal permission to discard the remaining records.
Illustrative example 4: Duplicate concealment
A source has 100 distinct folios. The target has 100 rows but five are duplicates, leaving 95 distinct folios and five missing identities. A row-total match therefore fails to prove completeness.
Illustrative example 5: Preserved signatures
Forty-eight dated signed records receive twelve lawful subsequent updates, maintained separately. The evidence inventory is sixty linked records: 48 preserved originals and twelve updates. Overwriting twelve originals would leave only 36 unchanged originals, defeating that preservation demonstration.
Illustrative example 6: Printable completeness
A register has six sections of thirty entries, or 180 entries. An export omits one section and contains 150. Thirty entries, or 16.67%, are missing. Successful PDF creation does not prove complete reproducibility.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Classify company population | Verify listed status or the applicable holder population. |
| 2 | Read amended wording | Use may and the historical notification context. |
| 3 | Inventory records | List every statutory register and document being converted. |
| 4 | Map mandatory fields | Retain prescribed formats and signature requirements. |
| 5 | Document Board arrangements | Identify the method and responsible custodian. |
| 6 | Test retrieval | Locate records by stable identifier and date. |
| 7 | Test printing | Compare complete output to source records. |
| 8 | Protect signed records | Demonstrate protection against alteration after signing. |
| 9 | Date updates | Preserve originals and link lawful changes. |
| 10 | Resolve differences | Reconcile identity, quantity and content before accepting migration. |
Sixteen practitioner FAQs
1. Is electronic adoption mandatory under Rule 27?
The current wording uses may for the specified company population.
2. Does exactly 1,000 meet the numerical wording?
Yes, on a properly established statutory population.
3. Are listed companies separately mentioned?
Yes. Do not apply the numerical shortfall as their sole exclusion test.
4. Does a new installation restart six months?
The explanation refers to the historical section 120 notification, not installation dates.
5. Does this rule alone prohibit all smaller-company digital records?
No. Examine the applicable record-specific framework rather than drawing that sweeping conclusion.
6. Who determines the maintenance manner?
The Board, subject to the rule’s safeguards.
7. May required particulars be removed for convenience?
No. Statutory formats and other requirements remain applicable.
8. Must the record be retrievable?
Yes. Readability, retrieval and printed reproducibility are required characteristics.
9. Is a scan always a required digital signature?
No. Verify the actual dating and signing requirements for that record.
10. Can a signed record be silently edited?
The rule requires protection against editing or alteration once dated and digitally signed.
11. Are lawful updates prohibited?
No. The rule permits updating according to law with its date recorded.
12. Does the rule name a software vendor?
No. Test capabilities against the actual requirements.
13. Are minutes within the record definition?
Yes. The definition expressly includes minutes.
14. Is equal row count sufficient?
No. Match distinct identities and substantive content as well.
15. Does digitisation remove inspection rights?
Do not assume so. Apply the relevant access and privacy rules separately.
16. Does Rule 27 prescribe one retention period for all documents?
No. Identify the retention requirement for each record type.
Conclusion
Rule 27 permits electronic records for its specified company population. Preserve statutory formats, readable output, required digital signatures and dated updates without altering signed records.