Direct answer: Continuous-supply invoice timing depends on the contract and the applicable limb of section 31. Goods follow successive statements or payments as applicable; services follow an ascertainable payment due date, receipt where no due date is ascertainable, or a payment-linked completion event. Contract cessation has its own service-invoicing rule.
Position checked on 22 October 2026. This article addresses registered suppliers making taxable continuous supplies and invoice timing under CGST Act sections 2(32), 2(33) and 31(4)–(6). It does not calculate output tax, determine a rate, or replace the separate time-of-supply, advance-receipt, e-invoice and return-reporting checks.
First classify the contract
Continuous goods involve continuous or recurrent contractual supply and regular or periodic invoicing; the definition is not confined to pipeline deliveries. Continuous services ordinarily require a contract extending beyond three months with periodic payment obligations, alongside any notified categories. Repeated transactions with the same customer do not establish that definition by themselves.
Prepare one contract abstract recording the nature of supply, term, billing cycle, due-date clause, payment milestones and termination clause. Attach the operative amendments. Separate independent purchase orders where they create separate supplies; a customer master marked recurring is not evidence that the statutory definition is satisfied.
Map the trigger before setting the invoice calendar
| Supply pattern | Statutory trigger | Billing control |
|---|---|---|
| Continuous goods with successive statements | Before or at each statement’s issue, as applicable | Capture the actual statement issue date. |
| Continuous goods with successive payments | Before or at each payment receipt, as applicable | Link receipts to the contractual billing arrangement. |
| Continuous services: due date ascertainable | On or before the contractual payment due date | Read the payment clause, not merely the expected collection date. |
| Continuous services: due date not ascertainable | Before or at payment receipt | Monitor the bank and collection records. |
| Continuous services: payment linked to an event | On or before completion of that event | Capture completion evidence and linked consideration. |
| Services cease before contractual completion | At cessation, for the supply already made | Determine actual scope completed and reconcile prior invoices. |
The GST Council-hosted CBIC tax-invoice flyer explains these invoice triggers. It is guidance to the statutory provisions, not authority to postpone an invoice until a customer’s accounts-payable team is ready. Read section 31(5) with its express preservation of the advance receipt-voucher provision in section 31(3)(d).
The relevant statutory wording was also cross-checked in ICAI’s April 2026 GST Act(s) and Rule(s)—Bare Law compilation. The older CBIC compilation linked above is used for these specific provisions, not as evidence that every neighbouring provision remains unchanged.
Resolve payment and acceptance clauses carefully
An invoice preparation date, customer approval date, contractual due date and receipt date can all differ. Record each separately. Where a contract makes payment conditional on certification, determine whether certification is the genuine completion event or whether the due date is already ascertainable. Do not rewrite a fixed payment obligation as uncertain merely because collection is disputed.
For event-linked payments, align the amount invoiced to the relevant contractual event. Operational completion must reach the billing team promptly. A month-end batch process is a weak control when a statutory trigger occurs earlier. Build a review queue for disputed milestones rather than suppressing them from the billing calendar.
Cessation and reconciliation
A terminated service arrangement needs a cut-off calculation: extent supplied, consideration attributable to it, and amounts already invoiced. Do not invoice the entire unperformed contract automatically. Equally, do not defer the completed portion merely because a settlement agreement is still being drafted. Review disputes, valuation and any credit/debit-note consequences on their own facts.
The examples assume genuine qualifying continuous contracts and taxable amounts exclusive of GST. The service contracts originally run for more than three months with periodic payment obligations. Amounts stated for cessation are already-supported values of actual supply; previously invoiced portions must not be invoiced twice. Illustrative dates after the research date assume no relevant legal change.
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: Goods billed by successive statements
A continuous-goods arrangement uses successive account statements. The October statement for ₹4,00,000 is issued on 31 October 2026; payment arrives on 15 November. On the stated statement-based facts, invoice by 31 October. Waiting for collection would defer issue by 15 days; the taxable value remains ₹4,00,000, before the separate GST calculation.
Illustrative example 2: Goods with successive receipts
Under a continuous-goods payment-based arrangement, ₹1,50,000 is received on 10 October 2026 for the relevant supply. The applicable invoice trigger is before or at that receipt. A system date of 31 October is 21 days later and is not justified by the ordinary month-end billing cycle.
Illustrative example 3: An ascertainable service due date
A qualifying annual service contract fixes payment of ₹2,00,000 for the relevant period on 31 October 2026. Collection occurs on 15 November. Section 31(5)(a) requires issue on or before 31 October; the 15-day collection delay does not move the contractual due-date trigger.
Illustrative example 4: Service payment without an ascertainable due date
A qualifying service contract has no ascertainable payment due date for the relevant ₹1,20,000. Payment is received on 12 October 2026. Invoice before or at 12 October under the receipt limb. A 31 October billing run would be 19 days after the identified trigger.
Illustrative example 5: A completion-linked service milestone
A qualifying contract worth ₹10,00,000 makes 30% payable on completing a specified stage. That event occurs on 20 October 2026. The milestone amount is ₹10,00,000 × 30% = ₹3,00,000; invoice on or before 20 October. A later finance approval should not silently substitute a new completion date.
Illustrative example 6: Services cease before completion
A ₹6,00,000 service arrangement ceases on 10 November 2026. Supported valuation shows 30% supplied, with nothing previously invoiced. Issue at cessation for ₹6,00,000 × 30% = ₹1,80,000. The unperformed balance is ₹4,20,000 and is not automatically part of that cessation invoice.
Ten-step verification table
| Step | Verification | Evidence to retain |
|---|---|---|
| 1 | Classify goods or services and the actual continuous-supply definition. | Contract, scope and statutory definition analysis. |
| 2 | Confirm term and periodic obligations for services. | Commencement, expiry and payment schedule. |
| 3 | Identify the relevant statement, receipt, due-date or event limb. | Written trigger conclusion for each billing line. |
| 4 | Extract all ascertainable contractual payment dates. | Signed clauses and effective amendments. |
| 5 | Capture statement issue and bank-receipt dates. | Statement archive and bank reconciliation. |
| 6 | Obtain completion-event evidence before billing cut-off. | Milestone certificate and project records. |
| 7 | Track cessation and the actual extent supplied. | Termination notice and supported valuation. |
| 8 | Reconcile earlier invoices and avoid duplicate values. | Contract-to-invoice roll-forward. |
| 9 | Review advance vouchers, tax timing and other invoice requirements separately. | GST review sheet and applicable transaction documents. |
| 10 | Record actual issue date and investigate delayed triggers. | Invoice register, exception log and corrective conclusion. |
Sixteen practitioner FAQs
1. Does every monthly invoice prove continuous supply?
No. First establish the statutory definition and contractual facts; a billing convention alone is insufficient.
2. Must continuous goods run for more than three months?
Do not import the services duration condition into the goods definition.
3. Is a three-month service contract enough under the ordinary definition?
The ordinary wording requires a period exceeding three months with periodic payment obligations. Examine any applicable notified category separately.
4. Can collection delay extend an ascertainable due date?
No automatic extension follows from delayed collection. Apply the operative payment clause.
5. What if no service due date is ascertainable?
The receipt limb requires issue before or at payment receipt, subject to the other applicable provisions.
6. What controls an event-linked payment?
Identify completion of the contractual event to which payment is linked and invoice on or before that completion.
7. Can the supplier wait for month-end after a milestone?
A month-end routine does not override an earlier statutory event trigger.
8. Is internal customer approval always the completion event?
No. Distinguish a contractual completion condition from an administrative processing step.
9. Do successive goods statements use the payment date automatically?
Determine which statement or successive-payment arrangement applies. Do not choose whichever date is later merely for convenience.
10. Does a receipt voucher become irrelevant for continuous services?
No. Section 31(5) is expressly subject to the advance receipt-voucher provision in section 31(3)(d).
11. What happens when services terminate early?
Invoice at cessation for the extent actually supplied and reconcile amounts already invoiced.
12. Must the remaining unperformed value be invoiced at termination?
Not automatically under section 31(6). Establish the completed supply and examine any separate settlement components.
13. Does this invoice analysis determine the GST rate?
No. Rate, classification, exemptions, valuation and tax timing require their own analysis.
14. Is an invoice date the same as a return filing date?
No. Track the statutory issue trigger independently from reporting and payment compliance.
15. Can contract amendments be ignored once billing is configured?
No. Maintain effective versions and assess their impact on the operative trigger without backdating documents.
16. What is the most useful audit work paper?
A contract-wise chronology linking the statutory limb, triggering evidence, amount and actual invoice issue date.
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
Classify the arrangement first, record the operative trigger and maintain a dated evidence trail. A convenient billing cycle should follow that analysis rather than determine it.