A contractor purchasing system review evaluates how effectively a government contractor buys goods and services, manages subcontracts, and follows government purchasing requirements. The review supports the administrative contracting officer’s decision to approve, withhold approval of, or withdraw approval from the purchasing system. If you are asking what is a contractor purchasing system review, the key distinction is that the government evaluates the purchasing system and its actual purchasing records, not simply one purchase or a software product.
What Is a Contractor Purchasing System Review: Purpose and Responsibility
The CPSR examines procurement policies, procedures and purchasing practices together. A written procurement manual alone does not demonstrate an effective purchasing system: the subcontract files must show how employees actually selected suppliers, evaluated prices and administered purchases. The Federal Acquisition Regulation connects that evaluation to the government’s purchasing-system approval decision.
The Defense Contract Management Agency commonly conducts CPSRs for defense contractors. The administrative contracting officer determines whether a review is needed and makes the purchasing-system approval decision. A contractor can prepare documentation and discuss readiness with the contracting officer, but buying software or requesting a review does not itself produce government approval.
A purchasing system includes supplier selection, price analysis, negotiation, purchase orders, subcontract administration and delivery follow-up. The scope extends beyond accounting records: reviewers need evidence that the contractor’s procurement decisions comply with the applicable prime contract and federal regulations.
Contractor Purchasing System Review Thresholds and Timing
Sales thresholds trigger a determination of whether a CPSR is needed, not an automatic requirement to conduct a full review. Under FAR 44.302, the general threshold is expected government sales above $25 million over the next 12 months; the defense rule uses $50 million instead. Contract categories and the applicable agency rules matter, so total company revenue is not the same measurement.
| Requirement | Figure or period | Meaning |
|---|---|---|
| General FAR review level | Above $25 million in expected government sales over the next 12 months | Determine whether a CPSR is needed; apply the sales exclusions in FAR 44.302. |
| Defense review level | Above $50 million in expected government sales over the next 12 months | The Department of Defense rule substitutes this threshold for the FAR level. |
| Later review decision | At least every three years | The contracting officer determines whether another purchasing-system review is necessary. This is not an automatic full-review schedule. |
The FAR excludes competitively awarded firm-fixed-price contracts, competitively awarded fixed-price contracts with economic price adjustment, and commercial supplies and services purchased under Part 12 from the threshold calculation. Sales otherwise include relevant prime contracts, subcontracts under government prime contracts and modifications. The responsible agency may adjust the review level.
Past performance and the volume, complexity and value of subcontracting also affect the decision. Being below a headline threshold does not settle every contractor’s situation. Before treating a number as a requirement, establish the agency, applicable contracts and sales included in the calculation.
Pro-Tip: Run a mock review using completed procurement files, not just the policy manual. Ask a reviewer to trace a purchase from the authorized request through competing quotations, supplier selection, price analysis, approval and subcontract terms. When a required decision cannot be reconstructed from the file, record the missing evidence, assign an owner and correct the working process. Check another file afterward to see whether the correction is being used. This tests whether the purchasing system works in practice rather than whether the manual describes a good process.
Contractor Purchasing System Review Documentation and Audit Areas
Reviewers examine whether procurement files support the supplier selected, the price paid and the subcontract terms used. FAR 44.303 identifies market research, competition, pricing methods, subcontractor responsibility and purchasing-system controls among the areas receiving attention. The evidence must correspond to the actual purchasing action.
- Supplier selection: Retain market research, quotations and the reasons for choosing the supplier. A supplier name alone does not explain the selection.
- Fair and reasonable pricing: Keep the applicable price or cost analysis and supporting data. A quotation records what a supplier requested; the analysis explains why the proposed price is acceptable.
- Responsibility checks: Document the supplier checks, including applicable SAM.gov exclusions checks and the handling of any issue.
- Contract terms: Include mandatory and applicable flow-down clauses from the prime contract. A generic clause package is not proof that the correct requirements reached a particular subcontract.
- Management controls: Show purchasing authority, internal audits, training, subcontract surveillance and the handling of subcontract changes.
- Other applicable requirements: Review small-business policies, Cost Accounting Standards, subcontract type selection and progress-payment controls where applicable.
For defense contracts containing the Basic clause, the DFARS Contractor Purchasing System Administration clause sets out 24 purchasing-system criteria. The criteria address both written controls and transaction documentation. Keep the distinction between a system requirement and a document needed for a specific purchase: not every purchasing action calls for identical analysis or certifications.
Contractor Purchasing System Review Types and Follow-Up
The DCMA CPSR Guidebook distinguishes initial or comprehensive reviews, special reviews and follow-up reviews. An initial or comprehensive review examines the purchasing system broadly. A special review concentrates on identified concerns or changes. A follow-up review examines whether corrective action has addressed earlier findings. These are review purposes, not different software certifications.
Keep the review scope with the purchasing records requested for that review. A response to a specific finding should connect the finding, the corrective action and the evidence that the correction has been implemented. Supplying an updated purchasing manual without evidence of changed purchasing practice does not explain whether the original problem was resolved.
For example, if a file lacked the rationale for a noncompetitive purchase, the useful corrective evidence includes the required approval, supporting analysis and an explanation of how future files will capture the same decision. That is a preparation example, not a claim that every finding requires the same documents.
Contractor Purchasing System Review Sales Calculation Examples
The following hypothetical calculations illustrate the thresholds, not actual contractor results. Assume the amounts are qualifying expected government sales for the next 12 months after exclusions, and assume the agency has not adjusted the review level. Compare the applicable sales amount with the applicable agency threshold before deciding whether a threshold-based CPSR determination is triggered.
| Illustrative expected sales | General $25 million level | Defense $50 million level |
|---|---|---|
| $30 million | $5 million above the level | $20 million below the level |
| $60 million | $35 million above the level | $10 million above the level |
The $30 million example explains why the agency distinction matters: the same sales figure exceeds one threshold but not the other. The $60 million example exceeds both. Neither calculation guarantees a full CPSR or a purchasing-system approval; the contracting officer still makes the relevant determination. Do not add commercial revenue excluded by the rule merely to make the company total match a threshold.
A contractor asking what is a contractor purchasing system review needs both the sales calculation and the purchasing-system context. Review the subcontracting volume, subcontract complexity and past performance alongside the applicable government sales. A small business with a different contract mix can have a different review position from a larger company with the same total revenue.
Contractor Purchasing System Review Price Analysis and Competition
Competition and price analysis explain why procurement spending is reasonable. The defense purchasing-system criteria require competitive sourcing where practicable and timely, adequate price or cost analysis. Sole-source and single-source awards require management-level justification and the appropriate analysis; removing competition does not remove the need to support the price.
For a competitive purchase, the procurement file should connect the quotations to the actual requirement. Differences in quantity, delivery, specifications or included services can make headline prices misleading. Record the comparison used to make the decision rather than leaving a reviewer to infer why one quotation was chosen.
For a noncompetitive purchase, retain the reason for the sourcing decision separately from the pricing rationale. A supplier’s unique capability can explain why the supplier was selected, but that explanation does not by itself show that the price is fair and reasonable. Preserve the supporting price or cost data and any negotiation record relevant to that purchasing action.
Contractor Purchasing System Review Approval and Its Limits
The approval decision concerns the contractor purchasing system as a working set of procurement controls. Keep the approval correspondence with the purchasing policies and procedures so employees can check the purchasing system’s status and any specific limitations before relying on it.
An approved purchasing system can reduce the need for individual consent to subcontract, but approval does not remove every consent requirement. Under FAR 44.201-1, consent still applies to subcontracts specifically identified by the contracting officer in the contract’s subcontract clause. The officer can require individual consent because of subcontract type, value, complexity or surveillance needs.
This distinction matters when deciding what is a contractor purchasing system review versus consent to subcontract. The CPSR evaluates the purchasing system; consent addresses a subcontract action. An approved system is not a guarantee of future contract awards, nor does approval excuse a contractor from following the prime contract’s terms.
Approval brings continuing administrative responsibilities as well as flexibility. Purchasing policies, training and procurement documentation must remain effective after the review. Preparation is not finished when a review team leaves.
Contractor Purchasing System Review Small-Business and Subcontract Controls
The CPSR also examines the purchasing system’s treatment of small business concerns. FAR 44.303 identifies policies and procedures for small disadvantaged, women-owned, veteran-owned, HUBZone and service-disabled veteran-owned small businesses. This concerns the contractor’s purchasing practices; it does not mean that every small business is automatically scheduled for a review.
Keep the applicable small-business requirements connected to the prime contract and the purchasing system’s supplier-selection process. A supplier category is not a substitute for documenting the actual procurement decision. The purchasing system still needs to show the selected supplier’s responsibility, the basis for the price and the terms included in the subcontract.
Other review areas include the appropriate subcontract type, Cost Accounting Standards where applicable, and management controls over subcontractor progress payments. A purchasing system review therefore reaches beyond the initial supplier quotation. For purchasing actions subject to those requirements, keep the supporting decisions available with the purchase documentation rather than relying on an employee’s recollection.
The purchasing policies and procedures should also explain how employees handle a subcontract change affecting cost or price. A changed specification, quantity or delivery requirement can change the procurement record. Keep the approved change, the pricing support and the reason for the adjustment connected so the purchasing system provides a complete history of the transaction.
Contractor Purchasing System Review Preparation With SpendLogic
A practical purchasing-system file check starts with the purchase request and ends with evidence of delivery and subcontract administration. Put the authorization, quotations, selection rationale, price analysis and subcontract terms where the reviewer can follow the purchasing decision. For a changed purchase order, retain the reason for the change and the effect on price rather than leaving only the revised total.
Prepare by bringing purchasing policies and completed procurement files into agreement. Start with the applicable requirements, examine a representative selection of purchasing actions and resolve gaps in the records and the underlying process. Updating a policy without changing daily purchasing practices leaves the same documentation problem in the next file.
Assign responsibility for supplier-selection records, price analysis, purchasing approvals and applicable flow-down clauses. Retain evidence of the checks actually performed. When employees use different forms or approval routes, confirm that each route captures the required information and that the purchasing manual describes the process employees follow.
SpendLogic’s tools automate procurement documentation tasks and provide step-by-step guidance on daily procurement documentation requirements. The software supports preparation and documentation, while the government retains the purchasing-system approval decision. Learn more through SpendLogic’s Guide to CPSR or schedule a demo.
