We use cookies to understand which pages and tools are useful, nothing more — no ad tracking across other sites. You can change this later from the footer.

Skip to content
Lekhya.in

Explainer4 min readPublished

The 'consultant' who had actually been an employee for two years, found during a payroll walkthrough

An illustrative, composite walkthrough of an individual invoiced monthly as a professional consultant for two years to avoid PF and ESI obligations, caught during a payroll walkthrough that compared consultant invoices to attendance and reporting lines.

This is a composite, illustrative scenario, not an account of a named client. During a payroll walkthrough — the procedure of tracing how a handful of individuals actually get paid, start to finish — one name kept appearing on the professional fees ledger instead of the payroll register, with an identical invoice amount submitted every month for just over two years. Asking what the person actually did surfaced that they worked fixed office hours, used a company email ID, reported daily to a department manager, and had been doing so continuously since being engaged — none of which is consistent with an independent professional relationship, and all of which is consistent with employment that had simply been structured as a consultancy to avoid PF and ESI registration and contribution obligations.

Why this did not surface in a sample of professional fee vouchers

A standard vouching sample of professional fee payments checks each invoice against a supporting bill, a TDS deduction under section 194J, and evidence of service rendered — and this arrangement passed every one of those checks individually. The invoice existed, TDS was deducted correctly, and a one-line description of services was attached each month. What a single-invoice test cannot show is that the same invoice, for the same amount, recurred identically for two years from someone working full-time on-site — a pattern only visible by looking at the relationship over time, not at any one transaction.

What the walkthrough actually checked

  1. 01Pulled every invoice from that vendor code across the two-year periodIdentical amount, identical description, monthly, with no variation a genuine project-based consultancy engagement would typically show.
  2. 02Checked building access logs and the email domain usedAccess logs showed daily entry during standard working hours matching the regular staff pattern, and the email address was on the company's own domain, not a personal or external one.
  3. 03Asked the department manager directly about the reporting relationshipThe manager described the person as part of the team, assigning tasks and approving leave requests exactly as for any other direct report.
  4. 04Compared the arrangement against the tests used to distinguish employment from contract for serviceControl over how and when the work is done, integration into the organisation, and absence of any real business risk borne by the individual all pointed to an employer-employee relationship in substance.
What an independent consultant looks like versus what this looked like
IndicatorIndependent consultantThis arrangement
Working hoursSet by the consultant, project-basedFixed office hours, same as staff
SupervisionDeliverable-based, not day-to-dayDaily task assignment by a manager
Invoice patternVaries with scope of work completedIdentical amount every month for two years
Tools and accessOwn equipment, limited accessCompany email, building access same as employees
What an independent consultant looks like versus what this looked like

What went into the file

  • The two-year invoice pattern and the indicators of control compared against the professional-fee contract on file.
  • The estimated PF and ESI contribution exposure, computed on the implied wage for the period the arrangement had run.
  • A note to management on the TDS treatment under section 194J versus the withholding that would have applied to this as salary.
  • A recommendation to review any other individuals paid through professional fees with a similarly recurring, invariant pattern.

This is a compliance exposure, not just a classification nicety — misclassified employment can trigger retrospective PF and ESI contribution liability (with interest and penalty) for the full period of the relationship, not just from the date it is corrected. The exposure here was quantified at two years of contributions before management began remediation.

This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.

Free tools, no signup

Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.