When an overseas client engages an independent contractor in India, the arrangement looks simple on paper — the contractor submits an invoice, the client approves the scope and amount, and the provider releases payment. In practice, this three-way relationship (end client, contractor, and the intermediary managing payments) sits on top of a specific set of Indian tax and compliance rules that have nothing to do with a standard vendor payment. Get them wrong, and the cost isn’t just an annoyed contractor — it’s disallowed expenses, interest, penalties, and in some cases a labour-law headache for the end client.
Here’s what actually matters when managing contractors in India, and where providers most often slip up.
The core compliance layer: TDS, not “payroll tax”
The single most important thing to get right is that a contractor is **not an employee**, and none of the deductions that apply to payroll apply to a contractor invoice. What applies instead is **Tax Deducted at Source (TDS)** under the Income Tax Act — and picking the right section matters more than most providers realise.
Section 194C — payments for “work.” This covers contracts for a defined piece of work, labour supply, or a deliverable-based engagement — things like manpower supply, event execution, or job-work. TDS here is 1% for an individual/HUF contractor and 2% for any other entity (company, LLP, firm). No TDS is required if a single payment doesn’t cross ₹30,000 and the aggregate for the year stays under ₹1,00,000 — but once either threshold is crossed, TDS applies to the *cumulative* amount, including payments already made earlier in the year.
Section 194J — payments for “professional or technical services.” This is where most contractors actually fall: developers, designers, consultants, engineers, writers, analysts — anyone applying specialised skill or knowledge rather than just supplying labour under supervision. TDS here is a flat 10% for professional services (2% for certain technical services), with a threshold of ₹50,000.
The two sections aren’t interchangeable, and the Finance Act 2024 specifically closed the grey area that let some payers classify professional-service invoices as “work” to justify the lower rate. Since April 2026, both sections have been folded into a consolidated Section 393 framework under the new Income Tax Act, 2025 — the rates and thresholds haven’t changed, but the reporting codes used in quarterly TDS returns have, so returns filed under the old 194C/194J codes after that date need to reference the updated table.
Why this matters practically: if a contractor is doing specialised, judgment-driven work and gets classified under 194C at 2% instead of 194J at 10%, the provider is left with an 8% shortfall the moment a tax officer looks at the contract. That shortfall doesn’t just sit with the contractor — under Section 40(a)(ia), the *payer’s* failure to deduct correctly can trigger a 30% disallowance of the entire expense, plus interest at 1–1.5% per month.
Mistake #1: Deducting professional tax from contractor payments
This is the one you flagged, and it’s a genuinely common error. **Professional tax (PT) is a state-level levy that applies to salaried employment** — it’s deducted by an employer from an employee’s salary under a state PT Act, and it exists alongside EPF, ESI, and Section 192 TDS as part of the payroll bundle. It has no legal basis in an independent contractor relationship, where there’s no employer-employee link and no salary being paid — only an invoice being settled.
Providers who default to their payroll checklist sometimes carry PT over to contractor payments out of habit, especially when the same team handles both EOR payroll and contractor payments. The result is an unauthorised deduction from the contractor’s invoice that has no statutory basis, creates a reconciliation mess, and — if it becomes a pattern — starts to look like evidence that the “contractor” is actually being treated as an employee (more on that below).
**The fix:** contractor payments should only ever see TDS under 194C/194J (or 194H for commission, 195 for non-resident payees). No PT, no EPF, no ESI, no Section 192.
Mistake #2: Blurring the line between contractor and employee
This is the mistake with the biggest downstream risk, and it’s not really a tax issue — it’s a labour-law and misclassification issue. If a contractor works fixed hours, reports to a manager, uses company equipment, can’t take on other clients, and is managed the way an employee would be, an Indian labour authority (or a foreign one, for the end client) can reclassify the relationship regardless of what the contract says. That exposes the end client to retrospective employee benefits, statutory dues, and termination-related liabilities — the exact risk an EOR/contractor model is supposed to avoid.
Practical markers that keep the relationship genuinely contractor-based: a defined scope of work or deliverable (not a role description), invoice-based payment tied to output rather than a fixed monthly amount styled as salary, no leave or benefits administration, and the contractor’s freedom to engage with other clients.
Mistake #3: Treating PAN collection as optional
If a contractor doesn’t furnish a valid PAN, or the PAN is inoperative due to non-linking with Aadhaar, TDS jumps to 20% under Section 206AA regardless of which section would otherwise apply. Providers who onboard a contractor quickly to unblock a payment — and chase PAN documentation “later” — either under-deduct (creating a liability) or end up needing to gross up or re-deduct after the fact, which is an avoidable mess. PAN verification should be a hard gate before the first invoice is processed, not a follow-up task.
Mistake #4: Not tracking the aggregate threshold across invoices
A contractor invoicing ₹20,000 a month looks like it’s under the ₹30,000 single-payment threshold every time — but six months in, the aggregate crosses ₹1,00,000, and TDS should have been deducted from the payment that pushed the total over the line, applied to the full cumulative amount. Providers that check each invoice against the threshold in isolation, rather than tracking a running total per contractor per financial year, routinely miss this.
Mistake #5: Getting the deduction timing wrong
TDS is triggered at the **earlier of payment or credit to the contractor’s account** — not at invoice date, and not at month-end. This also means an advance payment to a contractor triggers TDS at the time of the advance, even before any work is delivered. Providers sometimes wait for the invoice approval cycle to complete before thinking about TDS, which can mean the deduction happens later than the law requires.
Mistake #6: Missing the compliance calendar after deduction
Deducting TDS correctly is only half the job. The deducted amount needs to be deposited by the 7th of the following month (30 April for March deductions), reported in the quarterly Form 26Q return, and a Form 16A certificate issued to the contractor within 15 days of the return’s due date so it reflects correctly in their Form 26AS/AIS. A provider that deducts correctly but is slow on deposit or filing still exposes the end client to interest and late fees — the contractor’s tax credit doesn’t show up cleanly either, which creates friction and erodes trust in the provider’s process.
Mistake #7: Overlooking GST on the contractor’s invoice
Where a contractor is GST-registered (mandatory once turnover crosses ₹20 lakh, ₹10 lakh in a few north-eastern states), GST is typically shown separately on the invoice, and TDS should be calculated on the base value excluding GST, per CBDT guidance. Applying TDS to the GST-inclusive amount over-deducts and creates unnecessary reconciliation work with the contractor.
Every mistake above is fixable — the real question is whether it gets caught before or after a tax notice. Most in-house and finance teams handle this fine for two or three contractors. It gets noticeably harder to hold the line consistently as contractor headcount, invoice volume, and geography grow.
What a compliant contractor payment process needs to cover
In practice, this comes down to four things working together, consistently, across every contractor:
Correct classification at onboarding (194C vs 194J, based on the actual nature of the engagement rather than the invoice wording); accurate TDS on every payment — right rate, right base, right timing, including PAN checks and running threshold tracking; a deposit-and-filing calendar that doesn’t slip, month to month and quarter to quarter; and a periodic check that the working relationship hasn’t quietly drifted toward looking like employment.
Contractor management in India is straightforward once the distinction between “payroll” and “contractor payment” is treated as a hard line rather than a formality. Most of the errors above come from applying payroll logic — habits built around salaried EOR employees — to a relationship that is legally and procedurally a different animal. The providers that get this right aren’t necessarily doing more work; they’re just running two genuinely separate playbooks instead of one blended one.
Running two separate, fully compliant playbooks in-house is exactly what ExpanServe’s Contractor & Freelancer Management service is built for — from classification and TDS deduction through deposit, quarterly filing, and certificate issuance, so your team isn’t tracking thresholds and deadlines by hand as your contractor base grows. Get in touch with our team to see how we can take this off your plate.
Here’s the classification breakdown under Section 194J:
Professional Services — 10% TDS
| Category | Examples |
|---|---|
| Legal | Advocates, legal consultants, litigation support |
| Medical | Doctors, physicians, medical consultants |
| Engineering | Design engineers, structural consultants (advisory/design capacity) |
| Architectural | Architects, architectural design consultants |
| Accountancy | Chartered accountants, cost accountants, auditors |
| Technical consultancy | Strategic/advisory technical consulting (not hands-on execution) |
| Interior decoration | Interior designers |
| Advertising | Ad agencies, creative/campaign consultants |
| Other CBDT-notified professions (u/s 44AA) | Company secretaries, authorized representatives, film artists, information technology professionals |
| Sports-related | Sports coaches, commentators, umpires/referees, event managers, anchors, sports columnists |
| Company directors | Sitting fees / any non-salary payment to a director |
Technical Services — 2% TDS
| Category | Examples |
|---|---|
| Managerial services | Outsourced management functions, operational oversight |
| Technical services (execution-oriented) | Software development, system implementation, IT support, coding/customisation work |
| Call centre services | BPO/call centre operations |
| Royalty (specific carve-out) | Royalty for sale/distribution/exhibition of cinematographic films |
| Consultancy (non-professional, technical in nature) | Technical support consultancy that doesn’t rise to the “technical consultancy” profession bucket above |
The distinguishing principle
The legislature’s underlying test — not a formal legal definition, but the substance courts and practitioners apply — is:
- Professional service → driven by specialised human judgment, discretion, and personal accountability. Tailored to the specific situation. The person’s expertise is the deliverable.
- Technical service → execution-oriented, standardised, system- or process-driven, scalable across clients. The output/system is the deliverable, not personal judgment.
Where this gets genuinely contested — and matters most for an EOR handling IT/consulting contractors:
- A developer writing custom code or doing system implementation → technical (2%)
- A consultant advising on architecture, strategy, or digital transformation → professional (10%)
- Same contractor, same domain — the invoice description isn’t what decides it; the actual nature of what’s being delivered does.
Practical notes for classification
- The invoice description is not authoritative. “IT consulting services” could be either bucket depending on whether it’s hands-on build work or advisory judgment. Look at the SOW/contract, not just the invoice line item.
- The ₹50,000 threshold applies separately per category, not combined. If the same contractor bills ₹40,000 for professional work and ₹35,000 for technical work in a year, neither crosses its own threshold even though the combined total does.
- Misclassification risk cuts both ways — treating professional work as technical under-deducts (10% vs 2%, an 8% shortfall exposed on audit); treating technical work as professional over-deducts (creates refund friction for the contractor, though not a compliance risk for you).
- When genuinely ambiguous (especially IT/software engagements), the safer default is the higher rate (10%) — over-deduction is a minor inconvenience the contractor recovers via their ITR, while under-deduction creates a real liability for ExpanServe.
