Section 31 - Tax invoice
Reviewed by CA Nikhil Gupta and Kajri Singh · Last reviewed 30 August 2026
Finin2min Summary - Section in 2 Minutes
Creates the complete invoice-timing architecture for goods, services, continuous supplies, RCM recipient invoices, revised invoices, small-value supplies and special documents. Goods invoice: before/at removal where movement occurs, otherwise before/at delivery or availability. Service invoice: before or after supply but within the prescribed period. Special documents include revised invoice, bill of supply, receipt/refund/payment voucher and recipient-issued RCM invoice. For section 9(3)/(4) supplies from an unregistered supplier, the recipient invoice must follow the prescribed period; rule 47A fixes 30 days from receipt from 1 November 2024. Continuous supply and sale-on-approval transactions have separate statutory timing.
Why Section 31 matters
Section 31 (Tax invoice) is the section-level control point within Chapter VII — Tax Invoice, Credit and Debit Notes. Invoice, credit-note and debit-note provisions turn the underlying transaction into the tax document that drives supplier liability, recipient credit and return data.
Current-law and amendment control
validation 1 — controlling consolidated Act
India Code — Central Goods and Services Tax Act, 2017. Used for the current chapter/section inventory and consolidated provision status.
validation 2 — independent official cross-check
CBIC Tax Information Portal. Use the Act HTML/PDF and amendment history together with current notifications/circulars.
Transaction-date rule: Never treat today’s consolidated wording, a portal screen or an enacted-but-uncommenced amendment as proof of the law that applied on another date. Fix the relevant tax period first.
Official statutory text
The authoritative provision, footnotes and amendment notes are maintained in the official consolidated Act. This analytical page does not re-typeset amendment markers into the running statutory sentence.
- Open the India Code consolidated CGST Act PDF - as on 11 June 2026
- Open the India Code CGST Act register
- Open the CBIC Tax Information Act explorer
Official-source reference reviewed on 2026-07-28. Apply the version and commencement position relevant to the transaction period.
Clause-by-clause / paragraph-wise decode
Creates the complete invoice-timing architecture for goods, services, continuous supplies, RCM recipient invoices, revised invoices, small-value supplies and special documents. Goods invoice: before/at removal where movement occurs, otherwise before/at delivery or availability. Service invoice: before or after supply but within the prescribed period. Special documents include revised invoice, bill of supply, receipt/refund/payment voucher and recipient-issued RCM invoice. For section 9(3)/(4) supplies from an unregistered supplier, the recipient invoice must follow the prescribed period; rule 47A fixes 30 days from receipt from 1 November 2024. Continuous supply and sale-on-approval transactions have separate statutory timing.
Section–Rule–Form–Notification–Circular 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
Goods leave the supplier on 12 July and reach the customer on 15 July. The tax invoice must ordinarily exist by removal on 12 July, not on delivery.
Professional alert
Invoice timing drives tax period, interest, e- invoice validity, recipient ITC and penalty exposure. A portal document created late does not retrospectively cure the statutory breach.
Finin2min decision path
- Identify the document legally required for the transaction.
- Fix the statutory issue timing and prescribed particulars.
- Check e-invoice or other special procedural overlays.
- For credit/debit adjustments, test the tax-period and counterparty consequences.
- Reconcile document data to returns and recipient records.
Practical case studies
Accounting, ERP & portal touchpoints
Invoice engines should validate GSTIN, place of supply, tax breakup, document series, e-invoice status and credit/debit-note linkage.
Control: keep the legal conclusion separate from system configuration; document every tax-code/master change and its effective date.
Notice, litigation & evidence risk
Document errors can deny recipient credit or create outward-supply mismatches. Preserve original documents, revised documents and acknowledgement trails.
Evidence hierarchy: source transaction → books/ERP → statutory return/form → portal acknowledgement → legal working → correspondence/order.
Judicial position — how to read precedent
Start with binding Supreme Court authority, then the jurisdictional High Court, other High Courts and GSTAT where applicable. AAR/AAAR rulings are fact- and jurisdiction-sensitive and should not be presented as universal law. Always check whether a decision has been stayed, reviewed, distinguished or overtaken by amendment.
Open the Finin2min provision citator · Open the connected GST case-law module
Common mistakes to avoid
- Treating a commercial credit note as an automatic tax reduction.
- Ignoring invoice timing.
- Editing an invoice after reporting without a statutory correction trail.
- Assuming e-invoice compliance replaces Act/Rule invoice requirements.
Questions professionals actually ask
- When must a GST tax invoice be issued?
- Read the statutory document requirement together with the Rules and any applicable e-invoice procedure; one does not replace the other.
- Can a GST credit note reduce tax after the original invoice?
- Read the statutory document requirement together with the Rules and any applicable e-invoice procedure; one does not replace the other.
- Does e-invoicing apply to this invoice?
- Read the statutory document requirement together with the Rules and any applicable e-invoice procedure; one does not replace the other.
- How should a wrong GST invoice be revised?
- Read the statutory document requirement together with the Rules and any applicable e-invoice procedure; one does not replace the other.
Related law and practical resources
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 section 31 regulate?
- It regulates tax invoice. Read the exact text, conditions, exceptions and transaction date together.
- Which subordinate law should be checked?
- Rule 46, Rule 46A, Rule 47, Rule 47A, Rule 48, Rule 49, Rule 50, Rule 51, Rule 52, Rule 53, Rule 54, Rule 55. 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.