☐ Has the service been identified specifically? ☐ Has service category been determined (forward / RCM / voucher / residual / continuous / cross-border)? ☐ For forward-charge, has s. 31(2) compliance been verified? ☐ Has Rule 47 sectoral…
13
☐ Has the service been identified specifically? ☐ Has service category been determined (forward / RCM / voucher / residual / continuous / cross-border)? ☐ For forward-charge, has s. 31(2) compliance been verified? ☐ Has Rule 47 sectoral…
Section 13 services time-of-supply compliance — checklist (19 items)
Section 13 services time — of-supply compliance — checklist (19 items)
☐ Has the service been identified specifically?
☐ Has service category been determined (forward / RCM / voucher / residual / continuous / cross-border)?
☐ For forward-charge, has s. 31(2) compliance been verified?
☐ Has Rule 47 sectoral framework (banking / insurance / telecom) been considered?
☐ Has clause (a) been applied if invoice within framework?
☐ Has clause (b) been applied if invoice beyond framework?
☐ Has clause (c) been applied if (a)/(b) inapplicable?
☐ For RCM, has sub-s. (3) earlier-of rule been applied?
☐ Has 60-day-from-invoice anchor been verified?
☐ For cross-border related-party, has books-entry discipline been applied?
☐ For vouchers, has identifiability framework been applied?
☐ For residual cases, has sub-s. (5) been applied?
☐ For additions, has sub-s. (6) separate time-of-supply been applied?
☐ For continuous services, has invoice-cycle framework been applied?
☐ Has provision-date been documented?
☐ Has rate applicability been verified per time-of-supply?
☐ Has Bharti Airtel substance-over-form discipline been applied?
☐ Has audit-defensibility through time-of-supply file been ensured?
☐ Has the file been reviewed for audit-defensibility?
Worked examples — five live scenarios
Example 1 — Services with timely invoice
Facts: Service provided 10-Sep-2025. Invoice issued 25-Sep-2025 (within 30 days). Payment received 5-Oct-2025.
Analysis: Sub-s. (2)(a) — invoice within s. 31(2) framework. Earlier of invoice (25-Sep) or payment (5-Oct). Time of supply = 25-Sep-2025.
Result: Compliant invoicing. Standard time-of-supply on invoice date.
Example 2 — Late invoice triggering clause (b)
Facts: Service provided 10-Aug-2025. Invoice issued 25-Sep-2025 (beyond 30 days). Payment 1-Oct.
Analysis: Sub-s. (2)(b) — invoice not within s. 31(2). Earlier of provision-of-service (10-Aug) or payment (1-Oct). Time of supply = 10-Aug-2025. Late invoicing penalises the supplier — time-of-supply pushed back, interest from 10-Aug.
Result: Late invoice triggers earlier time-of-supply. Penalty discipline.
Example 3 — RCM legal services
Facts: Advocate invoice 1-Oct-2025 to corporate client. Payment 15-Dec-2025 (75 days).
Analysis: Sub-s. (3) — RCM. Earlier of (a) payment date 15-Dec; (b) 60 days from invoice = 30-Nov. Earlier — 30-Nov. Time of supply = 30-Nov-2025. Client pays RCM in November GSTR-3B.
Result: 60-day window triggers earlier time-of-supply.
Example 4 — Cross-border related-party service
Facts: Indian company receives software-development services from foreign group company. Books entry 1-Aug-2025. Invoice 15-Aug. Payment 30-Sep.
Analysis: Sub-s. (3) proviso — associated enterprise. Books-entry date governs. Time of supply = 1-Aug-2025. RCM applies; Indian company pays in August GSTR-3B.
Result: Books-entry discipline for cross-border related-party services.
Example 5 — Continuous supply — monthly rental
Facts: Office rent — Rs. 1 lakh/month. Lease provides monthly invoice on 1st of next month. August rent invoiced 1-Sep-2025.
Analysis: Continuous supply under s. 31(5) framework. Sub-s. (2)(a) — invoice within s. 31(2) framework (monthly cycle). Earlier of invoice (1-Sep) or payment (when received). If payment by 1-Sep, time of supply = 1-Sep.
Result: Invoice-cycle discipline for continuous services.
Planning and litigation strategy
Litigation defence
Cross-references