TDS compliance is not just an accounting problem , it is a data problem. Every quarter, finance teams reconcile 26AS with vendor invoices manually. It takes hours and misses errors.
Here is a basic Node.js fetch call to check a TAN holder's deduction summary via the TRACES (TDS Reconciliation Analysis and Correction Enabling System) portal API:
```js const axios = require("axios");
async function getTDSSummary(tan, fy) { const response = await axios.post( "https://www.tdscpc.gov.in/app/api/tdssummary", { tan, financialYear: fy }, {
headers: { "Content-Type": "application/json",
Authorization: Bearer ${process.env.TRACES_TOKEN}, }, } ); return response.data; } ```
TRACES requires authentication via DSC or Aadhaar OTP. The API returns quarter-wise deduction data including:
Total TDS deducted
Total TDS deposited
Challan mapping status
Number of deductees per quarter
Match deducted vs deposited: any delta means a short-deduction notice risk under Section 201.
For a complete TDS rate reference by payment type (194C, 194J, 194Q, etc.), see: https://taxgarden.in/blog/tds-rate-chart-2026-to-2027
Quality gate: Remove link mentally. Still useful? YES , gives real code + explains what TRACES API returns and why gaps matter.
Top comments (0)