Contractors tend to think about accounting system adequacy as a compliance box — something to pass so the auditors go away. It is more useful to think about it as a gate. A company without an adequate accounting system cannot be awarded a cost-reimbursable contract. Which means the system is not primarily a compliance artifact at all. It is the thing standing between a contractor and an entire category of work, and by extension between it and a class of buyers.
What the SF1408 Actually Is
Standard Form 1408 is the Preaward Survey of Prospective Contractor Accounting System. When a contracting officer is considering awarding a cost-type contract to a company that has not held one, DCAA is typically asked to perform a survey and report on the SF1408 whether the system is acceptable for award.
The critical thing to understand is what the preaward survey does and does not test. It asks whether the system is designed to accumulate and segregate costs appropriately — not whether it has done so successfully over years of operation. It is a design review, not a performance audit. A company can pass the SF1408 on a system that has never processed a cost-reimbursable invoice.
Passing the preaward survey means the system is capable. Surviving an incurred cost audit three years later means it actually worked. Contractors regularly assume the first proves the second, and are surprised when it does not.
The Criteria
The SF1408 walks through a set of design questions. In substance, the system must:
The DoD Business System Rule
For DoD contractors the obligation extends past the preaward survey. DFARS 252.242-7006, the Accounting System Administration clause, applies to covered contracts and sets out a detailed list of system criteria — considerably longer than the SF1408 — that the contractor's system must satisfy on an ongoing basis.
The consequential difference is the enforcement mechanism. Under the DFARS business systems framework, a system determined to have significant deficiencies can result in payment withholding. This is not a finding to be remediated at leisure while cash continues to flow. It is a direct interruption of receipts, applied against a company whose cost structure does not pause while the deficiency is corrected.
For a mid-market contractor operating on modest working capital, a withhold is an existential-category event rather than a compliance annoyance. It is the single strongest practical argument for investing in system adequacy before it is tested.
Where Growing Contractors Actually Fail
The failures cluster in predictable places, and almost none of them are about accounting software.
The system was sized for the company that existed at setup. A structure built to handle three contracts and one indirect pool is still in place at thirty contracts across multiple task-order vehicles. It technically functions. It does not produce clean contract-level cost data without manual intervention, and manual intervention is what auditors look for.
Job cost and general ledger have drifted apart. Reconciliation happens quarterly, or annually, or when someone notices. Every unreconciled period is an unresolved question about whether claimed costs are supportable.
Unallowables are reconstructed rather than segregated. Covered at length elsewhere in this volume, and the single most common source of expanded audit scope.
Timekeeping is compliant on paper. A policy exists. Whether employees follow it daily, whether supervisors approve meaningfully, and whether corrections are documented with reasons is a different question, and it is the question a floor check answers.
Nobody owns it. The system was configured by a consultant who left, is maintained by a controller who inherited it, and is understood end-to-end by nobody currently employed. This is simultaneously a compliance risk and, in a transaction, a founder-dependency finding.
The Valuation Consequence
System adequacy shows up in a transaction through three separate doors.
It determines what work the company can pursue. A contractor without an adequate system is confined to fixed-price and commercial work, which caps the addressable pipeline and constrains the growth story a buyer is being asked to underwrite.
It determines how much diligence hurts. Quality of earnings work on a contractor with clean contract-level cost data is a manageable exercise. On a contractor where contract profitability has to be reconstructed from spreadsheets, it becomes slow, expensive, and productive of exactly the kind of adjustments that reduce purchase price.
It determines who can buy the company. A private equity platform intending to bolt on additional contractors needs a system that can absorb them. A strategic acquirer needs one it can integrate. A system that only works because one person knows its quirks is not acquirable in the way either buyer needs.
None of this argues for a system built to a standard the company does not need. It argues for the system being deliberately sized to the work the company intends to win, reviewed when the work changes, and understood by more than one person.
Frequently Asked Questions
Ready to assess your readiness?
Take the GovCon CFO Readiness Diagnostic and benchmark your organization across compliance, reporting, forecasting, and M&A readiness.
Take the Diagnostic