Published 2026 | TIKC NewsWire
When you negotiate a sole-source price with the government above certain thresholds, you are often required to do something that feels unusual: open your books and certify that the cost or pricing data behind your number is accurate, complete, and current. That requirement comes from the Truth in Negotiations Act, now called Truthful Cost or Pricing Data, and the moment you sign that certificate, the quality of your data becomes a legal matter. If you left something out that would have lowered the price, the government can claw the difference back years later. That is defective pricing, and it is one of the most misunderstood risks in federal contracting.
When certified cost or pricing data is required
Certified cost or pricing data is generally required for negotiated procurements above a dollar threshold when there is no adequate price competition and no other exception applies, such as commercial items or prices set by law. If your award is competitive, or your product is a genuine commercial item, you usually avoid the requirement. But the moment you are in a sole-source negotiation over the threshold, assume the certificate is coming and that every number you give the contracting officer must be backed by current, complete, factual data.
What defective pricing actually means
Defective pricing does not mean you charged too much on purpose. It means the data you certified was not accurate, complete, or current as of the agreement date, and that the government relied on it and paid more than it would have otherwise. The classic example is simple and brutal: you had a lower vendor quote sitting in your inbox during negotiations, you based your price on an older higher quote, and you never disclosed the better one. Even an honest oversight can be defective pricing, because the test is whether the data was accurate and disclosed, not whether you meant to overcharge.
The government can look back
Here is what makes this risk so serious. The government can audit your pricing after award, sometimes years later, through a post-award review. If auditors find that accurate, complete, and current data existed but was not disclosed, they can demand a price reduction plus interest, and in cases involving knowing misconduct, the matter can escalate to False Claims Act liability. This is the same documentation discipline that protects your interim billing and that a contracting officer weighs when judging whether you are a responsible contractor. Sloppy cost files are not a small problem. They are a standing liability.
How honest firms get caught
Most defective-pricing findings are not fraud. They are disorganization. A quote that came in late and never made it into the file. A cost that dropped the week before agreement. A subcontractor price that was never updated. A pricing team that did not talk to purchasing. The lesson is that your defense is your paper trail. If you can show what data you had, when you had it, and that you disclosed it, you win the audit. If you cannot, the gap becomes the finding, the same way an out-of-scope sale becomes a problem on a GSA Schedule order.
What to do now
- Know your thresholds and exceptions. Understand when certified cost or pricing data is required and when a commercial-item or competition exception applies.
- Sweep for current data. Before you certify, pull the latest vendor quotes, labor rates, and costs so nothing newer or lower is sitting undisclosed.
- Disclose, do not judge. Give the contracting officer the data even if you think it is minor. Disclosure is the defense.
- Keep a dated cost file. Document what you knew and when, so you can prove accuracy as of the agreement date.
- Connect pricing and purchasing. Make sure the people negotiating the price see the latest numbers from the people buying the inputs.
Your price is only as honest as the data under it. Build clean, dated cost files now, and a post-award audit becomes a formality instead of a crisis. Brick by brick.
FAQ
What is the Truth in Negotiations Act?
Now called Truthful Cost or Pricing Data, it requires contractors on certain negotiated procurements to submit and certify that their cost or pricing data is accurate, complete, and current as of the agreement date.
What is defective pricing?
It occurs when certified data was not accurate, complete, or current, the government relied on it, and it paid more than it would have with the correct data. Intent to overcharge is not required.
When do I have to certify cost or pricing data?
Generally in sole-source negotiated procurements above a dollar threshold, unless an exception applies such as adequate price competition, commercial items, or prices set by law.
How do I protect myself from a defective-pricing finding?
Disclose all current data before certifying and keep a dated cost file proving what you knew and when, so you can defend the price in a post-award audit.
Sources
Truthful Cost or Pricing Data (Truth in Negotiations Act), 10 U.S.C. 3701 et seq. and 41 U.S.C. chapter 35. (2026).
Federal Acquisition Regulation. (2026). Subpart 15.4, Contract Pricing, and the defective pricing clauses.
This article is general information, not legal advice.
About the Author
Melanie Patterson
Founder and CEO of Team Integrity Knowledge Center and creator of GovCon iSource. Former nurse turned entrepreneur with over 10 years guiding small, women-owned, and minority-owned businesses to over $10 million in government awards. Build, grow, scale, brick by brick. Contact
