Fraud Risk along the Employee Lifecycle — Part 6: EXIT
When employment ends, what else ends?
The previous article, The Fraud Risk of Management Pressure and Control Override, examined how managerial authority influences decisions and the operation of controls.
EXIT follows that authority to the end of the employment relationship—and examines who takes responsibility for the work that remains.
An employee returns their laptop. HR records the departure. The corporate account is disabled.
Elsewhere, the same person may still be registered as a bank signatory, an administrator of an external service or an authorised contact for a supplier. An approval workflow may continue to route decisions to their name. An unresolved obligation may have no clearly identified successor.
For fraud risk assessment, it is useful to distinguish three events:
The employment relationship ends → authority is withdrawn → the withdrawal becomes effective.
These events may occur at different times. A documented departure does not, by itself, establish that every relevant capability has ended or that the remaining responsibilities have been accepted by someone able to fulfil them.
Access, authority and attribution
Residual access creates an opportunity that requires assessment. Its existence does not establish that anyone has used it improperly.
A review should distinguish:
- Capability: Could an account, credential or mandate still be used?
- Activity: Was it actually used after the relevant cut-off?
- Attribution: Who performed or initiated the action?
- Authorisation: Was the action permitted under a valid arrangement?
- Misconduct: Does the evidence establish deception, misappropriation or another breach?
This distinction matters where former accounts remain available to colleagues, automated processes or an external service provider. An action recorded under a former employee’s identifier does not necessarily identify the person who acted.
The resulting uncertainty can affect both the assessment of Access Rights Abuse and the fairness of an investigation.
A control reference for offboarding
The National Institute of Standards and Technology (NIST, USA) addresses personnel termination in SP 800-53 Rev. 5, control PS-4. It covers disabling access, revoking credentials, recovering relevant organisational property and retaining the organisation’s access to information previously controlled by the departing individual.
Control AC-2 connects account management with termination and transfer processes, including changes to shared credentials. PS-7 addresses notifications concerning relevant changes in external personnel. These are security and privacy controls to be selected and implemented in context; they do not establish a universal employment-law procedure. (NIST SP 800-53 Rev. 5, PS-4, AC-2 and PS-7)
The US federal Identity Lifecycle Management Playbook similarly treats departure as an event affecting the identity and its associated accounts and authenticators. This supports checking the full set of connected access rights when someone leaves. (Identity Lifecycle Management Playbook, Stage 3)
For this lifecycle analysis, the same question extends into business operations: Which decisions could this person still cause the organisation or an external party to accept?
The authority that sits outside IT
A practical review can distinguish several forms of continuing capability:
| Area | Question at exit |
|---|---|
| Financial authority | Have bank mandates, payment permissions and corporate purchasing arrangements been reviewed with their respective owners? |
| External representation | Could a supplier, customer or intermediary still reasonably treat the person as an authorised contact? |
| Operational approvals | Have open approvals and delegated responsibilities been assigned to an appropriate successor? |
| External platforms | Are separately managed portals and service accounts included in the departure process? |
| Information ownership | Can the organisation retrieve necessary records without continuing to operate through the former employee’s identity? |
These questions are an application of the lifecycle framework to business processes. The relevant actions depend on the organisation’s actual arrangements, contracts and jurisdictions.
For example, changing an internal role does not necessarily complete the separate steps required to change a bank mandate. Recording that a request was sent also differs from obtaining confirmation that the change has taken effect.
A practical example: the supplier portal
The following example is fictional.
A procurement manager leaves a trading company on Friday. Their laptop is returned and the corporate account is disabled that evening.
The company also uses an external supplier portal to manage rebates and credit balances. Access to that portal is administered separately. The departing manager remains registered as an authorised user.
On Wednesday, the supplier receives a request through the portal to refund a credit balance to a newly specified bank account. The request appears under the former manager’s identifier.
A finance employee notices that the requester has left and asks the supplier to pause the refund.
Several questions now require separate answers:
- When should the manager’s authority to submit such a request have ended?
- Who was responsible for notifying the supplier and removing portal access?
- Was the request made by the former employee, someone using their credentials or another authorised person?
- Was there a genuine commercial reason for the refund and the changed destination?
- Had any continuing role been agreed and documented?
- Who had accepted responsibility for the outstanding credit balance after the departure?
The active account establishes a control gap. It does not establish who submitted the request or whether the request was fraudulent.
A reliable assessment would connect the departure and handover records, portal permissions, supplier communications, authentication records and the underlying credit balance.
Closing the responsibility gap
An employee’s departure also creates a question of continuity: who becomes accountable for the responsibilities that remain?
An outstanding supplier claim still needs a decision. A recurring control still needs to be performed. A contract renewal still has a deadline. An unresolved concern still requires follow-up.
If these responsibilities are not explicitly transferred, the organisation can lose oversight even when the departing employee’s access has been removed correctly.
For this lifecycle analysis, responsibility transfer is a control activity in its own right.
A useful handover identifies:
| Element | What should be established |
|---|---|
| Responsibility | The specific process, decision, control or obligation being transferred. |
| Receiving owner | A named person who will be accountable from a defined point in time. |
| Open matters | Outstanding transactions, commitments, exceptions, concerns and deadlines. |
| Ability to act | The information, authority, access and capacity required to fulfil the responsibility. |
| Acceptance | Confirmation that the receiving owner understands and accepts the handover, including any unresolved gaps. |
Assigning a responsibility to “Finance” or “the team” may leave uncertainty about who must act. Naming a successor is also insufficient if that person cannot identify the open matters or exercise the necessary authority.
In the supplier-portal example, removing the former procurement manager’s access would address one exposure. A complete handover would also identify who now owns the outstanding credit balance, who may request a refund and who independently verifies any change to payment instructions.
The successor should receive a record of the unresolved balance and acknowledge responsibility for its follow-up. Required approvals and separation of duties should remain intact.
Where no permanent successor is available, an interim owner should be appointed with a defined scope and review date. Any responsibility that cannot yet be accepted should remain visible to the manager accountable for resolving the gap.
The handover record also creates a useful forensic boundary. It helps establish who held which responsibility at the relevant time, what information was available and which unresolved issues were communicated. Acceptance of future responsibility does not, by itself, establish responsibility for earlier conduct.
For each responsibility that survives the departure, the organisation should be able to identify who has accepted it, when the transfer takes effect and whether that person can fulfil it.
Making completion verifiable
The Software Engineering Institute at Carnegie Mellon University (USA) recommends a coordinated termination procedure in its Common Sense Guide to Mitigating Insider Threats. Best Practice 20 describes a checklist that identifies tasks, responsible persons, verification and completion timing. It also emphasises consistent and respectful treatment of departing personnel. (SEI, 2022, Best Practice 20, pp. 131–134)
Applied to the supplier example, a useful completion record would distinguish:
| Recorded step | Evidence of completion |
|---|---|
| HR notified the responsible business owner. | Notification and acknowledgement, with the effective departure time. |
| The supplier was asked to remove the authorisation. | Confirmation identifying the affected user and the effective change. |
| Open credit balances were reassigned. | A named successor and a documented handover of outstanding matters, with acceptance of responsibility. |
| The exception was resolved. | Verification that the former authorisation no longer permits the relevant action. |
An unresolved item should remain visible, with an owner and a defined response. Marking the overall departure as complete should not make an outstanding financial authorisation or an unassigned responsibility disappear from view.
Continuing work requires a defined new arrangement
Sometimes an employee leaves and returns as a consultant, adviser or temporary project resource.
That transition raises a new authorisation question.
Which tasks remain necessary? Who commissions the work? Which access and approval rights does the new role require? When will they expire?
Simply keeping the previous employee profile active can carry old responsibilities into a substantially different relationship. Conversely, removing every technical dependency without planning the transition can disrupt legitimate operations.
The review should therefore distinguish the person’s former employee authority from any newly approved mandate. The new arrangement needs its own scope, accountable owner and end or review date.
Protecting records while ending access
Offboarding also changes the availability of evidence.
A returned device may be reassigned. A mailbox may be deleted. A licence may be cancelled before relevant records have been transferred or preserved.
Where a specific concern has arisen, those routine actions can affect the ability to reconstruct events.
NIST SP 800-86 describes a forensic process that includes identifying relevant data, planning acquisition, checking integrity and documenting custody and handling. It also requires consideration of the authority and legal context for collection. The publication dates from 2006; its relevance here is the underlying preservation process, rather than instructions for current cloud platforms. (NIST SP 800-86, sections 2.5 and 3.1)
For an exit review, this means coordinating access removal with any justified preservation requirement. The record should explain what was preserved, why, by whom and under which authority. Together with the handover record and the relevant Audit Trail, it can help reconstruct decisions and responsibility at the relevant time.
Preservation should not become an indefinite archive of everything an employee ever did. Its scope and duration need a defined purpose, appropriate access restrictions and review against applicable retention and deletion requirements.
Reviewing concerns fairly
A departure, disagreement or move to a competitor does not establish dishonest intent.
Similarly, a large download shortly before departure could reflect an authorised handover, routine synchronisation or an improper transfer. The assessment needs the underlying facts.
Useful questions include:
- What information was involved?
- Was the activity consistent with the person’s role and assigned handover?
- Where did the information go?
- What permission existed at the time?
- Which alternative explanations fit the available evidence?
Any monitoring or investigation should have an established purpose and lawful scope. An organisation’s interest in protecting information does not automatically authorise access to private accounts or personal devices.
A sound review should preserve evidence that contradicts a suspicion as carefully as evidence that supports it.
What EXIT reveals about the earlier phases
An incomplete exit can expose weaknesses that began much earlier.
An unknown account may reflect incomplete onboarding records. An obsolete approval right may have survived several role changes. A shared identity may make individual actions difficult to reconstruct. Dependence on one employee may reveal an unresolved ownership problem.
EXIT therefore provides a final test of the preceding lifecycle:
Can the organisation identify, end or explicitly reauthorise the capabilities it previously granted—and demonstrate that the remaining responsibilities have been accepted by people able to fulfil them?
For this framework, completion means that former capabilities have been brought to a controlled end or explicitly reauthorised, while continuing responsibilities have a documented and accepted owner.
That question brings HIRE, ONBOARD, MOVE, REWARD, MANAGE and EXIT together. Each phase changes facts on which Internal Controls depend. The lifecycle helps locate those changes and connect them to evidence for Fraud Risk Assessment.
This article completes the six phase-specific examinations introduced in The Employee Lifecycle as a Lens for HR Fraud Risk. The framework remains a practical structure for analysis, rather than a prediction of individual misconduct.
Related glossary concepts
Sources and references
- Joint Task Force. (2020). Security and Privacy Controls for Information Systems and Organizations. NIST SP 800-53 Rev. 5. Particularly AC-2, PS-4 and PS-7.
- Federal Identity, Credential, and Access Management. Identity Lifecycle Management Playbook. Particularly Stage 3: Deletion (Deprovisioning/Revocation). Accessed 13 November 2026.
- Software Engineering Institute. (2022). Common Sense Guide to Mitigating Insider Threats, Seventh Edition. Carnegie Mellon University. Best Practice 20, pp. 131–134.
- Kent, K., Chevalier, S., Grance, T., & Dang, H. (2006). Guide to Integrating Forensic Techniques into Incident Response. NIST SP 800-86. Particularly sections 2.5 and 3.1.
