Nris Face New TDS Auditability Problem as India Demands Proof for Every Tax Deduction

(INDIA) — India’s tax administration has pushed TDS Compliance beyond the old checklist of deduction, deposit, return filing and certificate issuance, leaving employers, businesses, payers and NRIs under growing pressure to prove why they applied a particular tax rule on the exact date of payment or credit.

That shift has created what tax professionals increasingly describe as an auditability problem: not whether tax was deducted at source, but whether the deductor can show why a specific section, rate, threshold and PAN status were used at that moment.

Tax Deducted at Source, or TDS, remains one of the central compliance mechanisms under Indian income-tax law. It touches salaries, rent, contractor payments, professional fees, property deals, interest, dividends and consultancy income, reaching from large companies and startups to freelancers, landlords, tenants and overseas Indians with India-source income.

For years, many deductors treated TDS as a four-step process. Deduct the tax, deposit it with the government, file the quarterly TDS statement, and issue the certificate.

That structure still stands. A challan proves payment, and a return proves reporting, but neither answers the legal question that often drives a notice: why this section, why this rate, why no deduction, why resident rather than non-resident, and whether the PAN was operative on that date.

India’s tax systems now draw from a wider pool of data. TDS returns, the Annual Information Statement, `Form 26AS`, PAN records, property transactions, GST data and bank reporting sit closer together than before, making it easier for the department to compare one filing against another and identify mismatches in classification or rate selection.

That changes the pressure point for deductors. The department may ask whether a payment was correctly treated as contract work rather than professional fees, whether a threshold had already been crossed when the payment was credited, whether a lower deduction certificate existed, or whether the correct version of the law was applied during a period of statutory transition.

Most accounting systems, payroll systems and ERP software record the output of a TDS decision, not the reasoning that produced it. A record may show the vendor name, PAN, invoice amount, payment date, section applied, rate applied, amount deducted, challan details and filing status, yet leave no contemporaneous note explaining why that treatment was selected.

A common dispute shows the gap. A company may deduct TDS under section 194C on a contractor payment and deposit the tax at 2%, while the department later asks why the payment was not treated as fees for professional or technical services under section 194J. If the system preserves only “Section applied: 194C” and “TDS deposited: Yes,” the company still has to reconstruct the basis of the decision from agreements, invoices and internal approvals.

That missing trail matters in cases where the answer depends on facts fixed on a past date. A vendor may have been classified as a company at the time of payment, a threshold may have been crossed only after earlier invoices accumulated, or PAN status may have changed later. Current master data does not necessarily prove historical status.

NRIs sit squarely inside this risk. India-source payments to non-residents often involve TDS on sale of immovable property in India, rental income from Indian property, interest income from Indian deposits, dividend income, professional or consultancy income, payments from Indian companies, remittances involving `Form 15CA/15CB`, and cases involving a lower or nil deduction certificate.

Property transactions are among the clearest examples. When an NRI sells property in India, the buyer generally has to deduct TDS under the applicable provisions, and the rate can turn on whether the seller is resident or non-resident, the nature of the capital gain, surcharge, cess and the existence of a lower deduction certificate. If the buyer gets that treatment wrong, the NRI can face excess deduction and refund delays, while the buyer can face short-deduction exposure.

Cross-border payments add more layers. Treaty documents such as a Tax Residency Certificate and `Form 10F` can affect the tax position, and remittance paperwork can become part of the later record if a dispute arises. In those cases, auditability is not an abstract compliance term. It determines whether the payer can defend the decision and whether the recipient can match credits, claim refunds and support foreign tax credit positions.

Employers face a parallel problem in salary withholding. TDS on salary depends on salary structure, exemptions, deductions, the tax regime selected by the employee, declarations, investment proofs, the valuation of perquisites and the basis on which monthly deductions were computed.

If a mismatch emerges later, an employer may need to show which tax regime it considered, what declarations the employee submitted, whether proof was collected, how taxable salary was computed and why a particular monthly TDS amount was deducted. Cases involving employees who move between India and abroad become harder still, because residency, salary splits, foreign allowances, social security, tax equalisation and double taxation relief can alter the analysis.

Startups and digital businesses often face the problem at scale. They may pay software developers, content writers, marketers, consultants, influencers, gig workers, affiliates, landlords and cloud or SaaS vendors, sometimes in large volumes and sometimes across borders.

Those payments can look similar in an accounting system while carrying different tax consequences under the law. One payment may fit contract work, another may be professional fees, another commission, another royalty, and another fees for technical services. If the accounts team relies on a vendor master setup without preserving the rationale behind the tag, scrutiny can become difficult to answer, especially in section 201 proceedings.

Section 201 proceedings can arise when a person is treated as an assessee in default for failure to deduct tax, short deduction or failure to pay tax after deduction. The consequences can include tax demand, interest, penalty exposure, litigation and a larger compliance burden, particularly where the dispute turns on classification or rate rather than total non-deduction.

Freelancers and consultants also face the downstream effect, even when the payer made the original classification. Many look first to whether TDS appears in `Form 26AS` or the Annual Information Statement, but that check does not resolve whether the correct section was applied. A consultant may be treated as a contractor, a technical service provider as a normal vendor, a non-resident freelancer as a resident, or a payment may draw higher TDS because of a PAN-related issue.

That makes document retention part of the defence. Agreements, invoices, PAN details, residency status documents and correspondence with payers can all help explain why a payment received a given treatment and support later replies if income reporting, refund claims or mismatch notices come under review.

Five recurring weaknesses sit at the center of the auditability problem. One is wrong or unexplained section selection, where the system records the section but not the reason. Another is rate selection without historical proof, especially when the deductee category, PAN status or residency status changes later in the vendor record.

A third weakness lies in thresholds. Many TDS provisions apply only after a monetary limit is crossed, and the question is not the year-end total but the aggregate position on the exact date of payment or credit. A fourth lies in PAN status, because a PAN that is operative today does not prove it was operative on the payment date, and an inoperative PAN today does not prove it was inoperative earlier.

The fifth weakness concerns the move from the Income-tax Act, 1961 to the Income-tax Act, 2025. That transition can create practical issues in section mapping, form references, compliance systems and historical reporting, making it necessary to preserve the old section reference, new section reference, applicable date, rule version, form reference and legal basis for deduction.

The practical response begins at the time of transaction, not at year-end. Businesses that want stronger auditability can preserve the nature of payment, the basis for section selection, the basis for rate selection, the deductee’s status, PAN availability and operativeness on the payment date, the threshold position as of that date, linked agreements and invoices, certificates and declarations, and the approval trail showing who signed off on the treatment.

Historical snapshots matter as much as final records. Vendor classifications should stay accurate and updated, but systems also need to retain prior versions so a later change does not erase the status that existed when the payment was made. Payroll systems need the same discipline, particularly where an employee’s tax regime, declarations or assignment pattern changed during the year.

NRIs can reduce exposure by checking whether the payer deducted TDS under the correct provision, providing PAN and residency documents where required, preserving Tax Residency Certificate and `Form 10F` where treaty benefit is claimed, considering a lower deduction certificate in property sale cases, monitoring `Form 26AS` and the Annual Information Statement, and matching TDS credits with income reported in the return.

The direction of travel is plain. Indian tax administration now tests not just whether TDS was deducted, but whether the deductor can prove the deduction decision was legally correct on the date it was made, and that shift leaves the strongest defence in the documents, data snapshots and internal reasoning preserved before the notice arrives.