CGST Rule 56 — Maintenance of accounts by registered persons
Reviewed by CA Nikhil Gupta and Kajri Singh · Last reviewed 30 August 2026
Official sources
Use the official source for the controlling wording, footnotes, effective date and amendment history.
Source review date: 2026-07-28. Historical-period questions require the version applicable to the transaction date.
Finin2min Summary - Rule in 2 Minutes
Paragraph / test Plain-language meaning 56(1) Imports, exports and reverse-charge supplies require true and correct accounts supported by the listed source documents. 56(2) Non-composition taxpayers require a stock ledger covering opening, receipts, supplies, losses, theft, destruction, write-offs, gifts, samples, closing stock, raw material, finished goods, scrap and wastage. 56(3)-(4) Maintain separate advances and tax/ITC/document registers, including reverse-charge liability. 56(5)-(6) Record suppliers, recipients and every storage location. Undeclared storage without valid documents can trigger deemed-supply tax determination. 56(7)-(10) Books must relate to registered places. Manual volumes need serial control; electronic edits/deletions require logs; records found elsewhere may be presumed to belong to the taxpayer. 56(11) Agents need principal-wise authority, receipt, supply, account and tax records. 56(12)-(14) Manufacturers, service providers and works contractors need specialised quantitative and contract-wise records. 56(15)-(16) Electronic records are permitted with authentication, accessibility at related places and statutory preservation. 56(17)-(18) Carriers/C&F age
official statutory reference
Paragraph-wise decode
Paragraph / test Plain-language meaning 56(1) Imports, exports and reverse-charge supplies require true and correct accounts supported by the listed source documents. 56(2) Non-composition taxpayers require a stock ledger covering opening, receipts, supplies, losses, theft, destruction, write-offs, gifts, samples, closing stock, raw material, finished goods, scrap and wastage. 56(3)-(4) Maintain separate advances and tax/ITC/document registers, including reverse-charge liability. 56(5)-(6) Record suppliers, recipients and every storage location. Undeclared storage without valid documents can trigger deemed-supply tax determination. 56(7)-(10) Books must relate to registered places. Manual volumes need serial control; electronic edits/deletions require logs; records found elsewhere may be presumed to belong to the taxpayer. 56(11) Agents need principal-wise authority, receipt, supply, account and tax records. 56(12)-(14) Manufacturers, service providers and works contractors need specialised quantitative and contract-wise records. 56(15)-(16) Electronic records are permitted with authentication, accessibility at related places and statutory preservation. 56(17)-(18) Carriers/C&F agents and registered persons must produce custody records and other legally required books on demand.
Finin2min | P0-R03 Rules 56-58 Finin2min.com | Finance & Law Explained in 2 Minutes | Educational and professional reference Operational map Control Result Linked law CGST Act sections 35 and 36; sections 9, 10, 17 and applicable demand provisions Forms / documents No single statutory form; documentary records listed in the rule Timeline Continuous maintenance; preserve for section 36 period; 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 listed in this repository.
Practical example
A professional first identifies whether the facts trigger rule 56, fixes the relevant period, checks the mapped subordinate instruments and preserves evidence before filing or advising.
Professional alert
• A general ledger alone is not a substitute for stock, production, location, contract and custody records. • Deletion without an edit log is inconsistent with the electronic-record control in sub-rule (8). • A branch or warehouse not reflected in registration and stock records creates both registration and deemed- supply exposure. • Loss, theft, destruction, write-off, gifts and samples require separate stock and input-tax-credit analysis.
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 56 regulate?
- It regulates maintenance of accounts by registered persons. Read the exact text, conditions, exceptions and transaction date together.
- Which subordinate law should be checked?
- No direct CGST Rule has been listed in this repository. 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.
Repository module professional rule control
Why Rule 56 matters
Maintenance of accounts by registered persons should be read with its enabling CGST Act provision, prescribed forms, amendment notification, transaction date and the live portal workflow. The operative-text block already released on this page remains the legal core; Repository module adds application controls without altering that block.
Rule → Form → evidence bridge
- Confirm the Rule version that was operative on the relevant date.
- Check every proviso, explanation, inserted/omitted sub-rule and commencement notification.
- Use the current prescribed form/portal utility rather than a saved legacy template.
- Preserve the Rule source, filing/approval evidence, computation and decision-maker trail.
Finin2min decision path
- Trigger: What transaction, registration event, return, credit, valuation, refund, appeal or enforcement event activates this Rule?
- Date: Which Rule version and amendment notification applied on that date?
- Conditions: Have every mandatory condition and exception been tested?
- Form/portal: Is the prescribed form or electronic workflow the correct current version?
- Evidence: Can the conclusion be reconstructed from books, invoices, portal records and official sources?
Practical cases
Transaction test
Fix the tax period, legal trigger and effective version of the Rule.
Portal execution
Reconcile portal fields to the legal rule and retain the generated acknowledgement/order.
Dispute readiness
Preserve source version, computation and evidence so the position can be defended later.
Accounting, ERP and portal controls
- Do not let an ERP default or portal auto-population override the legal Rule.
- Map the Rule trigger to the correct tax period and retain before/after reconciliation where values change.
- Archive ARN, acknowledgements, generated PDFs, payment/ledger records, notices and orders where applicable.
Notice and litigation risk
- Separate a portal mismatch from a statutory breach; they are not automatically the same issue.
- Identify whether a circular/instruction is clarificatory or whether an amendment changed the Rule itself.
- Apply judicial hierarchy: Supreme Court → jurisdictional High Court → other High Courts → GSTAT; AAR/AAAR is not universal precedent.
Common mistakes
- Using today's Rule for an older transaction without an effective-date test.
- Reading a form instruction as if it overrides the Act or Rule.
- Ignoring State/UT procedural overlays where the Rule requires a local notification or officer action.
- Treating a source-gated local reproduction as cleared statutory text.
Finin2min Q&A
- What does CGST Rule 56 deal with?
- Maintenance of accounts by registered persons. Start with the operative Rule version and then test the connected Act provision, forms and amendments.
- Which GST form is connected to Rule 56?
- No single prescribed form is the primary trigger. The Rule and live portal workflow control.
- Can I rely only on the GST portal?
- No. Portal functionality is execution infrastructure; legal eligibility and consequences come from the Act, Rules and valid instruments.
- What should I keep on file?
- The official Rule version used, amendment/effective-date evidence, underlying transaction records, computation, portal submission and resulting acknowledgement/order.