DCAA-compliant ERP advisory for government contractors
Guide

DCAA-approved accounting system

What makes an accounting system DCAA-approved, how pre-award surveys work, and the documentation auditors require. Book an assessment.

DCAA-approved accounting system

"DCAA-approved" is not an official regulatory term, but it is widely used in the government contracting community to mean an accounting system that has received a finding of "adequate" from DCAA following an accounting system review. The approval is contractor-specific and system-specific — it applies to the system as implemented at that contractor, not to the software product in general.

Understanding this distinction prevents two expensive mistakes: assuming that purchasing a vendor's "DCAA-approved" software guarantees compliance, and assuming that a competitor's adequate finding means your identical software configuration will also pass.

The regulatory basis: DFARS 252.242-7006

The formal standard for accounting system adequacy is published in DFARS 252.242-7006, which appears as a contract clause in cost-reimbursable contracts above certain thresholds. The clause requires contractors to maintain an accounting system that meets 18 specific criteria and to disclose any significant changes to the system.

The clause also establishes consequences for inadequacy:

  • The contracting officer may withhold up to 10% of billings (maximum $1M per contract) pending resolution
  • The contracting officer must notify DCAA of findings
  • Repeated inadequacy findings can affect past performance ratings used in source selections

How the pre-award accounting system survey works

A pre-award accounting system survey (also called an accounting system review or ASR) is typically requested by the contracting officer when:

  • A contractor is being considered for its first cost-reimbursable contract
  • A contractor's existing system has not been reviewed within the past 3 years
  • A contractor has experienced significant system changes since the last review
  • DCAA identifies risk indicators (rapid growth, prior findings, complex cost structure)

The survey process:

  1. Survey request: the contracting officer submits a request to the appropriate DCAA field office
  2. DCAA contacts the contractor: typically within 10–30 days; schedules an entrance conference
  3. Data request: DCAA requests chart of accounts, sample transactions, timesheet data, billing history, and system documentation
  4. On-site review: 1–5 days on-site; DCAA tests specific system functions (can they enter backdated time? Do indirect rates reconcile? Are unallowable costs excluded from billing?)
  5. Preliminary findings: DCAA shares preliminary findings; contractor has an opportunity to respond
  6. Final report: DCAA issues a formal report to the contracting officer; adequate or inadequate with specific deficiencies
  7. Recommendation: DCAA recommends for or against award on the accounting system dimension (the CO makes the final award decision)

What DCAA actually tests during the review

The survey is not a document review — it is a system test. Auditors interact with the system to confirm that controls function as described. Common tests:

Timekeeping test: the auditor attempts to enter time for a period that is closed. If the system allows it (even with a warning), criterion 5/6 is at risk. The auditor may also interview employees to confirm they enter their own time daily, not weekly in batch.

Indirect rate test: the auditor traces an indirect cost from source document through the indirect cost pool to the allocation calculation. If the pool definition does not match the disclosure statement, the rate is wrong.

Unallowable cost test: the auditor selects a sample of costs and checks whether any unallowable costs (entertainment, lobbying, etc.) flowed through billing calculations.

Billing reconciliation test: the auditor traces a billing to the underlying cost data. The billed amount must reconcile to actual incurred costs at provisional rates.

Audit trail test: the auditor requests the transaction history for a modified entry. Who changed it, when, and what was changed must be visible and immutable.

QuickBooks and DCAA approval: the specific issues

Many contractors ask whether QuickBooks can pass a pre-award survey. The answer depends on the specific review, the complexity of the contract, and the configuration of add-on tools. The recurring challenges:

Timekeeping criterion: QuickBooks Time (TSheets) can be configured for daily entry and approval, but the period-lockout control (preventing entry after period close without documented exception) is weaker than purpose-built govcon systems. This is the most common failure point.

Indirect rate criterion: QuickBooks has no native indirect cost pool mechanism. Manual journal entries at period-end are the alternative. DCAA is skeptical of manual processes because the audit trail for a manual journal entry is weaker than an automated rate calculation.

ICS generation criterion: QuickBooks does not generate ICS schedules. The contractor must produce them from exported data, typically using spreadsheets. DCAA accepts this but views it as a higher-risk process.

For a more detailed analysis, see QuickBooks for government contractors.

What to do if your system receives an inadequate finding

An inadequate finding triggers a formal response process:

  1. Request the specific findings in writing within 10 business days. DCAA must identify which of the 18 criteria failed and the specific deficiency for each.
  2. Assess severity and priority: timekeeping and direct/indirect segregation findings are typically the most urgent to remediate; ICS formatting findings are the most straightforward.
  3. Submit a corrective action plan to DCAA and the ACO within 30–60 days. The plan must name the responsible party, the corrective action, and the completion date for each deficiency.
  4. Implement the corrections: this may involve software reconfiguration, policy updates, training, and documentation changes.
  5. Request a follow-up survey: after remediation is complete, request that DCAA conduct a focused follow-up on the specific deficiencies identified. A full re-survey is not always required.
  6. Negotiate an interim billing arrangement: while findings are being resolved, negotiate with the ACO to maintain partial billing rather than having all payments withheld.

ROI model: the cost of an inadequate finding

Item Conservative Aggressive
Billing withholding (10% of billings) on $5M contract $500,000 $500,000
Duration of withholding 60 days 180 days
Cash flow impact (at 5% cost of capital) $4,200 $12,500
Legal / consultant remediation cost $25,000 $100,000
Total cost of finding ~$29,000 ~$112,500
Cost of purpose-built govcon ERP implementation $50,000 $300,000

Illustrative model only. Actual figures depend on contract size, finding severity, and remediation complexity.

The model understates the full cost because it excludes: delayed contract award (revenue not received during the survey period), past performance impact on future proposals, and management time spent on remediation.

Ready to evaluate your options?

GovCon accounting and ERP decisions have long compliance tails. An implementation specialist can walk through your contract mix, indirect rate structure, and DCAA exposure before you commit to a platform.

Book an assessment — practitioner conversation, no sales deck.


Related guides

Frequently asked questions

No. DCAA does not publish or maintain a list of approved systems or software. Contractors, law firms, and consultants sometimes publish informal lists of "systems that have passed DCAA surveys" based on client experience — these are anecdotal, not official.