Automating TDS Reconciliation: What the Process Looks Like End-to-End

An IT services company with 75 active clients — each potentially deducting TDS under a different section across multiple quarters — has a Form 26AS that can run to 300 to 400 entries per financial year. Manual reconciliation of that volume against the TDS receivable ledger is not simply tedious; it is systematically incomplete. Entries that fall across quarters, deductors who file under the wrong section, and net-of-TDS bank receipts that need three-way matching all require logic that a spreadsheet cannot reliably apply at scale. Automating TDS reconciliation in India is about applying consistent matching logic across all three data sources — TRACES, the ERP ledger, and the bank statement — rather than relying on analyst judgment for each row.

What TDS Reconciliation Actually Involves

TDS reconciliation for an Indian company that receives payments net of TDS is a three-way matching exercise, not a two-way match. The sources are:

• Form 26AS / TRACES: shows TDS credited against the company’s PAN by each deductor, by section and quarter
• TDS receivable ledger (ERP): shows TDS amounts booked as receivable when invoices are raised, by client and section
• Bank statement: shows the net receipt — the payment received after the client deducted TDS

All three must reconcile for each invoice. A bank receipt of ₹90,000 against an invoice of ₹1,00,000 (TDS 10% = ₹10,000) is only fully reconciled when the ₹10,000 appears in Form 26AS against the correct TAN, section, and quarter. If any leg is missing, the entry remains open.

For Indian finance teams, this is more complex than the textbook description for two reasons. First, TRACES data is quarterly and retrospective — it reflects what deductors have filed, not what has been deducted at invoice level. Second, the mismatch types are India-specific: cross-quarter credits caused by deposit timing, Section 197 lower-deduction certificates that clients have but vendors have not provided, and multi-TAN deductors who split payments across state registrations.

Where Manual TDS Reconciliation Breaks

Mismatch Type 1: Cross-Quarter TDS Credits

TDS deducted in March (Q4) must be deposited by 30 April. A deductor who deposits in April files it under Q4. But if the deductor files their quarterly TDS return late — after the July 31 filing deadline — the credit may appear in Form 26AS for the next quarter. Finance teams doing quarter-by-quarter reconciliation will mark these as open mismatches until the deductor files. Without tracking the “expected but not yet appearing” category, the open mismatch list becomes misleading.

Mismatch Type 2: Wrong Section Filing

A client deducts TDS under Section 194C (contractor, 2%) on a payment that should have been under Section 194J (professional services, 10%). The amount deducted is lower than required. In Form 26AS, the entry appears under 194C. The vendor’s ledger has the invoice booked as 194J receivable. The two do not match on section. The vendor must pursue the client for a short-deduction correction return and may need to reverse the 194J receivable and rebook under 194C in their books.

Mismatch Type 3: Multi-TAN Deductors

Large Indian corporate clients — banks, FMCG companies, infrastructure groups — often have separate TAN registrations for each state or business division. A vendor dealing with HDFC Bank may receive payments from HDFC’s Mumbai TAN, HDFC’s Bengaluru TAN, and HDFC’s processing subsidiary TAN — three separate TAN entries in Form 26AS, all attributable to the same economic client. Manual reconciliation requires the analyst to know which TAN belongs to which client entity. Without a TAN master maintained against client records, this creates unmapped mismatches.

Mismatch Type 4: Section 197 Lower-Deduction Certificates

A vendor who has obtained a lower-deduction or nil-deduction certificate under Section 197 must share it with all deductors. If the certificate is issued in October and a client in November deducts at the standard rate because they did not receive the certificate, Form 26AS will show a higher TDS credit than the vendor’s books reflect as receivable (based on the nil-deduction expectation). The correction requires the vendor to ask the client to file a revised TDS return citing the Section 197 certificate.

The Automated TDS Reconciliation Process: Step by Step

Step 1: Structured Data Ingestion from Three Sources

The starting point is structured ingestion of all three data sources in a consistent format. Form 26AS is downloaded from TRACES in XML format and parsed into rows by: PAN, deductor name, TAN, TDS section, amount, quarter, and deposit date. The TDS receivable ledger is exported from the ERP — typically as a CSV or Excel file — with fields for client name, TAN (if captured at invoice level), section, invoice amount, TDS amount, and invoice date. Bank statement data is ingested in the standard format: date, narration, credit amount.

The narration field in Indian bank statements often carries reference information that identifies the deductor — particularly for NEFT/RTGS payments where the remitter name and UTR appear in the narration. This narration data is used to link the bank credit to the specific client.

Step 2: TAN-to-Client Master Mapping

Before matching can begin, the platform builds a TAN master: a mapping of every TAN that has appeared in Form 26AS to the corresponding client entity in the company’s books. This handles the multi-TAN problem — all TANs belonging to HDFC are mapped to “HDFC Bank” in the client master, allowing the system to aggregate TDS from multiple TANs against a single client’s receivables.

For new TANs appearing in Form 26AS for the first time (a new division or subsidiary of an existing client), the system flags these for manual mapping before the match run.

Step 3: Section-Level, Quarter-Level Matching

The core match runs at three levels simultaneously:

1. TAN + Section + Quarter: the primary match. A Form 26AS entry for TAN MUMB01234A, Section 194J, Q2 FY26, ₹25,000 is matched against the TDS receivable ledger entry for the same client, section, quarter, and amount.
2. Net-of-TDS bank receipt matching: the ₹2,25,000 bank receipt is linked to the ₹2,50,000 invoice (TDS 10% = ₹25,000) as a three-way match. This confirms the full transaction — invoice raised, payment received net of TDS, TDS appearing in Form 26AS.
3. Cross-quarter tolerance: entries where the Form 26AS credit is in Q3 but the ledger entry is in Q2 are flagged as “timing mismatch” rather than “open mismatch” — preserving the distinction between a deposit timing issue and a genuine short-deduction.

Step 4: Mismatch Classification and Exception Report

Every unmatched entry is classified by mismatch type rather than left as a generic open item. The exception report produced at the end of the match run shows:

This classification is what transforms TDS reconciliation from a 4-day exercise into a 2-to-4-hour exception review. Finance teams work from a structured list of specific actions rather than an undifferentiated pile of mismatches.

Step 5: Correction Tracking and Ledger Update

Mismatches that require deductor action — short deduction, wrong section, PAN error — are tracked through a correction pipeline. The system records: which deductor needs to file a correction, what the correction should reflect, when it was requested, and which quarter’s Form 26AS to monitor for the correction to appear. Once the Form 26AS is updated, the previously open entry is automatically matched and closed.

What This Looks Like for Indian Finance Teams Specifically

The India-specific complexity in TDS reconciliation does not appear in generic reconciliation guides. Three elements are structurally different:

Net-of-TDS receipts require three-way matching. Most payment reconciliation guides treat bank receipt matching as a two-way match: bank credit against invoice. For TDS-deducted payments, the match requires a third leg — Form 26AS — before the receivable can be closed. Finance teams that close invoices on net receipt without confirming Form 26AS credit are carrying phantom receivables.

TRACES is the authoritative source, not the deductor’s communication. A client may email a TDS certificate or inform the vendor of TDS deducted. Until the entry appears in Form 26AS (via the deductor filing their quarterly return and TRACES processing it), the TDS credit cannot be claimed. Automation that treats TRACES as the primary source — not client communications — produces a more accurate receivable position.

Quarter-end timing is a structural mismatch risk. The TDS deposit deadline for Q3 (October–December) is 7 January. A deductor who deposits on 8 January technically files in Q3 but may appear in TRACES in Q4 depending on bank processing. Finance teams closing Q3 books on 15 January face a structural timing gap. Automated reconciliation tracks these as timing mismatches rather than write-offs.

What Automation Changes for a Finance Team

TransactIG’s TDS reconciliation module handles the net-of-TDS three-way match natively — linking the bank receipt, the Form 26AS entry, and the original invoice in a single match rather than requiring the analyst to triangulate across three exports. Organisations that have deployed automated TDS matching have seen match rates move from the 51% range (manual, with systematic cross-quarter and multi-TAN gaps) to 88% in the first full quarter of operation, with the remaining exceptions pre-classified and actionable rather than requiring fresh analysis.

The integration points are three structured file uploads: Form 26AS XML from TRACES, TDS receivable ledger export from the ERP, and bank statement in standard format. No direct TRACES API connection is required — the file upload workflow fits the standard TRACES download process Indian finance teams already use.

For organisations evaluating TDS reconciliation software for the first time, the key question is whether the tool handles net-of-TDS matching or only matches Form 26AS against the ledger without the bank leg. Without the bank statement match, the three-way reconciliation remains incomplete.

Finance teams building the business case for automation can use the framework in our guide to reconciliation software India organisations use to quantify the cost of manual reconciliation versus structured tooling.

The Income Tax India e-filing portal provides TRACES access for Form 26AS downloads and the TDS certificate portal — the primary data sources for the automated match.

Common questions about the TDS reconciliation process, mismatch causes, and integration options are answered below.