UTGST — Section 9B: Order of utilisation of input tax credit
Finin2min Summary — Section in 2 Minutes
UTGST section 9B deals with order of utilisation of input tax credit.
- Identify the relevant electronic ledger and permitted utilisation route.
- Apply statutory order/restrictions before set-off.
- Reconcile transfer between Centre/Union territory accounts where required.
- Maintain ledger and return evidence.
Why this section matters
This provision is part of the Union Territory 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 27 June 2025
official statutory reference
Clause-by-clause Finin2min decode
- Trigger: identify the facts that bring section 9B into play.
- Legal consequence: apply the operative words of “Order of utilisation of input tax credit” 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
Finin2min decision path
- Identify the relevant electronic ledger and permitted utilisation route.
- Apply statutory order/restrictions before set-off.
- Reconcile transfer between Centre/Union territory accounts where required.
- Maintain ledger and return evidence.
Practical case studies
Case 1
A taxpayer tries to cross-utilise a credit against a liability that the statute does not permit—check the prescribed order first.
Case 2
Tax was paid under the wrong head—use the statutory correction/refund route rather than journal-only adjustment.
Case 3
A system ledger differs from books—preserve return, PMT and reconciliation evidence before correction.
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 UTGST section 9B cover?
It covers Order of utilisation of input tax credit. 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.