Rule 57 - Generation and maintenance of electronic records
Finin2min Summary - Rule in 2 Minutes
Paragraph / test Plain-language meaning 57(1) Maintain restorable backups. A backup that cannot be restored within a reasonable period does not meet the control objective. 57(2) Records must be producible in authenticated hard copy or an electronically readable format. 57(3) On demand, provide file details, passwords, code explanations, access information and a printed sample. Operational map Control Result Linked law CGST Act sections 35 and 36; rule 56 Forms / documents No statutory form Timeline Continuous backup and access readiness; produce on demand.
Exact operative text
Paragraph-wise decode
Paragraph / test Plain-language meaning 57(1) Maintain restorable backups. A backup that cannot be restored within a reasonable period does not meet the control objective. 57(2) Records must be producible in authenticated hard copy or an electronically readable format. 57(3) On demand, provide file details, passwords, code explanations, access information and a printed sample. Operational map Control Result Linked law CGST Act sections 35 and 36; rule 56 Forms / documents No statutory form Timeline Continuous backup and access readiness; produce on demand.
Section-Rule-Form-Notification bridge
The mapping is a legal concordance, not a round-robin related-link list. It is limited to instruments certified in this phase.
Practical example
A professional first identifies whether the facts trigger rule 57, fixes the relevant period, checks the mapped subordinate instruments and preserves evidence before filing or advising.
Professional alert
• Cloud hosting does not remove the taxpayer’s obligation to restore and produce records. • Encrypted files without controlled access and documented credentials can fail production requirements. • Backup testing, not merely backup scheduling, should be evidenced. • Legal-hold data must be preserved across ERP, e-mail, document systems and third-party platforms.
Finin2min | P0-R03 Rules 56-58 Finin2min.com | Finance & Law Explained in 2 Minutes | Educational and professional reference
Implementation checklist
- Fix the transaction, taxable period and jurisdiction.
- Read every subsection, proviso, explanation and omission marker.
- Open the mapped Rule, form, notification and circular.
- Test State/UT variation and portal version.
- Preserve evidence, approvals, working papers and acknowledgements.
- Record the conclusion, assumptions, source date and reviewer.
Evidence and retention checklist
- Contract, purchase order, invoice or underlying transaction document.
- Registration, return, ledger, challan and portal acknowledgement.
- Official Act/Rule/notification version used and effective date.
- Internal tax position paper, computation and management approval.
- Correspondence, notices, replies, orders and appeal papers where applicable.
Practical Q&A
- What does rule 57 regulate?
- It regulates generation and maintenance of electronic records. Read the exact text, conditions, exceptions and transaction date together.
- Which subordinate law should be checked?
- No direct CGST Rule has been certified in this phase. Notifications, circulars, forms and the corresponding SGST/UTGST layer may also apply.
- What evidence should be retained?
- Preserve the contract or transaction record, invoice or form, portal acknowledgement, payment/ledger evidence, correspondence, legal working and the official source version used.
- Can portal behaviour override the statute?
- No. Portal functionality is operational evidence; legal entitlement and liability remain controlled by the Act, Rules, notifications and binding decisions.