What is the DFARS contractor business systems rule?

The DFARS contractor business systems rule is the framework at DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts), Contractor Business Systems, that identifies six business systems, accounting, estimating, material management and accounting (MMAS), property management, purchasing, and earned value management (EVMS), and ties a material weakness in any one of them to a contract remedy: the government can withhold a percentage of payments until the contractor corrects the weakness. The DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) framework applies only to covered contracts subject to the Cost Accounting Standards and containing applicable system clauses; an underlying system clause may have a different prescription. It exists because these six systems, together, produce and control much of the cost data the government relies on when it pays a contractor.

What are the six contractor business systems?

The six systems named in DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) are: the accounting system (DFARS 252.242-7006 (or its class-deviation successor 252.242-7999 for new solicitations and contracts)), which produces and reports contract costs; the estimating system (DFARS 252.215-7002), which generates cost proposals; the material management and accounting system, or MMAS (DFARS 252.242-7004 (or its class-deviation successor 252.242-7997 for new solicitations and contracts)), which plans and allocates material cost; the property management system (FAR 52.245-1 and DFARS 252.245-7003), which controls government property in the contractor's custody; the purchasing system (DFARS 252.244-7001 (or its class-deviation successor 252.244-7998 for new solicitations and contracts)), which governs subcontracting and may be reviewed through a Contractor Purchasing System Review; and the earned value management system, or EVMS (DFARS 252.234-7002 (or its class-deviation successor 252.234-7999 for new solicitations and contracts)), which integrates cost and schedule performance on qualifying programs. Not every contractor is subject to every system: the DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) withholding framework depends on CAS coverage, while each underlying clause has its own contract-type, dollar-value, or other prescription, and some do not require CAS coverage.

What is the difference between DCAA and DCMA in business systems reviews?

DCAA, the Defense Contract Audit Agency, can review three systems: accounting, estimating, and MMAS. DCMA, the Defense Contract Management Agency, provides specialists for EVMS, purchasing, and property. The cognizant contracting officer approves or disapproves systems and makes the material-weakness determination, informed by the audit or functional-specialist findings. Neither agency approves or certifies a system as a permanent status. A finding of adequate today does not guarantee adequate at the next review, because business systems are reassessed on a recurring cycle.

How does a contractor remediate a material weakness?

The contractor has 30 days from the contracting officer's initial determination to respond in writing, and after a final determination confirming a material weakness and any associated withholding notice, 45 days to correct the weakness or submit an acceptable corrective action plan describing milestones and actions to eliminate the weaknesses. Documenting the root cause first is recommended practice, not a clause requirement, but it makes the plan easier to defend. The government reviews the plan, may request revisions, and the contracting officer may reduce or discontinue withholding when the clause's conditions are met, including evidence creating a reasonable expectation that corrective actions have been implemented and will correct the weaknesses. A follow-up review may later verify the fix. The practical work depends on the system-specific criteria: identify the process that failed the governing clause, redesign it, document it, and demonstrate it operating consistently over enough transactions that an examiner can test it.

SK Written by Sarika Krishnan with Robert LabardeeSenior Program Manager and Founder and CEO

Last updated August 2026.

The DFARS contractor business systems rule

The DFARS contractor business systems rule is the framework at DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) that names six business systems (accounting, estimating, material management and accounting (MMAS), property management, purchasing, and earned value management (EVMS)) that the Defense Contract Audit Agency and the Defense Contract Management Agency review for adequacy on covered defense contracts. A material weakness is a deficiency or combination of deficiencies creating a reasonable possibility that a material misstatement in business-system information will not be prevented, or detected and corrected, on a timely basis; it can trigger payment withholding.

DCAA-compliant accounting Talk to an ERP advisor

One clause ties six systems to a common payment-withholding remedy.

DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts), Contractor Business Systems, is the clause that consolidates business systems oversight into one framework. Rather than treating accounting, estimating, material management, property, purchasing, and earned value management as unrelated obligations, the clause names all six as business systems and supplies a common payment-withholding remedy when a material weakness exists in any of them. The clause preserves other contractual rights and remedies, and the system clauses also provide for system disapproval. That structure reflects how the systems work together in practice: the accounting system reports the cost, the estimating system priced it, the purchasing system bought the material behind it, MMAS allocated that material, the property system tracked the government-owned assets used to build it, and EVMS measured the program's progress against it. A weakness anywhere in that chain undermines the government's ability to rely on the affected system's information and controls, whether that is billing accuracy, property accountability, or program-performance data.

The DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) business-systems withholding framework applies only to covered contracts subject to the Cost Accounting Standards when the applicable system clauses are included. Because small-business contracts are categorically exempt from CAS, a small-business contract cannot, under the DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) framework, be subject to that six-system withholding structure; the MMAS clause prescription also expressly excludes small businesses. Separate underlying clauses that do not depend on CAS coverage may still apply when their own prescriptions are met. See the guide to government contract project accounting for how contract type and cost accounting standards coverage set the stage for which clauses apply.

Each of the six systems has its own clause, its own criteria, and its own reviewer.

DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) names the systems and the remedy. The adequacy criteria for each system live in a separate clause, and the reviews are split between DCAA and DCMA depending on the system.

Accounting system

The accounting system consists of the methods, procedures, controls, and associated subsystems a contractor uses to record and report costs. DFARS 252.242-7006 (or its class-deviation successor 252.242-7999 for new solicitations and contracts), Accounting System Administration, is prescribed based on contract and payment type, without a Cost Accounting Standards condition: the system must segregate direct costs from indirect costs, accumulate costs by contract and by cost objective, apply indirect cost pools and rates consistently, exclude unallowable costs under FAR Part 31, and produce billings that trace back to the books. The clause requires a sound internal-control environment, and its final criterion requires compliance with CAS when applicable and GAAP otherwise. DCAA can review three systems (accounting, estimating, and MMAS), and an accounting-system audit is distinct from incurred-cost audits, provisional billing-rate reviews, and pre-award surveys such as the SF1408. Lightbridge ERP's guide to DCAA-compliant accounting covers the full adequacy criteria and timekeeping controls relevant to review.

DCAA-compliant accounting

Estimating system

The estimating system is the set of policies, procedures, and practices a contractor uses to generate cost proposals for pricing negotiated contracts, and it supports pricing decisions on cost-reimbursement and other negotiated work where the government relies on the estimate to set a fair price. DFARS 252.215-7002, Cost Estimating System Requirements, is prescribed for all solicitations and contracts to be awarded on the basis of certified cost or pricing data. Its detailed system requirements apply to a large business that, in the preceding fiscal year, received DoD prime contracts or subcontracts totaling $50 million or more for which certified cost or pricing data were required, or $10 million or more but less than $50 million for which certified cost or pricing data were required plus written notice from the contracting officer. It requires the estimating system to produce well-supported proposals consistently: documented estimating methods and judgment applied consistently, appropriate source data, and comparisons of projected results against actual results. When certified cost or pricing data are required, that data must be accurate, complete, and current as of the date of price agreement (or an earlier mutually agreed date as close as practicable to price agreement), a separate FAR certification requirement. Conditions that could contribute to a material weakness include estimates that cannot be reconstructed or rely on data the contractor cannot substantiate. Lightbridge ERP is developing a dedicated guide to the contractor estimating system and DFARS 252.215-7002.

Material management and accounting system (MMAS)

MMAS governs how a contractor plans, controls, and accounts for the material that flows into a government contract: purchased parts, subcontracted components, and inventory drawn from common stock. DFARS 252.242-7004 (or its class-deviation successor 252.242-7997 for new solicitations and contracts), Material Management and Accounting System, sets ten standards an MMAS must meet, covering demand-based planning, reasonable and consistent allocation of material costs to contracts, timely identification of excess and residual inventory, audit trails, and valid allocation logic. The clause permits controlled allocations from common inventory and controlled commingling of certain costed inventories associated with fixed-price, cost-reimbursement, and commercial work; it does not require every purchase or issue to be traced to one consuming contract, but it expressly prohibits physically commingling government-furnished material or using it on commercial work. Conditions that could contribute to an MMAS material weakness include an allocation method that lacks a valid documented basis or audit trail, which may threaten the reliability of the costs the accounting system reports. Lightbridge ERP is developing a dedicated guide to MMAS and DFARS 252.242-7004 (or its class-deviation successor 252.242-7997 for new solicitations and contracts).

Property management system

The property management system tracks government-furnished and contractor-acquired property that the government owns but the contractor holds and uses to perform the contract: equipment, materials, and special tooling. FAR 52.245-1 sets the core property management standards, and DFARS 252.245-7003, Contractor Property Management System Administration, addresses system criteria, determinations, correction, and withholding; DFARS 252.245-7005 contains defense-specific management and reporting requirements. DCMA tests whether the contractor's records identify, control, maintain, and account for property accurately enough to support physical inventories, and whether the contractor can demonstrate custody and condition on demand. Conditions that could contribute to a material weakness include property records that do not reconcile to a physical count, or a control gap that lets property move, be consumed, or be disposed of without an approved transaction. Lightbridge ERP is developing a dedicated guide to contractor property management.

Purchasing system

The purchasing system governs how a contractor buys goods and services from its own subcontractors and suppliers for government contracts, and the contractor remains responsible for its procurement controls; purchasing-system approval does not relieve the prime contractor of that responsibility. DFARS 252.244-7001 (or its class-deviation successor 252.244-7998 for new solicitations and contracts), Contractor Purchasing System Administration, requires a system that documents price reasonableness, competes subcontracts appropriately, flows down required clauses, and manages subcontractor performance. Under the legacy, codified FAR 44.302 framework, the $25 million threshold concerns expected qualifying Government sales during the next 12 months, excluding competitively awarded firm-fixed-price and fixed-price with economic price adjustment contracts and Part 12 commercial sales. Under the active FAR overhaul (RFO) for current DoD solicitations and contracts, FAR 44.301-2 no longer contains that $25 million trigger. DFARS 244.301-2(a)(1) supplies a $50 million DoD threshold, consistent with the $50 million threshold in codified DFARS 244.302. It is a CPSR-need screening threshold: exceeding it prompts the ACO to consider whether a CPSR is needed, but it is not itself a CPSR or an applicability trigger for DFARS 252.244-7001 (or its class-deviation successor 252.244-7998 for new solicitations and contracts). That clause's prescription depends on FAR 52.244-2 or DFARS 252.246-7007. The ACO considers risk, performance, volume, complexity, and value. Conditions that could contribute to a material weakness include purchase decisions the contractor cannot justify as competitive or reasonably priced, or flow-down clauses that were never passed to a subcontractor. Lightbridge ERP is developing a dedicated guide to the Contractor Purchasing System Review and DFARS 252.244-7001 (or its class-deviation successor 252.244-7998 for new solicitations and contracts).

Earned value management system (EVMS)

EVMS is the project-controls system that integrates scope, schedule, and cost into a single measure of program performance, using planned value, earned value, and actual cost to calculate variances and forecast the final cost. DFARS 252.234-7002 (or its class-deviation successor 252.234-7999 for new solicitations and contracts), Earned Value Management System, requires a compliant EVMS on qualifying contracts, governed by the ANSI/EIA-748 guidelines. Under active Class Deviation 2026-O0011, qualifying contracts valued at $50 million or more require an EIA-748-compliant EVMS. At $100 million or more, the Cognizant Federal Agency must also determine that the EVMS complies with EIA-748 and is acceptable; the contracting officer separately approves or disapproves the system for the contract. If the system has not been accepted at award, the contractor shall apply its current system while taking the actions needed to meet the milestones in an approved EVMS plan. Actual cost may include estimated actuals when billing or recording lags, so the interfaces between EVMS, accounting, and the work breakdown structure need documented reconciliation. Lightbridge ERP's guide to earned value management covers the metrics, the ANSI/EIA-748 guidelines, and DCMA oversight in depth.

Earned value management (EVM and EVMS)

A material weakness is what triggers payment withholding, not any minor finding.

Not every audit finding or observation rises to a material weakness. DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) uses that term for a deficiency or combination of deficiencies in internal control over information in contractor business systems such that there is a reasonable possibility that a material misstatement will not be prevented, or detected and corrected, on a timely basis. The relevant criteria vary by system: the accounting clause requires a sound internal-control environment, while MMAS, property, and purchasing have their own allocation, recordkeeping, property, pricing, and flow-down requirements. The contracting officer, informed by a DCAA or DCMA review, makes the final determination and issues a written notice.

Once a contracting officer makes a final determination that a material weakness exists, DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) specifies 5 percent withholding from amounts due under progress payments and performance-based payments, with an aggregate cap of 10 percent when material weaknesses affect multiple systems. The total withholding for one or more weaknesses in a single system may not exceed 5 percent. If the contractor submits an acceptable corrective action plan within 45 days and the contracting officer determines it is being effectively implemented, withholding directly related to those weaknesses is reduced to 2 percent. The contractor may instead correct the weaknesses, and the contracting officer may discontinue withholding based on evidence creating a reasonable expectation that corrective actions have been implemented and will correct the weaknesses, before follow-up verification. Verify the current text of DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) on acquisition.gov before relying on it for a live contract decision.

Lightbridge ERP supports contractor readiness against the business systems criteria.

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm with deep in-house government contract accounting expertise. Because accounting and EVMS are its own published practice areas, its readiness work there goes deepest: advising on the cost structure, indirect rate pools, timekeeping controls, and work breakdown structure against the criteria in DFARS 252.242-7006 (or its class-deviation successor 252.242-7999 for new solicitations and contracts) and DFARS 252.234-7002 (or its class-deviation successor 252.234-7999 for new solicitations and contracts) respectively. Across the other four systems, estimating, MMAS, property management, and purchasing, Lightbridge ERP advises on configuring the ERP and related processes to support readiness against the criteria those clauses set: traceable cost proposals, material-allocation logic and audit evidence, property records that reconcile to a physical count, and purchasing documentation that shows price reasonableness and clause flow-down.

The control environment and access model should be assessed in the context of each system's governing criteria; a single ERP permission design may support some controls, but it does not replace system-specific policies, processes, scheduling tools, property processes, or other subsystems. Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, its platform and control recommendations follow fit, not commission. For the platforms this work most often runs on, see the Deltek Costpoint and Unanet practices, or start with a vendor-neutral ERP selection.

This guide is general information, not legal, audit, or accounting advice. DFARS clause text, dollar thresholds, and withhold percentages change through Department of Defense policy updates. Verify any specific figure against the current DFARS on acquisition.gov and consult qualified advisors before acting.

DFARS contractor business systems: frequently asked questions

What is the DFARS contractor business systems rule?: The DFARS contractor business systems rule is the framework at DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts), Contractor Business Systems, that identifies six business systems, accounting, estimating, material management and accounting (MMAS), property management, purchasing, and earned value management (EVMS), and ties a material weakness in any one of them to a contract remedy: the government can withhold a percentage of payments until the contractor corrects the weakness. The DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) framework applies only to covered contracts subject to the Cost Accounting Standards and containing applicable system clauses; an underlying system clause may have a different prescription. It exists because these six systems, together, produce and control much of the cost data the government relies on when it pays a contractor.
What are the six contractor business systems?: The six systems named in DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) are: the accounting system (DFARS 252.242-7006 (or its class-deviation successor 252.242-7999 for new solicitations and contracts)), which produces and reports contract costs; the estimating system (DFARS 252.215-7002), which generates cost proposals; the material management and accounting system, or MMAS (DFARS 252.242-7004 (or its class-deviation successor 252.242-7997 for new solicitations and contracts)), which plans and allocates material cost; the property management system (FAR 52.245-1 and DFARS 252.245-7003), which controls government property in the contractor's custody; the purchasing system (DFARS 252.244-7001 (or its class-deviation successor 252.244-7998 for new solicitations and contracts)), which governs subcontracting and may be reviewed through a Contractor Purchasing System Review; and the earned value management system, or EVMS (DFARS 252.234-7002 (or its class-deviation successor 252.234-7999 for new solicitations and contracts)), which integrates cost and schedule performance on qualifying programs. Not every contractor is subject to every system: the DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) withholding framework depends on CAS coverage, while each underlying clause has its own contract-type, dollar-value, or other prescription, and some do not require CAS coverage.
What counts as a material weakness?: DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) defines a material weakness as a deficiency or combination of deficiencies in internal control over information in contractor business systems such that there is a reasonable possibility that a material misstatement will not be prevented, or detected and corrected, on a timely basis. The relevant criteria vary by system: examples include an accounting system that cannot segregate direct from indirect costs, a purchasing system that cannot demonstrate price reasonableness, or an MMAS that lacks valid allocation logic or an audit trail. The contracting officer, informed by a DCAA or DCMA review, makes the final determination and issues a written notice.
How much can the government withhold for a business systems deficiency?: When the contracting officer issues a final determination that a material weakness exists in a covered contract, DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) specifies a 5 percent withholding from amounts due under progress payments and performance-based payments, and directs a 5 percent withholding from interim cost vouchers. The total withholding may not exceed 5 percent for material weaknesses in a single contractor business system or 10 percent for material weaknesses in multiple systems. If the contractor submits an acceptable corrective action plan within 45 days and the contracting officer determines that it is being effectively implemented, withholding directly related to those weaknesses is reduced to 2 percent. Within that 45-day period, the contractor may either correct the weaknesses or submit the plan. The contracting officer may also discontinue withholding based on evidence creating a reasonable expectation that corrective actions have been implemented and will correct the weaknesses, before follow-up verification. Verify the current clause text on acquisition.gov before relying on it for a live contract decision.
Does the business systems rule apply to every defense contractor?: No. The DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) withholding framework applies only to covered contracts subject to the Cost Accounting Standards that contain applicable system clauses. Each underlying system clause has its own prescription. For example, the estimating system requirements use qualifying prior-year DoD awards and written contracting-officer notice. The legacy, codified FAR 44.302 framework uses expected qualifying Government sales during the next 12 months, excluding competitively awarded firm-fixed-price and fixed-price with economic price adjustment contracts and Part 12 commercial sales, to screen whether a CPSR is needed. Under the active FAR overhaul (RFO) for current DoD solicitations and contracts, FAR 44.301-2 no longer contains that $25 million trigger. DFARS 244.301-2(a)(1) supplies a $50 million DoD threshold, consistent with the $50 million threshold in codified DFARS 244.302. The screening threshold does not itself make DFARS 252.244-7001 (or its class-deviation successor 252.244-7998 for new solicitations and contracts) applicable; its prescription depends on FAR 52.244-2 or DFARS 252.246-7007. A small-business contract cannot fall under the DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts) CAS-covered framework, although separate underlying clauses that do not depend on CAS coverage may still apply when their own prescriptions are met. The governing question for a specific contract is always what the contract's own clauses require, so check the contract and the current DFARS text rather than assuming the rule applies uniformly.
What is the difference between DCAA and DCMA in business systems reviews?: DCAA, the Defense Contract Audit Agency, can review three systems: accounting, estimating, and MMAS. DCMA, the Defense Contract Management Agency, provides specialists for EVMS, purchasing, and property. The cognizant contracting officer approves or disapproves systems and makes the material-weakness determination, informed by the audit or functional-specialist findings. Neither agency approves or certifies a system as a permanent status. A finding of adequate today does not guarantee adequate at the next review, because business systems are reassessed on a recurring cycle.
How does a contractor remediate a material weakness?: The contractor has 30 days from the contracting officer's initial determination to respond in writing, and after a final determination confirming a material weakness and any associated withholding notice, 45 days to correct the weakness or submit an acceptable corrective action plan describing milestones and actions to eliminate the weaknesses. Documenting the root cause first is recommended practice, not a clause requirement, but it makes the plan easier to defend. The government reviews the plan, may request revisions, and the contracting officer may reduce or discontinue withholding when the clause's conditions are met, including evidence creating a reasonable expectation that corrective actions have been implemented and will correct the weaknesses. A follow-up review may later verify the fix. The practical work depends on the system-specific criteria: identify the process that failed the governing clause, redesign it, document it, and demonstrate it operating consistently over enough transactions that an examiner can test it.
How does Lightbridge ERP help with contractor business systems?: Lightbridge ERP is an independent, vendor-neutral ERP advisory firm with deep in-house government contracting expertise. For the systems it has published guides on, accounting and EVMS, it provides independent readiness advice on the cost structure, controls, and data foundation against the criteria in those clauses. For the other systems named in DFARS 252.242-7005 (or its class-deviation successor 252.242-7998 for new solicitations and contracts), estimating, MMAS, property management, and purchasing, Lightbridge ERP advises on how the underlying ERP platform and related processes can support each system's evidentiary and control requirements. Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, its recommendations follow fit rather than commission. This guide is general information, not legal, audit, or accounting advice; confirm current clause language and thresholds against acquisition.gov and official DCAA and DCMA guidance before acting.

From six systems on paper to controls ready for review.

When the question shifts from what the business systems rule requires to whether your systems and controls are ready for a DCAA or DCMA review, Lightbridge ERP provides an independent, vendor-neutral readiness engagement across the accounting, control, and platform layers the rule tests.

Talk to an ERP advisor DCAA-compliant accounting