For most Gujarat businesses TDS touches contractors, transporters, professional fees, rent, commission and payroll all in the same month. The difficulty is almost never the law — it is keeping deduction, deposit and reporting aligned across all of them.
This handbook walks through the full cycle so quarterly returns are assembled from data that is already correct, and TRACES defaults stop appearing after the fact.
Key takeaways
- TDS is decided at the payment or credit stage — the accounting entry is where compliance succeeds or fails.
- Deposit and return are separate obligations; meeting one does not cure the other.
- Wrong PAN and wrong section codes are the most common and most avoidable causes of defaults.
- Reconcile the deduction ledger to the books every quarter, before filing rather than after.
- Clear defaults promptly — they attach to your deductee's credit and to your own records.
Why TDS is an operations problem, not a tax problem
Tax deducted at source is decided at the moment a payment is made or an amount is credited in your books — whichever is earlier. That means the decision point sits with accounts payable, not with the tax function at quarter end. By the time a return is being prepared, the deduction has either happened correctly or it has not.
This is why most TDS difficulty is procedural. Businesses rarely dispute that a deduction was required; they discover late that it was missed, made at the wrong rate, made under the wrong section or made against an incorrect PAN.
Fixing TDS therefore means fixing the payment process: vendor onboarding, invoice coding, and the checks that run before a payment is released.
Getting the deduction account number and profile right
A deduction account number is required before deductions can be deposited and reported. Where a business has multiple branches or divisions with independent payment processes, the structure of deduction accounts needs to be decided deliberately rather than by accident.
Keep the contact details and authorised person current. Default notices and reconciliation communications flow to the registered details, and a stale email is a common reason defaults are noticed months late.
Identifying deductible payments at source
Build a payment-type map. Professional and technical fees, contractual payments, rent, commission, interest, salary and purchases of certain kinds each carry their own treatment, and each is identified by the nature of the underlying service rather than by the wording on the invoice.
The practical control is to attach the correct section code to the expense at the point of invoice entry, driven by the expense account and the vendor master, rather than leaving it to be reconstructed later. When coding is automatic, deduction becomes automatic.
Watch the aggregation cases. Some obligations arise only once cumulative payments to a vendor cross a level during the year, which means a payment that required no deduction in April may trigger deduction, including on earlier amounts, later in the year. A running vendor-wise cumulative report is the control that catches this.
Advances deserve their own rule. Deduction is generally triggered by payment or credit, whichever is earlier, so an advance paid before an invoice arrives is usually the trigger point.
Vendor master data and PAN validation
An incorrect or missing PAN is the single most damaging data error in TDS, because it changes the rate applicable and breaks the deductee's ability to see the credit. Validate PAN at onboarding, and again if a vendor's name or entity type changes.
Capture entity type as well. Whether a vendor is an individual, a firm or a company can affect treatment for some payment types, and it is much easier to record at onboarding than to establish afterwards.
Where a vendor holds a certificate for lower or nil deduction, record its number, the rate, the sections covered and the validity period in the vendor master, and diarise the expiry. Applying a lapsed certificate creates a short-deduction default.
Depositing on time and correctly
Deposit is a separate obligation from the return, and it carries its own consequences for delay. Deposit the amounts deducted for the period by the applicable date, using the correct deduction account number, assessment year, section code and nature of payment.
Errors in a challan are more disruptive than they appear, because a return cannot be matched to a challan that carries the wrong details. Verify each challan the day it is paid rather than at return time — corrections are far simpler close to the event.
Reconcile deposits monthly: the deduction ledger in your books should tie to challans paid, with any difference explained by timing rather than left unexplained.
Quarterly returns and certificates
The quarterly return reports deductee-wise detail: PAN, amount, section, date of deduction and challan mapping. It is only as good as the data behind it, which is why the reconciliation belongs before filing, not after.
Run three checks before every filing. First, does total deduction per the books equal total deduction per the return? Second, does total deposit per challans equal total deduction reported? Third, does every deductee row carry a valid PAN and the correct section?
Certificates issued to deductees follow the return, and they matter commercially: vendors and employees rely on them. Issue them promptly, and treat requests for corrections as a signal to check whether the underlying return needs revision.
Defaults: how they arise and how to clear them
Defaults typically arise from short deduction, late deduction, late deposit, late filing, or PAN errors. Most are generated automatically by processing your return against the challans and PAN data, so they appear soon after filing rather than years later.
Deal with them immediately. A default that is left open compounds, and it also sits in your deductee's records, which produces awkward conversations with vendors and employees.
The clearance path depends on the cause: a data error is corrected by a revised return, a challan mismatch by correcting or re-tagging the challan, and a genuine short deduction by depositing the difference with applicable interest and then revising. Keep evidence of each correction with the quarter's working papers.
Salary deduction is its own discipline
Deduction on salary is computed on an estimated annual basis and spread across the year, which means it needs a mid-year review rather than a single April decision. Employee declarations of investments and other income should be collected early, reviewed for plausibility, and confirmed with evidence before the year closes.
Under-deduction discovered in the final quarter is uncomfortable for employees because the correction lands in one or two pay cycles. A December review is the standard control that prevents it.
A monthly and quarterly control calendar
Monthly: code invoices with section codes at entry, run the cumulative vendor report, deduct, deposit, verify challans and reconcile the deduction ledger.
Quarterly: reconcile books to challans to return, validate PAN and section codes, file, download and issue certificates, then check for defaults and clear them before the next quarter starts.
Annually: review vendor master quality, confirm lower-deduction certificates and expiries, and reconcile the year's deduction to the annual tax statement so that nothing is discovered during assessment that could have been found in June.
Frequently asked questions
- When is TDS triggered — on payment or on invoice?
- Generally at payment or credit in the books, whichever is earlier. That is why advances often trigger deduction before an invoice is even received.
- What happens if the deductee's PAN is wrong?
- The deduction may be treated at a higher rate and the deductee cannot see the credit, which usually produces a default notice and a request for a revised return.
- Is filing the quarterly return enough if the deposit was late?
- No. Deposit and filing are separate obligations, each with its own consequence for delay. Filing on time does not cure a late deposit.
- How quickly should defaults be addressed?
- As soon as they appear. Interest accrues, and an open default also sits in the deductee's records, which creates avoidable friction with vendors and employees.
This guide is general information only and is not professional advice. Rules and thresholds change; please confirm how they apply to your business before acting.