Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Finance teams compare TDS reconciliation tools on feature counts and miss whether the tool explains gaps between the credit statement and the TDS receivable ledger.
Score each tool on five tests: inputs it reads, matching keys, gap explanation, follow-up recording and exports, each marked must-have, useful or not needed for your deductor mix.
A decision table with a good answer, a weak answer, the evidence to request and a deal-breaker column signed off by the finance head before shortlisting.
A shortlist of tools that pass all must-have tests on your own closed-quarter data, with demo evidence filed for procurement.
The best TDS reconciliation software is not the one with the longest feature list. It is the one that passes five tests on your own data: what it reads, how it matches, how it explains gaps, what it records for follow-up and what it exports. Score each test as must-have, useful or not needed for your deductor mix, and drop any tool that fails a must-have.
For background on the process itself, read automating TDS reconciliation and the common Form 26AS reconciliation failure modes. This page is the buying checklist.
What should the tool read?
Four inputs, at minimum:
- The credit statement. Form 26AS for deductions up to 31 March 2026 and Form 168 for tax year 2026-27 onward, under the Income-tax Act, 2025, where non-salary TDS is consolidated in Section 393.
- The Annual Information Statement (AIS), where your team uses it to cross-check reported receipts.
- The TDS receivable ledger from your ERP, at invoice level, not a monthly summary.
- Bank receipts, because customers pay net of TDS.
Ask the vendor how each file enters (upload, scheduled pull, export) and what happens when your ERP adds a column. If the answer is “we will change the parser”, you depend on the vendor for every ERP upgrade.
How should it match and explain?
A credible match uses PAN, deductor TAN, section or payment code and quarter together. Section 194J professional fees at 10 percent map to payment code 1027; Section 194C contractor payments at 1 percent or 2 percent map to codes 1023 and 1024; Section 194H commission at 2 percent maps to code 1006. A tool should hold both labels on the same receivable.
More important than the match is the explanation. Every unmatched line should carry a reason: deductor has not filed, credit shown in a later quarter, wrong PAN quoted, amount lower than books, or no deduction recorded. One open balance per customer is a weak answer. Cross-era handling and the net-of-TDS bank leg are big enough to test separately; see the cross-era test script and the net-of-TDS matching test.
What does the decision table look like?
| Test | What to give the vendor | What a pass looks like | Weak answer | Deal-breaker? |
|---|---|---|---|---|
| Reads inputs | One quarter of Form 168 or 26AS, AIS extract, receivable ledger, bank statement | All four load without manual reformatting; row counts shown | ”Send us a cleaned Excel” | Finance head decides |
| Matches on keys | Ledger with PAN, TAN, section and quarter | Matches use all keys; old section and payment code on one line | Match on amount only | Yes |
| Explains gaps | Five lines you know are unmatched and why | Each carries the same reason your team found | ”Unmatched” with no reason | Yes |
| Records follow-up | One deductor you chased last quarter | Status, owner and date stored against the line | Notes kept in email | Useful |
| Exports evidence | Ask for the auditor pack for one deductor | Credit line, invoice, bank credit, chase log and sign-off in one export | Screenshot or PDF of a screen | Yes for audited entities |
Ask for evidence, not slides: the screen, the export file and the sample file you supplied, kept together for procurement.
How does a worked example expose a weak tool?
Illustrative case: a customer deducts ₹24,600 TDS (10 percent) on a ₹2,46,000 invoice and pays ₹2,21,400.
- Read. The ledger shows ₹2,46,000 receivable; the bank shows ₹2,21,400; Form 168 shows nothing yet because the customer has not filed its quarterly statement.
- Match. A good tool links the ₹2,21,400 credit to the invoice and parks ₹24,600 as TDS receivable awaiting credit. A weak tool marks the invoice short-paid by ₹24,600.
- Explain. The reason should read “deductor return not yet reflected”, not “unmatched”.
- Record. The line moves to follow-up with an owner and a review date after the deductor’s filing due date.
- Export. When the credit appears a quarter later, the export shows the original invoice, bank credit, credit line and closure date.
Most weak tools stop at step 2. That one error, repeated across a few hundred invoices a quarter, is how TDS receivable balances drift from the portal figure.
How should you score the shortlist?
Mark each test as must-have, useful or not needed. A company with five large deductors that file on time may treat follow-up recording as useful. A services firm with 300 customers deducting under several sections should treat all five as must-have. Run the same closed quarter through every shortlisted tool, then compare exception lists line by line. The pilot guide shows how to set that up with an answer key.
What questions separate a strong vendor from a weak one?
Ask these in the first call, before any demo is scheduled:
- Which credit statement formats do you load today? Form 26AS and Form 168 both, with the old-era and new-era lines on one receivable.
- How do you show quarter drift? A credit reported in a later quarter should be a labelled timing item, not an open mismatch.
- What happens to a receivable paid net of TDS before the credit appears? The cash part should match and the TDS part should wait for credit.
- How do you handle a lower-deduction certificate? The expected rate should be a setting per customer, so a 2 percent certificate does not show as an 8 percent short payment against a 10 percent standard rate.
- How are rule changes delivered? Ask for the change log for 1 April 2026; the rule-change questions go deeper.
- What does an export for one deductor contain? The answer should match your auditor’s request list; see the TDS credit evidence file.
A vendor that answers with a screen and a file on your own data is worth a pilot. A vendor that answers with a roadmap slide for any must-have test is not, for now.
How Terra Insight fits
TransactIG’s TDS reconciliation matches Form 26AS, Form 168 and AIS against your TDS receivable ledger, routes every gap to an exception queue with a reason and produces audit-ready exports. It covers the receivable side. We offer a representative-sample fit benchmark on your data; pricing is discussed in discovery.