Union territory GST — UTGST scope, semi-state treatment of Delhi and Puducherry, tax computation, and the credit utilisation rules for UT-based supplies.
The decision the finance head faces when configuring tax masters for a supply originating from Daman is operationally specific — whether that supply attracts CGST plus SGST, CGST plus UTGST, or IGST, and the answer depends on whether the destination is the same Union Territory, a state, another Union Territory, or one of the two Union Territories that carry the constitutional status of a semi-state. The framework is not complicated once the distinctions are clear, but missing them in the customer master configuration produces wrong tax treatment on every invoice — invoices that may need to be cancelled and re-issued through credit-note workflow, with downstream GSTR-1 reversal entries the accountant has to reconcile next month. Each of these surfaces as GST filing errors and input tax credit mismatches in the monthly reconciliation cycle.
Union Territory GST sits in a specific structural gap that the dual-tax framework otherwise leaves open. The Central GST applies on supplies anywhere in the country. The State GST applies on intra-state supplies — but Union Territories without their own legislatures cannot levy a state tax. UTGST fills this position for those Union Territories, replacing the SGST component in the CGST plus SGST structure for intra-UT supplies. The two Union Territories with their own legislatures — Delhi and Puducherry — fall under the constitutional definition of "state" for GST purposes, which means SGST applies on intra-UT supplies in their case. The sections below walk through the scope, the tax computation, and the credit utilisation rules along with the readiness checklist the finance team uses to configure UTGST treatment. The broader ERP subject area discussion for compliance-led businesses treats this kind of jurisdictional configuration as the foundation of the customer master accuracy.
When and why to use this UTGST readiness checklist
This readiness checklist applies to operations with units, customers, or vendors in any Union Territory, finance teams configuring tax masters across multi-jurisdiction supply patterns, or tax advisors structuring the engagement against multi-location entities with UT presence. Each item below names a specific UTGST provision along with the configuration or sign-off it requires. The accountant uses the checklist as input to the customer master, vendor master, and place-of-supply rule configuration. The finance head signs off the UTGST treatment before the first invoice is raised against any UT-based counterparty.
The UTGST readiness checklist
The items below are grouped under three categories — the scope of UTGST and the semi-state exception, the tax computation and treatment of inter-jurisdiction supplies, and the credit utilisation rules along with the configuration sign-off.
Scope and the semi-state exception
Identify the seven Union Territories under the GST structure.
The Union Territories under the GST framework are Chandigarh, Lakshadweep, Daman and Diu, Dadra and Nagar Haveli, Andaman and Nicobar Islands, Delhi, and Puducherry. Under the broader administrative restructuring that has applied since the article's original drafting, certain UT boundaries have been redrawn (for example, Daman and Diu and Dadra and Nagar Haveli were subsequently merged into a single Union Territory), and Jammu and Kashmir's status changed. The accountant should validate the current UT list and any associated administrative changes against the latest position published by the GST Council before configuring the customer master.
Apply the semi-state exception to Delhi and Puducherry.
Delhi and Puducherry are Union Territories with their own legislatures, which makes them "states" for GST purposes under the Indian Constitution. The State GST (SGST) applies on intra-jurisdiction supplies within Delhi and within Puducherry, just as it does for any of the states. UTGST does not apply on supplies within Delhi or Puducherry. The customer master for Delhi-based and Puducherry-based entities is configured with SGST treatment for intra-jurisdiction supplies, not UTGST. The finance head signs off this distinction before the first invoice flows against the Delhi or Puducherry GSTIN.
Apply UTGST to the remaining Union Territories without legislatures.
The Union Territories without their own legislatures — Chandigarh, Lakshadweep, Daman and Diu (and its successor configuration), Dadra and Nagar Haveli (and its successor configuration), Andaman and Nicobar Islands — attract UTGST in place of SGST on intra-UT supplies. The customer master for entities based in these UTs is configured with UTGST treatment for intra-jurisdiction supplies. The accountant validates each customer's UT registration against the current administrative boundaries before the configuration is signed off.
Tax computation and inter-jurisdiction supply treatment
Apply CGST plus UTGST on intra-UT supplies.
Where the supply takes place within a Union Territory (supplier and recipient both in the same UT, excluding Delhi and Puducherry), the tax structure runs as CGST plus UTGST in equal proportion. For a supply of automobile parts within Daman and Diu valued at ₹1,00,000 at a 12% rate, the tax computation runs as ₹6,000 CGST plus ₹6,000 UTGST, with a total invoice value of ₹1,12,000. The accountant configures the place-of-supply logic to trigger this treatment automatically based on the supplier and recipient UT registration.
Apply CGST plus SGST on intra-jurisdiction supplies within Delhi or Puducherry.
Where the supply takes place within Delhi or within Puducherry (supplier and recipient both in the same semi-state), the tax structure runs as CGST plus SGST in equal proportion — not as CGST plus UTGST. For a supply within Delhi valued at ₹1,00,000 at a 12% rate, the tax computation runs as ₹6,000 CGST plus ₹6,000 SGST. The customer master for Delhi-based entities is configured with SGST treatment, and the finance head signs off this configuration alongside the Delhi GSTIN.
Apply IGST on inter-jurisdiction supplies — UT to state, UT to UT, or UT to semi-state.
Where the supply crosses jurisdiction boundaries — from a Union Territory to a state, from one Union Territory to another Union Territory, from a Union Territory to a semi-state (Delhi or Puducherry), or from a semi-state to any other state or Union Territory — IGST applies. For a supply from Daman and Diu to West Bengal valued at ₹1,00,000 at a 12% rate, the tax computation runs as ₹12,000 IGST, with a total invoice value of ₹1,12,000. The customer master place-of-supply rule determines this automatically based on the destination GSTIN.
Tabulate the treatment matrix for the configuration sign-off.
The treatment matrix below consolidates the rules above for the finance head's sign-off against the customer master configuration.
Origin Destination Tax treatment Components UT (without legislature) Same UT Intra-UT CGST + UTGST Delhi or Puducherry Same semi-state Intra-state CGST + SGST UT (without legislature) Different UT or state Inter-jurisdiction IGST Delhi or Puducherry Different state or UT Inter-jurisdiction IGST Any state Any UT or semi-state Inter-jurisdiction IGST The accountant applies this matrix at customer master creation; the finance head signs off the configuration against a representative supply sample before invoicing begins.
Credit utilisation rules and configuration sign-off
Apply UTGST credit first against UTGST liability.
Input tax credit accumulated under UTGST is applied first against UTGST output liability. Any balance of UTGST credit after settling UTGST liability can be applied against IGST liability — but cannot be applied against CGST liability under any circumstance. The treatment parallels the SGST credit utilisation rule for states, with UTGST playing the equivalent position for UTs without legislatures. The accountant configures the set-off computation; the finance head reviews the monthly utilisation before GSTR-3B filing.
Maintain the no-cross-utilisation rule between CGST and UTGST.
The fundamental cross-utilisation restriction in the GST regime applies equally here — CGST credit cannot be applied against UTGST liability, and UTGST credit cannot be applied against CGST liability. Stranded balances in one head carry forward within the same head until matching liability arises. Operations with significant CGST credit and persistent UTGST liability (or the reverse) should review the underlying supply mix; the pattern typically signals an imbalance between intra-UT procurement and outward supply that warrants the next master refresh cycle. Where deeper period-over-period reporting matters, BI for ERP reporting holds the multi-period view of head-by-head credit utilisation patterns.
Sequence remaining IGST credit between CGST and UTGST optimally.
Where IGST credit remains after settling IGST liability, the balance can be applied against CGST liability and UTGST liability in any order — the order being a finance head judgment call based on the entity's accumulated balances and downstream cash flow position. Applying IGST against the head with less accumulated own-head credit typically reduces stranded credit risk. The accountant prepares the optimisation computation; the finance head signs off the order applied in the GSTR-3B set-off.
Configure the multi-GSTIN structure for operations with UT and state presence.
Operations with units in a Union Territory and also in one or more states have separate GSTINs for each jurisdiction. Each GSTIN's invoices upload to its own return on the GST portal — the UT GSTIN's returns carry the UTGST entries, the state GSTIN's returns carry the SGST entries. Inter-unit transactions between the same entity's UT-based unit and state-based unit are recorded as inter-jurisdiction supplies with IGST applying. The product configuration must hold this multi-GSTIN structure as a configured master with the correct routing logic. Where statutory payroll also forms part of the operational picture, HRMS for payroll and HR integration holds the same kind of multi-jurisdiction configuration discipline across statutory deductions.
Sign off the UTGST configuration before the first UT-based invoice.
The accountant prepares the UTGST configuration draft — UT customer master with the correct intra-UT versus inter-UT treatment, the matrix sign-off, the credit utilisation rules — and the finance head signs off against the prepared configuration before the first invoice flows against any UT-based counterparty. Skipping this sign-off produces wrong tax treatment on early UT-based transactions, which then surface as credit-note reversals in the subsequent return cycle.
Facing similar operational challenges?
See how exactllyERP manages inventory management, financial operations, and operational reporting — built for operational businesses.
See how exactllyERP handles operational complexity →How exactllyERP supports the UTGST configuration
The UTGST framework provisions translate into operational compliance only when the underlying customer master, vendor master, and place-of-supply rules hold each provision as a configured workflow rather than a manual control point. exactllyERP eliminates GST filing errors and input tax credit mismatches by carrying the UT-versus-state-versus-semi-state classification as a configured master with the correct CGST plus UTGST, CGST plus SGST, or IGST treatment applied at invoice posting. The multi-GSTIN structure across UT and state operations holds the correct return routing automatically; the credit utilisation order across UTGST, CGST, and IGST is applied at the GSTR-3B set-off computation; and the audit trail captures each transaction from source supply through to the filed return.
How exactllyERP handles this automatically: items 4 and 5 (intra-UT versus intra-semi-state classification with the correct CGST plus UTGST or CGST plus SGST treatment at invoice posting), items 6 and 7 (inter-jurisdiction IGST treatment applied from the treatment matrix), and items 8-10 (UTGST credit utilisation order including the no-cross-utilisation rule with CGST and the optimal sequencing of remaining IGST credit) are the three places where UT-related configuration translates directly into ongoing compliance accuracy. GST council changes to UT boundaries, rate slabs, and credit utilisation rules absorb through statutory updates rather than custom rebuilds. The audit trail captures the UT-specific transaction history back to the source document, which is what makes the statutory audit a documentation exercise rather than a reconstruction project. exactllyERP handles incorrect GSTR filing and HSN code mapping errors automatically through the configured rate-slab logic at the item master. See it live in a free demo against your UT-based customer mix and a sample previous-quarter filing.
