Lab 101 — The Forge
You're not catching the fraud. You're committing it.
You are Derek Holt, Account Executive at Meridian Consulting Group.
You have a dinner receipt from January.
Your documented business trip to Houston was in June.
Your personal candy bar receipt is $1.29.
The reimbursement maximum is $10.
All it takes is one field. This lab shows you exactly how it's done —
and exactly how detection systems catch it.
This dinner happened on January 12. Your Houston client meeting was June 9–14. Concur requires expenses to match travel dates.
Change the date field from January to June. Same receipt, same total, same server. One digit different. The company reimburses $75.09 for a dinner that happened months before the trip.
This lab uses real receipts from forensic fraud training datasets. You will make the edits yourself. Then you'll watch the audit system flag you.
Bernie's Burger Bus
Drag the date slider to June. Submit your expense claim.
Target — Columbus, OH
Drag the amount slider to $7.29. Submit your expense claim.
Concur Audit Engine
Checking submission:
Both Claims Approved
Concur processed both submissions. $82.38 disbursed to Derek Holt's account.
Three Detection Layers
Standard expense tools pass forged receipts that look plausible on the surface. Here's the stack that catches them.
