Incurred cost submissions that survive DCAA review without findings

ICS submissions are due six months after fiscal year-end and prove the rates

Every CAS-covered or FAR-flowdown contractor with cost-reimbursable work owes an incurred cost submission to DCAA within six months of fiscal year-end. The submission proves what the contractor actually spent in the year and trues up the provisional billing rates that were used to bill indirect costs throughout the year. The numbers in the ICS are the audit's primary input. If they cannot be reconciled to the underlying ledger, every line becomes a finding.

We have audited contractors who built their ICS in a 200-tab Excel workbook updated quarterly. The workbook was internally consistent. It also took six weeks to produce, three weeks to defend during the audit, and produced findings every cycle because the spreadsheet had drifted from the ledger in ways nobody could explain at audit.

Schedules A through O have a defined structure DCAA expects

The ICAM (Incurred Cost Audit Manual) and the ICE model define the schedule structure. Schedule A is the indirect rate summary; Schedule B breaks down the overhead pool; Schedule C breaks down G&A; H summarizes direct costs by contract; I is the contract-level schedule with billings, costs, and over/under positions; J is subcontract awards over the threshold; K is hours by contract; and so on through O. The structure is not optional and not negotiable.

Our GovCon ERP module generates each schedule directly from the ledger. The line items reconcile to the trial balance by construction. The schedule numbers tie to the underlying transactions through a clickable lineage trail. Auditors verify samples by drilling down rather than by reconstruction.

Schedules generated

A–O directly from ledger

ICS prep time

< 1 wk down from 6 wks

Audit response time

Hours per inquiry

Findings, last 4 audits

0 across deployed clients

Indirect rate computations have to be deterministic and reproducible

Every indirect rate is the ratio of pool to base. Fringe pool over total labor dollars. Overhead pool over direct labor. G&A over total cost input. The arithmetic is trivial; the discipline is in deciding what is in the pool, what is in the base, what is unallowable and excluded, and what allocation method the DCAA-accepted disclosure statement specifies.

When the rates are computed in spreadsheets, the inputs and the exclusions drift across cycles. When they are computed in the ERP from the chart of accounts and the unallowable flags, the rates are reproducible by definition. Re-running the computation against the same data always produces the same rate. That reproducibility is what audit defends.

Provisional billing rate true-up is the audit's central question

The contractor billed indirect costs throughout the year at provisional rates. The ICS computes actual rates against actuals. The difference is the true-up — additional billing if actual rates exceeded provisional, refunds if provisional exceeded actual, accrued in the ICS submission for settlement after audit. DCAA's job is to verify the true-up math; the contractor's job is to make the math obvious.

When the provisional billing throughout the year and the ICS true-up come from the same system of record, the math is obvious. The provisional billings show up in the contract billing detail. The ICS shows the actual rates and the variance. The auditor reconciles the two in an afternoon. When provisional billing was done in one system and the ICS in a spreadsheet, the auditor spends a week tracing reconciliations and finds errors.

Subcontracts and unallowable costs are where reviews dig hardest

Subcontracts over the threshold owe Schedule J disclosure with award amount, period of performance, and small-business socioeconomic categorization. Unallowable costs need to be excluded from rate calculations and disclosed in Schedule M. Both are areas DCAA audits aggressively because they are areas contractors often handle inconsistently.

Account-level unallowable flags propagate automatically into the rate computation and the Schedule M disclosure. Subcontract data flows from the procurement module into Schedule J without manual entry. The contractor stops 'preparing' these schedules because they generate themselves.

DCAA self-service is the goal — and the productivity unlock

When DCAA can run their own queries against the ledger, sample transactions themselves, and verify schedule numbers without controller-team mediation, the audit moves from controller-bound to auditor-paced. We deploy read-only DCAA access to the relevant ledger views and the schedule generation logic. The auditor uses it; the controller team supports rather than reconstructs.

This is the model the DCAA itself prefers. Contractors who provide self-service access get faster audits with fewer findings, because the auditor's time goes to actual examination rather than waiting on document requests. Contractors who guard ledger access get slower audits with more findings, because every controller-team handoff is a chance to introduce inconsistency.

The DCAA auditor told us he wished every contractor's ICS came out of a system this way. He used to spend his year reconciling spreadsheets. With us he spent his year auditing actual transactions. He cleared the engagement in two-thirds the time and zero findings.

— Government Compliance Director, defense subcontractor

What it takes to get there

Generating ICS schedules directly from the ledger requires the upstream architecture: clean indirect rate pool structure (three pools, allocation bases defined), unallowable cost segregation at the account level, project-level labor distribution, subcontract data integrated with procurement, and a chart of accounts that maps to the ICS schedule structure. None of that is achievable post-hoc; it is a phase-one decision in the GovCon ERP migration.

Contractors that try to retrofit ICS automation onto a commercial ERP without that foundation discover the foundation matters. The retrofit ends up producing schedules that are technically generated by code but still need controller reconciliation against the ledger. The unlock is the foundation, not the report writer.

Frequently asked

What is an incurred cost submission? +

An incurred cost submission (ICS) is the annual filing CAS-covered and cost-reimbursable government contractors owe DCAA within six months of fiscal year-end. It documents actual indirect rates against the provisional billing rates used during the year and trues up the difference. The submission is the audit's primary input; reconciling it to the underlying ledger is the central audit activity. Schedules A through O follow a defined structure in DCAA's ICAM model.

Why generate ICS schedules from the ledger instead of spreadsheets? +

Because spreadsheets drift from the ledger between quarterly updates, and the drift surfaces as audit findings. Generating schedules directly from the ledger means the line items reconcile to the trial balance by construction, the underlying transactions are reachable through clickable lineage, and the auditor can verify samples without controller-team reconstruction. Findings drop, audit duration shortens, and the controller team stops spending six weeks producing the workbook.

How does provisional billing rate true-up work? +

Throughout the year, contractors bill indirect costs at provisional rates set at the start of the fiscal year. The ICS computes actual rates from year-end actuals. The variance — actual minus provisional, applied to the billable base — produces the true-up: additional billing if actuals exceeded provisional, refund if provisional exceeded actuals. Both numbers are accrued in the ICS submission and settled after audit clearance.

What does DCAA self-service access actually look like? +

Read-only access to the relevant ledger views, the schedule generation logic, and the sampling tools, scoped to what the audit needs. The auditor runs their own queries, samples transactions, drills into rate computations, and verifies schedule numbers without waiting on the controller team to produce documents. Contractors who provide this access get faster audits with fewer findings; contractors who guard access get the opposite.

How are unallowable costs handled in the ICS? +

Unallowable costs are flagged at the GL account level, automatically excluded from indirect rate calculations, and disclosed in Schedule M. The flag propagates through every rate calculation and report generation, so unallowable costs can never accidentally enter a pool or a base. Manual unallowable cost identification at month-end is a failure mode; account-level flags make the control automatic and verifiable by audit.

How long should it take to prepare an ICS with this architecture? +

Less than a week, where it used to take six weeks. The schedules generate from the ledger, the rate calculations are reproducible, the subcontract and unallowable disclosures populate automatically. The remaining work is policy review, executive sign-off, and the cover narrative. Audit response time during fieldwork drops from weeks of digging to hours of explanation, because the underlying data and the submission share a single source of truth.