
A later certificate does not necessarily mean registration starts later
Where registration is effective before the certificate is issued, section 31(3)(a) permits revised invoices against invoices already issued during that intervening period. The revised invoice must be issued within one month from issuance of the registration certificate, following the prescribed requirements. The effective date selects the eligible supplies; the certificate-issue date starts the revision window.
This article addresses CGST Act section 31(3)(a) and CGST Rule 53(1)–(2), checked on 23 October 2026. It is a registration-gap documentation process, not a general facility to rewrite any old tax invoice, change a customer’s identity retrospectively or use a revised invoice instead of a credit/debit note for every later correction.
Create a gap-period register from the actual certificate
Read the effective registration date and the certificate-issue date from the authoritative record. Link each existing invoice or bill to its actual taxable supply and date. A supply before the effective date does not enter this route merely because the certificate was issued later; a later ordinary registered supply needs the usual invoice process.
The two dates must not be collapsed into the application date or the date the accountant downloaded the certificate. Maintain a calendar-month deadline. “One month” is not a universal thirty-day period, so a February timeline can differ materially from a spreadsheet that always adds thirty days.
Preserve the original document and create a clear revised-document link
Rule 53 requires the revised-invoice label where applicable, the supplier’s registration particulars, prescribed recipient particulars, issue date and a financial-year-unique serial number within its sixteen-character limit. The corresponding original invoice or bill number and date are critical to the audit trail. Do not delete the original document and recreate a falsely backdated registered invoice.
Build the taxable-value, rate and tax-head reconciliation alongside the required document particulars and the applicable general invoicing/reporting rules. The original price may have been tax-exclusive or contractually inclusive; registration does not by itself resolve who bears any extra tax commercially. Determine the actual value and tax liability before chasing an additional collection from the customer.
| Recipient/supply case | Revision control | Common mistake |
|---|---|---|
| Registered recipient | Maintain identified recipient and original-document linkage | Putting B2B supplies into an anonymous B2C consolidation |
| Unregistered recipient | Rule 53 permits consolidation for that recipient over the eligible period | Treating all local customers as one named recipient |
| Eligible inter-State B2C supply | State-wise consolidation can apply where each supply does not exceed ₹2.5 lakh | Testing only the combined State total |
| Outside the registration gap | Use the legally appropriate ordinary document/correction route | Using the gap-period revision as a universal edit function |
The inter-State B2C limit tests the supply, not the final summary
Rule 53(2) allows a consolidated revised invoice for taxable supplies to an unregistered recipient during the period. Its further proviso permits separate State-wise consolidation across unregistered recipients for inter-State supplies where the value of a supply does not exceed ₹2,50,000. A State summary can therefore exceed that amount even though the supplies being pooled each satisfy the threshold.
Do not mix different recipient States in one State-wise pool, treat a registered recipient as unregistered for convenience, or include an individual supply above the threshold in that cross-recipient consolidation. Retain the underlying supply list and recipient status. The consolidation permission does not make the underlying tax disappear.
Reconcile revenue, tax and customer balances once
A revised invoice documents the same underlying supply. If revenue was already booked from the original invoice, merely issuing the replacement should not book another sale. Reconcile original consideration, revised taxable value, tax liability, any legitimate additional receivable and amounts collected. Keep document history intact in the outward-supply and return workings.
Document issuance, reporting, payment of tax and the recipient’s ITC are related but distinct compliance questions. A revised invoice does not guarantee ITC without the recipient satisfying its applicable conditions, and a documentation window is not an automatic extension of tax-payment deadlines. These examples assume ordinary taxable supplies at the expressly assumed rate and do not resolve a particular product’s classification or e-invoicing obligations.
Worked illustrations
These illustrations use fictional facts and expressly stated assumptions. Amounts are Indian rupees unless a different currency or unit is specified. They are independent examples, not findings about any actual client.
Illustrative example 1: Map the gap and the issue window
Assume registration is effective from 1 September 2026 and the certificate is issued on 20 September 2026. The statutory gap runs from 1 to 20 September. Using a calendar-month computation, the revision-window outer date is 20 October 2026. A certificate download on 25 September does not reset that date.
Illustrative example 2: Exclude transactions outside the date gap
Under the preceding dates, existing taxable-supply documents relate to 30 August for ₹1,00,000, 1 September for ₹1,50,000, 20 September for ₹50,000 and 21 September for ₹80,000. The stated gap-period base totals ₹2,00,000 from the two September gap supplies. Do not sweep all ₹3,80,000 into this special revision route; the other supplies need their own proper treatment.
Illustrative example 3: Tax-exclusive intra-State working
Assume an eligible supply has agreed taxable value ₹2,00,000 and total GST rate 18%, with an ordinary intra-State split of 9% CGST and 9% SGST. Taxes are ₹18,000 each, total ₹36,000; total consideration including tax is ₹2,36,000. Commercial recovery of additional tax must still follow the actual agreement.
Illustrative example 4: Inclusive consideration must not be taxed twice
Assume the agreed consideration for an eligible supply is fixed at ₹1,18,000 inclusive of GST at 18%. Taxable value is ₹1,00,000 and GST ₹18,000. Adding another 18% of ₹1,18,000 would demand ₹21,240 extra and would not reflect the stated inclusive-price assumption.
Illustrative example 5: State-wise B2C consolidation can exceed the per-supply limit
Three eligible inter-State supplies to different unregistered recipients in one State have values ₹1,50,000, ₹2,40,000 and ₹2,60,000. The first two each meet the not-exceeding-₹2.5-lakh test and total ₹3,90,000 for the State-wise cross-recipient consolidation. The ₹2,60,000 supply is outside that pooling permission. At an assumed 18% rate, tax on the eligible ₹3,90,000 pool is ₹70,200; handle the larger supply separately.
Illustrative example 6: One month is not always thirty days
Assume a certificate is issued on 1 February 2027. A calendar month leads to 1 March 2027, which is 28 elapsed days later. A routine thirty-day addition would give 3 March 2027, two days later. Use the statutory month-based computation and an earlier internal issue target.
Ten-step verification table
| Step | Verification | Evidence to retain |
|---|---|---|
| 1 | Read both registration dates from the authoritative record | Effective date, certificate issue date and certificate copy |
| 2 | Identify original documents and actual taxable supplies | Date-wise invoice/bill and supply register |
| 3 | Separate the eligible gap from other periods | Included/excluded transaction schedule |
| 4 | Calculate the one-calendar-month issue window | Calendar calculation and internal deadline |
| 5 | Verify recipient registration and State details | GSTIN/status evidence and recipient location |
| 6 | Apply only the permitted consolidation route | Recipient-wise or qualifying State-wise underlying supply list |
| 7 | Preserve original linkage and revised-document numbering | Original number/date, revised issue date and valid serial series |
| 8 | Reconcile value, rate, tax head and price terms | Tax-inclusive/exclusive contract and calculation |
| 9 | Avoid duplicate revenue and collections | Original/revised document bridge and ledger reconciliation |
| 10 | Complete separate reporting/payment/ITC checks | Outward-supply working, tax evidence and recipient reconciliation |
Sixteen practitioner FAQs
1. Does the certificate date always equal the effective registration date?
No. Read the actual registration record. This process addresses the case where registration takes effect before certificate issuance.
2. Which date starts the revision window?
Section 31(3)(a) uses issuance of the registration certificate. Application, download and bookkeeping dates should not replace it.
3. Which supplies belong in the special gap?
The relevant taxable supplies during the period from effective registration to certificate issuance, supported by the original documents and applicable rule.
4. Can pre-effective-date invoices automatically be revised this way?
No. The special period is defined by the effective date. Determine the proper treatment of earlier supplies separately.
5. Is one month always thirty days?
No. Use a calendar-month computation, document it and plan earlier execution rather than a fixed thirty-day formula.
6. Should the original invoice be deleted?
No. Preserve the history and link the revised document to the original number and date. Do not create a false backdated audit trail.
7. Is a revised invoice the same as a credit note?
No. The registration-gap mechanism and section 34 credit/debit-note corrections serve different purposes. Select the route from the actual legal facts.
8. Can B2B supplies be pooled as anonymous B2C?
No. Registered-recipient details must be identified; the specific unregistered-recipient consolidation permission is not a shortcut for B2B documentation.
9. Can supplies to one unregistered recipient be consolidated?
Rule 53(2) provides a recipient-based consolidated revised-invoice route for the eligible period. Retain the underlying list and recipient identification.
10. How does inter-State cross-recipient consolidation work?
The further proviso permits State-wise pooling for unregistered recipients where the value of each relevant supply does not exceed ₹2.5 lakh.
11. Can the State pool itself exceed ₹2.5 lakh?
Yes on qualifying underlying supplies. The stated threshold concerns the value of a supply rather than automatically capping the aggregate State-wise document.
12. Can a ₹2.6 lakh supply enter that State pool?
It exceeds the stated per-supply threshold. Do not include it in the cross-recipient State-wise consolidation merely because other supplies are small.
13. Does revision always create additional customer recovery?
No. Check contractual price terms and taxable value. A fixed inclusive amount needs tax extraction rather than automatic addition to that amount.
14. Should revenue be booked again on revision?
The underlying supply is the same. Reconcile the original entry and any necessary tax/receivable adjustment instead of duplicating turnover.
15. Does the invoice guarantee the buyer’s ITC?
No. The recipient’s ITC depends on its applicable conditions. The revised-document process does not override those requirements.
16. Does the one-month window postpone tax payment too?
Do not assume that. Documentation, return reporting and tax-payment obligations must each be checked under their applicable provisions.
Working-paper organisation
Keep the source documents, calculation and final conclusion together for the same entity and period. If using assureTax or other assureOffice tools, use only confirmed available functions and retain this evidence with the output.
Conclusion
Keep the registration-gap dates, revision deadline and original-document linkage explicit. Apply consolidation only to the permitted recipient population, and reconcile the underlying sale and tax once.