Why DCAA and FAR Compliance Create Unique Expense Tracking Pressure
Federal Acquisition Regulation Part 31 defines which costs the government will reimburse on cost-reimbursable contracts. Every expense — from travel and meals to supplier invoices and equipment rentals — must be documented as allowable under FAR, allocated to the correct contract or indirect pool, and supported by original receipts with sufficient detail to withstand a DCAA audit. This is not a paperwork formality. DCAA auditors can test any transaction at any time, and a missing receipt or miscoded charge number is treated as an unsupported cost — which the company must absorb.
The challenge is structural. Aerospace program teams work across distributed locations: test facilities, fabrication shops, government installations, and remote sites. A technician at a government installation buys a $40 specialty fastener at a local supply house, stuffs the receipt in a toolbox, and submits a handwritten expense report two weeks later. By then, the charge number is guessed, the receipt is illegible, and the contract period has closed. Multiply this across dozens of employees and multiple active contracts, and you have the conditions that generate DCAA findings.
Vergo proposes the contract, charge number, cost element, and indirect pool the moment a transaction happens, from your own accounting structure and history, and chases the receipt itself — so every transaction carries its documentation and coding from day one.
Contributing factors that make expense tracking hard for aerospace companies:
- Multiple active contract numbers — employees must allocate costs to the correct CLIN, task order, or indirect pool in real time, not from memory
- Mixed direct and indirect costs — a single trip may contain both billable (direct) and non-billable (indirect/overhead) expenses that must be split accurately
- Government vs. commercial work on the same team — cost transfer between contract types triggers heightened scrutiny
- Manual, paper-based receipt workflows — documentation collected after the fact is incomplete by design
- ERP coding enforced only at month-end — when finance reconciles, employees can no longer remember which contract the cost belonged to
The Real Impact of Weak Expense Documentation
For aerospace companies operating on cost-reimbursable, T&M, or CPFF contracts, inadequate expense tracking carries consequences that go beyond a difficult audit cycle. Vergo's inference-based coding proposes the correct contract and cost element from your own accounting structure and history, so program teams confirm allocations in seconds instead of guessing from memory.
- Disallowed costs become direct financial losses. When DCAA disallows a cost, the company absorbs it — it cannot be billed to the government. On large programs, undetected miscoding can accumulate into large write-offs at audit.
- Indirect rate distortion. Costs booked to the wrong pool (G&A vs. overhead vs. fringe) distort provisional billing rates, leading to either underbilling or overcharges that require expensive rate adjustments.
- Incurred Cost Submission (ICS) errors. The annual ICS filing to DCAA reconciles estimated and actual indirect rates. Expense records with gaps or unsupported allocations create ICS findings that drag out audits.
- Fraud and False Claims Act exposure. Repeated patterns of unsubstantiated charges — even unintentional — can escalate from administrative findings to referrals under the False Claims Act.
- Month-end close delays are common when finance teams must chase down receipts, reconstruct allocations, and correct cost transfers before closing the books on a contract period.
How Leading Aerospace Companies Build Bulletproof Expense Tracking
The modern approach to DCAA-compliant expense management captures coding at the moment of purchase — not during reconciliation. Every expense carries the contract number, CLIN or charge number, cost element, and indirect pool before it reaches the ledger. Receipts are captured and timestamped. Approval workflows are tied to contract authority levels. The result is an audit-ready record created in real time, not reconstructed after the fact.
How Vergo Helps
Vergo is a card-agnostic expense and AP platform for aerospace and defense finance teams. Connect the corporate cards you already have and get full visibility and control over distributed program spending.
- Contract-level coding at the point of capture — Vergo proposes the contract number, CLIN or charge number, cost element, and indirect pool, and shows why, so reviewers confirm instead of re-keying.
- Allowable vs. unallowable flags — policy flags catch charges that need a second look, such as alcohol or entertainment, before they reach a direct contract.
- Receipts by text or from their phone — technicians and program managers submit receipts the moment they buy, and Vergo chases anything missing.
- Role-based approval workflows — route expenses through program managers, contract-level approvers, and controllers based on your org structure.
- Vergo integrates with Deltek Costpoint, Acumatica, IFS, and other aerospace ERPs, syncing coded expenses to the right charge number, program, and GL account without manual re-entry.
Related Questions
Where should you go next?
Frequently Asked Questions
What does DCAA look for when auditing expense reports?
DCAA auditors verify that each expense is allowable under FAR Part 31, allocated to the correct contract or indirect cost pool, and supported by original documentation — receipt, business purpose, and attendees if applicable. They also test whether approval authority matched contract requirements. Missing receipts or undocumented business purpose are the most common findings.
What is the difference between direct and indirect costs under FAR Part 31?
Direct costs are specifically identified with a single contract — materials, labor hours, and supplier charges billed to a particular CLIN. Indirect costs benefit multiple contracts and are pooled into overhead, G&A, or fringe rate categories. Misclassifying a direct cost as indirect (or vice versa) distorts both billing rates and contract profitability.
How do indirect rate errors in expense tracking affect the annual Incurred Cost Submission?
The ICS reconciles provisional billing rates against actual costs incurred. If expenses are miscoded to the wrong indirect pool throughout the year, the ICS will reflect distorted rates. DCAA may disallow costs, require rate adjustments, or issue a qualified audit opinion — all of which delay final contract closeout and cash settlement.
Why do general-purpose expense tools fall short for DCAA compliance?
General-purpose expense tools lack contract-level coding, CLIN and charge number structure, and FAR Part 31 cost element categories. They cannot keep indirect pools straight or produce the audit trail DCAA requires. Controllers end up exporting data and manually reclassifying costs in the ERP — reintroducing the human error the tool was supposed to eliminate.
How does Vergo help aerospace companies meet DCAA expense documentation requirements?
Vergo codes every expense to the contract, CLIN or charge number, and cost element from your own history, chases missing receipts, and keeps timestamped approvals. It integrates with Deltek Costpoint, Acumatica, IFS, and other aerospace ERPs, posting coded expenses to the right program and GL account — an audit-ready record without manual reclassification.
What are the most common expense-related findings in a DCAA floor check?
Floor checks most frequently cite missing or illegible receipts, unallocated or unallocable expenses charged to direct contracts, costs lacking documented business purpose, and unapproved charges exceeding contract authority thresholds. Travel and entertainment costs are the highest-risk category because they require both original receipts and documented connection to contract performance.
