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

Explainer2 min readPublished

How a ghost employee actually gets onto a payroll, step by step

A ghost employee isn't usually added through some dramatic hack — it's a normal-looking HR and payroll process with one person controlling both ends. How it actually happens, and a free way to check your own payroll.

A ghost employee almost never requires hacking a system — it requires one person having enough control over both hiring and payroll approval to create an employee record and keep approving payments to it with nobody else ever checking. The mechanism is administrative, not technical: an employee ID gets created, salary gets configured, and a bank account (often the creator's own, or a shared household account) receives the payment every month, indistinguishable in the payroll run from any other legitimate employee.

The steps, in order

  1. 01Create the employee recordUsually by someone with HR system access and no second approver required for a new hire below a certain level.
  2. 02Set the bank account for salary paymentThis is the step that actually leaves evidence — the account number on this record can be cross-checked against every other employee's account.
  3. 03Let the payroll run include it automaticallyA monthly payroll process that runs on whatever's in the system doesn't re-verify that every employee actually exists; it processes whatever's there.
  4. 04Keep it invisible by avoiding attentionNo unusual expense claims, no visible conflict, nothing that would prompt someone to ask who this person actually is.

The two checks that actually surface this — matching bank accounts across the whole employee population, and matching payroll against attendance records — are both full-population analytics, not something a sample-based review of a handful of employee files would typically stumble onto.

Why it survives for months, sometimes years

It survives because nobody is specifically looking for it. A payroll audit that checks calculation accuracy, statutory deductions, and approval sign-offs can pass every one of those checks for a ghost employee — the arithmetic is fine, the approval exists, the deductions are correctly computed. The scheme isn't an error in any individual calculation; it's an employee who shouldn't exist in the first place, which none of those checks are designed to ask about.

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.