The Question Nobody in HR Wants to Answer: Why Do We Still Pay People After They've Left?
There's a payroll failure so common that most large organisations have written a formal policy for it — and so persistent that writing the policy hasn't fixed it.
It's the "late leaver" problem: an employee resigns, is dismissed, retires, or dies in service — and payroll finds out too late to stop the next pay run. The result is an overpayment nobody wanted to make, followed by a recovery process nobody wants to run.
This isn't a rounding error
Because most private employers never disclose this publicly, the clearest evidence comes from the public sector, where Freedom of Information requests and audit committees force the numbers into daylight.
- Ireland's Health Service Executive — the country's largest employer, with roughly 144,000 staff — reported a significant, multi-million-euro payroll overpayment balance outstanding at year-end, with a substantial number of individual cases each running into five figures. Auditors named the cause directly: incorrect, insufficient, or late notification of changes to an employee's contract or circumstances.
- Highland Council reported a material net overpayment figure for a single financial year, with its own risk register naming "timeous notification of changes to the Payroll Team" as the specific control gap.
- Almost every NHS trust's published overpayment policy lists late notification of leavers as a named, recurring cause — not a one-off incident, but a structural feature of how the organisation runs payroll.
When the Chartered Institute of Payroll Professionals polled its own members on the single biggest cause of overpayments, "late payroll data and last-minute changes" topped the list — ahead of simple human error.
Why a problem this simple stays unsolved
The instinctive fix — "make resignation mandatory in the system, then lock the leaver in payroll" — is directionally right, and most large HRIS platforms already support some version of it. So why does the problem persist at this scale?
Because the late-leaver problem isn't one problem. It's four, and they each fail differently:
- Resignations — the delay usually sits with the line manager, who accepts notice informally and doesn't action it promptly.
- Redundancies, retirements, and fixed-term contract ends — the date is often known weeks in advance, but nothing automatically converts that known date into a system-triggered action, and approval chains eat the lead time.
- Dismissals — HR knows early, through the disciplinary process, but confidentiality and due process correctly prevent early system entry. The fix here is speed of execution after the decision, not earlier detection.
- Death in service or unexplained absence — genuinely unpredictable, and the hardest to prevent by system design alone.
A single "resignation trigger" only ever touches the first category. That's likely why the problem has survived so many well-intentioned fixes: they treat a four-part problem as if it were one part.
A more complete answer
- Branch the trigger by leaver type, not just resignation — a mandatory manager-initiated action for resignations, an auto-generated draft action for known dates like redundancy and contract-end, and a same-day fast-path for dismissals tied to disciplinary sign-off.
- Hold pay by effective date, not by trigger date. A blanket lock the moment a resignation is logged stops the employee being paid correctly through their notice period. The hold needs to activate on the last working day, not the day the paperwork is raised.
- Make the alert human-reviewed, not automated. A near-real-time flag to the payroll team — confirmed or corrected by a person before the cycle closes — avoids wrongly withholding pay from someone on leave, off sick, or simply working off-network, and keeps the design clear of the legal restrictions around solely automated decisions that affect someone's pay.
- Build the safety net you'll always need. Dismissals and deaths-in-service will sometimes still land after cut-off, however good the trigger is. A rehearsed retro-processing path, plus a leaver-versus-pay-run reconciliation report each cycle, catches what prevention misses.
- Close the governance gap, not just the system gap. A defined SLA between manager, HR, and payroll — with a joint KPI (days between confirmed last day and system entry; percentage of leavers locked before cut-off) — addresses the behavioural and approval-chain delays that no amount of clever automation fixes on its own.
None of this gets an organisation to zero. Automating around genuinely unpredictable events isn't possible. But closing the resignation, redundancy, contract-end, and dismissal gaps — the majority of cases — is well within reach of most HRIS/payroll landscapes already in place today.
Over to HR and finance leaders
This sits at the intersection of HR operations, payroll, legal, and finance — which is exactly why it tends to fall between them. I'd be genuinely interested to hear from people who've tackled this in their own organisations:
- Has anyone built a branched, leaver-type-aware trigger like this — and did it hold up in practice?
- Where has your organisation's late-leaver overpayment actually come from most: resignations, redundancies, or dismissals?
- Is this something you've made a joint HR/payroll KPI — and did it change behaviour, or just shift the blame around?
If your organisation is still quietly living with it — Talks to us EX3.
Contact us
