Four-check deterministic matching of TRACES Form 26AS against the TDS receivable ledger — Form 26AS TDS reconciliation in under 30 seconds per quarter.
| Deductor Name | TAN | Section | TDS (Rs) |
|---|---|---|---|
| Acme Retail Pvt Ltd | DLAC00012E | 194J | 25,000 |
| Acme Logistics Hub | MHAC00091F | 194C | 8,400 |
| Acme Bank Ltd | BNAC00044G | 194I | 30,000 |
| Acme Corp Ltd | KRAC00077H | 194J | 18,000 |
For every mid-market company in India, reconciling Form 26AS against the TDS receivable books register is a mandatory quarterly exercise that routinely consumes two to three working days of controller time in a spreadsheet with no audit trail.
The TRACES portal delivers Form 26AS as a structured XLSX by TAN, section, and quarter — but that structure never maps cleanly onto an internal books register built from invoices and journal entries. A controller must manually sort both files, build a composite key, compute row-level variances, and triage each difference. At 80–150 active deductors, that process takes 2–3 working days before each quarterly filing deadline.
Amount variances, section-code mismatches (e.g., the deductor filed 194C while the books show 194J), quarter-lag deposits, and unilateral entries — entries in 26AS with no books counterpart or in books with no 26AS counterpart — each require a different remediation path. A flat spreadsheet treats all four identically: uncoloured discrepancy rows that must be triaged by hand, one by one.
Section 199 of the Income Tax Act, 1961 restricts TDS credit to amounts that actually appear in the taxpayer's Form 26AS. If a deductor has deducted tax but not deposited it, or has filed the wrong section code, the credit is denied until the deductor corrects the statement under Section 200A. A company that skips the reconciliation and claims credit based on its books alone risks a CPC demand notice under Section 143(1).
The spreadsheet reconciliation produces a file that exists on a controller's desktop. There is no immutable record of which version of the 26AS extract was used, which matching logic was applied, or which exceptions were cleared and by whom. When the tax audit begins under Section 44AB, the controller must reconstruct the quarter's reconciliation from memory and disconnected email threads.
The median TDS credit at risk for a mid-market company with 100 active deductors when the quarterly reconciliation is skipped or incomplete. Each uncorrected discrepancy becomes a disallowed credit under Section 199 of the Income Tax Act, 1961, resulting in a CPC demand under Section 143(1) with interest under Section 234B or 234C until a rectification under Section 154 is resolved — a process that typically takes six to twelve months.
Form 26AS reconciliation sits at the intersection of four distinct statutory provisions. Getting any one wrong cascades into disallowed credits, demand notices, and a protracted rectification process that can drag across multiple assessment years.
TDS credit is granted to the deductee only to the extent the deducted amount appears in Form 26AS. Even if the deductor has genuinely withheld and deposited tax, a filing error under the wrong section or quarter means the credit does not flow through until Form 26AS is corrected. This makes the reconciliation a prerequisite for every ITR filing where TDS receivables are material.
When a deductor files TDS under the wrong section code, quotes an incorrect TAN, or deposits the tax in the wrong quarter, the deductee cannot unilaterally correct Form 26AS — only the deductor can file a correction statement under Section 200A. Identifying the discrepancy class (section mismatch vs. quarter lag vs. source-only) determines which party must act and by when.
Form 26AS is maintained by the Income Tax Department and made accessible through the TRACES (TDS Reconciliation Analysis and Correction Enabling System) portal under Rule 31AB. The download format — organised by deductor TAN, section code, quarter, and TDS amount — is the exact structure Cadel's reconciliation engine consumes. Since FY 2020-21, the Annual Information Statement (AIS) supplements 26AS, but Part A of Form 26AS remains controlling for TDS credit.
When the Centralised Processing Centre processes an ITR under Section 143(1), it cross-checks the TDS credit claimed on the return against the amounts in Form 26AS. Any excess credit claimed — whether due to a section mismatch, a books-only entry, or a timing difference — is automatically disallowed. The resulting demand carries interest under Sections 234B and 234C, compounding until a rectification under Section 154 is accepted.
For companies with 50 to 500 active deductors spanning Sections 194J (professional fees), 194C (contractor payments), 194H (commission), and 194I (rent), the quarterly reconciliation burden is heaviest relative to the finance team size — and the CBDT's AIS Feedback mechanism (Notification No. 16/2021) adds a fourth action path that requires identifying the discrepancy type before a response can be submitted.
Seven deterministic passes from two uploaded Excel files to a fully categorised, audit-ready reconciliation table — in under 30 seconds per quarter per entity.
Accepts two uploaded XLSX files — the Form 26AS extract downloaded from TRACES and the TDS-receivable books register exported from Tally Prime, Zoho Books, or SAP — and classifies each automatically without requiring the user to tag which is which. Parses every data row from both, including multi-section and multi-quarter entries.
Constructs a three-part match key for every row in both files: deductor/customer TAN + TDS section code + quarter label (e.g., DLAC00012E | 194J | Q4-FY26). Rows that share all three key fields are paired for validation; rows with no partner on either side are immediately flagged as unmatched exceptions before any validation logic runs.
For every matched pair, verifies that the deductor TAN in Form 26AS matches the customer TAN in the books register character-for-character. A TAN mismatch is a hard FAIL — the two rows cannot refer to the same underlying transaction and must be investigated before any credit is claimed under Section 199 of the Income Tax Act.
Compares the TDS section reported in Form 26AS against the section coded in the books register. Mismatches (e.g., 194J on 26AS vs. 194C in books) return a hard FAIL with both section codes displayed side-by-side, allowing the controller to determine whether the deductor filed the wrong section or an internal coding error occurred in the accounts receivable entry.
Computes the absolute difference between the TDS deducted amount in Form 26AS and the TDS certified amount in the books register. Any difference greater than Rs 1 returns a FAIL with the delta amount shown. The Rs 1 threshold matches the rounding that deductors apply when computing TDS under Sections 194J, 194C, 194I, and 194H, and is configurable at the workflow level for organisations with different tolerance policies.
Verifies that the quarter in which the deductor deposited the TDS (Form 26AS) matches the quarter in which the books recognised the receivable. A one-quarter lag — where the deductor deposited in Q1-FY27 what the books accrued in Q4-FY26 — returns a WARNING rather than a FAIL, consistent with the CBDT's position under Circular No. 275/201/95-IT(B) that credit is allowable in the year of deduction regardless of the deductor's late deposit.
Produces three output artifacts: (a) the row-level reconciliation table with each row colour-coded by status (Reconciled, Amount Mismatch, Section Mismatch, 26AS-Only, Books-Only, Quarter Warning) and stamped with the four check results; (b) a Section 199 credit summary showing total TDS in 26AS, total in books, net variance, and count of each exception class; and (c) a working paper formatted for direct inclusion in the tax audit file under Section 44AB and the statutory auditor's workpapers.
The workflow ships with a battery of synthetic test scenarios that exercise every failure mode seen in real-world quarterly reconciliations. Each scenario produces a deterministic outcome an auditor or controller can verify in seconds.
DLAC00012E), section (194J), quarter (Q4-FY26), and TDS amount (Rs 25,000).The workflow ships with two seeded sample files for Q4 FY2025-26 for Acme Corp Pvt Ltd. Both files describe the same set of deductor relationships and share the composite match key (TAN + section + quarter) — most rows reconcile end-to-end while a handful deliberately plant each exception class. Upload both together to see the full reconciliation.
Columns: Deductor Name, TAN, Section, Quarter, Amount Paid, TDS Deducted, Deposit Date. One row per deductor who filed TDS against Acme Corp's PAN for the quarter. Includes one planted 26AS-only row and one section-mismatch row.
Columns: Customer Name, TAN, Section, Quarter, Invoice Amount, TDS Certified, Invoice Date. 46 rows covering the same deductor set as the 26AS extract, with one additional books-only row (the customer never deposited) and one amount-mismatch row to exercise all exception classes.
Uploaded together, the two sample files produce a single reconciliation across 45–46 customer/deductor relationships for Q4 FY2025-26. Most rows reconcile cleanly on TAN + section + quarter with the TDS amount within the Rs 1 tolerance. The remaining rows plant exactly the five exception classes the workflow is built to catch.
Forty rows across Sections 194J, 194C, 194H, and 194I where Acme Corp Pvt Ltd's books and the TRACES Form 26AS agree on all four check dimensions. The aggregate Rs 9.4 lakh is immediately available as a Section 199 TDS credit with no further action required before ITR filing.
The most operationally significant exception is the 26AS-only row: Rs 18,000 of Section 199 credit sitting in Form 26AS that Acme Corp's books never accrued — found money that would be left unclaimed without automated detection. The books-only row (Rs 12,400) requires a Section 200A correction by the deductor before any credit can be claimed.
A quarterly Form 26AS reconciliation that takes a controller 2–3 working days in a spreadsheet — sorting, key-building, formula-writing, and exception triage across four exception classes — completes in under 30 seconds on Cadel, with a zero-miss rate on all five exception classes and a fully audit-ready output artifact attached.
The most common source of unclaimed TDS credit is a 26AS entry for which no books entry exists — the company was never aware the customer had deposited. Cadel surfaces every source-only row before ITR filing, ensuring the full credit available under Section 199 is identified and booked with the correct journal entry before the return is filed.
Each of the five exception classes requires a different action: Section 200A correction for books-only rows, a journal entry for source-only rows, a deductor enquiry for section mismatches, and a tolerance review for amount deltas. Cadel labels each row with the precise exception class and the remediation path, eliminating the manual triage step that consumes most of the 2-day manual process.
The output working paper carries the run timestamp, source file names, Form 26AS Part A parameters (PAN, quarter, assessment year), and the per-row check results in a format consistent with ICAI guidance on documentation standards and directly attachable to the Section 44AB tax audit file. The statutory auditor receives a structured artifact, not a manually annotated printout that cannot be independently reproduced.
The questions tax controllers, chartered accountants, and finance teams ask most often before deploying Form 26AS TDS reconciliation automation.
Two files for one quarter — the Form 26AS extract downloaded from the TRACES portal, and your TDS-receivable books register (the ledger of TDS your customers were expected to deduct on the invoices you raised). Both are structured Excel files; drop them together and Cadel classifies each automatically.
Every Form 26AS row is matched to its books counterpart on a composite key of deductor/customer TAN + TDS section + quarter. Rows that share all three keys are paired and run through the validation checks; rows with no partner on either side become unmatched exceptions — either a 26AS-only credit to book or a books-only receivable to chase.
Section 199 of the Income Tax Act, 1961 grants TDS credit only to the extent the amount appears in Form 26AS. If a customer deducts tax but deposits it under the wrong TAN, section, or quarter — or never deposits it — the credit is denied until the statement is corrected under Section 200A. Claiming credit on your books alone invites a demand notice from the Centralised Processing Centre when the return is processed under Section 143(1), with interest accruing under Section 234B or 234C until a rectification under Section 154 is accepted.
Five. Amount mismatch (TDS differs by more than Rs 1 between the two sides), section mismatch (booked under 194J but filed under 194C, or similar), quarter lag (the deductor deposited a quarter later than the books recognised the receivable — a WARNING, not a hard fail), source-only (in Form 26AS but never accrued in the books), and target-only (accrued in the books but the customer never deposited it). Each class surfaces with the relevant TAN, section, and amount so the controller knows exactly which party must act.
The default tolerance is Rs 1, matching the rounding deductors apply when computing TDS under Sections 194J, 194C, 194I, and 194H. Any difference greater than Rs 1 trips a FAIL on the amount-within-tolerance check. The threshold is a workflow-level setting your Cadel administrator can adjust if your organisation reconciles to a different rounding policy.
When Form 26AS shows the TDS deposited in a different quarter from the one in which the books recognised the receivable, the quarter check returns WARNING rather than FAIL. This reflects the position that the deductee is entitled to credit in the year of deduction regardless of the deductor's late deposit, per CBDT Circular No. 275/201/95-IT(B). The row still appears in the exception queue so you can confirm the credit year before filing — it is not silently cleared.
The books register is a structured Excel file (customer name, TAN, section, quarter, invoice amount, TDS certified, invoice date) — a layout you can export directly from Tally Prime's TDS report, Zoho Books' TDS summary, or a SAP custom query. No API connector is required: export the register, upload it alongside the TRACES Form 26AS extract, and Cadel parses both automatically.
No. Your documents are processed only to produce this workflow's reconciliation results and are never used to train any model. Each run is isolated to your organisation's data environment.