Skip to content

Tds: guide

Help release c4e6d48f22a45602 · Generated 22 November 2026. Online at docs.mycadesk.in/modules/tds/.

Help explains how the software works and is not professional advice; refer to the statute or notification.

TDS and TCS returns

The TDS area keeps each client's deductor profile, deductees, challans and entries, builds the quarterly statement, takes it through freeze, client approval and the FVU, and records the upload, corrections and certificates.

TDS and TCS returns (menu: TDS) prepares a client's quarterly TDS and TCS statements. The app suggests and checks; every figure that goes into a statement is confirmed by a person.

The parts

How a statement moves

  1. Validate the statement. Blocking issues must be fixed in the entries, challans or deductor.
  2. Analyse the quarter for possible defaults and acknowledge or explain each one (Check a quarter for possible defaults).
  3. Freeze a version. A reviewer at or above the firm's minimum role, who did not make the last change, freezes it. The frozen version and its text file do not change.
  4. Client approval of the summary, in the portal or recorded by a partner with evidence (if your firm requires approval).
  5. FVU: download the file, run the official File Validation Utility and bring back its result.
  6. Upload: file on the e-filing portal or at a TIN facilitation centre and record the token number. The compliance calendar completes.
  7. Processing: record whether the statement was accepted or rejected. Changes after upload go through a correction statement (Correct a TDS statement already filed).

TRACES certificates (Form 16, 16A and their 2025-Act successors) are imported, matched to deductees and shared from the workspace (Import and share TRACES certificates). The Read the TDS quarter board shows every deductor's quarter at a glance.

Which Act and forms apply depends on the date of the deduction: see .

Features switched on per firm

The workspace (ff.tds.workspace), the 2025-Act forms (ff.tds.act_2025), the default analyser (ff.tds.analyser), TRACES imports and corrections (ff.tds.corrections), certificate bundles and sharing (ff.tds.certificates) and entry suggestions from books (ff.tds.books_derive) are rolled out per firm. You see a part only when it is on.

Check a quarter for possible defaults

The analyser lists possible defaults of a quarter (short deduction, late deposit and similar) with predicted amounts. Each must be acknowledged or explained before the statement is frozen.

The Possible defaults panel of the quarter workspace runs the analyser over the quarter's entries, challans, deductees and certificates, using the published parameters for the period. Findings never block on their own, but every open finding must be dealt with before the statement is frozen, on an analysis of the current entries.

Analyse

Choose Analyse (or Analyse again after entries changed). Each finding shows what it is, the quarter, the months and the predicted amount. Pay before filing (the client pays) sums what the analyser predicts the client should pay with the statement, by minor head. A finding that matches one of the previous run keeps its decision.

Decide each finding

  • Acknowledge: you have seen it. A reviewer at or above the firm's minimum role (TDS and TCS settings) acknowledges.
  • Explain this finding: give a reason of at least 20 characters (for example why no deduction applied). Findings at or above the firm's partner threshold are explained only by a partner; a reviewer below partner can send a request, which a partner decides from the approvals inbox.

Compare with TRACES

After processing, import the TRACES justification report under Data imports and choose Compare with TRACES. The panel shows Predicted and TRACES defaults side by side (Only predicted, Only in TRACES, or both with the Difference).

Correct a TDS statement already filed

A correction statement starts from the TRACES consolidated file of the filed statement. You record the changes over it; the app writes a file of the changed records only, which then goes through freeze, approval, FVU and upload.

Once a statement is uploaded it is locked: changes are made only through a correction statement.

Start a correction

Steps

  1. Request the consolidated (conso) file of the statement's token on TRACES and import it under Data imports. You can track the request under TRACES requests on the deductor.
  2. In the quarter workspace, choose Start a correction, pick the Quarter and give the Imported TRACES conso file (dataset id). The token comes from that file; it is the correction's only baseline.
  3. On the correction statement, Add a change for each correction: Correct a PAN, Change a deductee row, Change a challan, Deductor details changed or Cancel the statement, with the row or challan number from the conso file.
  4. Check Correction issues, then validate, freeze, get the client's approval, run the FVU and record the upload as for a regular statement (Validate, freeze and file a TDS statement).

The file holds only the changed records with their correction types. The original filing stays completed in the compliance calendar.

A challan you add to a correction must have balance that no other statement has used (). Changing a frozen correction that is not yet uploaded reopens it.

Import and share TRACES certificates

Import the certificate bundle downloaded from TRACES, match each certificate to its deductee by PAN, merge Form 16 Part B, file the certificates in Documents and share them to the client's portal.

Certificates are kept exactly as TRACES issued them, byte for byte; the app never makes a certificate of its own. They are in the Certificates panel of the quarter workspace.

Import a bundle

Steps

  1. Download the certificate zip from TRACES and import it under Data imports as a TRACES certificate bundle of the deductor's TAN.
  2. In the workspace, choose Import a TRACES bundle, pick the import, the kind (for example Form 16A (TRACES), Form 16 Part A (TRACES, annual) or, for tax years from 2026-27, Form 130 (TRACES, annual)) and the Period (Q:FY2025-26:4 for a quarter, Y:FY2025-26 for Form 16, TY:2026-27 for Form 130).
  3. Enter the Zip password only if TRACES protected the zip. It is used once and never kept.

Match, merge and file

  • Each certificate is matched to a deductee by the PAN TRACES printed. Certificates shown as Not matched (for example PAN not in the deductee master or PAN appears twice) can be matched by hand, only to a deductee with that PAN.
  • For Form 16 and Form 130, Merge Part B adds the salary details; the batch is then Ready to file.
  • File in documents stores the certificates in the client's Documents.
  • Share to the client portal makes them available to the client; give a reason and confirm it's you. Deductees get certificates from their deductor; the app sends no e-mail.
  • Download PDF for one deductee, or Export selected as zip.

TDS summaries

After a statement is frozen, TDS summaries produces a labelled summary per deductee from the frozen version. It is a summary, not a certificate.

Keep a deductor's profile, deductees and challans

The deductor page holds the profile (address and responsible person), the deductees, the challans with their CSI status, lower-deduction certificates and declarations, and the client's quarter workspaces.

Profile

Fill in the Address, City, State code, PIN and the Responsible person with their designation, PAN and mobile. Choose Save profile. A statement cannot be frozen while the profile is incomplete ().

Deductees

Add a deductee with the name, class (individual or HUF, company, firm, government, non-resident) and the PAN if you have it. PANs are shown masked, with their PAN status. One deductee per PAN for each deductor.

Challans

Add a challan with the BSR code, Deposited on date, Challan serial and the tax deposited. The app builds the CIN and checks it. Each challan shows its Balance (what is not yet allocated to entries) and its CSI status: Matched in CSI, Amount differs in CSI, Not in CSI or Not checked.

To check challans, import the challan status file under Data imports and choose Match with a CSI file with its dataset id. Whether an unmatched challan blocks a freeze is a firm setting (TDS and TCS settings).

A government deductor that adjusts tax by book entry records Book entry challans instead.

Lower-deduction certificates and declarations

Lower-deduction certificates list each certificate's deductee, section, rate, validity and Used of limit. The app warns when a certificate is nearly used up (a firm setting). Under Declarations (15G/15H), record the declarations received for each year; for tax years from 2026-27 the app uses the successor forms.

Quarter workspaces

The client's quarterly TDS engagements are listed here. If none exists, create a "TDS quarterly" engagement on the client; then open its workspace (Work in a TDS quarter workspace).

Ledgers and sections, TRACES requests

When suggestions from books are on, map the client's ledgers to TDS sections under Ledgers and sections. Under TRACES requests, track requests made on TRACES (for example the consolidated file or Form 16A downloads) and the date each falls on; the app reminds you a few days before.

Set up a TDS deductor

The deductors list shows the firm's TDS and TCS deductors, one per client TAN. Set one up from a TAN on the client's profile, then complete its address and responsible person.

The list shows each deductor's Category, its Profile (Complete or Incomplete) and its Statements. Filter by TAN. Open a deductor to work on it (Keep a deductor's profile, deductees and challans).

Set up a deductor

Steps

  1. Choose Set up a deductor.
  2. Choose a client with a TAN. The TAN must already be an identifier on the client's profile; add it there first if it is missing.
  3. Create the deductor. The category and the statements it files come from the client profile.
  4. Open the deductor and fill in its address and responsible person. Until then its profile is Incomplete and statements cannot be frozen.

There is one deductor per TAN ().

Validate, freeze and file a TDS statement

On a statement you validate it, freeze a version, get the client's approval, run the official FVU on its file, record the upload with the token number and record the processing status.

The statement page shows the totals (Amount paid or credited, Rows, Unallocated rows), the Validation issues and, once frozen, the version with its File and SHA-256 fingerprint.

Steps

Steps

  1. Validate. The app builds the statement and its text file and runs the content rules. Fix each blocking issue in the entries, challans or deductor profile, and validate again.
  2. Freeze version. A reviewer at or above the firm's minimum role freezes it. The reviewer must not be the last person who changed an entry, challan or allocation of the statement (a solo practice is allowed; this is logged). Open possible defaults must be acknowledged or explained first (Check a quarter for possible defaults), and challans must match the CSI file when the firm requires it.
  3. Client approval (when the firm requires it). The summary goes to the client's portal contacts. If the client approved by other means (e-mail, a signed summary), a partner chooses Record the client's approval with a reason of 20 characters or more and an evidence document.
  4. FVU. Choose Download the text file or FVU package and checklist, run the official File Validation Utility on that file, then Bring back the FVU result: Passed with the .fvu file (stored in Documents), or Failed with the error report imported under Data imports. The file the FVU read must be the frozen file.
  5. Record the upload. After uploading on the e-Filing portal or at a TIN facilitation centre, enter the Token number (15 digits), the Uploaded on date and the Channel. The compliance calendar then completes in the background.
  6. Processing status. Record Accepted, or Rejected (reopens the statement), with the date.

Downloads and recording the upload ask you to confirm it's you.

If the page shows File format in CA review: check with the FVU before upload, the file layout the app writes has not been signed off yet; rely on the FVU result.

After a change

Work in a TDS quarter workspace

The quarter workspace holds the entries of a quarterly TDS engagement, each with a suggested rate, their allocation to challans, the salary annexure, the statements of its quarters and the checks for possible defaults.

Open a workspace from the deductor's Quarter workspaces or from the Read the TDS quarter board.

Entries

Steps

  1. Choose Add an entry.
  2. Pick the Deductee, the Section and the Date paid or credited, and enter the Amount (₹). Enter the date first: the sections offered depend on it ().
  3. The app shows the suggested rate before you save; open How the rate was suggested to see why (the deductee's class and PAN status, a lower-deduction certificate, a declaration).
  4. Save the entry. The tax deducted is kept with the entry.

Each row in Entries shows the amount Paid or credited, the Rate, the Tax, the Regime (the Act) and its Challan.

Allocate tax to challans

Every entry's tax must sit on a challan with enough balance. Allocation proposals suggests a challan for each unallocated entry; a person confirms each proposal. The totals show what is Allocated and Unallocated. If no challan has enough balance, add the challan on the deductor first.

Salary annexure

For the year's last quarter, the salary annexure keeps each employee's salary details with a Worksheet that computes the Tax for the year and the Shortfall. Salary details are for managers and partners unless the firm lets assigned staff see them (TDS and TCS settings).

Statements

Start a statement for a Form and Quarter. Each statement is listed with its stage; open it to validate, freeze and file (Validate, freeze and file a TDS statement). One statement per deductor, form and quarter.

Other panels

Read the TDS quarter board

The quarter board lists every deductor you can see with its statements by form for one quarter, their stage, open findings, the predicted amounts for lateness and the date risk.

Choose the Quarter. Under Statements by TAN and form, each row is one deductor and form:

ColumnShows
Client, Deductor, Formwhose statement it is
Stagefrom Not started through draft, frozen, FVU and upload to accepted or rejected
Open findingspossible defaults not yet acknowledged or explained (Check a quarter for possible defaults)
Predicted interest, Predicted feewhat the analyser predicts for late deduction, payment or filing, from the published parameters; a prediction, not a demand
Due (F2) and Due riskthe compliance calendar's date for the statement and whether it is On time, Due within 7 days, Overdue or has No due date

Open a row to go to its statement or quarter workspace.

This quarter's dates

The compliance calendar's dates for the statements of the quarter that ended last, which are usually the ones being filed now:

StatementDate in the calendar
Salary (24Q, or Form 138 under the 2025 Act)current value: see your app
Resident, non-salary (26Q, or Form 140)current value: see your app
Non-resident (27Q, or Form 144)current value: see your app
Tax collected at source (27EQ, or Form 143)current value: see your app

For the quarter in progress, the salary statement's date is current value: see your app. A date moved by a notified extension shows the original date too. The board shows the same date for each deductor's statement.

TDS and TCS settings

The firm's TDS rules - who may freeze, whether the client approves before upload, how strictly challans must match the CSI file, who sees salary details, and the warning thresholds.

Open TDS → Settings. Partners and firm administrators change these settings; settings marked Security setting: owner or partner are changed only by the owner or a partner, with a fresh identity check and a reason. Every change is recorded in the firm's audit log.

On the settings page

SettingKeyDefaultWhat it does
Who may freezetds.review.min_roleManagerSenior or manager: the lowest role that may freeze a statement version and acknowledge findings.
Client approval before uploadtds.client_approvalRequiredSecurity setting. Required: the upload waits for the client's approval or a partner-recorded approval. Optional: no approval step.
Challans must match the CSI filetds.csi.require_matchYesSecurity setting. Off: an unmatched challan is a warning instead of a block at freeze.
Block when the CSI file changedtds.block_on_source_changeYesA frozen, not yet uploaded version whose CSI import was superseded must be frozen again before upload.
Staff may see salary detailstds.salary.staff_may_viewNoSecurity setting. Off: salary details and worksheets are for managers and partners only.
Salary shortfall tolerance (₹)tds.salary_tolerance1000 to 10,000. A salary worksheet shortfall below this raises no warning.
Certificate limit warningtds.ldc.warn_pct8050 to 99, a percentage. The app warns when a lower-deduction certificate is used up to this share of its limit.

Read by the app, not yet on the page

KeyDefaultWhat it does
tds.finding.partner_threshold10,000Security setting. Possible defaults of this many rupees or more are explained only by a partner (Check a quarter for possible defaults).
tds.deposit.complete_from_csiNoWhen every challan of a month matches the CSI file, complete that month's deposit in the compliance calendar with the CIN.
tds.traces.reminder_days31 to 30. Days before a tracked TRACES request's date that the in-app reminder shows.
tds.traces.auto_requestsconso file, Form 16ATRACES requests created automatically for tracking after a statement is accepted.

Until they appear on the page, contact support if one of them should change for your firm.