The fraud tax is already in your budget. You’re just calling it something else.

Bottom line

Most organizations are already paying for candidate fraud. The cost shows up as churn, rework, early replacements, and delivery slippage — not as a fraud line item. Procurement has the tools to make this visible and govern against it.

The problem with waiting for an incident

Most organizations treat candidate fraud governance as something that activates after a high-impact event. A payroll diversion. An access breach. A substitution scheme that gets exposed. Before that, the costs sit across teams and categories, and no one connects them.

They show up as repeated screening and resubmission cycles. Non-productive starts. Early replacements. Project delays from false capacity. Time-to-fill restarts after a role falls through. Teams treat each instance as a bad hire, a performance issue, or a market quality problem. Without measurement, it becomes normal variance.

Procurement already has the lens for this. Managing third-party risk by reducing variance is the job. The question is whether fraud-related cost is being treated as a distinct category worth measuring, or absorbed quietly as ordinary friction.

A field example

A simple model: The cost continuum

Use this to align stakeholders without arguing about intent. The value of the continuum is that it gives buyers a framework for naming costs they have been absorbing without language for them.

Procurement impact comes from reducing Level 1 through 3 before Level 4 forces a crisis response. Most organizations have decent visibility into Level 1. They are absorbing Level 2 and 3 without measurement. Level 4 is the one no one plans for — which is usually the wrong time to start.

What procurement can measure in 30 to 60 days

You do not need perfect attribution to take action. Start with two indicators most organizations can already access:

As your measurement matures, add:

• Cycle churn: requisitions reopened due to early failure or concerns 
• Disputed outcomes: invoicing disputes, ownership disputes, questions about who verified what 

Questions worth asking internally

These questions are designed for program leaders and procurement executives who want to understand where their exposure sits before an incident makes the question urgent.

1. When a contingent placement fails in the first 60 days, what category does it land in — bad hire, performance issue, or fraud indicator? Who decides?
2. Do you know your start failure rate by supplier and channel, or only in aggregate?
3. Has anyone mapped which sourcing channels have the least consistent verification? Is that also where your highest-risk roles sit?
4. If a Level 3 incident happened last year — a delayed project traced back to a worker delivering at 60% capacity — would anyone have recognized it as fraud-related, or is it sitting in a project delay budget somewhere?
5. When did you last review early replacement data by supplier? What did it show?

Start here

Baseline your start failure and early replacement rates by supplier and channel. The variance will tell you where minimum standards will have the most impact. You do not need to prove fraud intent to act on the data — the pattern is enough to justify tighter requirements.

If any of this maps to what you’re seeing in your program, I’m happy to compare notes. You can reach me at [email protected]  or connect with me on LinkedIn.