An eFAACT indirect-rate output needs fiscal-period and billing reconciliation

Name the rate and the period before using it

eFAACT's official page establishes current provider positioning for indirect-rate and related government-contractor accounting workflows. The direct operating answer is that an output labeled as an indirect rate remains incomplete evidence until the record identifies what kind of rate it is, which legal entity and fiscal period it covers, which cost pool and allocation base produced it, which accounts and projects were included, and what authority permits it to be used for the intended purpose.

Preserve the contractor entity, business unit where relevant, fiscal year and accounting period, rate name and type, pool definition, base definition, account and cost-object mappings, inclusion and exclusion rules, unallowable-cost treatment, allocation sequence, service-center or intermediate allocations, direct and indirect classification basis, year-to-date actuals, forecast inputs, adjustments, rounding, software and configuration version, run time, preparer, reviewer, approval, and effective status. Provisional, billing, forward-pricing, target, and final rates must not share an unlabeled field.

Reconcile the source ledger before the percentage

A mathematically correct division can still be wrong if the underlying population is incomplete, duplicated, late, mapped to the wrong objective, or processed in the wrong period. Teams should reconcile time, payroll, expense, accounts payable, journal entries, project structure, contract and task identifiers, organization changes, transfers, accruals, credits, and prior-period corrections to the controlled general-ledger and subsidiary records used for the rate calculation.

The reconciliation should expose changes between periods. A new account, contract, employee class, organization, acquisition, shared service, leave treatment, cost transfer, or closing adjustment may alter the pool or base without changing the displayed formula. Keep source-to-rate control totals and mapping versions so a reviewer can reproduce the numerator and denominator. A rate trend is not self-explanatory; it can reflect business mix, timing, accounting corrections, policy decisions, mapping errors, or genuinely changed cost behavior.

Keep calculation, billing, submission, and settlement separate

The provider page also connects indirect-rate information with invoicing and ICE schedules. Those are related but distinct records. A calculated rate is not automatically the contractual billing rate. An invoice generated with a burden and ceiling is not proof that the underlying cost was allowable, allocable, reasonable, authorized, supported, or accepted. A schedule produced by software is not proof that a submission is complete, timely, accurate, reviewed, or agreed by the government.

For a representative cost-reimbursement invoice, retain contract and clause context, cost period, direct-cost source, applied rate and type, ceiling or cap, fee basis, funding and limitation checks, prior billings, adjustments, approval, submission receipt, rejection or question, correction, payment, withhold, and ledger reconciliation. When provisional or billing rates change, preserve which invoices and periods were recalculated, the delta, credit or additional amount, customer communication, cash result, and closeout treatment rather than overwriting the original billing record.

Read the official sources within their limits

The registered eFAACT record establishes provider claims about QuickBooks integration and government-contractor workflows. FAR Part 42 supplies adjacent official regulation for contract administration and audit services. Neither source establishes accounting-system adequacy, DCAA approval, correct indirect-rate structure, cost allowability, invoice acceptance, audit outcome, contract compliance, or business performance for a contractor. Those conclusions depend on the applicable contract, facts, records, policies, and authorized government and contractor decisions.

GovCon Market Brief reviewed the official records on August 27, 2026. No dated post-August 26 material change was established, so this is source-bounded analysis rather than a change-ledger event. Buyers should demonstrate a normal period, a late journal, a new account, an unallowable cost, an organization change, a ceiling, a rate revision, a rejected invoice, and a year-end true-up. Qualified contracts, finance, accounting, legal, compliance, systems, and government stakeholders retain their respective judgments.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

GovCon Market Brief will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.