Government contractor case study

GovCon DCAA-Compliant Timesheet-to-Billing Case Study

A federal services contractor moved labor distribution, indirect rate calculation, and project billing into an automated, DCAA-ready workflow with audit pack output every cycle.

Client profile: Composite case study based on an $80M federal services contractor with 280 staff, 90 active project codes, Costpoint GL, 5-person accounting team.
Case study breakdown

How the workflow changed from manual effort to controlled automation

Company context — a $90M federal services contractor

The client is a federal professional-services contractor with $90M annual revenue, ~420 employees, running on Deltek Costpoint with Costpoint Time as the timekeeping front-end. The contract portfolio is roughly 60% Time-and-Materials (T&M), 25% Cost-Plus-Fixed-Fee (CPFF), and 15% Firm-Fixed-Price (FFP), spread across 14 prime contracts and 28 active subcontractor agreements. Indirect rate structure is the standard federal services trio — fringe, overhead, G&A — with a separate material-handling rate for the small materials-pass-through portion.

What makes GovCon accounting different from commercial accounting isn't the technology — it's the evidence bar. DCAA can pull audit support on 30 days' notice. Provisional indirect rates need defensible computation against the cost pool definition in the rate-agreement letter. Unallowable costs need to be screened before they hit a billable project, not after. And the Incurred Cost Electronic (ICE) model needs to be defensible at the contract level, the rate level, and the cost-pool level when the year-end submission goes in.

  • $90M annual revenue, federal services prime + sub contractor
  • ~420 employees with weekly Costpoint Time entry
  • 14 prime contracts (60% T&M, 25% CPFF, 15% FFP)
  • 28 active subcontractor agreements
  • Indirect rate structure: fringe, overhead, G&A, material-handling
  • Annual ICE submission, quarterly provisional-rate true-ups
  • FAR Part 31 / DFARS 231 cost-allowability framework
  • CMMC Level 2 in flight; CUI handling required

Before automation

Timesheet review, labor distribution, indirect rate calculation, and project billing were spread across four systems and six spreadsheets. The three-day cycle from timesheet close to billing meant cash collection ran ~5 days slower than it had to. DCAA audit support pulled 8–10 staff days per cycle and consumed weeks of senior accounting time during the annual ICE submission.

  • Timesheet review across multiple supervisors with no exception queue
  • Labor distribution spreadsheet recalculated per cycle by hand
  • Indirect rate variances tracked manually, often discovered at year-end true-up
  • Project billing assembled per project per cycle, off a list maintained in Excel
  • DCAA audit pulls required reconstructing evidence each time
  • Unallowable cost screening done quarterly, not at point of entry
  • Subcontractor labor reconciled to time records and billings manually
  • ICE submission consumed ~6 weeks of senior accounting time annually

What Ledger Summit implemented

An automated timesheet-to-billing workflow built on top of Costpoint, with labor distribution, indirect rate calculation, and per-cycle audit pack output. Tool Box AI handled the workflow and exception routing; the controller kept review and sign-off. The architecture preserves Costpoint as the system of record — every transaction still posts there — but adds the workflow, evidence, and exception-handling layer that DCAA actually wants to see.

  • Timesheet review with exception queue and supervisor escalation
  • Automated labor distribution by project and indirect pool
  • Indirect rate calculation with variance flagging vs. provisional rates
  • Project-level billing assembly (T&M, FFP, CPFF)
  • Per-cycle DCAA audit pack: timesheets, rate calc, billing, evidence
  • Unallowable cost screening at timesheet entry per FAR Part 31 categories
  • Subcontractor labor reconciliation to time records and billings
  • ICE-readiness pack auto-assembled from cycle data

Contract type variants — what changes per type

GovCon billing logic is contract-type-specific. The engine handles each type with type-specific rules for what flows to billing, what gets withheld, and what's evidence-required.

Contract typeBilling logicIndirect rate handlingDCAA evidence focus
Time-and-Materials (T&M)Hours × loaded labor rate; materials pass-through with material-handling burdenBurden built into loaded labor rate; subject to ceilingTimesheet support; loaded-rate computation; material receipts
Cost-Plus-Fixed-Fee (CPFF)Direct cost + provisional indirect + fixed fee; subject to fee ceilingProvisional rates applied; year-end true-up to actualsCost-allowability per FAR Part 31; rate computation; fee schedule
Firm-Fixed-Price (FFP)Milestone or schedule-based; revenue per ASC 606 over-time-percentage-of-completion typicalIndirect rates affect cost realization, not billingCost realization vs. plan; estimate-at-completion (EAC) discipline
Cost-Plus-Award-Fee (CPAF)Direct cost + provisional indirect + award fee per evaluation periodProvisional rates with year-end true-upAward-fee determination; cost-allowability
Cost-Plus-Incentive-Fee (CPIF)Direct cost + provisional indirect + share-line incentive computationProvisional rates with year-end true-upCost target tracking; share-line computation
Indefinite-Delivery-Indefinite-Quantity (IDIQ)Per task-order, type per task-orderPer task-order indirect rate applicationTask-order-level evidence rolled up to contract

Indirect rate structure and provisional-to-actual mechanics

Provisional indirect rates approved by DCMA at the start of the fiscal year are the basis for all interim billing on cost-reimbursement contracts. At year-end, actual rates are computed from the cost pool and base, and a true-up flows back to each contract: under-billing produces a final-voucher claim, over-billing requires repayment.

The engine tracks provisional vs. actual variance monthly so the controller sees emerging variance instead of discovering it at year-end. A 3% variance on G&A this year produced a $180K under-billing across the contract portfolio that was caught and adjusted in October instead of at the December year-end true-up — a working-capital improvement plus a cleaner ICE submission.

  • Fringe rate — fringe pool / total direct labor; includes fringe benefits, employer taxes, paid leave
  • Overhead rate — overhead pool / direct labor + applicable fringe; includes facilities, fringe-on-OH-labor, depreciation on direct-charge assets
  • G&A rate — G&A pool / total cost input (TCI) base; includes corporate G&A, executive compensation, finance, HR
  • Material-handling rate — separate small rate for material pass-through; reduces material-burden impact on billing
  • Provisional-to-actual variance — tracked monthly, alerted on threshold breach
  • Cost pool integrity — composition tested against rate-agreement letter quarterly
  • Base composition — direct labor, TCI, or other base tested for consistency with rate-agreement letter

Implementation timeline — 8 weeks from kickoff to clean cycle

  • Week 1: Discovery. Mapped current workflow, indirect rate structure, exception types, contract portfolio composition, prior DCAA findings.
  • Week 2–3: Build. Timesheet workflow, labor distribution rules, billing assembly logic per contract type, subcontractor reconciliation.
  • Week 4: Rate engine. Indirect rate calculation, variance flagging, audit pack template, unallowable-cost screening rules per FAR Part 31.
  • Week 5: Parallel run. One full cycle in shadow alongside legacy workflow. Variances reconciled to zero; eight reconciling items found and resolved.
  • Week 6: Cutover. First cycle on the new workflow with full audit pack output.
  • Week 7–8: Hypercare. Rule refinement, DCAA walk-through prep, ICE-readiness pack template tested against prior submission.

Measured results

MetricBeforeAfterDelta
Timesheet-to-billing cycle3 business days1 business day−66%
Manual labor distribution time14 hours / cycle2 hours / cycle−86%
Indirect rate variance investigation6 hours / cycle1 hour / cycle−83%
DCAA audit support pulls8–10 staff days1 staff day−88%
Unallowable cost findings (annual)5 avg0 in first cycle−5
Days Sales Outstanding (DSO) on T&M52 days44 days−8 days
ICE submission prep time (annual)~6 weeks~2 weeks−66%
Subcontractor labor reconciliation time4 hours / cycle20 minutes / cycle−92%

Controls and DCAA-ready evidence

  • Timesheet entry with unallowable cost screening at point of entry per FAR Part 31
  • Labor distribution rules versioned with approval trail; rule changes require controller sign-off
  • Indirect rate calculation with monthly variance flagging vs. provisional rates
  • Project billing tied to source timesheets and approved rates with three-click trace
  • Per-cycle DCAA audit pack: timesheets, rate calc, billing, evidence, reviewer log
  • Independent reviewer sign-off on indirect rate variances >5%
  • Subcontractor labor reconciled to time records and billings each cycle
  • CUI handling boundary preserved — engine deploys inside the client's CMMC scope

FAR Part 31 unallowable cost screening — what gets caught at entry

Unallowable costs aren't always obvious. The screening engine catches the FAR Part 31.205 categories at point of entry — far cheaper than removing them at year-end ICE prep. Each rule has a documented citation and reviewer-override capability for legitimate edge cases.

  • FAR 31.205-1 — public relations and advertising (with the narrow exceptions)
  • FAR 31.205-3 — bad debts
  • FAR 31.205-8 — contributions and donations
  • FAR 31.205-13 — entertainment costs
  • FAR 31.205-14 — interest and other financial costs
  • FAR 31.205-22 — lobbying costs
  • FAR 31.205-27 — organization costs (mergers, IPOs)
  • FAR 31.205-32 — fines and penalties
  • FAR 31.205-46 — travel costs (per-diem ceiling enforcement)
  • FAR 31.205-47 — defense of fraud proceedings
  • FAR 31.205-49 — goodwill

Why this matters for GovCon specifically

GovCon accounting has a higher evidence bar than most industries: DCAA can pull audit support on short notice, indirect rates need defensible computation, and unallowable costs have to be screened before they hit a billable project. Most automation work in this space stays in the Deltek ecosystem — we layer on top of Costpoint or Unanet, keeping the GL where it already is, and add the workflow + evidence layer.

When this approach fits

  • $20M–$300M revenue federal services or AEC contractor
  • Costpoint, Unanet, JAMIS, or comparable GovCon ERP already in place
  • Mix of T&M, CPFF, and FFP contracts — at least one cost-reimbursement contract type
  • Provisional indirect rate agreement in place with DCMA
  • Annual ICE submission required
  • CMMC scope active or being prepared for
  • Subcontractor labor or material pass-through volume material to billing

When this approach doesn't fit

  • Below ~$15M revenue and pre-DCMA-rate-agreement. Cost-allowability discipline is more important than automation at that scale; we typically advise stand-up first, automate later.
  • FFP-only contractors with no cost-reimbursement contracts. The indirect-rate engine is overhead they don't need; project-cost discipline is the real lever.
  • Construction / AEC with heavy AIA billing. Different workflow shape; Sage Intacct + AIA billing tools usually fit better than a Costpoint layer.
  • Pure commercial with no federal contracts. Different evidence bar; commercial-grade close discipline is the right pattern.
  • Companies in active DCAA audit findings remediation. Stabilize the underlying accounting first; automation amplifies whatever discipline is already there.

Lessons learned and what we'd do differently

  • Indirect rate structure review before workflow build. Two of the eight parallel-run reconciling items came from a labor pool definition that didn't match the rate-agreement letter exactly. Future projects: rate-structure audit is week-one, not week-three.
  • Subcontractor reconciliation as its own workstream. Subcontractor labor reconciliation was treated as a tail-end concern; it's actually a leading indicator for billing accuracy. Build it earlier.
  • FAR Part 31 screening rules require legal review. A few categories (entertainment, advertising) have nuanced exceptions; legal-review sign-off before deployment saves later debate.
  • Engage DCAA via DCMA at week 4. Pre-walking the new evidence pack with the cognizant DCAA-DCMA point-of-contact gets buy-in before the first cycle. We didn't on this project; we do now.
  • ICE-readiness as a continuous output. The annual ICE prep used to be a 6-week sprint. Once cycle data assembles into ICE-format continuously, the annual submission is just a final review. Plan for this as a goal from week 1.

Frequently asked questions

Does this work with Unanet too, not just Costpoint?

Yes. The workflow is system-agnostic; we've implemented similar setups on Unanet GovCon. Project structures and indirect rate setup look different, but the labor distribution → indirect rate → billing → audit pack flow is the same.

How does the DCAA pack differ from what Costpoint already produces?

Costpoint has the data; the audit pack is what assembles it into a single, walkable narrative per cycle (with timestamped logs, reviewer sign-off, and exception trail). Most DCAA pulls request exactly this — and historically it took 8+ staff days to assemble. Now it's already assembled.

What about cybersecurity / CMMC implications?

We work within your existing CMMC and security boundary. Tool Box AI deploys inside your environment for clients with this requirement; data doesn't leave your tenant.

How does this handle indirect rate true-ups?

Provisional vs. actual rate variance is tracked monthly. At year-end, the engine produces the contract-by-contract true-up walk and the final-voucher claim or repayment as applicable. ICE-readiness pack assembles automatically from cycle data.

Does it support multi-tier subcontractor flow-down?

Yes — for prime contracts with subcontractor labor, the engine reconciles subcontractor invoices against time records and contract terms, applies handling burden, and includes the trace in the billing pack.

What about labor categories and qualifications?

Labor category mapping is configured per contract; the engine validates that the timekeeper's labor category and qualification matches the contract's approved category before allowing the time to bill. Mismatches go to an exception queue.

How do you handle T&M ceilings?

Per-contract ceiling tracking with monthly burn-rate alerts. Approaching-ceiling notifications fire at 75%, 90%, and 95% so the contract manager can engage on a modification or scope discussion before billing stops.

What's the typical implementation timeline?

6–10 weeks for $20–100M contractors with established Costpoint/Unanet. Larger or multi-segment contractors typically run 10–14 weeks.

Do you handle ICE submission prep?

The cycle data assembles into ICE format continuously, and the annual submission becomes a 1–2 week final review rather than a 4–6 week sprint. Submission itself is still done by the client's team — we don't sign or submit on the contractor's behalf.

What about CAS-covered contracts?

Cost Accounting Standards (CAS) compliance — for contractors above the $50M / $25M / $7.5M thresholds — is a deeper discipline. The engine supports CAS Disclosure Statement maintenance and consistency testing, but full CAS compliance program is its own engagement.

How does this interact with our DCMA-approved billing system?

The engine doesn't replace your billing system — it sits on top of it, adding the workflow, exception, and evidence layer DCMA expects. The system of record stays Costpoint or Unanet.

GovCon close eating your team? DCAA pulling for audit support?

A 30-minute call maps your timesheet-to-billing workflow and tells you what's automatable on top of Costpoint or Unanet.

Book a free call