Paper 06 of 13

ICS preparation takes40 to 120 hoursin a legacy ERP firm.It takes zero hours in a compliant one.

12 min reading time
Compliance Mechanics

Interim Cost Submissions (ICS)

"ICS preparation time is a direct measure of compliance architecture quality. A firm that requires 40 to 120 hours to prepare an ICS package is demonstrating that its systems did not maintain cost data in ICS-ready format throughout the year. A contract-native system requires zero hours because the ICS schedules are continuously generated from live operational data."

Paper 6 covers ICS purpose and regulatory requirements, the full required schedule structure (Schedules A through O), rate forecasting mechanics, pool/base reconciliation, daily ICS readiness, and the six most common ICS findings — and how each is prevented by architecture rather than annual effort.

Paper 6 makes a distinction that most GovCon firms miss: rate forecasting is not a financial planning exercise. It is a compliance early warning system. A firm that forecasts its year-end indirect rates monthly using live pool and base data can identify a 15% provisional rate variance in March and revise its PBR agreement in April. A firm that discovers the same variance at ICS submission in June has no options left — only retroactive billing adjustments and a billing system adequacy question from DCAA about why the variance was not identified and addressed earlier.

What This Paper Defines

  • Schedule B data extracted from G/L — weeks before deadline
  • Schedule C reconciled from timekeeping, payroll, and G/L separately
  • Unallowable cost review performed at submission time
  • Rate calculations performed at submission from assembled data
Doctrine Access

Download the Executive Paper

Complete the form to receive the full research, frameworks, and architectural blueprints.

You will receive a direct download link by email.
xpdOffice does not share your information with third parties.

The Argument

Why Rate Forecasting Is a Compliance Early Warning System

Paper 6 makes a distinction that most GovCon firms miss: rate forecasting is not a financial planning exercise. It is a compliance early warning system. A firm that forecasts its year-end indirect rates monthly using live pool and base data can identify a 15% provisional rate variance in March and revise its PBR agreement in April. A firm that discovers the same variance at ICS submission in June has no options left — only retroactive billing adjustments and a billing system adequacy question from DCAA about why the variance was not identified and addressed earlier. ""Rate forecasting is not a financial planning exercise. It is a compliance early warning system. The difference between identifying a 15% PBR variance in March and discovering it at ICS submission in June is the difference between a proactive revision and a retroactive correction.""

The False Claims Act Connection

The ICS certification requirement adds a legal dimension that pure accounting submissions do not carry. When a company officer signs the ICS certification, they are certifying that all costs are allowable, allocable, and reasonable. If the submission contains costs that the certifier knew or should have known were unallowable, the certification may create False Claims Act exposure beyond the DCAA finding. This is why the unallowable cost segregation architecture in Paper 4 is not just a rate accuracy mechanism — it is a certification integrity mechanism.

ICS Readiness — The Adequacy Test

One question determines ICS readiness: if DCAA requested your ICS today — with no advance notice and no preparation time — could you submit a complete, compliant, fully reconciled package? In a contract-native system, the answer is always yes. In a legacy ERP system, the answer is: not without 40 to 120 hours of work. The preparation time is the finding.

6
Months after FYE for submission
June 30 deadline for calendar-year firms
40–120h
ICS prep in legacy ERP firms
Per engagement — eliminated by daily ICS readiness
0h
ICS prep in a compliant system
ICS is always current — never prepared
A–O
Required ICS schedule range
9 standard schedules plus supplementals

The Architecture of Choice

Side-by-side comparison of structural assumptions and operational outcomes.

ICS as Annual Preparation Project (Legacy ERP)

Schedule B data extracted from G/L — weeks before deadline

Pool cost detail must be extracted, formatted, and reconciled from the general ledger. Chart-of-accounts may not map directly to ICS schedule structure. Manual reformatting required.

Schedule C reconciled from timekeeping, payroll, and G/L separately

Direct costs per contract assembled from three systems with different transaction records. Reconciliation differences must be identified and resolved before Schedule C can be certified.

Unallowable cost review performed at submission time

Period-end review of costs to identify and remove unallowable items from pools. Corrections required retroactively. Schedule H populated from this review — not from continuous tracking.

Rate calculations performed at submission from assembled data

Schedule D rates calculated from the reconciled pool and base totals assembled during the preparation project. Rate has not been visible during the year. Variances discovered at submission.

ICS as Reporting Event (xpdOffice)

Schedule B continuously maintained from live cost entries

Every cost entry posts to the correct pool in ICS format. Schedule B is always current. No extraction, no reformatting, no reconciliation effort required at year-end.

Schedule C current by contract from every posted transaction

Direct costs organized by contract and CLIN as they are posted. Schedule C is a live view, not a year-end assembly. Reconciliation to the general ledger is a system query.

Unallowable costs segregated at entry — Schedule H always current

Costs flagged as unallowable at the point of entry are continuously tracked in Schedule H format. No year-end unallowable cost review because unallowable costs never entered pools.

Rate calculations current to last write event all year

Schedule D rates updated on every cost entry. Rate variance from provisional rates visible daily. Variances identified and addressed months before the ICS deadline.

Strategic Prediction

Strategic Insight

""Rate forecasting is not a financial planning exercise. It is a compliance early warning system. The difference between identifying a 15% PBR variance in March and discovering it at ICS submission in June is the difference between a proactive revision and a retroactive correction.""

Frequently Asked Questions

What happens if ICS is submitted late?

FAR 52.216-7(d) gives the contracting officer authority to withhold subsequent billings when an ICS is not submitted by the deadline. The withhold typically applies to a percentage of billed amounts across all cost-type contracts under the cognizant contracting officer. The withhold is released when the overdue ICS is submitted. Beyond the immediate cash flow impact, late ICS submission signals to DCAA that the firm's financial management systems are not maintaining adequate cost records — which typically results in a more intensive incurred cost audit when the ICS is eventually submitted.

What is the difference between an ICS and a FICS?

The ICS (Interim Cost Submission) is submitted annually for each fiscal year while contracts are still active. It covers costs for a single fiscal year and reconciles provisional billing rates to actual rates for that year. The FICS (Final Incurred Cost Submission) is submitted when all cost-type contracts in a given fiscal year reach final settlement — meaning all deliverables have been accepted, all billings have been made, and all rate adjustments have been finalized. The FICS closes out the cost accounting for those contracts permanently. Paper 7 covers FICS mechanics in detail.

How many years of ICS can DCAA audit simultaneously?

DCAA audits ICS submissions on a rolling basis and maintains a backlog. It is common for DCAA to be auditing three to five years of ICS submissions simultaneously for a large firm. This means that cost accounting inconsistencies in the current year may be compared to practices in prior years under audit. A firm that changed its cost accounting practices without updating its CAS Disclosure Statement may face consistency findings that span multiple audit years simultaneously. Daily ICS readiness means that every year's submission is in the same format, derived from the same system, with the same cost accounting methodology — reducing multi-year consistency risk.

Want to model your own ROI?

Use our interactive calculator to see how a contract-native architecture can transform your margin.

Run ROI Calculator