Kickback Schemes in Construction Procurement: How They Work and How to Catch Them
A kickback scheme is one of the quietest forms of fraud a contractor can suffer, because nothing about it looks broken. Invoices arrive, work gets done, the project moves forward. There is no missing money in an obvious sense — every dollar is supported by a real invoice for real work. The loss is hidden inside the price. A buyer or project manager steered the award to a favored subcontractor or supplier, that vendor padded its bid, and the two of them split the markup. The contractor overpaid, the budget absorbed it, and the only victim was the margin.
Construction is unusually exposed to this. Procurement is decentralized across projects, individual buyers and PMs hold real discretion over who gets awarded, scopes are complex enough that price comparisons are hard, and the people negotiating are often far from the home office. Add the relationship-driven culture of the trades — where doing business with people you know is normal and often sensible — and the line between a trusted vendor and a corrupt arrangement gets blurry. This post explains how procurement kickbacks actually work in construction, the red flags that expose them, and the controls that make them hard to run.
The mechanics are simple. An employee with influence over awards — a buyer, an estimator, a project manager, a purchasing agent — has the power to decide, or heavily shape, which subcontractor or supplier wins work. A vendor offers that employee something of value to use that power in its favor. In return, the vendor wins awards it might not win on merit, and it recovers the cost of the bribe by charging more than it otherwise would. The contractor pays the inflated price; the employee and the vendor share the spread.
Common forms the scheme takes
- Bid steering — the buyer shapes the specification, timeline, or bid list so the favored vendor is the only realistic winner
- Bid rigging — competing bids are solicited only for show, sometimes with the favored vendor's help drafting losing 'complementary' bids
- Price inflation — the favored vendor wins legitimately but quietly raises unit prices, knowing the buyer will not push back
- Change-order abuse — a low initial bid wins the award, then padded change orders deliver the real profit where scrutiny is weakest
- Phantom or split scopes — the favored vendor bills for work that is duplicated, never performed, or carved up to stay under approval thresholds
The kickback itself does not have to be an envelope of cash, and rarely is. It can be a 'consulting fee' paid to a shell company the employee controls, free work on the employee's home, a no-show job for a relative, lavish entertainment and travel, or an ownership stake in the vendor that the employee never disclosed. The harder the benefit is to trace, the longer the scheme survives.
Roughly 0%
The share of annual revenue a typical organization is estimated to lose to occupational fraud, with corruption schemes such as kickbacks among the most common in construction (ACFE)
A kickback always has at least two sides: an insider with award authority and an outside vendor willing to pay for it. Understanding the roles helps you see where the control points belong.
It is whoever can move the award — and that is broader than the purchasing department. Estimators decide which subs go on the bid list and how scopes are written. Project managers approve subcontracts, sign off on change orders, and certify pay applications. Purchasing agents and buyers negotiate supplier pricing. Even a superintendent who can declare a unit-rate material 'the only thing that works on this job' is exercising procurement influence. Discretion plus low oversight is the risk profile, regardless of title.
On the other side is the subcontractor or supplier receiving steered work. They are frequently a real, competent company — which is part of the cover, because the work passes inspection and the relationship looks like a normal good one. What sets the favored vendor apart is a pattern: a win rate that does not match their competitiveness, prices that drift up without complaint, and an unusually close personal relationship with the insider steering the work.
No single indicator proves a kickback. Kickbacks reveal themselves as a cluster of patterns over time, which is why the most effective detection looks at procurement data in aggregate rather than one award at a time.
Patterns that warrant a closer look
- Single-bid awards, or 'competitive' bids where the same vendor always wins and the losing bids are suspiciously close in price or format
- One buyer or PM whose projects consistently route work to the same narrow set of vendors, while peers use a wider field
- A vendor's unit prices drifting steadily upward over successive jobs with no market explanation
- Bid lists, specifications, or timelines that appear written around one vendor's strengths
- Change orders concentrated with a particular vendor, especially right after a notably low winning bid
- Resistance to vendor rotation, competitive bidding, or any review of a favored vendor's pricing
- A buyer who handles a vendor relationship entirely alone and discourages others from contacting that vendor directly
- Visible lifestyle changes — a new vehicle, home renovations, expensive travel — that do not fit the employee's known income
The lifestyle red flag is real but it is a corroborating signal, not a starting point. Begin with the procurement data — award concentration, price trends, bid patterns. Lifestyle changes help confirm a suspicion the numbers already raised; they should never be the basis of an accusation on their own.
Most fraud controls are built to catch payments that should not have been made. A kickback defeats them because the payment is legitimate on its face — a real vendor, a real invoice, real work delivered. Three-way matching passes. The approval was given by someone with authority to give it. There is no duplicate, no ghost vendor, no altered document. The fraud is not in the transaction; it is in a decision made before the transaction, and that decision left no obvious trace.
Construction makes it harder still. Every project is unique, so there is no clean apples-to-apples benchmark for whether a price was fair. Scopes are technical, which lets a steered specification look like sound engineering judgment. And procurement authority is spread across many projects and many people, so a scheme confined to one PM and one vendor can run for years inside a single division without ever showing up at the company level — unless someone is deliberately looking across projects.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
You cannot eliminate the discretion that procurement requires — buyers and PMs need judgment to do their jobs. What you can do is constrain how that discretion is exercised, force decisions into the open, and make patterns measurable.
Require a genuine minimum number of independent bids above a defined dollar threshold, and require a documented, reviewed justification whenever a single-source award is used. Separate the people who write the specification and bid list from the people who evaluate the bids, so no one person controls the award end to end. A competitive-bidding policy that exists on paper but is routinely waived under deadline pressure provides no protection.
Maintain the approved vendor list at the company level, not in an individual buyer's head, and review it periodically. Where it does not compromise quality or schedule, rotate work across qualified vendors rather than letting one buyer-vendor pairing become permanent. Permanence is what lets a kickback relationship mature.
Require everyone with procurement influence to disclose, in writing and on a recurring basis, any financial interest in or personal relationship with a vendor — and to update the disclosure when something changes. Disclosure does not stop fraud by itself, but it sets a clear expectation, creates an accountability record, and turns a concealed relationship into an act of falsifying a company document, which strengthens any later case.
This is the control that actually surfaces kickbacks, because the scheme is a pattern and patterns live in data. Analyze procurement spend across all projects: award concentration by buyer and by vendor, win rates, unit-price trends for the same scope over time, change-order rates by vendor, and the share of single-bid awards by buyer. An outlier — one PM funneling work to one vendor at prices climbing faster than the market — is exactly the signal that a one-award-at-a-time review will never see.
When vendor and invoice data is centralized rather than scattered across project files, cross-project patterns become visible. A platform like Covinly that consolidates vendors and invoice history gives you the company-wide view a kickback scheme depends on you never having.
“We found it in the data, not in an accusation. One PM's projects showed the same three subs winning everything, with unit prices climbing about eight percent a year while the rest of our spend was flat. The pattern asked the question for us.”
— VP of Operations, commercial general contractor
If a pattern raises a real concern, resist two opposite mistakes: confronting the employee on a hunch, and pretending you never noticed. Both make things worse — one tips off the subject and invites a defamation problem, the other lets the scheme keep running and the loss keep growing.
Handle a suspicion deliberately
- Do not confront the employee or the vendor yet — premature confrontation destroys evidence and your leverage
- Bring it to leadership, and involve legal counsel early; a kickback investigation has employment-law and contract-law dimensions
- Quietly preserve the relevant records — bid files, award documentation, the vendor's pricing history, emails, change orders, approvals
- Build the picture from the data and documents before anyone is interviewed, and document the timeline as you go
- Consider whether the affected procurement decisions should be paused so the loss does not compound while the review runs
- Treat it as a control failure to be corrected, not only an individual to be removed — the gap that allowed it needs closing
Kickbacks thrive on three things: unchecked discretion, permanent buyer-vendor pairings, and the absence of a company-wide view of spend. Take those away — with real competitive bidding, vendor rotation, conflict-of-interest disclosure, and spend analytics that look across every project — and steering a corrupt award becomes difficult, visible, and risky. That combination is what protects the margin a kickback is quietly designed to take.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts