Scenario-Based Compliance Training
Accurate Records & Financial Integrity Scenarios
Two realistic workplace situations where employees face pressure — or the temptation — to falsify financial records. Each scenario illustrates why a small adjustment to a record is never as harmless as it seems.
Quick Answer
Why do accurate records and reporting scenarios matter in compliance training?
Most financial record falsifications start with a rationalization that sounds reasonable — the expense was real even if the receipt is missing, the deal was agreed before quarter-end even if the paperwork wasn’t. The employee isn’t thinking about fraud. They’re solving a problem. These scenarios build recognition that the solution they’ve chosen violates the policy, regardless of the underlying facts.
Three Ways to Use These Scenarios
|
Embed in a Course Add to a full Code of Conduct or financial integrity course to address recordkeeping obligations directly. |
Deploy as Reinforcement Push before quarter-end when expense reporting pressure peaks — the moment these situations are most likely to occur. |
Add to Existing Training Layer onto any existing compliance program as reinforcement — effective for finance, sales, and field employee populations. |
Expense Records
I Lost a Receipt and Inflated My Mileage Claim to Cover It. Is That Really a Problem?
An employee genuinely spent $75 on a business entertainment expense but lost the receipt. To recover the loss, they inflate their mileage claims the following month by an equivalent amount. The expense was real. The amounts balance out. The employee doesn’t see themselves as committing fraud.
Why it’s harder than it looks: The employee’s reasoning — “the money was spent, I’m just recording it differently” — is internally consistent. But submitting inflated claims to offset a real loss is a false record, regardless of the underlying expense. There is no good-faith exception for falsification even when the amount is accurate in aggregate.
Right call: Report the lost receipt and follow the proper process. Absorb the loss if necessary — don’t create a false record to avoid it.
Sales Records — Manager Pressure
My Supervisor Asked Me to Backdate a Receipt to Count Toward the Quarter. Is That Okay?
A supervisor asks an employee to backdate a cash receipt by 2 days so a deal counts toward the current quarter’s sales figures, affecting bonus calculations. The supervisor says the deal was verbally agreed upon before quarter-end. “It’s just an administrative correction.”
Why it’s harder than it looks: A verbal agreement before quarter-end feels like it should count — and the supervisor’s framing as an “administrative correction” is designed to make it seem harmless. But a verbal agreement is not a financial record. Changing a document date to affect quarterly reporting is falsification regardless of what was verbally agreed. The employee who does it — not just the supervisor who asked — is responsible for the false record.
Right call: Decline and consult finance. Documenting your objection while proceeding does not create a compliance safe harbor.
What These Scenarios Have in Common
Both scenarios involve falsification driven by a rationalization that sounds reasonable. The money was real. The deal was real. But a false record created to resolve a real problem is still a false record — and the employee who creates it is accountable regardless of the circumstances that prompted it.
“There is no good-faith exception for falsification.” That’s the principle both scenarios are designed to make concrete, particularly when the pressure comes from a manager.
More Scenario Clusters
|
Reporting & Non-Retaliation Three scenarios covering reporting obligations, retaliation patterns, and the false complaint myth. |
Anti-Corruption & FCPA Six scenarios covering bribes, kickbacks, government officials, and FCPA red flags. |
Full Scenario Library Browse all compliance training scenarios across every topic area. |
Want These Scenarios in Your Program?
These scenarios can be embedded in a new course, deployed as reinforcement before quarter-end when record falsification risk peaks, or added as a layer on top of your existing compliance program.