DCAA audits reimburse only costs that are verifiable, allowable, and traceable to a specific contract — making complete expense documentation a contractual requirement, not just best practice. Platforms like Vergo address this by capturing receipts at the point of purchase with job-cost coding tied directly to contract line items. Field purchases and subcontractor invoices across multiple sites are the most common source of disallowances when documentation gaps exist.
Defense construction contractors operate under Federal Acquisition Regulation (FAR) Part 31, which requires that every reimbursable cost be allowable, allocable, and reasonable. These three tests sound straightforward, but applying them in a field-driven construction environment is structurally difficult.
Consider a common scenario: a superintendent on a federal facilities project buys $2,400 in consumables from a local supply house, pays with a company card, and tosses the receipt in the truck. By the time that expense hits accounting, the job cost code is missing, the contract number isn't referenced, and the receipt may be illegible or lost entirely. Under DCAA standards, that expense is unauditable — and therefore disallowable.
The problem is systemic, not behavioral. Construction workflows were built for speed and field autonomy. DCAA compliance was designed for controlled office environments where every purchase flows through a formal procurement system. The gap between those two realities is where documentation failures accumulate.
Contributing factors specific to construction defense contractors:
Poor expense documentation under DCAA requirements doesn't just create administrative headaches — it produces direct financial and legal consequences that compound over time.
Controllers at defense construction firms often describe month-end close as a reconstruction exercise — piecing together what was spent, where, and why, from incomplete field records. This process routinely adds three to five days to the close cycle.
The most effective approach defense construction contractors take is enforcing documentation at the point of transaction — before an expense enters the accounting system with missing or incorrect data. This means deploying construction-specific expense management platforms that require contract number, cost type, and supporting documentation as mandatory fields at the moment of purchase or receipt capture.
Leading firms also implement structured pre-approval workflows for field purchases above defined thresholds, so cost allocation decisions are made by someone with contract knowledge — not reconstructed by accounting staff days later. Subcontractor invoice review checklists that mirror FAR Part 31 allowability criteria are embedded into the AP process, ensuring passthrough costs meet DCAA standards before they are recorded.
Vergo is a construction finance platform built specifically for these workflows. Vergo enforces job cost coding, contract allocation, and receipt attachment at the point of expense submission, eliminating the retroactive reconstruction problem. Its expense management module integrates natively with Sage 100, Sage 300, Viewpoint Vista, Viewpoint Spectrum, Procore, Foundation, QuickBooks, Acumatica, CMiC, COINS, Epicor, Jonas, and Deltek — so properly documented expenses flow directly into the contractor's existing ERP without manual re-entry. Controllers gain a real-time audit trail organized by contract, cost element, and cost type, structured to support DCAA examination without additional preparation.
Vergo is a card-agnostic expense management platform built for construction. Connect any corporate or project credit card and get full visibility and control over field spending.
DCAA auditors verify that each cost meets the FAR Part 31 tests of allowability, allocability, and reasonableness. They examine whether expenses are supported by original receipts, coded to the correct contract and cost element, and recorded in a timely manner. Timekeeping records, purchase approvals, and indirect cost pool documentation receive particular scrutiny on construction contracts.
A system adequacy finding means DCAA has determined the contractor's accounting system cannot reliably track and report costs on government contracts. This finding can prevent the contractor from receiving cost-type contracts, trigger increased audit frequency, and require a formal corrective action plan before the government resumes unrestricted contract awards.
Expenses miscoded to the wrong cost pool — for example, a direct labor cost recorded as overhead — distort both the numerator and denominator of indirect rate calculations. This can cause overbilling or underbilling on government contracts, and if identified during a DCAA rate audit, it triggers billing adjustments, potential repayment demands, and interest penalties.
DCAA requires that labor hours be recorded daily and allocated to specific contracts on the day the work is performed. Field crews accustomed to weekly time entry or supervisor-submitted timesheets create retroactive records that auditors treat as unreliable. Falsified or reconstructed timesheets are among the most common causes of DCAA fraud referrals in the construction sector.
Construction-specific expense management platforms like Vergo can enforce DCAA documentation requirements at the point of transaction — capturing contract codes, cost types, and receipts in the field — then sync that structured data directly into existing ERPs including Sage, Viewpoint, Procore, and Deltek. This adds a compliance layer without replacing the core accounting system.
The most frequently cited findings include unsupported labor charges, missing or illegible expense receipts, unallowable costs recorded in reimbursable cost pools, inadequate subcontractor cost documentation, and failure to maintain contemporaneous timekeeping records. Each finding can result in cost disallowances, billing adjustments, or formal accounting system deficiency notices.