Anti-Corruption & FCPA Scenario

The Clean-Looking Invoice

A finance analyst finds every red flag of third-party bribery on an invoice her manager already approved. What does she do?

Quick Answer

What should an employee do when a “consulting fee” invoice raises red flags for third-party bribery?

When an invoice carries the classic markers of corruption risk — a vague scope, round-number amounts kept just under an approval threshold, and a third-party intermediary tied to a government official — an employee should not process it on the strength of a manager’s approval. The right move is to hold the payment and escalate the pattern through a compliance channel outside the local chain of command. Under the FCPA, “I was told to pay it” is not a defense, and looking away from obvious red flags can be treated as knowing.

Pressure Type: Authority + Relationship + Speed

The invoice is already approved by her manager. The payment protects the region’s biggest contract. And she is asked to process it today, to keep a “delicate relationship” smooth. Three pressures, all pointing in the same direction: just pay it.

The Situation

Iris Moreau is a finance analyst in Marrenford Industrial’s regional office in the Republic of Veturia. On her screen is the fourth invoice this quarter from a firm called Halvorne Advisory: $48,000 for “strategic advisory services.” One line of description. A round number — and, she notices, just under the $50,000 mark that would force a second signature.

All four invoices trace back to the same deal: the national infrastructure contract Marrenford just won in Veturia, the one leadership keeps calling a company-maker. It is roughly 12% of Marrenford’s projected global revenue for the year.

Last week, a colleague mentioned — half-jokingly — that Halvorne’s principal is the brother-in-law of someone senior at the ministry that awarded the contract. Iris didn’t think much of it then.

Her manager, regional controller Owen Pratt, has already approved the invoice. He stopped by her desk this morning: “Get that one out today. The relationship over there is delicate — let’s not make waves.”

The payment is queued. Her cursor is on Approve.

You’re already doing it. If reading this made you think, “our finance team would never just pay that,” pause there. That reaction is the exact reflex this scenario is built to surface. Everyone spots the bribe in a calm room with the red flags listed out. The question isn’t whether your team knows better. It’s whether the pressures that make “just pay it” feel reasonable — an approved invoice, a star contract, a manager saying don’t make waves — exist somewhere in your organization right now.

What Should Iris Do?

Choice A — Process the payment

It’s approved by her manager, the invoice is documented and coded correctly, and second-guessing the region’s biggest contract isn’t an analyst’s job.

Choice B — Hold the payment and escalate the pattern

Document what she sees — vague scope, round numbers under the threshold, a third-party tied to the awarding official — and raise it to Compliance through a channel outside her regional reporting line.

Choice C — Ask Pratt once, then let it go

Raise the concern with Pratt. When he says the vendor has been vetted and tells her to process it, accept that, and pay.

The Right Call

For Iris: Choice B

The combination in front of her — a third-party intermediary, a vague scope, round amounts structured just under the approval threshold, and a consultant tied by family to the official who controls the contract — is a textbook FCPA third-party red-flag pattern. The law does not require proof that she knew the money was a bribe; under the “knows or has reason to know” standard, processing the payment anyway can itself create exposure.

She escalates outside the local chain on purpose: the local chain is where the pressure is coming from. A report routed back through the people who approved the payments can quietly die. Documenting the pattern and raising it to group Compliance or the hotline protects the company — and protects Iris.

Why It’s Harder Than It Looks

The paperwork is technically clean.

Corruption rarely arrives as a smoking gun. It arrives as an ordinary, approved payment with a vague description. The cleanliness is the camouflage, which is exactly why “the invoice looks fine” is not the same as “the payment is fine.”

She’d be questioning the company’s star.

The contract is the region’s crown jewel and a chunk of global revenue. Flagging the payments feels like accusing the most celebrated deal — and the most celebrated people — in the building.

The pressure comes from her own manager.

Escalating means going around — or over — the person who signs her review. “Let’s not make waves” is not a threat. It is the gentle, deniable way in which silence is manufactured.

Doing nothing feels like the safe choice.

Processing an approved invoice feels low-risk in the moment. Under the FCPA’s books-and-records and “reason to know” standards — for a payment a public company recorded as a clean “consulting fee” — it can be the opposite.

Scenario Vehicle

A consulting invoice

What It’s Really About

Third-Party Governance and the Courage to Escalate

The real lesson is not about invoice formatting. It is about recognizing that “approved and papered” is not the same as legitimate — and that the duty to escalate has to survive contact with your own manager.


Frequently Asked Questions

Is paying a third-party consultant illegal under the FCPA?

No — legitimate consultants are normal and lawful. The risk is paying an intermediary when you know, or have reason to know, that the money will reach a government official to win or keep business. Red flags like a vague scope, a consultant related to the official, and pressure to pay fast are what trigger the duty to stop and ask questions.

Iris didn’t pay a bribe herself — is she really exposed?

Processing a payment despite obvious red flags can be treated as deliberately ignoring what the facts suggested. And recording a suspected bribe as a clean “consulting fee” is itself a books-and-records problem for a public company. Escalating is what protects both Iris and the organization.

Her manager already approved it. Doesn’t that settle it?

No. A manager’s approval does not cure a corruption red flag, and “I was told to” is not a defense. When the person applying the pressure is the same person who approved the payment, that is a reason to escalate higher — not a reason to stop.

Why escalate outside the local office?

Because the local chain is where the pressure originates. A report routed back through the managers who approved the payments can quietly disappear. A channel outside that chain — group compliance or the hotline — protects the integrity of the report and the person who made it.

How to Use This Scenario in Training

Use it in onboarding and refreshers for finance, accounts payable, and procurement teams — especially those supporting higher-risk markets — and in anti-corruption modules for any employee who touches third-party payments. The strongest facilitation prompt is not “what are the red flags?” but “what would make it hard for you to hold this payment, and who would you escalate to if your own manager was the one pushing?”

This scenario is also the front-line companion to the Executive Decision Lab™ “The Consulting Fee”, which puts the leadership team in the room months later, once a report like Iris’s has surfaced and the clock is running.

More Scenarios

Cluster

Anti-Corruption & FCPA Scenarios →

Gifts, facilitation payments, consulting fees, and third-party pressure in global business.

Related Cluster

Third-Party Risk Scenarios →

Vendor due diligence under pressure, distributor red flags, and supply-chain integrity.

Executive Companion

The Consulting Fee — Executive Decision Lab →

The 90-minute leadership session begins the day a report like this one lands on the hotline.

Build the reflex before the invoice lands

Xcelus scenario-based training turns policy awareness into recognition — so the right call is the reflex, not the afterthought. It applies the Decision Readiness Engine™ to the moments that actually create risk.

Get in Touch →

© 2005–2026 Xcelus LLC. All rights reserved.