Every dollar billed needs a rate behind it
Ask a government contractor's controller what an indirect cost rate audit actually feels like, and the honest answer is rarely about the math. Dividing a pool total by a base total is arithmetic a spreadsheet handles instantly. What actually consumes the weeks before a DCAA incurred cost audit is proving where every number in that division came from — which invoice, which payroll period, which timesheet, pulled from a year of vendor bills and payroll registers that were never filed with an audit in mind.
An indirect cost rate schedule that can't be traced back to source documents, line by line, isn't just an administrative inconvenience — it's a rate an auditor can question, and a questioned rate can mean a cost disallowed, a rate adjustment, or in a worse case a broader sustained-questioned-cost finding that ripples across every contract the rate was billed against.
This page describes how the documents behind an indirect cost rate — vendor invoices, payroll registers, timesheets, general ledger detail — are read and organized into one traceable workbook, not to replace the cost accounting judgment behind pool structure and allowability determinations, but to remove the manual re-keying step where a supporting schedule most often quietly drifts from the source records it's supposed to represent.
Where indirect rate documentation breaks down
Most gaps in an indirect cost rate schedule didn't start as a dramatic error — they started as an ordinary consequence of assembling a year of cost data by hand, under a deadline, once a year. A handful of patterns show up again and again when an incurred cost submission gets a close read.
A vendor invoice coded to the wrong pool
An invoice split by hand between overhead and G&A, with a transposed split percentage that doesn't match the actual allocation policy applied everywhere else that year.
Payroll hours that don't tie to the timesheet system
A labor distribution report pulled from payroll doesn't match the underlying timesheets it's supposed to summarize, a gap that's invisible until someone actually compares the two.
A pool total that doesn't foot to the general ledger
A supporting schedule built in a separate spreadsheet drifts from the books over a year of manual updates, so the rate schedule and the GL tell two slightly different stories.
An unallowable cost left in a pool
A single meals-and-entertainment invoice or a fine, unnoticed among hundreds of routine vendor bills, sits in an overhead pool it was never allowed to be in.
A base total missing a cost center
A new department or subsidiary's direct labor gets added to the books mid-year but never gets folded into the allocation base spreadsheet, quietly understating the base and overstating the rate.
None of these need a dramatic explanation — they're the ordinary cost of a recurring, manual task performed across a growing volume of invoices and payroll records. Reading every source document the same way, with every figure traceable, closes most of this gap simply by removing the re-keying step where inconsistency creeps in.
Why this isn't a simple spreadsheet formula
A rate calculation itself — pool divided by base — is one cell in a spreadsheet. What makes indirect rate documentation genuinely hard is everything upstream of that cell: hundreds or thousands of vendor invoices that each need to be read, coded to a pool, and checked against the general ledger, plus payroll registers that need to be split correctly across direct labor, fringe, overhead and G&A for every employee, every pay period, for the full fiscal year.
Multiply that reading and coding task across a full year of vendor activity and payroll cycles, and a task that looks like an afternoon's reconciliation on a handful of invoices becomes a recurring exercise that's easy to rush at year-end — right up until an auditor pulls a sample invoice and asks why it was coded the way it was, and nobody can find the original document quickly.
What an indirect cost rate actually is
An indirect cost rate expresses the relationship between costs that can't be traced directly to a single contract — rent, utilities, fringe benefits, administrative salaries — and a base of direct costs those indirect costs support, most often direct labor dollars or total cost input. The rate is then applied to each contract's direct costs to allocate a fair share of the indirect pool to that contract's bill.
The rate itself is simple division. What makes it defensible is that both numbers in that division — the pool total and the base total — are complete, correctly classified, and traceable to the actual books and source documents for the period, not a spreadsheet estimate that happens to look reasonable.
The pools most contractors build
Most government contractors organize indirect costs into a small number of pools, though the exact structure is a cost accounting policy decision that varies by contractor size, business type and what a cost accounting advisor recommends — this isn't a one-size-fits-all structure, and smaller contractors sometimes combine pools that a larger CAS-covered contractor would split apart.
| Common pool | What typically sits in it |
|---|---|
| Fringe benefits | Payroll taxes, health insurance, retirement contributions, paid leave |
| Overhead | Facility costs, supervision, equipment depreciation tied to a specific operating group |
| General & Administrative (G&A) | Executive salaries, accounting and legal, business development, corporate-level admin |
| Material handling (where used) | Procurement, receiving and warehousing costs tied to material purchases |
| B&P / IR&D (where used) | Bid and proposal costs, independent research and development |
Every pool is built from the same underlying activity: vendor invoices for facility and admin costs, payroll registers for salaries and benefits, and sometimes allocated shared costs from a corporate parent. Reading and organizing that activity the same way, pool by pool, is the actual document work behind a rate schedule — the structure of the pools is a policy decision your cost accountant sets; what this tool handles is getting the underlying figures out of the documents accurately and consistently once that structure is set.
Choosing the allocation base
Each pool is divided by an allocation base chosen to reasonably reflect how that pool's costs benefit the contracts it's allocated to. Direct labor dollars is the most common base for a fringe or overhead pool; a G&A pool is often allocated over a total cost input base — direct material, direct labor and other direct costs combined, sometimes with an adjustment for pass-through material and subcontract costs on larger contracts.
Getting the base total right requires the same document-level accuracy as the pool — every payroll register correctly summed for direct labor, every direct-charged invoice correctly excluded from indirect and included in the base. A base that's understated by a missed cost center inflates every rate calculated against it, understating no single pool but overstating every rate the base feeds into.
What gets read
| Data | Typical source |
|---|---|
| Vendor, invoice number, date, amount | Vendor invoice header |
| Line-item detail and cost description | Invoice body |
| Gross wages, taxes, benefits by employee | Payroll register |
| Hours by cost objective (direct vs. indirect) | Timesheet or labor distribution report |
| Account code, cost center | General ledger export, where coded |
A field that can't be read with confidence — a total obscured by a stamp, a figure split across a page break — is flagged rather than filled in with a best guess, so a reviewer's time goes to the handful of documents that genuinely need a second look, not to re-checking every invoice from scratch.
How it works
Upload the year's vendor invoices and payroll registers
For the fiscal year the rate schedule needs to cover — however many documents that involves.
Each document is read on its own
Amounts, dates, vendor and line-item detail extracted from each document's own layout.
Figures organized by pool and base
Every figure tagged and lined up into the same structure, ready to map against your cost accounting policy.
Gaps and mismatches flagged, not guessed
An invoice with an unclear cost objective, or a total that doesn't foot to the general ledger, is marked for review.
Exported
Excel, CSV or JSON, with every figure traceable back to the document it came from.
A rate, documented
A mid-size contractor uploads a full fiscal year of vendor invoices and twenty-six payroll registers ahead of preparing its annual incurred cost submission.
| Result | Count |
|---|---|
| Vendor invoices processed | 1,140 |
| Payroll registers processed | 26 |
| Figures matched with high confidence | 97% |
| Flagged for coding confirmation | 38 invoices |
The 38 flagged invoices turn out to be a mix of split-coded facility invoices that needed a manual allocation percentage applied and a handful of vendor bills with an ambiguous description — reviewed in an afternoon rather than the days it would have taken to find and re-check them individually across a year of accounts-payable folders.
Provisional rates vs. final rates
Most cost-reimbursement contractors bill throughout the year using provisional, or billing, rates — an estimate agreed with the contracting officer at the start of the year. At year-end, the actual indirect cost rates are calculated from the real pool and base totals and submitted as part of the incurred cost submission, then trued up against what was actually billed during the year.
That true-up is exactly where documentation quality matters most: a final rate that's materially different from the provisional rate, without clean supporting detail for why, invites a closer look from the auditor reviewing the submission. Keeping the same document-level traceability throughout the year — rather than reconstructing it only at year-end — means the final rate calculation is a summary of work already done, not a scramble.
Unallowable costs and why they matter here
FAR Part 31 identifies categories of cost that are expressly unallowable on government contracts — entertainment, alcohol, certain lobbying and public relations costs, fines and penalties, and a number of other specific categories. These costs can remain in a contractor's books, but they have to be identified and excluded from any indirect cost pool billed to the government.
Finding an unallowable cost buried in a pool of a thousand vendor invoices is a document-reading problem before it's anything else — every invoice needs to actually be read and its cost description understood well enough to flag against your unallowable-cost policy, which is exactly what a manual review under year-end time pressure is most likely to rush past. This tool surfaces every invoice's description and amount clearly for that review; the determination of what's actually unallowable under FAR 31.205 stays a judgment your compliance team or CPA applies.
Manual vs. automatic
| Manual | Automatic |
|---|---|
| Invoices and payroll re-keyed into a spreadsheet by hand | Every document read and organized automatically |
| Coding errors found only when an auditor samples a document | Ambiguous coding flagged for review as it's processed |
| Source document retrieval means searching a shared drive | Every figure links directly back to its source document |
| Redone from scratch as invoice volume grows | Same method applies regardless of how many documents exist |
From one contract to a full portfolio
A small contractor with a single cost-reimbursement contract and a handful of employees is a manageable manual exercise, if tedious. A contractor running a full portfolio of contracts across several agencies, with multiple pools and hundreds of vendors, turns the same exercise into a recurring job that consumes weeks of staff time every fiscal year-end.
Reading and organizing each year's documentation the same way, regardless of how many contracts or pools are involved, keeps the effort per document flat as the contract portfolio grows — what changes is only how many figures need a human look, which a well-tuned extraction keeps small.
Who uses this
Government contractor controllers
A traceable rate schedule built from source documents, ready before an incurred cost submission is due.
Contracts and compliance managers
Vendor invoices and payroll registers read and organized without a manual re-keying pass every year-end.
Outside CPAs preparing incurred cost submissions
A structured starting point instead of a stack of unrelated invoice and payroll PDFs.
Small and mid-size contractors without a full compliance team
The same document-level rigor a larger contractor's back office applies, without needing the same headcount.
Edge cases worth knowing
A credit memo or a vendor refund that partially offsets an earlier invoice needs to be matched back to the original charge and its pool, rather than treated as an unrelated line item that leaves the pool overstated by the amount that was actually credited back.
An invoice that spans two fiscal years — a facility lease paid a month in advance, for instance — needs its cost allocated to the correct period rather than booked entirely in the period the invoice happened to be paid, and is flagged for that allocation decision rather than assumed.
Why a traceable figure beats a rounded one
A rate schedule that shows only pool and base totals, without the documents each figure came from, is easy to trust until a DCAA auditor samples five invoices and asks for support. Reconstructing that support later means going back through a year of accounts-payable records and starting over under a deadline.
Keeping the source document attached to every figure in the pool and the base — vendor, invoice number, page reference, confidence level — turns that reconstruction from a scramble into a detail already sitting in the data, ready the moment a sample request comes in.
What this doesn't do
Doesn't calculate your indirect cost rates for you
It organizes the pool and base figures each document contributes — applying your cost accounting policy and computing the rate stays your step.
Doesn't determine cost allowability
It surfaces every invoice's description and amount clearly — deciding what's unallowable under FAR 31.205 is a judgment call for your compliance team or CPA.
Doesn't replace a DCAA-compliant accounting system
It's the document-reading layer many contractors use alongside their books to gather and organize supporting evidence.
Doesn't give legal or compliance advice
Any question about CAS coverage, cost accounting structure or audit strategy belongs with your advisors, not this tool.
What it does fits in one sentence: turn a year of vendor invoices, payroll registers and ledger detail into one consistent, traceable workbook, so a rate schedule doesn't have to be assembled from scratch every time an auditor or a proposal deadline asks for it.
Feeding into the incurred cost submission
An annual incurred cost submission typically needs several supporting schedules — a summary of claimed indirect rates, the detail behind each pool, direct costs by contract, and a general and administrative expense schedule, among others depending on the specific format required. Every one of those schedules draws on the same underlying source documents this tool reads.
Building the schedules themselves — matching your contractor's specific submission format and cost accounting structure — is a step your compliance team or outside CPA typically owns. What this tool changes is how much of the underlying legwork, pulling and organizing a year of source documents, is already done by the time that schedule-building step starts. See the step-by-step schedule-building guide for how that process fits together.
Security and privacy
Uploads are encrypted with TLS from end to end.
Processing runs on infrastructure with SOC 2-aligned controls.
Original documents are deleted shortly after processing.
Nothing you upload is ever used to train AI models.
For financial and payroll records tied to government contract billing, that matters — details are on the security page.