Paper 08: Procurement and Subcontractor Compliance

Procurement and Subcontractor Compliance

"Every subcontract cost that lacks adequate competition documentation, cost/price analysis, or flowdown compliance creates allowability exposure that flows directly into indirect pools and direct costs. A procurement deficiency is not a contracting paperwork failure — it is an ICS and FICS finding waiting to be discovered."

Paper 8 covers the FAR Part 44 procurement system adequacy standard, competition documentation requirements by procurement type, when cost analysis is required vs. price analysis, subcontractor flowdown requirements including CAS, the six-section procurement file adequacy standard, and the DCAA examination approach to every procurement system review.

The reason DCAA has authority to examine procurement files is that subcontractor costs are cost elements in the contractor's direct and indirect pools. An undocumented sole-source procurement creates a cost allowability question: if the price wasn't established as fair and reasonable, the cost may not be allocable under FAR Part 31. A missing flowdown clause creates a regulatory exposure question: if the subcontractor didn't have audit rights, can the subcontractor's costs be verified? In both cases, the procurement deficiency creates a cost accounting consequence that flows into the ICS and FICS.

What This Paper Defines

Regulatory frameworks
Architectural compliance
DCAA audit proofing

Doctrine Access

Download the Executive Paper

Complete the form to receive the full research, frameworks, and architectural blueprints.

The Argument

Why DCAA Examines Procurement Files — The Cost Accounting Connection

The reason DCAA has authority to examine procurement files is that subcontractor costs are cost elements in the contractor's direct and indirect pools. An undocumented sole-source procurement creates a cost allowability question: if the price wasn't established as fair and reasonable, the cost may not be allocable under FAR Part 31. A missing flowdown clause creates a regulatory exposure question: if the subcontractor didn't have audit rights, can the subcontractor's costs be verified? In both cases, the procurement deficiency creates a cost accounting consequence that flows into the ICS and FICS. ""A procurement system is adequate when it enforces compliance at the point of every procurement action — not when it can produce documentation of compliance on request. The same principle that governs timekeeping adequacy governs procurement adequacy: enforcement architecture, not documentation assembly.""

The Retroactive Assembly Problem

DCAA examiners are trained to identify procurement files assembled retroactively rather than built contemporaneously. Indicators include: documents with metadata creation dates after the procurement action they document, missing intermediate steps in the procurement sequence, justifications that appear written to support a decision already made rather than to document the decision process, and source selection evaluations that don't align with the solicitation criteria. A procurement system that generates complete, contemporaneous files as a byproduct of every procurement action eliminates this risk. A system that requires staff to assemble documentation before each CPSR creates it.

Flowdown Adequacy Test

For any subcontract: (1) Does it incorporate all mandatory flowdown clauses regardless of value? (2) Does it incorporate all threshold-based clauses applicable to its type and value? (3) Are CAS requirements flowed down consistent with the subcontract type and applicable CAS coverage? If any answer is no, the subcontract has a flowdown deficiency that creates both regulatory and cost allowability exposure.

FAR 44

Procurement system adequacy standard

Regulatory basis for every DCAA procurement review

$250K

Simplified acquisition threshold

Full and open competition required above this threshold

$2M

Certified cost/pricing data threshold

Cost analysis and subcontractor certification required above this

Before

Procurement files built before award

Documentation assembled after award fails the adequacy standard

Strategic Prediction

Strategic Insight

""A procurement system is adequate when it enforces compliance at the point of every procurement action — not when it can produce documentation of compliance on request. The same principle that governs timekeeping adequacy governs procurement adequacy: enforcement architecture, not documentation assembly.""

Frequently Asked Questions

What is a CPSR and when does DCMA conduct one?

A Contractor Purchasing System Review (CPSR) is a comprehensive evaluation of the contractor's procurement system conducted by DCMA. It is required for contractors whose annual subcontracting exceeds $50 million (for DoD contractors under DFARS 252.244-7001). The CPSR evaluates whether the procurement system has adequate written policies and procedures, enforces competition and documentation requirements, performs appropriate cost/price analysis, ensures flowdown compliance, and maintains adequate procurement files. A CPSR finding of "inadequate" can result in withholds on prime contract billings and requires a corrective action plan validated by DCMA before the system is re-approved.

When is cost analysis required versus price analysis?

Price analysis is sufficient when adequate price competition exists — meaning two or more responsible offerors submitted responsive proposals based on the same statement of work. When adequate price competition does not exist and the subcontract exceeds $2 million, cost analysis is required. Cost analysis examines each significant cost element in the subcontractor's proposal: direct labor hours and rates, materials, overhead rates, G&A rates, and profit. The cost analysis must support a conclusion that each element is reasonable before the prime contractor can award the subcontract. Relying on price analysis when cost analysis was required creates defective pricing exposure if the price is later found to be unreasonable.

Why is CAS flowdown the most commonly deficient flowdown requirement?

CAS flowdown is commonly deficient because many contracts staff do not realize it applies to subcontracts — they associate CAS with the prime contract relationship and overlook the regulatory requirement to flow CAS coverage to qualifying subcontracts. The consequence of a CAS flowdown failure is that the subcontractor's cost accounting practices may not be consistent with the prime's Disclosure Statement, creating a cost accounting inconsistency finding when the subcontractor's costs are incorporated into the prime's ICS. Correcting a CAS flowdown failure retroactively requires amending executed subcontracts — which subcontractors may resist — and potentially filing a CAS noncompliance disclosure, which attracts additional DCAA scrutiny.

Previous Paper FICS permanently closesthe cost record.There is no reopeningafter final settlement. Next Paper SoD enforced byorganizational hierarchyis not SoD.It is a policy that can be bypassed.

Want to model your own ROI?

Use our interactive calculator to see how a contract-native architecture can transform your margin.

Run ROI Calculator

Procurement compliance isa cost accounting problem,not just a contractingrequirement.