Concur Detect Demo [updated] -

The demo showed a receipt that looked fine to the human eye. Detect gave it a 12% integrity score. Why? The metadata showed the PDF was created in Photoshop, not by the restaurant. The employee had edited the tip amount. Caught.

Within three seconds, the screen flashed concur detect demo

A $450 dinner receipt at a high-end steakhouse. The Employee: A mid-level manager. The Policy: Dinner limit is $100 per person (including tip). The demo showed a receipt that looked fine to the human eye

[Link to SAP Concur Detect Demo Request] Have you run a fraud audit on your T&E data recently? What is the strangest expense you have ever seen approved by accident? Let me know in the comments. The metadata showed the PDF was created in

I recently sat through a live demo of Concur Detect. Here is exactly what happened, what it caught, and why it changes the game. In the demo, the facilitator ran a standard expense report through a legacy system first. The result? Green lights everywhere. The amounts matched the receipts. The categories were correct. The total was under the limit.

Why? The legacy system checked math . Concur Detect checked context . Here is the specific "gotcha" the demo revealed:

You aren't just auditing expenses. You are playing detective with a time machine that only works backwards.