Ravishankar Yadav on the 2026 TDS System Reset

Ravishankar Yadav recently shared something that caught my attention: "TDS Changes from 1 April 2026 - Are You Ready? Most people think TDS changes mean rate changes... But this time, it’s much bigger." That framing matters, because it shifts the conversation away from a narrow focus on percentages and toward the bigger operational reality: India’s TDS compliance experience is being redesigned.

In his post, Ravishankar also summed up the practical takeaway in a way I wish more tax updates did: "Rates are mostly same... but system is now smarter, faster & unified." If you work in accounts payable, payroll, procurement, or handle cross-border vendor payments, that line should trigger planning mode. When the system changes, teams that rely on older checklists, older mappings, and manual follow-ups are the ones that feel the pain first.

Below, I’m expanding on what Ravishankar outlined and translating it into what it could mean for day-to-day finance operations, process owners, and compliance teams as 1 April 2026 approaches.

The headline: this is not just a rate update

For years, many TDS conversations have started and ended with: "What’s the new rate?" Ravishankar’s point is that the 2026 change is more structural. The design of the law and the design of the filing and approval workflows are moving toward simplification and consolidation.

Key idea from Ravishankar Yadav: don’t anchor on rates. Prepare for a unified, restructured TDS framework.

That difference is huge. Rate changes can be handled with a master update in ERP and a revised rate chart. System changes touch master data, forms, mapping logic, exception handling, approvals, and reconciliation.

What’s changing (and why it matters)

Ravishankar listed several changes that, taken together, point to a single theme: less fragmentation.

1) New Income-tax Act, 2025: structured and simplified TDS

A new Act that reorganizes provisions is not cosmetic. Even if the underlying policy intent remains similar, the renumbering and re-alignment of sections can impact:

• Internal control documentation and SOPs
• ERP configuration references (section codes, reason codes, and tax codes)
• Compliance checklists used by AP and payroll teams
• Training material for new joiners and shared services

The risk is not that the tax suddenly becomes unknowable. The risk is operational: teams keep using the old mental model and the old mapping tables.

2) Forms renamed and reduced

Ravishankar mentioned forms being renamed and reduced. When forms are consolidated, it usually reduces confusion, but it also forces transition work:

• Updating templates used for monthly closing packs
• Revising statutory calendar trackers
• Re-aligning responsibilities between AP, treasury, and tax

If you’ve ever lost time because a vendor asked for a certificate format that your team no longer issues (or you issued the wrong one), you know why fewer forms can be a real win.

3) A single unified TDS form: fewer filings

A unified form is one of those changes that sounds small until you run operations at scale. Multiple filings often mean:

• Multiple validation rules
• Multiple upload cycles
• Multiple error queues
• Multiple reconciliation points

Consolidation can reduce duplicated effort. But expect a transition period where teams need to understand new validations and how legacy data flows into the new format.

4) PAN-based TDS for NRI property (no TAN): relief for buyers

Ravishankar called out a very practical pain point: property purchases involving NRIs. Removing the TAN requirement (and leaning on PAN-based mechanics) can reduce friction for buyers who are otherwise forced into a compliance task they do once in a lifetime.

Operationally, this hints at a broader direction: identity-based withholding processes that reduce the need for additional registrations, especially for occasional deductors.

5) Automated NIL / Lower TDS approval: fewer manual follow-ups

This is the change I’d expect to have the most visible impact inside finance teams.

Today, NIL or lower deduction workflows can create bottlenecks:

• The requester submits documentation
• Someone follows up repeatedly
• AP holds payments or applies standard rates to avoid risk
• Vendors escalate because cash flow is impacted

Automation, if implemented well, reduces email chasing and makes outcomes more predictable. But it also increases the importance of clean data and clear audit trails.

The most important structural shift: section consolidation

Ravishankar’s biggest update was about re-alignment of multiple familiar sections into new consolidated sections.

He highlighted that sections like:

• 194A (Interest)
• 194J (Professional fees)
• 194I (Rent)
• 194Q (Purchase of goods)
• 195 (Foreign payments)

are aligned under Section 393, while Salary TDS (192) moves to Section 392.

Why consolidation matters in real life

This is where compliance and operations meet. Even if rates and thresholds remain "mostly the same," your processes reference these sections everywhere:

• Vendor master tax determination logic
• Nature of payment coding
• TDS GL mapping and ledger posting rules
• Certificate issuance logic
• Statutory reporting and reconciliations

If you are a finance leader, the key question is not "What is Section 393?" The key question is: what in my system currently keys off 194J vs 194I vs 195, and how will that be represented going forward?

A practical example: professional fees and rent in the same reporting bucket

Consider a common mid-sized company scenario:

• You pay consultants (professional fees)
• You pay office rent

Today, teams often treat these as separate compliance streams, with separate internal checks. With consolidation, the law may still distinguish the nature of payment, but the reporting umbrella changes. That can be good, but only if your internal classification stays accurate.

What could go wrong during transition:

• A consultant is mistakenly coded as rent or vice versa
• A new unified form rejects records due to mismatched classification fields
• Reconciliation becomes harder because legacy reports were section-based

The fix is not panic. The fix is planning and controlled migration.

What finance and tax teams should do before April 2026

Ravishankar’s post is a reminder to prepare early. Here’s a focused checklist I’d recommend if you own AP, payroll, or compliance operations.

1) Build a section mapping bridge

Create a mapping document that connects:

• Old sections (like 194A, 194J, 194I, 194Q, 195, 192)
• New consolidated sections (392, 393)
• Your internal nature-of-payment codes
• ERP tax codes and GL accounts

This becomes the single source of truth for training and configuration changes.

2) Review workflows that depend on manual approvals

If NIL/lower deduction approvals become automated, identify the current bottlenecks:

• Who requests certificates?
• Who validates them?
• Where are they stored?
• How is expiry tracked?

Automation works best when inputs are standardized and ownership is clear.

3) Prepare your vendor and employee master data

Unified reporting and PAN-based workflows increase sensitivity to master data quality. Start cleaning:

• PAN validation status
• Vendor residency flags (resident vs non-resident)
• Nature of payment accuracy
• Supporting documents storage

4) Align stakeholders: tax, AP, payroll, procurement, and IT

These changes are cross-functional. Procurement influences correct nature-of-payment selection. IT supports ERP changes. Tax validates interpretation. AP executes.

A short alignment meeting now can save weeks of rework later.

5) Plan for parallel runs and reconciliations

Even if the go-live is 1 April 2026, consider running parallel internal reporting for a period (where feasible):

• Compare output from old section-based reports vs new consolidated logic
• Validate exception handling
• Confirm vendor communications and certificate expectations

A quick note on why Ravishankar’s post resonated

The post performed well because it reframed the update. Instead of a dry list of rates, it highlighted system design: fewer forms, unified filings, automation, and a simplified structure. In compliance, that’s the difference between "memorize" and "prepare."

"Rates are mostly same... but system is now smarter, faster & unified." The operational implication: invest in process and data readiness, not just rate tables.

Final takeaway

If you only take one thing from Ravishankar Yadav’s update, take this: treat April 2026 like a systems change, not a spreadsheet change. Start mapping, cleaning master data, and aligning workflows now, and you’ll avoid the typical year-one chaos that follows major compliance redesigns.

This blog post expands on a viral LinkedIn post by Ravishankar Yadav, Driving Accurate Finance Operations | Senior Accounts Executive @ Powerweave Software Services Pvt Ltd | Accounts Payable | Payroll | Vendor Payments | TDS & GST. View the original LinkedIn post →