Form 121 and UIN-Based Nil-TDS Declarations: The 2026 Workflow Deductors Must Control

The Income-tax Rules, 2026 have introduced a more structured compliance architecture for situations where a taxpayer expects nil tax liability and wants specified receipts to be paid without tax deduction at source. Form No. 121 is the statutory declaration at the centre of that architecture, but the real operational change is larger: deductors now need a reliable process for declaration intake, Unique Identification Number (UIN) tracking, quarterly reporting and portal validation.

Why Form 121 matters

According to the Income Tax Department’s official Form 121 user manual, Form 121 is prescribed under the Income Tax Rules, 2026 for a taxpayer to declare that tax liability on estimated total income for the relevant tax year is nil. Where the declaration is valid, the payer may make specified payments without deducting TDS. The Department advises that the declaration should ideally reach the deductor before the income is credited or paid and preferably at the start of the tax year.

This shifts the compliance question from a simple “do we have a declaration?” to a controlled process: was the declaration received before payment, is it complete, has a UIN been allotted, is the payer’s TAN valid and registered, and has the quarterly reporting obligation been completed on time?

The UIN is now a key control point

The Department’s filing guidance states that a Unique Identification Number is assigned to each declarant. The UIN is a 26-character identifier comprising the letter “D”, nine random numerical digits, six digits relating to the selected tax year, and the ten characters of the payer’s TAN. This creates a traceable link between the declarant, the relevant tax year and the deductor reporting the declaration.

For finance and tax teams, that means the UIN should not live only inside the e-filing portal. It should be captured in the vendor or payee master, linked to the underlying declaration, mapped to the relevant tax year, and retained with the supporting documentation used to justify non-deduction.

Quarterly reporting cannot be treated as an afterthought

The Income Tax Department states that the deductor must file Form 121 by the 7th of the month following the relevant quarter. The portal filing process requires the deductor to select the applicable filing type, tax year and quarter, and then report details of the payer and the declarations received. The declarant data is uploaded through a prescribed CSV structure and the form is then electronically verified.

The operational risk is obvious: a valid declaration received by the accounts team can still turn into a compliance failure if it is not captured in the quarter-end reporting file or if the UIN, PAN, declaration date or related payment data is inconsistent with the records used by the TDS team.

What deductors should change in their process

A robust Form 121 process should have at least five layers of control. First, declarations should be routed through a central tax or compliance mailbox rather than handled informally by individual business teams. Second, the declaration should be validated before the first payment or credit wherever possible. Third, the UIN and declaration period should be captured in the payee master and linked to withholding logic. Fourth, a quarter-end reconciliation should compare all payments made without TDS against the Form 121 reporting population. Fifth, the acknowledgement number and transaction ID generated on filing should be retained with the quarterly TDS working papers.

Why the 2026 framework is more audit-friendly—and less forgiving

The new workflow is designed to create a stronger electronic trail. The payer logs in through its TAN, reports declarant-level information, uses a prescribed UIN format, uploads structured data and electronically verifies the filing. That makes it easier for tax authorities to compare non-deduction positions with payer records and taxpayer filings. It also means that weak internal documentation, stale declarations or quarter-end omissions are more likely to surface in reconciliation or scrutiny.

Practical takeaway

Form 121 should be treated as a withholding-tax control process, not merely as a form-filing exercise. Businesses making recurring payments without TDS should integrate declaration collection, UIN tracking, payment processing and quarterly reporting into one workflow. The strongest defence in any future review will be a clean audit trail showing why tax was not deducted, when the declaration was received, which UIN applied, which payments were covered and when the quarterly filing was completed.

Disclaimer: This article is intended for general professional information and does not constitute tax or legal advice. Applicability depends on the nature of the payment, taxpayer status and the specific provisions in force for the relevant tax year. Professional advice should be obtained before acting on a nil-TDS declaration.