The Lockheed Martin engineers who certified F-35 pricing proposals from 2013 through 2015 were almost certainly not in their same seats when the Department of Justice settlement landed in February 2025. A decade passed. The proposals were archived. The supplier quote files were buried. And Lockheed still paid $29.74 million to resolve False Claims Act allegations tied to data those engineers signed off on.
Most GovCon CFOs treat the signed Certificate of Current Cost or Pricing Data as the end of TINA risk. Signing the certificate is the start of a six-to-ten-year exposure window. The defective pricing defense problem does not arrive when the contract closes. It arrives when the DCAA notification letter shows up years after the proposal team moved on, the emails are in someone’s archived PST file, and you have ninety days to defend a number you set in a different fiscal year.
The 2024-2025 enforcement wave makes this concrete: Raytheon paid $428 million for TINA violations spanning 2009-2020, and L3 Technologies reportedly settled for $62 million for misconduct alleged to run from 2006 to 2014 (settlement citation pending verification). Three major settlements closed in eighteen months. The audit environment is active. The question is whether your documentation survives it. The full text of FAR 15.407-1 at acquisition.gov sets the standard, and the DOJ press release on the Lockheed Martin settlement documents the modern enforcement template.
Defective pricing under FAR 15.407-1 occurs when a contractor submits cost or pricing data that was inaccurate, incomplete, or noncurrent as of the date of final agreement on price. Practitioners organize the defense around three elements drawn from FAR 15.407-1: (1) the data qualified as cost or pricing data under TINA; (2) the contractor failed to disclose it accurately and completely; and (3) the government relied on the defective data, causing an increase in the contract price. Liability includes price reduction and interest from the date of overpayment under FAR 52.215-10, and a penalty equal to the overcharge if the submission was knowing under FAR 15.407-1(b)(7)(iii).
Bottom line: Defective pricing liability attaches at certification. The audit surfaces years later. The government has six years to act, measured from when the right of action accrues under 28 USC 2415. Courts applying the discovery rule have measured that period from when the government knew or should have known of the defect. Every contractor above the $2.5M threshold needs a documented pre-certification sweep and a defensible audit file.
The Exposure Window Most CFOs Ignore
A typical defective pricing case runs: contract award, two to five years of silence, a DCAA audit notification, one to two years of fieldwork, a contracting officer determination, and a potential ASBCA appeal. From certificate signing to final resolution, eight to twelve years is normal. Raytheon’s case covered misconduct from 2009 through 2020.
The government has six years to bring a defective pricing claim, measured from when the right of action accrues under 28 USC 2415. Courts have applied a discovery rule, measuring that period from when the government knew or should have known of the defect, not from contract award. A 2021 contract award does not close out in 2027. Exposure continues until six years after DCAA discovers the pricing discrepancy, which might be 2026, 2028, or 2030.
Every document that supported your certified cost proposal must survive in retrievable form for a decade: supplier quote files, internal cost-estimating worksheets, ERP standard cost runs as of the agreement date, and the sweep procedure you followed before certifying. The contractor who cannot produce these is not claiming innocence. The auditor fills the gap with an adverse inference.
The Three-Element Defective Pricing Framework
Practice note: The three elements below are a practitioner analytical framework drawn from FAR 15.407-1. The regulation does not use the phrase “Three-Prong Test.” The framework describes what the government must demonstrate and where a contractor’s defense can succeed.
DCAA post-award defective pricing audits follow a documented procedural framework under DCAM Chapter 14 (citation pending verification of current CAM text). Contractors mount a defective pricing defense by attacking the government’s case on any one of three elements. The framework structures the contractor’s defense across most enforcement scenarios:
| Element | What the Government Must Demonstrate | Contractor Defense Angle |
|---|---|---|
| 1. Data Was Defective | The information was cost or pricing data (factual, not judgmental) and it was inaccurate, incomplete, or noncurrent as of the date of final agreement on price [FAR 15.407-1(b)(1)] | Show the data was an estimate or judgment, not a fact; show the data was current as certified; demonstrate the cutoff date applied correctly |
| 2. Government Relied on It | The contracting officer used the defective data when negotiating the price, and the reliance was reasonable [FAR 15.407-1(b)(1)] | Show the CO independently determined fair price; show price was based on competition or market data; demonstrate CO had access to accurate data through other means |
| 3. Government Was Overcharged | The defect caused an increase in the contract price above what the government would have paid with accurate data [FAR 52.215-10] | Invoke the offset provision: other data understated the price, netting the overcharge to zero or near-zero; challenge the damages calculation methodology |
The case Lockheed Martin Aero. Co., ASBCA No. 56547 (Jan. 22, 2013) is cited as an illustration of a successful defense where the government’s claim failed. As reported in practitioner commentary, the board found the data either was not cost or pricing data within the TINA meaning, or the contractor had meaningfully disclosed it, or the government could not prove reliance caused an overcharge. Winning on any single element defeats the government’s claim entirely.
Alloy Surfaces Company, ASBCA No. 59625 is cited for the meaningful disclosure doctrine: disclosure does not require formal proposal inclusion. As reported in practitioner commentary, a contractor satisfies the disclosure obligation if the government had reasonable access to accurate data through other means. The audit file, not the formal proposal binders alone, determines whether data was disclosed.
How DCAA Finds Defective Pricing in a Post-Award Audit
Post-award defective pricing audits follow a documented investigative pattern. The auditor compares the certified cost proposal against the contractor’s accounting records, ERP data, and supplier files as of the agreement date. Standard cost system runs, purchasing records, and supplier quote files all provide a contemporaneous data trail the auditor reconstructs independently. DCAA does not need the contractor’s cooperation to find the discrepancy.
The four failure patterns DCAA exploits most frequently:
- No documented sweep. The contractor cannot produce evidence a sweep occurred. In post-award audits, auditors in practice treat the absence of a documented sweep as circumstantial evidence the contractor did not look for updated data before certifying.
- Sweep performed too early. The sweep captured data as of proposal submission, not as of the agreement date. A two-week gap between submission and price agreement is enough time for a supplier revision to create exposure.
- Buried supplier data. A supplier provided a revised quote via email between submission and agreement. The quote sat in the purchasing manager’s inbox, never reached the proposal team, and DCAA found it. The contractor certified the original quote as current.
- Selective disclosure. The contractor disclosed favorable data (higher-than-expected costs) while withholding unfavorable data (supplier reductions, efficiency gains). DoD IG flags this as fraud, triggering FCA referral rather than a price reduction negotiation.
The Pre-Certification Sweep Checklist
A sweep is a documented internal review performed between agreement on price and signing the Certificate of Current Cost or Pricing Data [FAR 15.406-2]. The contractor systematically queries every data source for updated cost information and discloses material updates to the contracting officer before certifying. The sweep memo is the primary documentary evidence a defective pricing defense relies on when an audit surfaces years later.
Run this checklist for every TINA-covered contract and modification above $2.5 million [FAR 15.403-4(a)(1)]:
| Data Source | What to Query | Documentation Required |
|---|---|---|
| Supplier quote files | All vendor quotes, revised quotes, extensions, and expirations received after proposal submission through agreement date | Save all quotes; note date received vs. agreement date; document any rate revisions |
| ERP and purchasing system | Standard cost runs, labor rate updates, BOM changes, MRP updates, POs reflecting revised pricing, volume discount confirmations | Export standard cost roll and PO log as of agreement date; reconcile to proposal rates |
| Finance and accounting | Accruals, journal entries, and cost adjustments that changed expected costs; labor rate journal entries | GL trial balance extract as of agreement date; reconcile to proposal cost elements line by line |
| Email, intranet, and engineering | Supplier portal messages, engineering change orders, BOM changes, internal cost discussions contradicting proposal assumptions | Search supplier email folders; document search terms and results; retain relevant ECO logs |
| Subcontractor files | Sub quote updates, sub cost revisions, sub certifications (required if sub portion exceeds $2.5M) | Sub certification copies; documentation of prime’s flow-down request and response date |
The sweep must be dated and signed by the responsible financial officer and retained with the contract file, not the proposal file alone. Store it in the contract administration system and a dedicated compliance folder labeled with the contract period plus ten years. A sweep memo that cannot be located in 2030 provides no defense.
The sweep memo is the documentary anchor of a defective pricing defense. It proves what data was current as of the agreement date and creates the evidentiary foundation for the meaningful disclosure doctrine. For the TINA threshold and certification requirements, see our guide to TINA compliance and the $2.5M threshold.
The Defective Pricing Defense Framework
DCAA post-award audit notifications give the contractor ninety days to respond to the draft report. The defective pricing defense is not built in ninety days. It is built at the time of proposal. The response period is the time to deploy documentation that already exists.
Four defenses survive the three-element framework when documented:
1. The Meaningful Disclosure Defense. The government had access to the data through means other than the formal proposal submission. Internal company documents on a government-accessible system, data provided in prior negotiations, or information available in DCAA’s own audit files might satisfy the disclosure obligation. As reported in Alloy Surfaces, ASBCA No. 59625 (opinion pending verification at asbca.mil), the disclosure standard looks to reasonable access, not formal proposal inclusion. Document every channel through which the government could have accessed updated data.
2. The Offset Defense. Under FAR 52.215-10(c)(2)(i), a contractor claiming the government was overcharged by defective data on one cost element may offset that overcharge against undercharges on other cost elements, subject to the contracting officer’s determination of the appropriate offset amount. If the proposal understated labor costs but the government claims material was overstated, a net calculation reduces or eliminates the damages figure. This requires a cost-element-by-cost-element reconstruction of what the proposal would have shown with accurate data.
3. The Judgmental Data Defense. TINA covers cost or pricing data, defined as factual information. Estimates, judgments, and management decisions are not cost or pricing data and do not support a defective pricing claim. When the government attacks a pricing assumption, the contractor argues the assumption was a judgment about future performance, not a factual representation of historical cost. This defense is strongest on forward-pricing rate proposals where indirect rates involve significant judgment [FAR 15.408 Table 15-2].
4. The Voluntary Disclosure Mitigation. Proactively disclosing a pricing discrepancy to the contracting officer before audit notification is recognized in practice as a mitigating factor. A contractor who identifies and discloses a discrepancy post-award typically avoids the knowing-submission penalty under FAR 15.407-1(b)(7)(iii) and reduces FCA referral risk, even though the base price reduction obligation under FAR 52.215-10 remains.
See what triggers a DCAA post-award audit and review the most common DCAA audit findings to understand the full investigative scope.
Subcontractor Liability Under FAR 52.215-12
Prime contractors carry liability for subcontractor defective pricing even without knowledge of the defect [FAR 52.215-12]. The prime’s defective pricing defense depends on the quality of its flow-down compliance. Three steps are non-negotiable:
- Issue written flow-down requirements to subcontracts above $2.5M, citing FAR 52.215-12 and FAR 52.215-13
- Obtain and retain subcontractor certifications with the same agreement-date cutoff discipline as the prime certification
- Perform a sweep of subcontractor pricing data using the same checklist applied to prime cost elements and document the verification process
A prime with no flow-down documentation has no defense and no recovery path. For cost element documentation standards, see the government contract cost proposal guide and the compensation reasonableness standards for labor data obligations.
Frequently Asked Questions
What is defective pricing defense in government contracting?
Defective pricing defense is the evidentiary strategy a contractor uses to defeat a government claim under FAR 15.407-1. Practitioners analyze the government’s case around three elements: defective data, reliance during negotiation, and a resulting overcharge. Defeating any one element defeats the entire claim. The defense rests on sweep documentation, contemporaneous accounting records, and the meaningful disclosure doctrine.
How long after contract award does DCAA have to audit pricing?
The government has six years to bring a defective pricing claim under 28 USC 2415, measured from when the right of action accrues. Courts have applied a discovery rule, starting that clock when the government knew or should have known of the defect, not from award. In practice, audits begin two to five years after award; total exposure runs eight to ten years. A contractor who certified a proposal in 2022 should retain supporting documentation through at least 2032.
What is a TINA sweep and when must it happen?
A TINA sweep is a documented internal review of all data sources for updated cost information between proposal submission and the agreement date [FAR 15.406-2]. It covers supplier quote files, ERP standard cost runs, purchasing records, accounting accruals, email correspondence, and subcontractor certifications. The dated sweep memo is the primary documentary defense against a future post-award audit.
Is the prime contractor liable for subcontractor defective pricing?
Yes. Under FAR 52.215-12, the prime bears liability for subcontractor defective cost or pricing data even without knowledge of the defect. Prime contractors must flow down TINA certification requirements, obtain and retain sub certifications, and document the flow-down process. A prime with no subcontractor documentation has no defense and no recovery path.
What penalties apply if DCAA finds defective pricing?
The contract price reduces by the overcharge amount plus interest under FAR 52.215-10. Knowing submission adds a penalty equal to the overcharge under FAR 15.407-1(b)(7)(iii). False Claims Act exposure adds treble damages and per-claim civil penalties under 31 USC 3729. Raytheon’s $428 million settlement reflects FCA exposure layered on top of the base TINA price reduction.
Is an intranet sufficient disclosure if the data was available on a company system?
Possibly. The meaningful disclosure doctrine holds that formal proposal inclusion is not required if the government had reasonable access through other means, as reported in Alloy Surfaces, ASBCA No. 59625 (opinion pending verification). An intranet the government cannot access does not satisfy the standard. Document every access channel explicitly in the sweep memo rather than relying on this defense after the fact.
Key Takeaways
- The government has six years to bring a defective pricing claim under 28 USC 2415, measured from when the right of action accrues. Courts apply a discovery rule. A 2021 certificate carries potential exposure through 2031 or beyond.
- Practitioners analyze defective pricing liability around three elements drawn from FAR 15.407-1: defective data, government reliance, and resulting overcharge. Defeating any single element defeats the entire claim.
- A documented pre-certification sweep performed as of the agreement date is the most important single document in a defective pricing defense. Run it, date it, sign it, retain it for a decade.
- Prime contractors are liable for subcontractor defective pricing under FAR 52.215-12. Flow down the certification requirement, collect sub certifications, and document the process.
- The offset defense under FAR 52.215-10(c)(2)(i) allows undercharges on other cost elements to net against the government’s overcharge claim. A thorough cost-element reconstruction often reduces calculated damages significantly.
A defective pricing audit arriving years after contract award is survivable when the documentation exists. The contractors paying nine-figure settlements built no audit file. Review our DCAA compliance services to see how CPA-managed bookkeeping builds the pricing defense infrastructure before the audit letter arrives. Ready to assess your current exposure? Book a discovery call with our team.
