Skip to main content

GST | 28 September 2026

GST Accounts and Records: Section 35, Rule 56 and the Audit Trail Businesses Should Maintain

Finin2min Editorial Desk | Review: Ravi Sisodia

A reliable GST Accounts and Data trails position begins with classification of the entity, covered period and underlying event. GST accounts and records rules turn ordinary business data into tax evidence. The compliance objective is not to maintain one separate GST book; it is to ensure that procurement, sales, inventory, logistics, tax ledgers and returns can be traced to each other.

Finin2min 2-Minute Summary

Practical workflow

A practical record architecture starts with master data and transaction identifiers. Invoice number, GSTIN, HSN/SAC, place of supply, warehouse movement, e-way bill, e-invoice IRN where applicable, payment and accounting voucher should be linkable so that a reviewer can reconstruct the supply.

Worked example

A distributor questioned about stock at a branch should be able to move from physical stock count to inventory ledger, inward invoice, e-way bill and ITC record without manual guesswork. Gaps between warehouse and GST data are often more damaging than a filing delay.

Detailed practical analysis

GST record keeping should be designed around the life of a transaction. Sales records need to connect the customer order, tax invoice, e-invoice where applicable, e-way bill or dispatch proof, receipt or credit note and the ledger posting. Purchase records should connect the vendor invoice, receipt evidence, payment, ITC treatment and any reversal. Rule 56 adds detail to the statutory duty under section 35, so the record set should be more than a general ledger dump. Stock, advances, tax payable, tax collected, reverse-charge transactions and electronic records may each require specific support. Businesses with multiple locations should document which records are maintained centrally and how registration-wise information can be produced. Editing rights are another control point: if ERP entries can be overwritten without an audit trail, the business may struggle to establish the history of a transaction during scrutiny. Retention should be linked to the statutory period and extended where litigation requires records to be kept longer. A quarterly “retrievability test” is useful: select a sample sale and purchase and ask a person outside the transaction team to rebuild the GST treatment from archived records. If the evidence cannot be located quickly, the weakness is operational even if the return itself was filed correctly. Good records shorten notices, support ITC and reduce dependence on employee memory.

Implementation and review notes

Electronic records deserve the same discipline as paper documents. Define who can create, edit and approve GST-relevant master data, and retain system logs for material changes to GSTIN, tax rate, place-of-supply logic or invoice series. Number-series gaps should be investigated and cancellation reasons retained. If invoices are generated through multiple applications—ERP, marketplace, billing tool and e-invoice connector—ensure the final accounting record reflects the same document identity. Backups should be tested, not merely scheduled; a backup that cannot be restored during a notice is not an effective record-retention control. Third-party cloud providers should have contractual retention and access arrangements aligned to statutory needs. Businesses should also maintain a record map so staff know where each category—contracts, invoices, e-way bills, stock, payment, returns and correspondence—is stored. When employees leave, transfer ownership of tax folders and portal credentials formally. These governance details often determine whether a taxpayer can respond quickly to an old-period inquiry. The goal of section 35/Rule 56 compliance is not document accumulation; it is reliable reconstruction of taxable events and reported amounts.

Final reviewer note

Use CGST Act section 35 as the legal anchor for the closing file, but prove the factual result through GST data dictionary. The checker should independently inspect invoice-to-ledger trace test. If testing reveals The exception log must flag keeping only PDF copies without searchable indexes, segregate those cases and calculate exposure. If it reveals A recurring weakness is case files split across undeclared locations, obtain the missing support before release. Refer to CBIC GST Accounts and Records Rules for related procedure. Preserve the evidence actually used for the decision, not a generic checklist, so a later audit can reconstruct the conclusion from the same records.

Control points

Risk indicators

Primary / Official Sources