Fraud Risk along the Employee Lifecycle — Part 5: MANAGE
From incentives to management decisions
The previous article, The Fraud Risk of Incentives and Performance Targets, examined whether rewards remain connected to genuine, eligible and sufficiently evidenced achievements.
MANAGE follows that question into everyday decisions.
An employee questions a transaction. A manager requests an urgent exception. A control owner refuses to approve incomplete documentation. A colleague reports a concern involving someone influential.
What happens next?
For this lifecycle analysis, management includes supervision, performance assessment, allocation of responsibilities, disciplinary decisions and the handling of disagreements. These activities influence who can challenge a decision and what consequences may follow.
A useful sequence to examine is:
Managerial instruction → employee response → control decision → escalation → organisational consequence
Each step can leave evidence of how the organisation handles competing priorities.
When authority changes the operation of a control
A manager may have authority to approve a transaction without having authority to disregard the conditions governing that approval.
This distinction matters when assessing Control Override.
In financial statement auditing, PCAOB AS 2401 identifies management’s ability to manipulate accounting records and circumvent otherwise functioning controls as a particular fraud risk. It also recognises that management may involve employees in carrying out the conduct. These observations concern financial reporting; their application to other operational processes requires a separate assessment. (PCAOB AS 2401, paragraphs .08 and .57)
For the employee lifecycle, the practical question is how managerial authority affects the evidence and challenge behind a decision.
| Situation | What deserves examination |
|---|---|
| A manager uses a defined exception procedure. | Whether the procedure permits the exception, the decision-maker is authorised and the required safeguards are applied. |
| A manager gives an instruction outside their delegated authority. | Whether the instruction is recognised as an exception and referred to someone authorised to decide. |
| Employees are asked to record a check as completed before it has occurred. | Whether the resulting record misrepresents what was actually verified. |
| A second approver accepts a decision because a senior manager supports it. | Whether the second approval includes a substantive review or merely repeats the first decision. |
| A temporary workaround becomes the usual process. | Whether repeated use has changed the control arrangement without an explicit review. |
These situations are not equivalent. A properly governed exception may be necessary. An unauthorised deviation may reflect misunderstanding or poor process design. Deliberately creating a false record raises a different concern.
The assessment needs to establish what happened, what the applicable rules allowed and what the participants understood.
Leadership becomes visible in specific decisions
Tone at the Top becomes tangible when employees see how leaders handle an inconvenient result, an influential colleague or a delayed transaction.
The Evaluation of Corporate Compliance Programs issued by the United States Department of Justice (DOJ, USA) considers the conduct of senior and middle management, including whether their commitment to compliance persists when business objectives compete with it. This is US prosecutorial guidance, not a globally binding management standard. (DOJ, September 2024, section II.A)
Within the lifecycle review, performance discussions deserve particular attention.
An employee may be formally responsible for checking supporting evidence while being informally criticised for slowing down approvals. A supervisor may expect staff to escalate unusual activity while treating escalation as evidence that they cannot manage their workload.
The resulting conflict can be examined through concrete questions:
- Does the employee have enough time and information to perform the assigned control?
- Can an unresolved issue be recorded without being treated automatically as poor performance?
- Do appraisal criteria distinguish avoidable delay from justified challenge?
- Can someone question a manager’s instruction through a route that the same manager does not control?
These questions connect HR processes directly to the operation of Internal Controls.
Why people may remain silent
A reporting channel can be available while employees remain reluctant to use it.
Two research perspectives help explain why.
Amy Edmondson’s study of 51 work teams in a manufacturing company found an association between team psychological safety and learning behaviour. Psychological safety concerns employees’ shared expectations about the interpersonal consequences of asking questions, acknowledging mistakes or raising difficult issues. The study examined team learning; it did not measure the effectiveness of fraud prevention programmes. (Edmondson, 1999)
Morrison and Milliken developed a conceptual model of organisational silence: conditions in which employees collectively withhold concerns about organisational problems. Their analysis examines how management practices and shared interpretations can make speaking up appear risky or ineffective. It is a theoretical explanation, rather than an estimate of fraud prevalence. (Morrison & Milliken, 2000)
For fraud risk assessment, these perspectives suggest examining two distinct expectations:
What might happen to me if I raise this concern?
What is likely to happen to the concern itself?
An employee may fear an adverse appraisal or loss of responsibility. Another may expect no personal disadvantage but see little purpose in reporting something that previous reports failed to resolve.
Neither silence nor a low complaint count establishes that an organisation is free of misconduct. Equally, a high reporting volume does not establish that misconduct is widespread. Numbers require context.
A practical example: the urgent supplier payment
The following example is fictional.
An industrial company needs a replacement component before a planned production shutdown. A supplier requests an advance payment.
The accounts payable employee notices that the bank account differs from the supplier master record. The procedure requires independent verification before the change can be accepted.
The operations manager insists that the payment must leave that afternoon. The employee is told to mark the verification as complete and obtain confirmation afterwards.
The employee raises the concern with their line manager. The response focuses on the operational consequences of delay. No one documents who is authorised to accept the exception or how the account will be verified.
The payment is released. Later, during a performance discussion, the employee is criticised for being insufficiently responsive to business needs.
Several issues require separate assessment.
The urgency may have been genuine. The changed account may have been legitimate. The performance criticism may have involved additional circumstances. None of those possibilities removes the need to examine why an unperformed check was recorded as complete.
A focused review would distinguish:
- Whether the payment destination was valid.
- Whether the exception was authorised and accurately recorded.
- What each participant knew when the payment was released.
- Whether the employee’s challenge influenced the subsequent appraisal.
Even if the payment reached the correct supplier, the control record would still warrant review. A favourable transaction outcome does not establish that the decision process was reliable.
Making exceptions reviewable
For this lifecycle review, exception handling should make the actual decision visible.
In the supplier example, a useful record would identify the outstanding verification, the reason for urgency, the person authorised to decide, any alternative checks and the point at which the remaining issue must be resolved.
The record should distinguish accepting a documented residual risk from claiming that a safeguard has been performed.
Repeated exceptions also deserve examination as a group. If the same verification is routinely postponed, possible explanations include an impractical procedure, insufficient staffing, poor planning or deliberate avoidance. The organisation needs to establish which explanation fits the evidence.
The objective is a process in which operational difficulties can be addressed without making the underlying facts less reliable.
Handling concerns without prejudging the outcome
The DOJ guidance examines trusted reporting mechanisms, protection against retaliation and independent, objective investigations. It also addresses consistent consequences for established misconduct. These provide useful reference points for assessing how concerns are handled. (DOJ, September 2024, sections I.D and II.C)
Applied to the fictional case, the employee should have a route for raising the issue beyond the people whose decisions are being questioned.
The review should distinguish the content of the concern from unrelated performance matters. If an adverse appraisal follows a report, timing is relevant evidence, but does not by itself prove Whistleblower Retaliation. Earlier assessments, stated criteria, comparable decisions and the explanations of those involved may help clarify the relationship.
The same care applies to the person accused of bypassing a control. An allegation is a starting point for examination. It is not an established finding.
A credible process should be capable of correcting an unsupported allegation as well as substantiating a well-founded one.
Specific legal protections, confidentiality requirements and employment procedures vary by jurisdiction. The organisational recommendations here do not define a universal legal entitlement.
Signals that warrant closer examination
The following observations can help identify where management practice deserves a more detailed review:
- The same manager repeatedly requests exceptions without resolving their underlying cause.
- Approval records describe checks that the responsible employees say they did not perform.
- Concerns about a manager are repeatedly returned to that manager for final closure.
- Appraisal comments criticise employees for raising documented control issues.
- Similar conduct receives materially different treatment depending on seniority or commercial importance.
- Matters described as resolved continue to reappear in operational records.
These are review signals, not findings of fraud.
Different treatment may reflect different facts. A repeated exception may expose a poorly designed process. A complaint may be mistaken. The assessment should test plausible alternatives and identify what evidence would support or contradict them.
For Fraud Risk Assessment, the value lies in connecting the observations rather than turning each one into an accusation.
What matters in a forensic review
A forensic review needs to reconstruct the decision environment at the relevant time.
| Evidence | What it can help establish |
|---|---|
| Delegations, approval limits and procedure versions | What each participant was authorised and expected to do. |
| Workflow history and exception records | Which safeguards operated, which were bypassed and how deviations were represented. |
| Relevant instructions and communications | What was requested, questioned or explained before the decision. |
| Reporting and escalation records | Who received the concern, how it was assessed and why it was closed or referred. |
| Appraisals and responsibility changes | Whether subsequent employment decisions have a documented basis and how they relate to the concern. |
| Comparable cases and remediation records | Whether the response was consistent and whether identified weaknesses were addressed. |
A system Audit Trail may identify the person who entered an approval. It may not reveal who instructed that person to act or what information was available to them.
Likewise, a written instruction may establish that a manager requested an action without establishing that the employee carried it out.
The analysis should keep authority, instruction, execution, knowledge and benefit distinct. Evidence should be obtained through authorised processes and assessed for both incriminating and exculpatory explanations.
Where MANAGE fits in the lifecycle
The earlier phases establish identity, access, authority and incentives. MANAGE examines how these arrangements operate when people exercise judgement, face competing demands and challenge decisions.
The central question is:
Can someone insist on a necessary control, record an unresolved problem or challenge an instruction—and have the issue assessed fairly?
Answering it requires looking at actual decisions: exceptions, approvals, appraisals, reporting routes and responses to concerns.
The next phase, EXIT, examines what happens when the employment relationship ends, including residual access, continuing authority and the handling of information.
This article forms part of The Employee Lifecycle as a Lens for HR Fraud Risk. The lifecycle provides an organising framework for practical analysis, rather than a predictive model of individual misconduct.
Related glossary concepts
- Control Override
- Tone at the Top
- Internal Controls
- Whistleblowing
- Whistleblower Protection
- Whistleblower Retaliation
- Fraud Risk Assessment
- Audit Trail
Sources and references
- PCAOB. AS 2401: Consideration of Fraud in a Financial Statement Audit. Paragraphs .08 and .57.
- United States Department of Justice (DOJ, USA), Criminal Division. (2024). Evaluation of Corporate Compliance Programs. Updated September 2024; sections I.D, II.A and II.C.
- Edmondson, A. (1999). Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly, 44(2), 350–383.
- Morrison, E. W., & Milliken, F. J. (2000). Organizational Silence: A Barrier to Change and Development in a Pluralistic World. Academy of Management Review, 25(4), 706–725.
