Ghost Workers: How HRMIS Cleans Up Your Payroll
Every employer fears the same quiet problem: a name on the payroll that should not be there. It may be someone who left months ago, a duplicate record, or a person who never existed. These are usually called ghost workers. The cost is rarely one big theft. It is small amounts, paid every month, that nobody notices. This post explains how it happens and which controls in an HRMIS help close the gap. We have written it for HR, finance and audit teams in The Gambia.
How ghost workers get on the payroll
Ghost workers rarely come from the pay run itself. They come from the gaps around it. Payroll is often kept apart from HR, so when someone resigns, retires or is dismissed, the exit has to travel by letter or message from one office to another. Any delay, or any step that is forgotten, leaves a name still being paid.
- Staff who have left, but whose exit never reached payroll.
- Duplicate records for one person, created by re-entering data.
- Fictitious employees added by one person acting alone.
- Salary or allowance changes made without a second set of eyes.
- No regular check that every name on the payroll matches a real person in post.
Start with one employee record
The strongest fix is structural. When HR and payroll use the same employee record, there is only one place where a person exists. A new joiner is created once, a promotion or posting is recorded once, and an exit is recorded once. Payroll reads from that record rather than keeping a separate copy. There is no second list to fall out of date.
Controls to look for in any HRMIS
- Maker-checker approval: a new employee record, or a change to one, must be approved by a second user. The person who made the request can never approve it.
- Exit records: resignation, retirement, termination and death are recorded as formal HR processes, not informal messages.
- Payroll setup visibility: the system shows employees who have no payroll setup, and the headcount of active, confirmed and terminated staff.
- Documents on file: contracts, IDs and certificates are stored against each record, with expiry alerts.
- Employee photos and lists: reports that let a supervisor check that the people on the list are the people in the office.
- Payroll variance report: a month-to-month comparison that flags unexpected changes before the money is paid.
- Bank and cash schedules: every payment can be traced to a named person and an account.
Payroll is only as clean as the employee record behind it. Fix the record, and most of the leakage goes with it.
A practical rollout
Cleaning up an existing payroll does not need to wait for new software. It does need a clear order of work. The steps below are the ones we would follow with any organization that wants to start.
- Run a headcount: match every name on the payroll to a real person in post, with a photo or ID on file.
- Load the verified list into the HRMIS as the single source of employee data.
- Switch on approvals so every new record and change needs a second person.
- Record all exits through the HR process, and compare the exit list with the payroll each month.
- Review the payroll variance report before each pay run, and investigate any unexplained change.
- Repeat the headcount at least once a year.