TINA and CAS Compliance Threshold Relief Isn't Risk Relief

What the FY2026 NDAA Actually Means for Your Pricing Exposure

Congress just handed government contractors a genuine win. The Truthful Cost or Pricing Data Statute, still known as TINA, now only applies above $10 million, up from $2.5 million, for contracts entered into after June 30, 2026. Cost Accounting Standards moved with it: modified coverage jumps from $2 million to $35 million, and full CAS coverage now starts at $100 million instead of $50 million. For a wide band of mid-size contracts, the formal certification burden just disappeared.

Most of the industry is covering the TINA and CAS compliance threshold changes as unambiguous good news. It is good news, but it's not the whole story, and treating it as the whole story is where contractors get exposed.

What the threshold increase actually removes

TINA certification was never the source of the "fair and reasonable price" requirement. That obligation lives in FAR 15.404, and it has no dollar floor. It applies to every negotiated procurement, certified data or not. What TINA's threshold controlled was the formal, standardized proof mechanism, the paperwork that forced a contractor to document exactly how a price was built, in an auditable format.

Raise the threshold, and contracting officers, DCAA, and program-level inspectors general keep every right they had to challenge a price. What changes is how much support a contractor is required to have ready before that challenge comes. Fewer contracts will require certified data. That doesn't mean fewer contracts will get questioned. It means more of them will be defended, if they're defended at all, on whatever internal cost analysis happened to exist at the time.

The second reform makes this sharper, not softer

While Congress was raising thresholds, the Department of War was rebuilding acquisition around speed. The new Warfighting Acquisition System restructures program offices into Portfolio Acquisition Executives with fewer approval layers, makes speed to capability the top scorecard metric, and rewards early delivery while penalizing delays. A January 2026 executive order goes further, tying contractor capital allocation, dividends and buybacks, directly to delivery performance.

Congress endorsed the direction but flagged the risk in its own report language: speed "must be factored alongside cost, performance, lethality, and scalability." That's Congress naming the exact failure mode this reform makes more likely: faster timelines, thinner formal documentation, real financial consequences if a price doesn't hold up.

Why this is a CFO question, not a compliance footnote

Put the two reforms side by side and the result isn't risk reduction, it's risk relocation. The burden moved from a standardized process requirement to whoever owns the individual pricing decision, on a compressed timeline, with capital allocation now watching. A defective pricing finding doesn't check whether TINA applied. It checks whether the number was reasonable and how the contractor knows. Under the old thresholds, certification forced that rigor to exist by default. Under the new ones, it's optional, right up until someone asks.

Where the actual advantage sits

None of this argues for slowing down. Speed is the mandate now, full stop. It argues for what "fast" has to include. The contractors who benefit from this reform will be the ones who can produce certified-grade, audit-ready cost and pricing data at the same speed the Pentagon is demanding, without rebuilding the compliance overhead Congress just tried to remove.

That's a capability question, and it separates contractors running estimating on spreadsheets and email threads from contractors running it natively inside their ERP. When cost estimating, labor rates, and audit trail are built into the estimate itself, DCMA/TINA/DFARS-aligned by construction rather than by a separate compliance review after the fact, certified-grade data stops being overhead and becomes a byproduct of doing the estimate at all.

Where Twenty5 fits

This is exactly the gap iPE was built to close. Every estimate generated in iPE carries a full audit trail back to its original source data in SAP, cost by cost, price by price, whether or not that contract ever crosses the TINA or CAS threshold. There's no separate compliance pass to run when a contracting officer asks how a number was built, because the answer already lives inside the estimate. For contractors trying to move at Warfighting Acquisition System speed without gambling on which contracts might get questioned later, that's the difference between scrambling to reconstruct a defense and already having one.

The bottom line

The government removed a paperwork requirement. It did not remove the underlying obligation, and it added a speed mandate that makes that obligation harder to satisfy after the fact. Contractors who read this as pure relief are setting themselves up to be the ones without a defensible number when someone finally asks. Contractors who read it correctly, as a reallocation of exposure rather than a removal of it, have a genuine, compounding advantage: the same speed the Pentagon is demanding, with the certainty regulators still expect.

Sources: FY2026 National Defense Authorization Act (Pub. L. 119-60), Section 1804; Department of War "Transforming the Warfighting Acquisition System" strategy (Nov. 7, 2025); Executive Order 14265 and the January 2026 executive order on defense contracting capital allocation; House/Senate FY2026 appropriations report language (Jan. 20, 2026).