Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Companies buy TDS software without deciding whether their problem is deductor-side compliance or deductee-side credit recovery, and end up with a tool for the wrong side.
Map symptoms to the side: default notices and challan mismatches point to the deductor side; missing credit and a receivable above the portal figure point to the deductee side.
A decision table listing need, tool category, data read, owner and the questions that separate the categories.
A clear statement of which side or sides you are buying for, with owners named and the right test data prepared.
TDS reconciliation is two jobs that share a name. Deductor-side work checks what you deducted, deposited and filed on payments you made. Deductee-side work checks what your customers deducted from payments to you against Form 26AS, or Form 168 from tax year 2026-27. Decide which problem you have before you look at any tool.
For the processes behind each side, see TDS quarterly filing reconciliation (deductor side) and multi-deductor TDS reconciliation (deductee side).
Which side is your problem?
| Symptom | Side | What it usually means |
|---|---|---|
| Short-deduction or short-payment default from TRACES | Deductor | Rate, code or PAN errors in what you deducted or reported |
| Late-filing fee under Section 234E (₹200 per day under the 1961 Act) | Deductor | Quarterly statement filed late |
| Interest demand under Section 201(1A) | Deductor | TDS not deducted (1 percent a month) or deducted but deposited late (1.5 percent a month) |
| Challan not matching the return | Deductor | Wrong challan details or payment code |
| Credit missing in Form 168 or Form 26AS | Deductee | Customer has not filed, quoted the wrong PAN or reported in another quarter |
| TDS receivable above the portal figure | Deductee | Unrecovered credits building up |
| Invoice looks short-paid by exactly 2 percent or 10 percent | Deductee | Customer deducted TDS and paid net |
If most of your pain is in the first four rows, you need a deductor-side tool, and your ERP may already be close. If it is in the last three, you need deductee-side reconciliation.
What does your ERP’s TDS module already do?
Check four things in your current system:
- Deduction at posting. Does the vendor master carry the right section, or payment code from April 2026 (for example code 1023 or 1024 for Section 194C contractors, code 1006 for Section 194H commission at 2 percent)?
- Challan linking. Can each deduction be tied to its challan?
- Return preparation. Can it produce the quarterly statement file?
- External statement and bank. What does it do with a downloaded credit statement, and with a bank receipt that arrives net of TDS?
Most ERPs answer yes to the first three and no to the fourth. The fourth is the deductee side.
How do the tool categories differ?
| Need | Tool category | Data it reads | Owner | Question that separates them |
|---|---|---|---|---|
| Correct deduction and filing | Deductor-side compliance tool or ERP module | Payables ledger, challans, return status | Tax team | Does it validate PAN, code and rate before the return is filed? |
| Recover TDS credit | Deductee-side reconciliation tool | Form 26AS or Form 168, AIS, TDS receivable ledger, bank receipts | Receivables or finance operations | Does it give a reason for every credit gap and track follow-up? |
| Both | Two tools, or one tool tested twice | All of the above | Both teams | Can you show me each side on my own data, separately? |
What does a company with both problems look like?
Illustrative example: a services company pays ₹12,00,000 a quarter to contractors and deducts ₹24,000 at 2 percent under Section 194C. In the same quarter it bills customers ₹80,00,000 for professional services, and its customers deduct ₹8,00,000 at 10 percent under Section 194J.
- Deductor side (tax team): did the ₹24,000 go out by challan by the due date, under the right code, and appear in the return? Error cost: interest and fees on you.
- Deductee side (receivables team): does the ₹8,00,000 appear in your credit statement, deductor by deductor? Error cost: credit you cannot claim, which is lost cash.
The deductee-side amount is more than 30 times the deductor-side amount here, which is common for service businesses. The owners, files and month-end tasks are different, so test them separately. The TDS reconciliation runbook shows how both fit into one calendar.
What should you ask before shortlisting either kind of tool?
For a deductor-side tool:
- Does it check the rate against the transaction date, for example Section 194H at 5 percent before 1 October 2024 and 2 percent after?
- Does it apply the Section 194-I rent threshold of ₹50,000 per month or part of a month from 1 April 2025?
- Does it still treat Section 206AB as live? It was omitted from 1 April 2025, so a tool applying the higher non-filer rate today is out of date.
- Can it validate PAN and payment code before the quarterly statement is filed?
For a deductee-side tool:
- Does it load both Form 26AS (for periods up to 31 March 2026) and Form 168?
- Does it link bank receipts that arrive net of TDS to the invoice and the credit line? See the net-of-TDS matching test.
- Does every credit gap get a reason and a follow-up owner?
If one vendor claims both, run both sets of questions with separate data and separate owners in the room. The buyer’s checklist has the full deductee-side scoring table.
How Terra Insight fits
The documented TransactIG TDS reconciliation workflow is deductee side: Form 26AS, Form 168 and AIS against your TDS receivable ledger, with an exception queue and audit-ready exports. If you also have a payables-side need, raise it in discovery. For credit gaps, start with the Form 168 shortfall investigation guide.