Quick answer. TDS is a deduction-at-source mechanism with ~30 active sections, each with its own threshold, rate, and deductee scope. The operational discipline is: (1) classify every vendor and every payment against the right section, (2) deduct correctly and on time, (3) deposit by the 7th of the following month, (4) file the quarterly return (24Q for salary, 26Q for non-salary residents, 27Q for non-residents, 27EQ for TCS), (5) issue Form 16/16A from TRACES. The mistake space is huge, wrong section, wrong rate, missed PAN-not-furnished penalty, late deposit interest. The right system makes it boring.
TDS in one diagram
The mental model that makes everything else click:
PAYMENT EVENT (bill / advance / journal entry)
│
▼
WHICH SECTION? ← determined by nature of payment + deductee status
│
▼
THRESHOLD MET? ← annual aggregate per deductee, per section
│
▼
PAN AVAILABLE? ← if not, rate jumps to 20% (Section 206AA)
│
▼
DEDUCT AT SOURCE ← entry passes net of TDS
│
▼
DEPOSIT WITHIN 7 DAYS ← (30 days for March deductions)
│
▼
FILE QUARTERLY RETURN ← 24Q / 26Q / 27Q / 27EQ
│
▼
ISSUE FORM 16 / 16A ← from TRACES, downloadable PDFEvery error in TDS traces back to one of these gates being wrong.
The sections you actually deal with
There are ~70 TDS/TCS sections in the Income Tax Act. For a typical mid-market business, ~12 sections cover 95% of transactions. Know these cold:
| Section | Nature of payment | Threshold (FY 2025-26) | Rate (resident) | Notes |
|---|---|---|---|---|
| 192 | Salary | Slab-based | Slab rate | Computed monthly using estimated annual income |
| 194A | Interest other than securities | ₹40,000 (₹50,000 senior) | 10% | Bank FDs are the most common |
| 194C | Contractor / sub-contractor | ₹30,000 single / ₹1,00,000 aggregate | 1% individual / 2% other | Watch for “transport” exemption with PAN |
| 194H | Commission / brokerage | ₹15,000 | 5% | Common for distributor commissions |
| 194I(a) | Rent of plant/machinery | ₹2,40,000 | 2% | Aggregate per FY |
| 194I(b) | Rent of land/building | ₹2,40,000 | 10% | Aggregate per FY |
| 194J | Professional / technical services | ₹30,000 | 10% (2% for technical) | Most consulting falls here |
| 194Q | Purchase of goods (buyer’s TDS) | ₹50,00,000 aggregate per seller per FY | 0.1% | Applies if turnover > ₹10 cr previous FY |
| 206C(1H) | Sale of goods (seller’s TCS) | ₹50,00,000 aggregate per buyer per FY | 0.1% | Mutually exclusive with 194Q |
| 194R | Benefit / perquisite to business | ₹20,000 per FY | 10% | Watch for sales incentives, gifts |
| 195 | Payment to non-resident | None (every payment) | DTAA rate or 20%/30% | Form 15CA/15CB needed |
| 194O | E-commerce operator on seller payouts | ₹5,00,000 (individual seller) | 0.1% | Marketplace-only |
194Q vs 206C(1H): the most-confused pair. Buyer turnover > ₹10 cr last FY → buyer deducts 194Q, seller does NOT collect 206C(1H). Buyer below the threshold but seller above ₹10 cr last FY → seller collects 206C(1H). They can never both apply on the same transaction.
Where automation actually pays off
TDS is a high-volume, low-judgment problem after the first time you set it up. The pieces that should never be done by hand:
1. Vendor classification
Every vendor master row must carry:
- PAN (validated against the IT department’s PAN search API)
- Tax status, individual / HUF / firm / LLP / company / non-resident / specified person / SEZ / etc.
- Default TDS section, the section that applies most of the time for this vendor (often 194C for contractors, 194J for consultants)
- Default TDS rate, derived from section + tax status
- Lower-deduction certificate (LDC) if any, with start/end dates and rate
- PAN-Aadhaar link status, unlinked PANs are “inoperative” since 1 July 2023 and trigger 20% TDS under 206AA
- TDS exemption certificate if any (e.g., 197 certificate)
If your vendor master doesn’t carry these fields, every bill becomes a judgment call. Get this right once.
2. Section detection at the bill level
When a bill is posted, the system should pick the section automatically:
- Default to the vendor’s default section.
- Allow line-level override (e.g., a contractor who occasionally invoices for design work, 194C for build, 194J for design).
- Auto-detect 194Q applicability based on YTD purchases per vendor.
- Auto-detect 194R applicability for non-cash benefits (free samples, sponsored travel).
- Block 194I bills that don’t carry a property-vs-equipment classification.
3. Threshold tracking
Most TDS sections have annual aggregate thresholds per deductee. The system should:
- Track YTD payments per (vendor × section) automatically.
- Flag the bill that crosses the threshold.
- Apply TDS retrospectively on prior bills (the rule under most sections is that once you cross the threshold, all bills in the FY become deductible).
This is where teams trip, they deduct correctly on the bill that crosses the threshold but forget the catch-up on prior bills.
4. PAN validation and 206AA enforcement
Every vendor PAN must be validated against the Income Tax department’s API. Common return codes:
| Code | Meaning | Action |
|---|---|---|
Existing and Valid | PAN active | Normal rate |
Inoperative | PAN-Aadhaar not linked | Apply 206AA, rate becomes higher of (specified rate × 2) or 20% |
Deleted/Deactivated | PAN cancelled | Treat as no-PAN, 20% under 206AA |
Fake/Bogus | PAN flagged | Halt payment, investigate |
Marked as Specified | Section 206AB applicable | Higher rate (5% or 2× specified) |
Validate monthly, not just at vendor onboarding. A PAN that was operative when you onboarded the vendor can become inoperative the next quarter.
5. Deposit and challan generation
TDS deducted in a month must be deposited by the 7th of the next month (30 April for March). Late deposit attracts:
- Interest at 1.5% per month under Section 201(1A)(ii) from the date of deduction to the date of deposit.
- Disallowance of the underlying expense under Section 40(a)(ia), 30% of the expense disallowed for income tax until the TDS is finally deposited (and the underlying expense becomes deductible only in the year of deposit).
Most teams over-pay interest because they batch by section and forget that one section’s late deposit carries a separate interest computation. The right approach: a single consolidated payment by the 7th, generated as one challan per major section type. Modern banking integrations can post the OLTAS challan directly from the AP system without a TRACES handoff.
6. Quarterly return filing
| Form | Covers | Due date |
|---|---|---|
| 24Q | Salary TDS | 31 Jul (Q1), 31 Oct (Q2), 31 Jan (Q3), 31 May (Q4) |
| 26Q | Non-salary resident TDS | Same as above |
| 27Q | Non-resident TDS | Same |
| 27EQ | TCS | 15 Jul / 15 Oct / 15 Jan / 15 May |
Returns must reconcile exactly with deposit challans (CSI file matching). Mismatches between book TDS, challans deposited, and return entries are the #1 cause of demand notices six months later. A clean system has all three living in the same record.
7. Form 16 / 16A generation
Form 16 (salary, annual) and Form 16A (non-salary, quarterly) are downloaded from TRACES after the corresponding return is processed. The mechanic is: file the return → wait 7–10 days for processing → download from TRACES → distribute to deductees.
Common operational fail: returns get filed but Form 16As never get distributed because someone has to log into TRACES. Vendors then chase, AP scrambles. The fix is to make the TRACES download a scheduled job and the distribution part of an automated email flow.
Two scenarios that catch teams out
Scenario A: 194Q kicks in mid-year
Your turnover crossed ₹10 cr last FY. From 1 April this FY, you are required to deduct TDS under 194Q on every seller you cross ₹50 lakh aggregate purchases with.
The trap: by the time you notice you’ve crossed ₹50 lakh with a particular vendor, you may have already paid them in full multiple times. The correct treatment:
- From the bill that crosses ₹50 lakh, deduct 0.1% on the excess over ₹50 lakh (not on the entire bill).
- From every subsequent bill, deduct 0.1% on the full bill.
- Communicate to the seller, they should stop collecting TCS under 206C(1H) on you, because 194Q overrides.
A good system tracks YTD per vendor and surfaces the threshold-cross bill before posting.
Scenario B: PAN goes inoperative mid-quarter
Vendor’s PAN was operative when you posted bills in April–May. In June, it goes inoperative (Aadhaar not linked).
The treatment depends on the date of credit or payment:
- Bills posted in April–May, paid in April–May: TDS at the normal rate is fine. The PAN was operative at the time of credit/payment.
- Bills posted in April–May but paid in July (after PAN goes inoperative): TDS rate at the time of payment governs, 20% under 206AA.
Most ERPs don’t capture the PAN status at the right point. The capture must happen at posting AND at payment, with the higher rate prevailing.
Common errors and how to prevent them
| Error | Frequency | Prevention |
|---|---|---|
| Wrong section picked for the payment type | High | Vendor-level default section + line-level override + a section-detection rule engine |
| TDS not deducted on advance (only on bill) | High | Trigger TDS on whichever event (advance, bill, payment, journal) comes first |
| Late deposit interest | Medium | Calendar-driven cron job, deposit by 7th regardless of internal sign-off |
| 26Q mismatch with challan | High | Single source of truth, books, challan, return all from one system |
| PAN-Aadhaar inoperative not enforced | High | Monthly PAN validation, blocking gate at payment |
| Form 16A not distributed | Medium | Scheduled TRACES download, automated email |
| 194R missed on non-cash benefits | Medium | Tag every “marketing expense” / “incentive” as 194R-eligible at COA level |
| TDS under wrong PAN of group | Low but expensive | Vendor master gates PAN selection per legal entity |
The CFO dashboard, what to watch
A finance leader running a TDS function should see, weekly:
- Late deposit aging, deductions sitting in the books past their deposit date. Should always be zero.
- Mismatch buckets, bills posted without TDS where TDS was due, and vice versa.
- PAN inoperative count, vendors needing PAN remediation.
- Threshold-watch list, vendors approaching 194Q/194C/194J thresholds.
- Form 16A distribution, quarter-on-quarter, % distributed within 15 days of filing.
If your monthly close has surprises, one of these dashboards is broken.
Tooling: what to look for
- TRACES integration, automatic CSI download, 16A download, demand-notice ingestion.
- OLTAS integration, direct challan generation from the system, no manual portal entry.
- PAN API integration, bulk validate every PAN monthly.
- Section rule engine, codified rules for every section, with thresholds, rates, and PAN-rule overlays.
- Books-of-account synchronisation, TDS payable, deposit, and Form 26AS reconciliation in one record.
- 24Q wage-master integration, for salary TDS, the system must compute monthly slab-rate TDS using each employee’s estimated annual income and exemption declarations.
OneFinOps does this on one record, bills, TDS, deposits, returns, Form 16/16A, so TDS isn’t a separate workflow tied together with spreadsheets. Start a free trial or book a 30-min walkthrough.
Frequently asked questions
Do I deduct TDS on advances or only on bills?
On the earlier of credit or payment, whichever comes first. If you advance ₹5 lakh to a contractor in April and the bill comes in June, TDS is deductible on the advance in April, with the deposit due by 7 May.
What if the vendor refuses to share their PAN?
Apply Section 206AA, the rate becomes the higher of (specified rate) or 20%. Most teams default to a flat 20% for no-PAN cases. Document the no-PAN evidence; the IT department occasionally questions 206AA application during scrutiny.
Can I claim TDS deducted by a customer on me?
Yes, that customer’s 26Q reports your TDS, which appears in your Form 26AS. You claim it as advance tax in your annual return (ITR). If 26AS doesn’t reflect what the customer says they deducted, raise a 26Q correction with the customer; you can’t claim TDS that 26AS doesn’t show.
What’s the penalty for late filing of 24Q/26Q?
₹200 per day under Section 234E until filing. Plus, the IT department can disallow the underlying expense under Section 40(a)(ia), 30% added back to taxable income, taxed at the company rate, which dwarfs the ₹200/day. Don’t be late.
Can TDS be revised after filing?
Yes. File a correction return (24Q-C, 26Q-C, etc.) with the corrected statement. The original challan-statement linkage matters, make sure the corrected return references the right challans. Most teams over-correct; the right discipline is to rerun reconciliation, identify only the affected rows, and file a targeted correction.
Does GST charged on professional fees attract TDS?
Yes, on the net of GST value. If the consultant invoices ₹1 lakh + ₹18,000 GST, TDS under 194J is on ₹1 lakh, not ₹1.18 lakh. Same logic for 194C, 194H, 194I. (Confirmed via CBDT Circular 23/2017.)
Sources
- Income Tax Act, 1961, Sections 192–206C, full TDS/TCS section catalog.
- CBDT Circular No. 23/2017, TDS on GST component of services.
- TRACES Portal, return processing, Form 16/16A, demand reconciliation.
- OLTAS Challan e-Payment, direct deposit gateway.
- PAN-Aadhaar Inoperative, CBDT Notification (Mar 2023), Section 139AA implications.
- Section 194Q vs 206C(1H), CBDT Circular No. 13/2021.
This guide is operational, not legal advice. Cross-border TDS (Section 195), 194R determinations, and 206AB lookups should be reviewed by your tax counsel.
Tags
- TDS automation
- Section 194Q
- Section 206C(1H)
- Form 26Q
- Form 24Q
- Form 16A
- TDS deduction rules
- TRACES filing