IGST — Section 9: Supplies in territorial waters

Finin2min Summary — Section in 2 Minutes

IGST section 9 deals with supplies in territorial waters.

• Identify supplier and recipient location before rate analysis.
• Test the statutory place-of-supply rule for the exact transaction.
• Determine inter-State/intra-State result and tax head.
• Retain contract, invoice, movement/event/delivery evidence supporting the conclusion.

Why this section matters

This provision is part of the Integrated Goods and Services Tax Act, 2017. It should be read as a legal decision point, not as an isolated definition: identify the factual trigger, effective date, connected subordinate law and evidence before applying it.

Current-law and effective-date control

CURRENT — Use the consolidated Act text together with subsequent subordinate law and effective-date controls.

double-check sources

• India Code / official Act record
• Official consolidated/Gazette Act text — source cut-off noted as 23 May 2025

official statutory reference

Clause-by-clause Finin2min decode

• Trigger: identify the facts that bring section 9 into play.
• Legal consequence: apply the operative words of “Supplies in territorial waters” rather than a commercial label.
• Subordinate-law layer: test Rules, Forms, notifications, rate instruments or portal procedure authorised by the Act.
• Evidence layer: preserve records capable of proving each statutory condition and the relevant date.

Act–Rule–Form–Notification bridge

• Chapter 4: Determination of Nature of Supply
• CGST Act bridge
• Rates & classification
• Practical GST pathways
• Notifications, Circulars, Orders & amendment engine

Finin2min decision path

1. Identify supplier and recipient location before rate analysis.
2. Test the statutory place-of-supply rule for the exact transaction.
3. Determine inter-State/intra-State result and tax head.
4. Retain contract, invoice, movement/event/delivery evidence supporting the conclusion.

Practical case studies

Case 1

A supplier and customer are registered in different States but the goods are delivered to a third location—test the statutory deeming rule before choosing IGST.

Case 2

A service is performed across several States—allocate value only if the relevant provision/rule requires an allocation method.

Case 3

A cross-border service appears export-like, but one export condition fails—retest place of supply and zero-rating separately.

Accounting, ERP & portal touchpoints

• Use a tax code that reflects the correct statute/head and effective date; ERP labels cannot override the Act.
• Reconcile statutory classification to invoice/return/payment data and preserve system audit trails.
• Where portal functionality implements the provision, retain acknowledgements, ARN/challan/order references and downloaded evidence.

Notice, litigation & evidence risk

• Do not rely on a current summary for an earlier tax period without checking the historical amendment position.
• Distinguish binding Supreme Court/High Court/GSTAT decisions from fact-specific AAR/AAAR outcomes.
• Preserve contemporaneous documents; post-facto explanations are weaker than transaction-time evidence.

Common mistakes to avoid

• Reading the section without its effective-date or commencement status.
• Using a GST Council recommendation as though it were a notified law.
• Stopping at the Act and ignoring the Rule/Form/notification that controls implementation.
• Assuming a portal outcome itself proves the legal position.

Questions professionals actually ask

What does IGST section 9 cover?

It covers Supplies in territorial waters. Start with the statutory text, then apply the linked Rules/notifications and the factual trigger.

What date should I test?

Use the transaction, tax period, machine/process, order or filing date relevant to the issue. Current wording must not be back-cast into an earlier period.

Can I rely only on this summary?

No. Finin2min explains the provision, but the official Act, Rules, notifications and judicial position control the legal outcome.

What evidence should I retain?

Keep source documents proving the factual trigger, computation, filing/payment, portal acknowledgement and any officer communication relevant to the provision.

Finin2min evidence checklist

• Official Act version and amendment trail saved for the relevant date.
• Contract/invoice/transaction or machine/process records supporting the factual trigger.
• Return/payment/refund/appeal records where applicable.
• Portal acknowledgements and officer communications.
• Working paper documenting why this provision and not an alternative provision applies.