CGST Rule 58 — Records to be maintained by owner or operator of
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 58(1) An unregistered warehouse operator, storage operator or transporter covered by section 35(2) uses ENR-01 to obtain an enrolment number. 58(1A) A transporter with multiple GST registrations under one PAN may obtain one common enrolment number through ENR-02 for Chapter XVI. Proviso to 58(1A) After the common enrolment number is obtained, the transporter cannot use the GSTINs for the Chapter XVI purpose covered by the proviso. 58(2)-(3) ENR-01 enrolment has cross-jurisdiction effect and particulars must be amended where required. 58(4)(a) Transporters maintain branch-wise records of goods transported, delivered and stored in transit, with registered Finin2min | P0-R03 Rules 56-58 Finin2min.com | Finance & Law Explained in 2 Minutes | Educational and professional reference Paragraph / test Plain-language meaning consignor and consignee GSTINs. 58(4)(b)-(5) Warehouse/godown operators maintain stay-period and movement records and store goods so they are identifiable item-wise and owner-wise and available for verification. Operational map Control Result Linked law CGST Act section 35(2); Chapter XVI e-way-bill rules; rule 56 Forms / document
official statutory reference
Paragraph-wise decode
Paragraph / test Plain-language meaning 58(1) An unregistered warehouse operator, storage operator or transporter covered by section 35(2) uses ENR-01 to obtain an enrolment number. 58(1A) A transporter with multiple GST registrations under one PAN may obtain one common enrolment number through ENR-02 for Chapter XVI. Proviso to 58(1A) After the common enrolment number is obtained, the transporter cannot use the GSTINs for the Chapter XVI purpose covered by the proviso. 58(2)-(3) ENR-01 enrolment has cross-jurisdiction effect and particulars must be amended where required. 58(4)(a) Transporters maintain branch-wise records of goods transported, delivered and stored in transit, with registered
Finin2min | P0-R03 Rules 56-58 Finin2min.com | Finance & Law Explained in 2 Minutes | Educational and professional reference Paragraph / test Plain-language meaning consignor and consignee GSTINs. 58(4)(b)-(5) Warehouse/godown operators maintain stay-period and movement records and store goods so they are identifiable item-wise and owner-wise and available for verification. Operational map Control Result Linked law CGST Act section 35(2); Chapter XVI e-way-bill rules; rule 56 Forms / documents FORM GST ENR-01 and FORM GST ENR-02 Timeline Enrol before operating where applicable; amend business particulars when required; maintain records continuously.
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 58, fixes the relevant period, checks the mapped subordinate instruments and preserves evidence before filing or advising.
Professional alert
• Section 35(2) applies irrespective of whether the transporter or storage operator is registered. • Owner-wise and item-wise traceability must exist in the physical layout as well as the books. • The common transporter enrolment number changes the identifier used for Chapter XVI; operational systems should prevent mixed use. • Portal availability and current utility instructions should be checked before filing ENR-01 or ENR-02.
Finin2min | P0-R03 Rules 56-58 Finin2min.com | Finance & Law Explained in 2 Minutes | Educational and professional reference Forms, evidence and retention matrix Record / form Legal basis Minimum control Owner Timing Stock register Rule 56(2) Opening, receipts, supplies, losses, gifts/samples, scrap, wastage and closing stock Non-composition registered person Continuous; retain under section 36 Tax and ITC register Rule 56(4) Tax payable/collected/paid, reverse charge, input tax and ITC claimed Non-composition registered person Tax-period and continuous Supplier/recipient/location register Rule 56(5) Names, addresses and every storage location including transit Every registered person Continuous Edit/delete audit log Rule 56(8) Who changed what, when, old value, new value and reason Electronic-record user Continuous and immutable Production account Rule 56(12) Inputs/services consumed, output, waste and by- products Manufacturer Monthly Service quantitative record Rule 56(13) Goods used, input services used and services supplied Service provider Continuous/periodic Works-contract ledger Rule 56(14) Customer, project inputs, utilisation, payments and suppliers Works contractor Contract-wise Backup and restoration evidence Rule 57(1) Backup schedule, locations, test logs and restoration results Electronic-record user Continuous; periodic restore test Access package Rule 57(2)-(3) Readable export, credentials, file map, code explanation and print sample Electronic-record user Ready on demand FORM GST ENR-01 Rule 58(1) and (3) Business enrolme
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 58 regulate?
- It regulates records to be maintained by owner or operator of. 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 58 matters
Records to be maintained by owner or operator of 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 58 deal with?
- Records to be maintained by owner or operator of. Start with the operative Rule version and then test the connected Act provision, forms and amendments.
- Which GST form is connected to Rule 58?
- ENR-01E, ENR-02U, ENR-01A, ENR-02T, ENR-01R 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.