The employee number is real. The person may not be.
What looked normal
An employee ID sits in the master. Salary clears every cycle. Cost center looks fine. Ask who last saw them at a desk, on a badge reader, or in a system login—and the trail goes quiet.
That is the ghost-employee problem: pay without presence. Sometimes the person never existed. Sometimes they are a duplicate persona. Sometimes they are shelved headcount still marked active while someone else collects the deposit.
Why people should care
Ghost payroll is not a rounding error. It is recurring cash leaving the company every pay cycle.
Headcount reports and sample audits rarely catch it. Ghosts look complete in HR forms and payroll output—until you join identity, bank details, activity, and pay results across the full population.
Eight analytics that expose ghost employees
These tests use employee master, bank details, pay results, and—where available—access or time data. In SAP-style landscapes that often means Employee Master (PA0000 / PA0001), Bank Details (PA0009), Basic Pay (PA0008), and Payroll Results (PCL2 / RT).
-
Paid with no recent activity signal
Join payroll to badge, VPN, SSO, or timesheet activity. Surface active employees paid with zero recent presence.
Business impact: Strong no-show / shelved-headcount signal across locations.
-
Duplicate national ID, tax ID, or contact
Match employees on national ID, tax ID, phone, or email—exact and near-duplicate—under different employee numbers.
Business impact: One person (or one fabricated identity) occupying multiple payroll seats.
-
Shared bank accounts across “employees”
Detect two or more active employees remitting to the same IBAN / account (PA0009).
Business impact: Classic collection point for ghost or proxy payroll.
-
Employee bank matches a vendor bank
Compare employee bank details to vendor bank master (LFBK) for exact account / IBAN matches.
Business impact: Diversion path between payroll ghosts and AP payees.
-
Incomplete or placeholder master data
Flag active paid employees with missing tax ID, blank address, generic email, or placeholder names.
Business impact: Fictitious records often skip the fields real onboarding requires.
-
Impossible supervisor / org span
Detect managers with implausible direct-report counts, circular reporting, or reports with no org home.
Business impact: Ghosts need a reporting line—weak org design hides them.
-
Created and paid with almost no tenure signal
Short gap from employee create date to first large payment, with weak onboarding or access evidence.
Business impact: Rushes used to insert fictitious workers into a pay run.
-
Off-cycle pay without corresponding presence
Cluster manual / off-cycle payments to employees who also fail activity and identity tests.
Business impact: Override paths that fund ghosts outside the standard cycle.
Why headcount reviews miss this
Headcount and sample payslips
Reconcile FTEs to budget and spot-check a few employees. Assumes every active ID is a real, present person.
Identity + presence + pay joins
Duplicate IDs, shared banks, missing master fields, and zero-activity pay— across the full payroll population, not a sample of names.
An employee number is not proof of a person. Join identity, bank details, presence, and pay results—and ghost payroll stops looking like headcount.
How foretale.ai helps
foretale.ai runs payroll risk analytics across employee master, bank details, and pay results— no-activity paid employees, duplicate identities, shared banks, employee–vendor bank matches, incomplete masters, and off-cycle anomalies—with explainable evidence for every finding.
Payroll, HR, and audit teams review prioritized ghost-employee risks across the full population—not only a sample of names.
Who on your payroll has never shown up?
Identity, bank, and activity signals often sit in data you already have. Continuous AI analytics can surface ghost employees before the next cycle clears again.
Request a demo