Why Is My TDS Being Deducted at a Higher Rate Than Normal?

You raised the invoice for Rs 5 lakh in professional fees under Section 194J. The customer’s remittance advice arrives and the amount credited is Rs 4 lakh, not Rs 4.5 lakh. Form 16A on the customer’s TRACES account shows a Rs 1 lakh TDS entry against your PAN — twice what you expected.

The customer’s finance team says the deduction is correct at their end. Your working capital has taken a Rs 50,000 hit that you now have to fund until the annual refund cycle. The extra deduction did not happen by accident — but why?

The quick answer

Higher-rate TDS on an Indian invoice traces to one of five triggers. Section 206AA — the deductee did not furnish a valid PAN, so tax runs at the higher of the section rate or 20 per cent. Section 206AB — the deductee is a specified person (return not filed for the immediately preceding assessment year for which the Section 139(1) due date has expired, and aggregate TDS or TCS of Rs 50,000 or more in that preceding previous year), so tax runs at the higher of twice the section rate or 5 per cent. Section 206CCA — the TCS-side parallel of Section 206AB. Section 195 read with Section 90 — a non-resident deductee has not filed a Tax Residency Certificate or a Form 10F, so the DTAA rate is unavailable and the statutory rate applies. Or the Compliance Check Utility miss — the deductor never ran the specified-person check and applied the doubled rate defensively.

The recovery route is different for each. The one to escalate first is the trigger that is still open on the next invoice — either the outstanding Section 139 return under Section 206AB, or the missing TRC and Form 10F under Section 195. The rest is post-facto correction.

Trigger 1 — Section 206AA, missing or invalid PAN

Section 206AA of the Income-tax Act 1961 is the oldest of the higher-rate mechanisms. Where the deductee has not furnished a valid PAN to the deductor, tax is deducted at the higher of three rates — the rate specified in the relevant provision of the Act, the rate or rates in force under the applicable Finance Act, or 20 per cent. For a Section 194J payment normally at 10 per cent, the 20 per cent flat rate is the higher of the three and the deduction runs at 20 per cent.

The three most common Section 206AA fact patterns. A typo in the ten-character PAN on the invoice — one wrong character silently fails the TRACES PAN validation and the deductor withholds at 20 per cent. A PAN that is technically valid in format but does not exist in the Income Tax Department’s master — a deactivated PAN, a PAN cancelled following a merger, or a PAN that was never issued despite the format being correct. A PAN provided at proposal stage that was corrected on a subsequent invoice, but the deductor’s AP vendor master was not updated to the new PAN.

Illustrative arithmetic on a Section 194J invoice. Invoice value Rs 5 lakh. Normal deduction at 10 per cent = Rs 50,000. Section 206AA deduction at 20 per cent = Rs 1 lakh. Extra deduction = Rs 50,000. The deducted amount is credited to the wrong PAN (or no PAN) on Form 26AS, so the vendor cannot claim the higher deduction as a credit against the assessment year’s tax liability until the deductor files a C1 correction on the affected quarterly return.

Recovery route. Send a written PAN correction communication to the deductor with a self-attested PAN card copy. Ask for a C1 (deductee PAN update) correction on the TRACES portal for the affected Form 26Q quarter. Processing takes three to seven business days. Once the C1 is processed, Form 26AS and Form 168 refresh with the corrected credit and the underlying higher-rate deduction becomes claimable at the section rate on the annual return.

Trigger 2 — Section 206AB, the specified-person non-filer

Section 206AB was inserted by the Finance Act 2021 and refined by the Finance Act 2022 to reduce the two-year lookback to one year. The mechanic — where the deductee is a specified person, tax is deducted at the higher of twice the section rate, twice the rate or rates in force, or 5 per cent. A specified person is a person who has not furnished the return of income for the assessment year relevant to the previous year immediately preceding the financial year in which tax is required to be deducted (for which the Section 139(1) due date has expired), and whose aggregate TDS or TCS in that preceding previous year was Rs 50,000 or more.

The Rs 50,000 aggregate threshold catches most professional-services firms with even modest deductor exposure. A firm with a single retainer customer withholding Rs 5,000 a month under Section 194J crosses Rs 50,000 in the tenth month. A vendor to two large corporate customers can accumulate Rs 50,000 in the first quarter alone.

Illustrative arithmetic on the same Rs 5 lakh Section 194J invoice. Normal deduction at 10 per cent = Rs 50,000. Section 206AB deduction at higher of (2 × 10 per cent = 20 per cent) or 5 per cent = 20 per cent. Extra deduction = Rs 50,000. From 1 April 2026, the Section 393(1) code on the deduction is code 1027 (professional fees) — the code migration does not change the higher-rate mechanic; the Section 393 payment code finder is the operational lookup.

Recovery route. File the outstanding return for the immediately preceding assessment year — even a belated return under Section 139(4) closes the specified-person status prospectively for the next financial year. Ask the deductor to re-run the Compliance Check Utility on the TAN portal within one month of the return-filing acknowledgement; the specified-person list refreshes to reflect the belated filing. For the current higher deduction, no in-year reversal is possible on the deductor’s side — the Rs 50,000 excess flows into the vendor’s own return as a claim for refund against the annual tax liability. The Section 206AB and 206CCA MOFU walkthrough covers the full mechanism, the Compliance Check Utility workflow, and the deductor-side control model.

Trigger 3 — Section 206CCA, the TCS-side parallel

Section 206CCA is the TCS-side mirror of Section 206AB. Where a collection is required under Chapter XVII-BB — typically Section 206C(1H) on the sale of goods above Rs 50 lakh at 0.1 per cent — and the buyer is a specified person on the Compliance Check Utility, tax is collected at the higher of twice the section rate (2 × 0.1 per cent = 0.2 per cent) or 5 per cent. The 5 per cent floor is the operational rate.

Illustrative arithmetic. A seller invoices a corporate buyer Rs 1 crore for goods in FY 2026-27. Normal Section 206C(1H) TCS at 0.1 per cent on the amount above Rs 50 lakh = Rs 5,000 on Rs 50 lakh. Section 206CCA collection at higher of 0.2 per cent or 5 per cent = 5 per cent on Rs 50 lakh = Rs 2.5 lakh. Extra collection = Rs 2,45,000. The exposure asymmetry between Trigger 2 and Trigger 3 is stark — the doubled section rate on a small TCS rate barely moves the number, but the 5 per cent floor makes Section 206CCA one of the most cash-flow-punishing of the five triggers when it is missed on the buyer-side vendor master.

Recovery route. Same as Section 206AB from the buyer’s angle — file the outstanding return, refresh the specified-person status, and claim the excess collection as a refund on the annual return. The seller has no discretion to lower the collection once the Compliance Check confirms the specified-person status.

Trigger 4 — Section 195, the non-resident TRC and Form 10F miss

Section 195 of the Income-tax Act 1961 requires deduction on any sum paid to a non-resident that is chargeable under the Act, at the rates in force. The rates in force include the rate under a Double Taxation Avoidance Agreement (DTAA) — often materially lower than the statutory Section 195 rate. But the DTAA rate is available only where two documentary conditions are met.

Section 90(4) requires the non-resident to hold a Tax Residency Certificate (TRC) issued by the tax authority of the country of residence, containing the information prescribed in Rule 21AB(1) — the TRC’s issue date, the period of residence certified, the residence status, and the country of residence. Section 90(5) requires the non-resident to file a Form 10F declaration. From FY 2022-23 onwards, the Form 10F must be filed electronically on the Income Tax portal — either under the non-resident’s own PAN, or (for a non-resident with no PAN) through the temporary Non-Resident login route the portal introduced in April 2023.

Illustrative arithmetic. A UK-resident consultant invoices an Indian company Rs 5 lakh for professional services. Under the India-UK DTAA Article 13, technical fees are taxable at 10 per cent (subject to make-available and other conditions). Section 195 statutory rate is 10 per cent for royalty and fees for technical services under the Income-tax Act — but where the beneficial provisions of DTAA are unavailable, the general Section 195 rate (or the rate specified in the relevant Notification for a make-available or non-treaty case) applies, and the effective grossed-up deduction on a net-of-tax contract can approach 20 per cent. The Form 15CA and Form 15CB foreign remittance reconciliation walkthrough covers the remittance-authorisation documentation trail that has to accompany every cross-border payment.

Recovery route. File the TRC and Form 10F with the Indian deductor. Ask the deductor to correct the current-quarter Form 27Q to reflect the DTAA rate — a C3 (deductee record) correction on TRACES against the affected acknowledgement number. For the balance of the current year, request the deductor to apply the DTAA rate from the next invoice onwards. The excess deduction already made is claimable as a refund on the non-resident’s own India return under Section 139(1), subject to the DTAA-country reporting reciprocity.

Trigger 5 — the Compliance Check Utility miss

The fifth trigger is a book-side control failure rather than a statutory event. The Compliance Check Utility on the Reporting Portal is the operational route by which a deductor verifies the specified-person status of a payee before deduction. The utility supports single-PAN lookup and bulk verification for up to ten thousand PANs at a time through a CSV upload.

Where the deductor’s AP process does not include a Compliance Check refresh — either at the start of every financial year (when the specified-person list resets) or on a rolling quarterly basis — two failure modes surface. The deductor deducts defensively at the specified-person rate even where the vendor is not a specified person (over-deduction, Rs 50,000 excess on the illustrative Rs 5 lakh Section 194J invoice). Or the deductor deducts at the section rate on a payee who is in fact a specified person (under-deduction, exposing the deductor to a Section 200A intimation with Section 201(1A) interest at 1 per cent per month on the shortfall).

Recovery route on defensive over-deduction. Send the deductor a written communication with the Compliance Check Utility output confirming the vendor is not a specified person. Ask for a C3 (deductee record) correction on TRACES to reflect the section rate rather than the higher rate. The TDS PAN validation mismatch article covers the parallel controller-side control model for maintaining the vendor master accuracy that sits behind the Compliance Check discipline.

Which trigger to escalate first

The escalation order is not the biggest number — it is the trigger that is still open on the next invoice. Section 206AB and Section 195 both carry ongoing exposure until the underlying filing is completed (the outstanding Section 139 return in Section 206AB; the TRC and Form 10F in Section 195). Every subsequent invoice to the same customer, or to any other customer for the same vendor PAN, will carry the same doubled deduction until the trigger is closed.

Section 206AA and the Compliance Check Utility miss (Trigger 5) are per-invoice corrections — a C1 correction on TRACES resolves the current quarter, but the next quarter is safe if the vendor master has been updated. Section 206CCA sits between the two, structurally identical to Section 206AB but with the exposure carried by the buyer’s non-filing status rather than the seller’s.

For a vendor experiencing Trigger 2 or Trigger 4, the sequence is straightforward — close the underlying filing gap first, then chase the current-year over-deduction as a refund on the annual return. Reversing the order (chasing the refund before closing the gap) means the same Rs 50,000 doubled deduction recurs on the next invoice, and the same vendor is running two open Section 200A queues at year-end rather than one.

The Section 200A intimation and the interest exposure on the deductor side

For the deductor, a Section 200A intimation flagging a Section 206AB or Section 206CCA under-deduction carries Section 201(1A) interest at 1 per cent per month from the payment date to the deduction date and 1.5 per cent per month from the deposit date to the date the shortfall is regularised. The why is there interest showing on my TDS challan article is the sibling TOFU walkthrough on the interest-computation mechanic. A shortfall of Rs 50,000 regularised six months late carries roughly Rs 4,500 in Section 201(1A) interest — a small absolute figure, but the Section 271C penalty ceiling at the Assessing Officer’s discretion can extend to a sum equal to the tax not deducted. The controller-level control on the deductor’s side is the Compliance Check refresh; on the vendor’s side, it is the timely filing of the Section 139 return.

When the manual vendor-master and specified-person register outgrows itself

For a mid-market deductor with under 200 active vendors and one or two non-resident payees, the vendor master and the specified-person register fit inside a single Excel schedule that the AP executive refreshes quarterly. The Compliance Check Utility bulk-upload workflow closes in an hour a quarter; the TRC and Form 10F folder is a shared drive with one document per non-resident vendor.

Above 500 active vendors, or above five concurrent non-resident payee relationships, the manual schedule starts to leak. A vendor whose Section 139 filing status changed mid-year sits on the wrong tier of the specified-person register for a quarter. A non-resident TRC expires without a renewal reminder and the DTAA rate lapses on the next invoice. A vendor merger transfers the PAN without an AP master update and the next quarter’s Form 26Q is filed with the stale PAN. Each miss compounds into a Section 200A intimation, and the aggregated intimation register carries an open Section 201(1A) interest balance until the corrections are filed.

At that scale, moving the vendor master, the specified-person register, and the DTAA-documentation checklist onto continuously refreshed detection — where Terra Insight’s TDS reconciliation software treats the Compliance Check refresh, the TRC-expiry calendar, and the higher-rate deduction classification as first-class outputs — is what stops the fifth Rs 50,000 doubled deduction on the same PAN before it lands on the sixth Form 16A. Below that scale, the Excel schedule holds and the quarterly Compliance Check discipline is the right control.

Go deeper

• Section 206AB and Section 206CCA — the non-filer higher-rate mechanism in full
• TDS PAN validation mismatch and Section 206AA — the vendor-master control model
• Section 195 non-resident TDS and the DTAA route
• Form 15CA and Form 15CB foreign remittance reconciliation
• The twelve-step Form 168 shortfall investigation — the illustrative Rs 1.69 lakh case walked end-to-end
• Why is there interest showing on my TDS challan — the Section 201(1A) mechanic
• Section 393 payment code finder — the Section 194X to Section 393(1) code lookup
• TDS reconciliation software for India

Frequently Asked Questions

My customer deducted TDS at 20 per cent under Section 194J when the rate should be 10 per cent. Why?

The most common reason is Section 206AB — the deductor’s Compliance Check Utility query returned your PAN as a specified person, meaning the Income Tax Department’s records show your firm has not filed a return for the immediately preceding assessment year for which the Section 139(1) due date has expired, and your aggregate TDS or TCS in that preceding previous year was Rs 50,000 or more. Where Section 206AB applies to a Section 194J payment, the deduction runs at the higher of twice the section rate (2 × 10 per cent = 20 per cent) or 5 per cent — the 20 per cent figure is the higher of the two, hence the doubled deduction. The second most common reason on a Section 194J payment is Section 206AA — a wrong or invalid PAN on the invoice, which triggers deduction at the higher of the section rate or a flat 20 per cent. The two look identical on the certificate, and the recovery route is different: Section 206AB is fixed by filing the outstanding return and refreshing the Compliance Check; Section 206AA is fixed by supplying a valid PAN and requesting a correction.

How do I check whether my PAN is a Section 206AB specified person?

The Compliance Check Utility on the Reporting Portal (compliance.insight.gov.in) is the operational route. A deductor holds the login credentials against a TAN; a vendor cannot directly query their own status on that utility. The vendor’s own check is procedural — verify that the return of income for the assessment year relevant to the previous year immediately preceding the current financial year has been filed on or before the Section 139(1) due date, and confirm that the aggregate TDS or TCS in that preceding previous year did not exceed Rs 50,000. If the return was filed late (after the Section 139(1) due date), or was not filed at all, and the aggregate TDS or TCS was Rs 50,000 or more, the PAN is on the specified-person list until the next financial year’s refresh. The deductor’s Compliance Check output as at the deduction date is what the department relies on — a subsequent late filing does not retroactively reverse the higher deduction already made.

The customer says they applied Section 206AA because the PAN is invalid — but the PAN is correct. What went wrong?

Three fact patterns commonly surface. First, a typo in the PAN on the invoice or in the vendor master — one wrong character in the ten-character PAN silently fails PAN validation on TRACES and the deductor withholds at 20 per cent. Second, a PAN that is technically valid in format but does not exist in the Income Tax Department’s PAN master — a deactivated PAN, a PAN cancelled following a merger, or a PAN that was never issued despite the format being correct. Third, a PAN provided at proposal stage that was later corrected on a subsequent invoice, but the deductor’s AP master was not updated. The recovery route is a written PAN correction communication to the deductor with a self-attested PAN card copy, followed by a C1 correction (deductee PAN update) on the TRACES portal for the affected quarterly return. Once TRACES processes the C1 correction, your Form 26AS and Form 168 refresh with the corrected credit and the underlying higher-rate deduction becomes claimable at the section rate on the annual return.

I am a non-resident and my Indian customer deducted TDS at a higher rate than the DTAA rate. How do I fix this?

The DTAA rate is available to a non-resident deductee only where two documentary conditions are satisfied under Section 90(4) and Section 90(5) read with Rule 21AB. First, a Tax Residency Certificate (TRC) issued by the tax authority of the country of residence, containing the information prescribed in Rule 21AB(1). Second, a Form 10F declaration filed electronically on the Income Tax portal under the non-resident’s own PAN (or under the temporary Non-Resident login route if the non-resident has no PAN) from FY 2022-23 onwards. If either the TRC or the Form 10F is missing on the deduction date, the deductor is required to deduct at the statutory Section 195 rate — often 20 per cent grossed-up or the rate in force — rather than the DTAA rate. The recovery route is to file both documents with the deductor, request a fresh Form 15CA and Form 15CB workflow for future payments, and file the non-resident’s own India return to claim the higher deduction as a refund. The Form 15CA and Form 15CB reconciliation article walks through the workflow end-to-end.

The Section 200A intimation from TRACES says I under-deducted under Section 206AB. What is the interest exposure?

Under Section 201(1A), a deductor who fails to deduct the whole or any part of the tax is liable to pay simple interest at 1 per cent per month or part of the month from the date on which the tax was deductible to the date on which the tax is deducted, and a further 1.5 per cent per month or part of the month from the date on which the tax was deducted to the date on which the tax is actually paid to the Government. On a Section 206AB shortfall — the deductor deducted at the section rate 10 per cent instead of the specified-person rate 20 per cent — the interest at 1 per cent per month runs from the payment date to the deduction date (typically the same day, so a nominal exposure), and the 1.5 per cent per month runs from the deposit date to the date the shortfall is regularised through a correction and fresh challan. A shortfall of Rs 50,000 that is regularised six months after the original challan carries roughly Rs 4,500 in Section 201(1A) interest by the correction date, before any Section 271C penalty exposure at the Assessing Officer’s discretion. The TDS interest and penalty impact calculator models the running exposure across the delayed correction timeline.

Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published Invalid Date

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024