Start with the payment, the payer and the period
TDS on contractor payments is a withholding obligation: the payer deducts tax from a covered payment and accounts for it to the government. For an Indian business, the practical challenge is deciding which payments are covered, applying the correct treatment and maintaining evidence through payment, reporting and reconciliation. A vendor described as a contractor in your purchase register does not automatically determine the applicable tax treatment.
This guide sets out a review process rather than a rate chart. Before processing a transaction, verify the law, rules and notifications applicable to its period. For FY 2026-27, do not copy section references, forms or compliance dates from an older working paper without checking their applicability under the Income-tax Act, 2025 framework. Earlier periods require their own review.
Classify the contract before selecting a rate
Read the scope of work, purchase order and invoice together. A construction assignment, labour arrangement, transport contract, professional engagement and purchase of goods may require different analysis. The commercial label on an invoice is only a starting point. Identify what the vendor is actually supplying, who provides the materials and whether the invoice combines distinct obligations.
Establish the payer's legal constitution and relevant business facts. The withholding obligation can depend on the category of payer as well as the nature of payment. Confirm the payee's residential status separately: an Indian postal address or bank account alone does not establish tax residence. Payments involving non-residents need a separate review rather than automatic use of resident-contractor treatment.
- Retain the signed contract and all amendments affecting price or scope.
- Record the vendor's legal name, PAN, constitution and verified bank details.
- Document why the selected withholding category matches the actual work.
- Escalate mixed contracts, cross-border services and unusual reimbursements before release.
Build a defensible rate and threshold check
A sound rate working records the applicable provision, payment category, payee status, threshold test and any exception relied upon. Check both the individual transaction and cumulative payments or credits for the relevant period where the applicable rule requires them. Reviewing each invoice in isolation can miss a threshold crossed by several smaller bills.
Maintain one vendor identity across branches and cost centres. Duplicate vendor codes can fragment the annual total and hide earlier advances. Agree who consolidates the data and how frequently it is refreshed. Where the governing rule uses a payer-level threshold, a branch spreadsheet should not be treated as the complete record.
Do not hard-code a lower rate simply because it was used last year. If a vendor supplies a lower or nil deduction certificate, verify its authenticity, validity period, covered payer, category and available amount before relying on it. Missing or invalid identification details can also affect treatment. Record the checks rather than accepting an email request as authority.
Determine the base and timing carefully
The amount payable to the vendor and the amount subject to withholding are not always interchangeable. Separately shown indirect tax, material components, reimbursements, advances and retention require examination under the relevant rules and guidance. Avoid a blanket policy that every invoice component is always included or always excluded.
Check when the deduction obligation arises under the applicable provision. Waiting until the bank payment can miss an earlier trigger linked to credit or booking. Year-end expense accruals deserve particular attention because the finance team may have recognised a liability before a final bill arrives. Keep the booking date, payment date and deduction date visible in the register.
An illustrative calculation
Assume a reviewed transaction has a withholding base of Rs 80,000 and the verified applicable rate is 2%. The deduction is Rs 1,600, leaving Rs 78,400 against that base. These figures illustrate multiplication only; they do not establish that 2% applies to a particular contractor or that every component of a real invoice belongs in the base.
Record any additional invoice components separately and reconcile the resulting settlement to the vendor ledger. If the contract promises a net receipt or includes a tax gross-up clause, obtain a specific calculation. Subtracting a percentage from the headline invoice without reading the agreement may produce the wrong payable.
Separate deduction, deposit and reporting controls
Deducting tax is one stage of compliance. The business must also deposit the amount through the applicable process, report the correct payee information and provide the required evidence of deduction. Use a compliance calendar checked against current official requirements for the period and payer category. Allocate a preparer and reviewer for every stage.
| Stage | Evidence to retain | Control question |
|---|---|---|
| Invoice review | Contract, invoice and classification note | Is the category supported? |
| Deduction | Base, rate, dates and ledger entry | Does the calculation match the rule? |
| Deposit | Payment acknowledgement and allocation | Does the deposit cover the recorded liability? |
| Reporting | Filed statement and processing status | Are vendor details and amounts correct? |
Reconcile the register every month
Match the contractor ledger to the withholding register, then match the register to deposits and reported entries. Investigate differences separately: an unbooked deduction, incorrectly allocated deposit and invalid PAN require different corrective actions. A total that agrees at company level can still contain a wrong allocation between two vendors.
Ask vendors to raise credit discrepancies with invoice references and supporting details. Where an error is confirmed, follow the applicable correction process and retain the acknowledgement. A journal entry in your books alone does not correct a filed statement or ensure the contractor receives the appropriate tax credit.
Handle exceptions without hiding the trail
Credit notes, cancelled bills, advance adjustments and disputed invoices should remain traceable to the original transaction. Do not delete the initial entry simply to make the month-end register look clean. Document the commercial event, tax review, revised calculation and reporting action so another reviewer can reconstruct the movement.
If a missed deduction or delayed deposit is discovered, quantify the affected transactions promptly. Review the potential interest, fees, expense treatment and other consequences under the applicable law rather than relying on a generic penalty table. Give management a dated correction plan with responsibilities and evidence of completion.
Connect accurate records to financial reporting
Contractor costs, unpaid vendor balances and withholding liabilities should agree across the ledger and financial statements. Incorrectly treating tax deducted as a reduction of the business expense can distort both profitability and liabilities. Keep the gross expense, vendor settlement and tax payable distinguishable in the accounting records.
For broader financial review, explore the Finxora tools. When contractor expenditure forms part of a new unit or expansion proposal, the project report module can prepare project cost, projected statements and repayment analysis from the figures entered. Review the underlying tax treatment before using those figures in a bank proposal.
A repeatable contractor-payment process combines correct classification, a documented rate check, timely action and reconciliation. Assign ownership at vendor onboarding, invoice booking and period close. That gives the reviewer evidence to support each deduction and makes an exception visible while it can still be investigated.
