From the TIKC Advisory Team · Compliance & Regulatory Alerts
A $29.5 Million Reminder That Your Certifications Have to Be True
A major defense contractor just agreed to pay $29.5 million over allegations that it certified compliance with federal rules it was not actually following. The…

Published 2026 | TIKC NewsWire
A major defense contractor recently agreed to pay about $29.5 million to resolve claims from the government, split between a $22 million False Claims Act settlement with the Justice Department and a $7.5 million agreement with the EEOC. The government alleged the company certified that it was following federal anti-discrimination requirements while its actual employment practices did not match those certifications. You can set aside the politics of the underlying topic. The part that matters for every contractor, large or small, is simpler and more important: when you certify compliance with a federal rule, that certification is a legal promise, and the government can sue you under the False Claims Act if it is not true.
Why a paperwork promise became a $29.5 million problem
The False Claims Act does not only cover padded invoices. It also covers the certifications that sit behind your right to be paid. When you take a federal contract, you certify compliance with a long list of requirements, from labor and employment rules to cybersecurity to sourcing. The government’s theory in cases like this is that if you certified compliance you did not actually have, every payment you collected was tainted by a false statement. That is how an employment matter turns into a False Claims Act case instead of just a labor dispute.
The certifications you sign without reading
Here is the uncomfortable part for small contractors. You sign these certifications constantly, often without reading them. Your registration in the government’s system carries a stack of representations. Each contract adds more. Most owners treat them as paperwork to click through so they can get to the work. But a certification you did not read is still a certification you made. If it says you comply with a rule you are quietly ignoring, you have the same exposure the headline contractor just paid millions to resolve.
The pattern across every recent case
Look at the enforcement wave as a whole and one theme repeats: contractors getting caught not for the work, but for what they said about the work. Cybersecurity certifications that overstated protection. Sourcing certifications that hid where parts came from. Now employment certifications. The common thread is the gap between what you promised and what you did. Closing that gap, on every rule you certify, is the same defense whether the subject is a written certification or a quiet assumption no one checked.
What to do now
- Read what you certify. Before you sign or submit, know which rules you are promising to follow.
- Match practice to promise. For every certification, confirm your company is actually doing what it says.
- Review your SAM representations. The reps and certs in your registration are promises too, and they need to stay accurate.
- Fix gaps before you bid. If a certification would not be true, close the gap first instead of certifying and hoping.
- Keep proof of compliance. Document how you meet the rules you certify, so you can show it if asked.
You do not need a compliance department to survive this enforcement wave. You need to treat every box you check as what it legally is: a promise the government can hold you to. Read your certifications, make them true, and keep the proof, and the risk that is costing other contractors millions becomes something you simply do not have. Brick by brick.
FAQ
How can an employment issue become a False Claims Act case?
When a contractor certifies compliance with federal employment requirements to get or keep a contract, and that certification is not true, the government can argue the payments it made rested on a false statement. That is what moves the matter from a labor dispute into False Claims Act territory.
Does this only affect big defense contractors?
No. The legal principle applies to any contractor that signs certifications, which is all of them. Small firms often have more exposure because they click through certifications without reviewing them.
What certifications should I worry about?
All of the ones tied to payment: your SAM representations, labor and employment rules, cybersecurity, sourcing, and any contract-specific certifications. The risk is any promise you made that does not match what you actually do.
How do I protect my company?
Read your certifications, confirm your practices match them, fix any gaps before you certify, and keep documentation showing how you comply. Accuracy is the entire defense.
Sources
U.S. Department of Justice. (2026). Settlement resolving False Claims Act allegations tied to contractor employment-practice certifications.
U.S. Equal Employment Opportunity Commission. (2026). Agreement providing monetary relief to affected employees.
This article is general information, not legal advice.
About the Author
TIKC Staff Writer
Team Integrity Knowledge Center is a GovCon education and consulting platform helping small, women-owned, and minority-owned businesses win and keep federal and state contracts with plain-English guidance. Build, grow, scale, brick by brick. Contact
Your next step
Talk it through with a TIKC advisor
Continue reading
Related stories

When Your Costs Rise Mid-Contract: Economic Price Adjustment Clauses
A fixed-price contract can turn into a money-loser when material costs spike. An Economic Price Adjustment clause is the built-in tool that lets your price…

Personal Services and the Line a Contractor Cannot Cross
A contract can be legal to win but illegal to perform if the government ends up supervising your people like employees, or if you start…

Doing Extra Work for Free? The Changes Clause and Getting Paid for It
The government can direct you to change the work mid-contract, and sometimes it changes the work without ever saying so. The Changes Clause entitles you…

Your Invoice Is a Legal Claim: Getting WAWF Right
On most defense contracts you bill through an electronic system called WAWF, and every invoice you submit is a formal claim for payment. A sloppy…
SBIR Data Rights: The Protection Most Small Innovators Give Away by Accident
If you win an SBIR or STTR award, the research you create comes with special data-rights protection the government does not get with most contracts…

The Government Just Told You to Stop. Now What?
A stop-work order can freeze your contract overnight, and what you do in the first few days decides whether you get paid for the disruption…
After a Merger, Are You Still a Small Business? The Recertification Rule
A merger or acquisition can cost you your small-business status overnight, and the rules make you report it. Keep running set-aside work as if nothing…

Technical Data Rights: How to Keep the Government From Giving Your Designs to a Competitor
When you deliver drawings, software, or technical data to the government, the markings you put on them decide who else can use them. Mark them…

Selling Your Company? The Government Has to Agree to Keep Your Contract
You cannot simply hand your federal contract to a buyer the way you would transfer a commercial deal. The government has to approve the transfer…

Earned Value Reporting: When Your Progress Numbers Become a Legal Statement
On big contracts you report how much work you have earned, not just how much you spent. Inflate that number to look on track and…

Expressly Unallowable Costs: When Billing the Wrong Expense Comes With a Penalty
Some costs are not just disallowed when you bill them to the government. They carry an automatic penalty on top, sometimes double. Here is what…




