Unallowable costs that enteran indirect pool overstate every rateapplied to every contractfor the entire year.
Job Costing and Indirect Rates
"Indirect rate adequacy is not achieved by calculating accurate rates at period end. It is achieved by a cost accumulation system that evaluates allowability at entry, segregates unallowable costs before they contaminate pools, and calculates rates from live data current to the last write event."
Paper 4 covers the complete mechanics of DCAA-compliant job costing: FAR Part 31 cost allowability, pool and base structure requirements, indirect rate calculation methodology, rate application across all contract types, and rate stability requirements for provisional billing rate adequacy.
The largest dollar exposure in most DCAA incurred cost audits comes from three sources: unallowable costs that contaminated indirect pools, rates applied to invoices that were not supported by contemporaneous cost data, and provisional billing rate variances that were not identified and addressed before ICS submission. All three are system architecture failures, not accounting errors.
What This Paper Defines
- Pool and base totals extracted at month-end close
- Unallowable costs accumulate in pools between scrubs
- Rate instability discovered at ICS submission
- FAR 42.704 ceiling breach not detected in time
Download the Executive Paper
Complete the form to receive the full research, frameworks, and architectural blueprints.
The Argument
Why Indirect Rate Adequacy Is a System Architecture Question
The largest dollar exposure in most DCAA incurred cost audits comes from three sources: unallowable costs that contaminated indirect pools, rates applied to invoices that were not supported by contemporaneous cost data, and provisional billing rate variances that were not identified and addressed before ICS submission. All three are system architecture failures, not accounting errors. ""The question is not whether the rate was correct at period end. The question is whether the rate applied to each invoice was supported by the cost data current at the time of billing. A live rate system always answers yes. A period-end system always answers: it depends on when the bill was generated.""
Rate Application Across Contract Types
Paper 4 covers rate application mechanics for all four major contract types: cost-plus contracts (actual rates applied to actual costs, reconciled at ICS), T&M contracts (indirect rates embedded in loaded labor rates), fixed-price contracts (rates embedded in price at award), and multiple award task order contracts (rate application tracked by task order type). Each has different DCAA examination focus and different ICS adjustment risk.
Three questions determine adequacy: (1) Are unallowable costs identified and segregated at the point of entry, before they can contaminate any pool? (2) Are pool and base totals current to the last write event, or to the last period close? (3) Can DCAA trace any indirect rate applied to any invoice back to the pool and base data that supported it, without manual reconstruction?
The Architecture of Choice
Side-by-side comparison of structural assumptions and operational outcomes.
Period-End Rate Calculation (Legacy ERP)
Pool and base totals extracted at month-end close
Rate is always at least 30 days stale when applied to the next month's billings. Cost events between calculation and billing are not reflected in the applied rate.
Unallowable costs accumulate in pools between scrubs
Entertainment, lobbying, and other unallowable costs posted during the period contaminate pool totals until the period-end review identifies and removes them. The rate is overstated for the entire period.
Rate instability discovered at ICS submission
Significant variance between provisional billing rate and actual rate may have accumulated for 12 months before ICS preparation reveals it. Retroactive billing corrections and ICS adjustments required.
FAR 42.704 ceiling breach not detected in time
15% variance ceiling between provisional and actual rates may be breached before detection. Rate revision request to contracting officer should have been filed months earlier.
Live Rate Calculation (xpdOffice)
Pool and base updated on every cost entry
Rate current to last write event. Billing rates applied today reflect today's actual cost composition. No staleness window between cost event and rate update.
Unallowable costs flagged at entry β never enter pools
FAR Part 31 allowability evaluated at the point of cost entry. Unallowable costs rejected or segregated before posting. Pool totals never contaminated by unallowable costs.
Rate deviation from provisional rates visible daily
Compliance Command Center shows the spread between current actual rate and provisional billing rate in real time. Rate instability surfaced before it compounds into a material variance.
FAR 42.704 ceiling approach flagged with lead time
Variance ceiling monitoring triggers alert when approaching 15% threshold. Rate revision request filed with contracting officer with time to negotiate before the ceiling is breached.
Strategic Insight
""The question is not whether the rate was correct at period end. The question is whether the rate applied to each invoice was supported by the cost data current at the time of billing. A live rate system always answers yes. A period-end system always answers: it depends on when the bill was generated.""
Frequently Asked Questions
What happens when unallowable costs contaminate an indirect pool?
What is a provisional billing rate agreement and why does it matter?
How does the CAS Disclosure Statement affect pool structure?
Want to model your own ROI?
Use our interactive calculator to see how a contract-native architecture can transform your margin.
