TDS errors usually begin before payment—when the vendor or nature of service is classified incorrectly.
Tax manager and accounts payable
At invoice and monthly filing
Build a current TDS rate matrix.
Vendor tax master.
Create a payment taxonomy for salary, professional service, contract, commission, rent, interest, purchase, benefits and cross-border items. The applicable provision, threshold and rate depend on current law and facts.
Residency and permanent-establishment or royalty questions can change withholding. Foreign payments require tax and FEMA review before remittance rather than after the bank rejects documents.
Deduction, deposit, return and certificate are separate controls. A tax amount sitting in the ledger is not compliance until paid, reported and reconciled with the deductee’s records.
| Control | What it covers | Operating rule |
|---|---|---|
| Onboarding | PAN, residency and payment nature are captured. | Flag foreign and lower-certificate cases. |
| Invoice review | Contract and service determine classification. | Do not rely on invoice wording alone. |
| Payment control | Deduction is calculated before release. | Use approved rate master. |
| Reporting | Deposit, return and certificate reconcile. | Resolve defaults and corrections. |
Tag every tax working with the income period and governing Act. The 2026 transition means older-year returns and current-year payments can follow different statutory references.
Use exception reports for missing PAN, lower-rate certificates, non-resident vendors, year-end provisions and unmatched challans.
Document the decision, owner, due date and evidence expected. A verbal explanation should be converted into a board note, approved working, contract amendment, portal acknowledgement or reconciliation before the item is treated as closed.
Rules, forms, thresholds and interpretations can change. The operating team should use the latest official source and the actual company facts instead of copying a control from another entity or prior year.
Ask four questions: Is the obligation or accounting treatment applicable? Has the underlying transaction been completely recorded? Does the evidence agree with the books and portal? Has an independent reviewer challenged the exception?
The review should distinguish a timing difference from an error, a judgement from a missing document, and a control failure from a one-time operational delay. Repeated small exceptions deserve root-cause action because they often become material during audit, fundraising, notice or distress.
The operating record should connect the control stages—onboarding, invoice review, payment control, reporting—to the same transaction population. If the source list, accounting ledger, tax return, board record and management dashboard use different populations, the review can appear complete while exceptions remain outside the test.
Management should define an exception threshold, but the threshold must not hide repeated failures. A small error occurring every month can signal weak master data, unclear ownership or a broken interface. The reviewer should record root cause, immediate correction and preventive action separately.
Closure requires evidence. At minimum, the file should show who prepared the work, who reviewed it, which source documents were used, what differences remained and when the next follow-up is due. Screenshots without context or spreadsheets without source references are not a durable control record.
Tag every working with the legal entity, tax period and governing law. The filing date alone does not decide which Act, rate, form or limitation period applies, especially during the 2026 income-tax transition or where a notice covers earlier GST periods.
Portal data should be downloaded and preserved with the filing version. Later supplier corrections, updated statements or portal changes can otherwise make it difficult to prove what information management used when the return or response was approved.