GST Registration, Invoicing, E-way Bill, Accounts and Records

Why this cluster groups together at Final level

Registration, invoicing, e-way bill and accounts-and-records share a common thread this paper's method chapter would place at the earliest stages of the GST pipeline: they are the documentation and compliance infrastructure a taxable supply is built on top of, established before or at the point a supply actually occurs, rather than computational stages like value or credit. Intermediate covered each at a basic, descriptive level; this paper deepens the harder registration scenarios, the e-invoicing layer now mandatory for specified categories of taxpayer, and the accounts-and-records depth that directly anticipates the GST administration, assessment and audit chapter immediately following this one, since an auditor examining a taxpayer's compliance can only do so against records this chapter's own requirements establish.

Registration: the harder scenarios

Special category states and the differentiated threshold. Beyond the general registration threshold Intermediate already established, specified special category states carry their own, generally lower, threshold, reflecting a deliberate policy accommodation for states with distinct economic and geographic circumstances (smaller economies, more challenging terrain and logistics) where a uniform, higher national threshold could otherwise leave a disproportionately large share of these states' own genuine economic activity outside the GST net compared to the rest of the country.

Persons required to register irrespective of turnover, revisited with harder fact patterns. Intermediate already established the compulsory-registration categories (inter-state suppliers, casual taxable persons, persons liable under reverse charge, e-commerce operators, and others) regardless of turnover. The harder application at this level is recognising when a specific, real-world fact pattern falls into one of these categories despite not obviously announcing itself as such — for instance, a supplier making even a single, isolated inter-state supply of taxable goods is required to register regardless of how small that one transaction's value is, or how far below the general threshold the supplier's own aggregate turnover otherwise remains, since the compulsory-registration trigger here is the inter-state nature of the supply itself, not the supplier's aggregate turnover.

Registration for a non-resident taxable person, and its distinct compliance profile. A non-resident taxable person (occasionally undertaking taxable supply in India without a fixed place of business here) must obtain registration through a specific, distinct procedure, generally valid for a specified, limited period, with an advance deposit of estimated tax liability required at the time of registration, reflecting a deliberate policy response to the practical difficulty of otherwise ensuring tax compliance from a person with no ongoing, fixed presence in India for the tax administration to rely on for future enforcement.

Invoicing: the specific document each transaction type requires

Tax invoice, revisited with harder timing rules. Intermediate established the tax invoice's basic content and general timing requirements. This paper's harder application recognises that the specific timing rule itself varies by transaction type — a supply of goods generally requires invoicing at or before the time of removal or delivery, while a supply of services generally requires invoicing within a prescribed period from the date the service is actually supplied, and a continuous supply (of either goods or services) requires invoicing tied to each periodic due date or event the contract specifies, rather than a single, undifferentiated timing rule applied uniformly across every transaction type.

E-invoicing: a mandatory, system-validated layer for specified taxpayers. Registered persons whose aggregate turnover exceeds a specified threshold are required to generate invoices through the e-invoicing mechanism, reporting specified invoice details to a government-notified portal, which validates the invoice and returns a unique invoice reference number and a QR code that must then be incorporated onto the physical or electronic invoice actually issued to the recipient; an invoice issued by a person required to follow this mechanism, but without this validation, is not treated as a valid tax invoice for GST purposes, even if every other content requirement is otherwise satisfied, reflecting the deliberate policy purpose e-invoicing serves: giving the tax administration real-time, system-level visibility into invoice-level transaction data specifically for the larger taxpayers whose transaction volumes make this real-time reporting both administratively valuable and practically feasible to require.

Revised invoice and self-invoicing for reverse charge from an unregistered supplier. A revised invoice is issued to reflect the period between the effective date of registration and the date the registration certificate is actually issued, ensuring supplies made in this interim period are properly documented once registration is confirmed. Where a registered person receives a taxable supply from an unregistered supplier and is liable to pay tax under reverse charge on that supply, the registered recipient must issue a self-invoice, since the unregistered supplier is, by definition, not in a position to issue a valid GST tax invoice itself, and the recipient's own reverse-charge liability still requires a proper invoice-level document to be generated and retained.

E-way bill: the movement-tracking layer

Why e-way bill exists as a distinct requirement from invoicing. An invoice documents a transaction; an e-way bill documents the physical movement of goods, generated before the commencement of movement of consignments exceeding a specified value, and required precisely because a transaction can be correctly invoiced yet the actual physical movement of goods could still occur without any corresponding, verifiable trail, an enforcement gap e-way bill specifically closes by requiring advance, system-generated documentation of the movement itself, checkable by tax authorities at transit points.

Validity period tied to distance, and its practical compliance implication. An e-way bill's validity period is tied to the distance the goods are to be transported, with a specified validity period per specified distance slab, and goods found in transit after the e-way bill's validity has expired, without a valid extension having been obtained, are treated as goods being transported without a valid e-way bill, exposing the transporter and consignor to detention, seizure and penalty consequences regardless of how legitimate and properly invoiced the underlying transaction actually is — a frequently tested point illustrating that e-way bill compliance is a genuinely separate, independent requirement from invoice compliance, and a fully compliant invoice does not cure a lapsed e-way bill.

Situations where e-way bill is not required despite an otherwise-qualifying movement. Specific categories of movement (goods of a specified, exempted nature, movement by specified modes of non-motorised conveyance, and other specifically listed situations) are excluded from the e-way bill requirement even where the consignment value would otherwise cross the threshold, reflecting that the requirement is deliberately calibrated to situations genuinely warranting this additional movement-tracking documentation, rather than applying indiscriminately to every movement of goods above a bare value threshold regardless of the goods' own nature or the mode of transport involved.

Accounts and records: the foundation the audit chapter builds on

What a registered person must maintain. Every registered person is required to maintain, at their principal place of business, true and correct accounts of production or manufacture of goods, inward and outward supply of goods or services, stock of goods, input tax credit availed, output tax payable and paid, and other prescribed particulars, in the manner and form the rules prescribe, whether maintained manually or through electronic means, and these records must be retained for a specified minimum period from the due date of furnishing the annual return for the relevant year, a materially longer retention period than the ordinary limitation period for most GST proceedings, reflecting that some categories of proceeding (particularly those involving a longer period specifically because of alleged fraud or wilful misstatement, connecting directly to this paper's own demand and recovery chapter) can look back over a longer historical period than the ordinary limitation window, requiring correspondingly longer record retention to actually support such a proceeding.

Additional records for specific categories of registered person. An owner or operator of a warehouse or godown, and specified categories of transporter, are required to maintain specific additional records regarding goods stored or transported, even where these persons are not themselves the registered supplier of the goods in question, reflecting a deliberate policy extension of record-keeping obligations to persons who, while not the taxpayer whose supply is ultimately at issue, are nonetheless well-positioned to hold records that materially assist verifying the movement and storage of goods that a supplier's own records alone might not fully capture.

Why this chapter's records requirement is the audit chapter's own starting point. A GST audit, the subject of this paper's next chapter, is fundamentally an examination of whether a taxpayer's actual records, returns and underlying transactions align with what GST law requires; an auditor's entire examination is only possible because this chapter's own accounts-and-records requirements first establish what records must exist, in what form, and for how long, meaning a genuine mastery of this chapter's specific requirements is not merely a standalone topic but the necessary foundation for engaging meaningfully with the assessment and audit content immediately following it.

Why this cluster deserves careful, non-mechanical study despite its procedural surface

It is tempting to treat registration, invoicing, e-way bill and accounts-and-records as a purely mechanical, memorisation-heavy cluster, in contrast to the more conceptually rich supply, valuation and credit chapters. This is a mistake: the harder scenarios this chapter develops (an isolated inter-state supply triggering compulsory registration, an expired e-way bill exposing an otherwise fully compliant transaction to penalty, an invoice issued without required e-invoicing validation being treated as no invoice at all) show that this cluster's genuine difficulty lies precisely in recognising when a seemingly routine transaction actually falls into one of these specific, consequential compliance traps, exactly the kind of applied judgement a case-study question is designed to test, not mere recall of the underlying rule in isolation.