Setting off input tax credit against tax liability — the GST set-off order across CGST, SGST, and IGST with worked examples and a governance checklist.
The question the finance head faces at the close of every GSTR-3B cycle is not whether input tax credit is available — that part is settled the moment the purchase register reconciles against GSTR-2B. The question is the order in which the available credits can be utilised against the month's output tax liability across CGST, SGST or UTGST, and IGST. The sequencing matters because the GST set-off rules don't permit unrestricted cross-utilisation. CGST credit cannot be applied against SGST liability, SGST credit cannot be applied against CGST liability, and IGST credit carries its own utilisation order against the three liability heads. Getting the sequence wrong leaves credit stranded in a head where there's no corresponding liability, with cash going out for tax that could have been settled through credit.
Setting off input tax credit against tax liability is, in operational terms, a monthly cash-flow decision before it is a compliance decision. Every rupee of credit utilised correctly reduces the cash outflow on tax payment; every rupee left stranded carries forward to the next period waiting for matching liability that may not arise for several months. The sections below walk through the set-off rules across the three GST liability heads, illustrate the application with two worked examples, and set out the governance checklist the finance team should run through each month before the GSTR-3B is filed. The broader ERP subject area discussion for compliance-led businesses treats this monthly set-off discipline as one of the highest-leverage compliance practices the finance head owns.
The set-off framework — how the GST credit utilisation order works
Every taxable supply under GST attracts one of three tax structures depending on the place of supply. Where the transaction is intra-state — head office in Maharashtra supplying within Maharashtra — Central GST (CGST) and State GST (SGST) apply in equal proportion. Where the transaction is intra-Union Territory, Central GST (CGST) and Union Territory GST (UTGST) apply. Where the transaction is inter-state — head office in Maharashtra supplying to a buyer in Karnataka — Integrated GST (IGST) applies. The same logic runs on the purchase side: input tax credit accumulates under the head corresponding to the supply received.
The utilisation rules under the GST regime constrain how credit accumulated under one head can settle liability under another. The current statutory position requires IGST credit to be fully utilised before any CGST or SGST/UTGST credit is set off against the corresponding heads. The detailed order of utilisation, applied in this sequence each month, runs as follows.
| Credit head | Can be utilised against | Sequence rule |
|---|---|---|
| IGST | IGST liability first; then any balance against CGST or SGST/UTGST liability in any order | Must be fully exhausted before CGST or SGST/UTGST credit can be utilised |
| CGST | CGST liability first; then any balance against IGST liability | Cannot be utilised against SGST or UTGST liability under any circumstance |
| SGST | SGST liability first; then any balance against IGST liability | Cannot be utilised against CGST liability under any circumstance |
| UTGST | UTGST liability first; then any balance against IGST liability | Cannot be utilised against CGST or SGST liability under any circumstance |
The fundamental constraint that runs across the framework: cross-utilisation between CGST and SGST or UTGST is not permitted. Credit balances in CGST cannot be moved to settle SGST liability, and vice versa. The two are treated as separate ledgers for set-off purposes, and any imbalance between them carries forward to subsequent periods within the same head.
Two worked examples that show the framework in action
The set-off framework is easier to absorb through worked examples than through rules alone. The two scenarios below cover the most common patterns operational businesses encounter — an intra-state-dominant pattern and an inter-state-dominant pattern. Both use the same illustrative entity (F&M Clothing, a clothing manufacturer based in Mumbai, Maharashtra) but with different transaction profiles.
Scenario 1 — Intra-state purchase and intra-state sale
F&M Clothing's transactions for the month run as follows. Inward supply of cloth from XYZ Textiles based in Pune, Maharashtra against input tax credit of ₹45,000 as CGST and ₹45,000 as SGST. Outward supply of garments to Lara Fashion based in Pune, Maharashtra against tax liability of ₹10,000 as CGST and ₹10,000 as SGST.
The set-off at the end of the month applies the framework as follows. The CGST credit of ₹45,000 is first applied against the CGST liability of ₹10,000, leaving a balance of ₹35,000 in CGST credit. The SGST credit of ₹45,000 is first applied against the SGST liability of ₹10,000, leaving a balance of ₹35,000 in SGST credit. Both balances carry forward to the next period within their respective heads. The CGST balance cannot be utilised against any future SGST liability, and the SGST balance cannot be utilised against any future CGST liability — each carries forward to await matching liability in its own head.
Scenario 2 — Inter-state purchase and inter-state sale
F&M Clothing's transactions for a different month run as follows. Inward supply of cloth from XYZ Textiles based in Bangalore, Karnataka against input tax credit of ₹45,000 as IGST. Outward supply of garments to Lara Fashion based in Chennai, Tamil Nadu against tax liability of ₹10,000 as IGST.
The set-off applies the framework as follows. The IGST credit of ₹45,000 is first applied against the IGST liability of ₹10,000, leaving a balance of ₹35,000 in IGST credit. Under the utilisation order, this remaining IGST credit can be applied against either CGST liability or SGST/UTGST liability in any order — but must be fully exhausted before any CGST or SGST/UTGST credit accumulated separately can be utilised against the corresponding heads. Where the entity has CGST liability of, say, ₹20,000 and SGST liability of ₹20,000 for the same month, the remaining IGST credit of ₹35,000 covers ₹20,000 of CGST and ₹15,000 of SGST, leaving ₹5,000 of SGST liability to be settled through SGST credit or through cash. The flexibility on the order between CGST and SGST after IGST is what creates the optimisation question — the finance head can sequence the remaining IGST against the head that produces the cleaner downstream cash and credit position.
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 →The governance checklist for monthly ITC set-off
The set-off computation runs each month before the GSTR-3B is filed. The discipline that prevents stranded credit, misapplied set-off, and downstream reconciliation work sits in twelve sequenced checks the finance team owns. Each item below names a specific review point with a documented sign-off.
Confirm the available credit balance under each head as on the cycle close.
The accountant pulls the closing input tax credit balance under CGST, SGST or UTGST, and IGST as on the last day of the relevant month from the electronic credit ledger on the GST portal. Reconcile against the internal purchase register to confirm the credit balances match. Mismatches are flagged for investigation before any set-off computation begins. The finance head signs off on the credit balance position before the next step proceeds.
Validate the GSTR-2B reconciliation against the purchase register for the period.
GSTR-2B is the auto-drafted credit statement based on supplier filings. Credit available for utilisation in the GSTR-3B for any month is generally limited to what appears in GSTR-2B for that month, subject to the eligibility conditions under Section 16 of the CGST Act. The accountant matches each line of the purchase register against GSTR-2B; mismatches typically involve supplier-side filing delays, wrong GSTIN entry, or invoice number mismatches. Each unresolved mismatch represents potentially deferred credit and a downstream cash impact.
Compute the output tax liability under each head from the sales register.
The output tax liability for the period under CGST, SGST or UTGST, and IGST is computed from the consolidated sales register, including invoices, debit notes, credit notes, and reverse charge entries. The place-of-supply mapping on each customer master determines whether the transaction sits under CGST plus SGST or under IGST. Misclassifications here flow directly into wrong set-off computations downstream.
Apply IGST credit first to IGST liability.
The IGST credit available is first applied against the IGST output tax liability for the period. Any balance of IGST credit after settling IGST liability becomes available for application against CGST or SGST/UTGST liability in any order. The accountant records the IGST credit utilisation against IGST liability before moving to the next step.
Determine the optimal sequencing of remaining IGST credit between CGST and SGST/UTGST.
Where IGST credit remains after settling IGST liability, the finance head sequences it against CGST liability and SGST/UTGST liability in the order that produces the cleaner overall credit and cash position. The choice depends on the entity's accumulated balances in CGST and SGST credit — applying IGST against the head with less accumulated own-head credit typically reduces stranded credit risk. This is the one optimisation point in the monthly cycle that benefits from finance head judgment rather than auto-application.
Apply CGST credit against remaining CGST liability.
After IGST credit has been fully utilised, CGST credit is applied against the remaining CGST liability. Any balance of CGST credit after settling CGST liability can be applied against IGST liability — but CGST credit cannot under any circumstance be applied against SGST or UTGST liability. The accountant records the CGST credit utilisation in the set-off computation.
Apply SGST or UTGST credit against remaining SGST or UTGST liability.
SGST or UTGST credit is applied against the remaining SGST or UTGST liability after IGST credit has been utilised. Any balance after settling the corresponding head can be applied against IGST liability — but SGST or UTGST credit cannot be applied against CGST liability under any circumstance. Cross-utilisation between SGST and UTGST is itself restricted by state and union territory boundaries.
Compute the final cash tax payment under each head.
After all credit utilisation, the residual tax liability under each head — CGST, SGST or UTGST, and IGST — is the cash payable through the electronic cash ledger. The accountant computes the cash component head-wise. The finance head reviews the final cash outflow against the prior month's pattern to flag any unusual variances before payment is initiated.
Document the closing balance of unutilised credit under each head.
The unutilised credit at the end of the period under each head carries forward to the next period within the same head. The accountant records the closing balance against the electronic credit ledger and reconciles to confirm match. Balances stranded persistently in one head over multiple periods signal an operational pattern — typically a mismatch between purchase mix and sales mix on intra-state versus inter-state — that warrants finance head attention.
Validate the set-off computation against the GSTR-3B draft.
The set-off computation is entered into the GSTR-3B draft for the period. The accountant validates that the IGST, CGST, and SGST utilisation amounts in the draft match the set-off computation, and that the residual cash payable matches the figures intended for payment. Mismatches at this point typically trace back to manual entry errors or to misalignment between the set-off computation and the draft.
Obtain finance head sign-off before GSTR-3B submission.
The completed GSTR-3B draft, the supporting set-off computation, and the documentation of carry-forward credit balances are reviewed by the finance head before submission. The sign-off page records the available credit, the liability under each head, the utilisation sequence applied, the residual cash payment, and the closing credit balances. This sign-off becomes part of the audit trail.
Update the running ledger of utilised and carry-forward credit for the year.
The annual running ledger of utilised and carry-forward credit balances is updated after each GSTR-3B filing. This running view supports the annual reconciliation under GSTR-9 and the year-end audit defence. The accountant maintains the ledger; the finance head reviews monthly. Where statutory payroll also forms part of the operational picture, HRMS for payroll and HR integration extends the same monthly discipline to PF, ESI, PT, and TDS deposit cycles.
How exactllyERP supports the monthly set-off discipline
The set-off computation is conceptually simple but operationally exacting because it depends on clean inputs across three sources — the electronic credit ledger from the GST portal, the purchase register reconciled against GSTR-2B, and the sales register with correct place-of-supply mapping. exactllyERP eliminates GST filing errors and input tax credit mismatches by holding all three sources as configured outputs of the standard transaction flow. The purchase order, GRN, and supplier invoice produce the purchase register with GSTIN, HSN, and tax classification captured at source. The sales order, dispatch, and invoice produce the sales register with place-of-supply rules applied at posting. The reconciliation of GSTR-2B against the purchase register runs as a configured monthly process rather than as a manual reconciliation pass.
How exactllyERP handles this automatically: the GSTR-2B reconciliation against the purchase register (Item 2) catches input tax credit eligibility issues at master-creation rather than at the set-off stage. The place-of-supply logic at invoice posting (Item 3) ensures correct CGST/SGST or IGST classification on every transaction, removing the misclassification risk that flows into wrong set-off computations. The configured set-off computation across CGST, SGST/UTGST, and IGST applies the utilisation order automatically, with the finance head sequencing remaining IGST credit between CGST and SGST liability as the one judgment point retained for review. GST council changes to the utilisation order — as occurred with the introduction of Section 49A and 49B — absorb through statutory updates rather than custom rebuilds. The audit trail captures each transaction back to the source document, which is what makes the GSTR-9 annual reconciliation a documentation exercise rather than a reconstruction project. Request a free demo to walk through how the monthly set-off computation would map to your specific GSTIN structure, transaction mix, and credit balance pattern with our team.
