Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
CBDT Circular No. 23/2017 requires TDS to be computed on the base invoice value only, excluding the GST component. Deductors that compute on the gross amount (base plus 18 percent GST) over-deduct and create Form 26AS credits the vendor cannot claim. For a ₹1,18,000 invoice at 10 percent under 194J, the excess is ₹1,800 per invoice.
Split each vendor invoice into base value and GST component at entry, either from a separately stated invoice line or by dividing the gross by one plus the applicable GST rate. Compute TDS only on the base value using the section-appropriate rate. Flag invoices without a GST break-up for vendor follow-up before TDS computation.
Invoice parser that extracts base and GST lines. Vendor-master GST rate field to derive base when GST is not separately shown. Exception queue for invoices without a GST break-up.
Correctly computed TDS on base value only, clean Form 26AS credits that the vendor can claim, and reduced correction return volume for GST-inclusive over-deductions.
Deducting TDS on the GST component of an invoice is one of the most common and consequential errors in Indian TDS compliance. CBDT Circular No. 23/2017 settled this question definitively: TDS under Chapter XVII-B of the Income Tax Act does not apply to the GST portion of an invoice. The deduction must be computed on the base value only. Finance teams processing high-volume vendor invoices — particularly under sections 194C, 194J, and 194H — need to apply this correctly at transaction entry, not discover the error at quarter-end.
What CBDT Circular No. 23/2017 Actually Says
CBDT Circular No. 23/2017, dated 19 July 2017, was issued shortly after GST implementation to clarify the interaction between TDS under the Income Tax Act and GST. The circular states that wherever GST on services is indicated separately in the invoice, TDS under Chapter XVII-B is to be deducted on the amount paid or credited excluding the GST component.
The rationale is straightforward: GST is a tax collected by the vendor on behalf of the government and remitted through their GST return. It is not “income” of the vendor. Deducting TDS on a government-mandated tax passthrough creates a false tax liability against the vendor’s PAN.
Two Invoice Scenarios and the Correct Treatment
Scenario A: GST Shown Separately on the Invoice
This is the standard case. The invoice shows:
- Base value: ₹1,00,000
- GST @ 18%: ₹18,000
- Total: ₹1,18,000
TDS at 10% (e.g., under Section 194J) is computed on ₹1,00,000 = ₹10,000. The payment to the vendor is ₹1,18,000 minus ₹10,000 = ₹1,08,000. This is the correct treatment.
Scenario B: GST Not Separated on the Invoice
Some vendors — particularly smaller GST registrants — issue invoices showing only the total amount without a line-by-line GST breakup. In this case, the deductor must still compute TDS only on the base value. Ask the vendor to provide a revised invoice or a supplementary document confirming the GST component. Deducting TDS on the gross amount without seeking the breakup is not acceptable as a compliance position.
The Common Error and Its Reconciliation Consequence
| Invoice Item | Correct Treatment | Incorrect Treatment |
|---|---|---|
| Base value | ₹1,00,000 | ₹1,00,000 |
| GST @ 18% | ₹18,000 | ₹18,000 |
| Total invoice | ₹1,18,000 | ₹1,18,000 |
| TDS rate (194J) | 10% | 10% |
| TDS deducted | ₹10,000 (on base) | ₹11,800 (on total) |
| Excess TDS | — | ₹1,800 |
| Vendor receives | ₹1,08,000 | ₹1,06,200 |
The ₹1,800 excess appears in the vendor’s Form 26AS as TDS credit against their PAN. The problem: it represents tax deducted on GST, which the vendor pays to the government through their own GSTR-3B. The vendor cannot claim this ₹1,800 as income tax credit — it sits in Form 26AS as a credit that creates a reconciliation mismatch between their books and the tax system.
Reverse Charge Mechanism and TDS
When a transaction attracts RCM — for example, import of services or services from an unregistered supplier — the buyer pays GST directly to the government rather than through the vendor invoice. The vendor’s invoice may show the base value with a note that GST is payable under RCM. In this scenario, TDS is still deducted only on the base invoice value. The fact that the buyer is separately bearing the GST under RCM does not alter the TDS computation.
Correction When Excess TDS Has Been Deducted
If TDS was deducted on a GST-inclusive amount and already deposited via challan, the deductor must file a correction return through TRACES. The correction adjusts the TDS amount in the quarterly return (Form 26Q or 27Q). Once processed, the vendor’s Form 26AS is updated. The excess challan amount can be adjusted against future TDS liability in the same quarter or refunded through TRACES.
For organisations processing hundreds of vendor invoices monthly, identifying which invoices had TDS computed on gross amounts requires a systematic review of TDS entries against invoice details. TDS reconciliation software that matches TDS deductions against invoice base values can flag these discrepancies automatically rather than requiring manual line-by-line review.
Building a clean TDS deduction process requires not just getting the computation right at source, but ensuring that the ledger entries, Form 26AS credits, and vendor statements are consistent. Reconciliation software India finance teams use typically handles the three-way match between TDS deducted, challan deposited, and Form 26AS credit — catching GST-inclusion errors as part of the mismatch classification.
The Income Tax India e-filing portal provides access to Form 26AS and TRACES for verifying TDS credit positions against PAN.
Common questions from deductors handling GST-inclusive invoices are addressed below.