A DCAA auditor opens your client's incurred cost submission and stops on one line. Defense Base Act insurance, booked as a direct cost on a cost-plus overseas contract. The figure is six digits, and the auditor wants support for every dollar.
This is a routine moment on cost-reimbursement work, but it decides real money. The government pays DBA premiums on cost-type contracts as an allowable cost. It only pays what is reasonable, allocable, and properly credited back when the carrier issues a refund. Miss one of those tests and the auditor questions the cost.
For a DBA attorney, this matters for two reasons. First, the premium your client's employer paid is the clearest proof that coverage existed and that a carrier stood behind the policy. Second, the audit trail names the contract vehicle, the awarding agency, and the period of performance that fix which carrier was on the risk.
You do not need to be a government cost accountant to use this. You need to understand what the FAR makes allowable, how DCAA tests the premium, and where auditors challenge it. Those pressure points tell you where the coverage evidence lives and why premiums sometimes vanish from a contractor's books.
This article walks the FAR framework that makes a DBA premium allowable, the mechanics of a DCAA incurred cost audit, and the places auditors push back. It also shows how premium refunds and War Hazard recoveries flow back to the government. Each of those points is a thread you can pull in a coverage investigation.
Why Is a DBA Insurance Premium an Allowable Cost?
The Defense Base Act sits at 42 U.S.C. 1651 through 1654. It extends the Longshore and Harbor Workers' Compensation Act, 33 U.S.C. 901 through 950, to civilian employees on overseas military and government contracts. A covered contractor must carry workers' compensation insurance for those employees or qualify as a self-insurer.
Federal contracts make that duty explicit. FAR 28.309 directs the contracting officer to insert the Defense Base Act clause, FAR 52.228-3, into covered contracts. The clause requires the contractor to provide DBA insurance and to flow the obligation down to subcontractors. The paper trail this creates is exactly what a coverage investigation needs, as the analysis in the contract clause that builds the DBA carrier paper trail explains.
Because the contract requires the coverage, the premium is an allowable cost. FAR 31.205-19 governs insurance and indemnification costs. It treats premiums for insurance the contractor is required or approved to carry as allowable, subject to reasonableness limits and the credit rules for refunds and dividends.
Allowability is never automatic though. FAR 31.201-2 sets the general test every cost must pass. The cost must be reasonable, allocable to the contract, consistent with GAAP and applicable Cost Accounting Standards, compliant with the contract terms, and not barred by any specific FAR limitation.
A DBA premium usually clears the first hurdles with ease. The coverage is mandatory, the statute is clear, and the clause is in the contract. The fight is rarely about whether DBA insurance is allowable in principle. It is about how much, charged to which contract, and net of what credits.
Contract type also shapes the question. On a cost-reimbursement contract, the government reimburses the actual premium as an allowable cost. On a firm-fixed-price contract, the premium is baked into the price and the government does not separately audit it. DCAA scrutiny concentrates on cost-type and flexibly priced work.
An auditor almost never argues that a required DBA policy was unnecessary. Instead the auditor tests the amount and the allocation. That framework is the starting point for any DCAA audit DBA insurance premium allowability cost reimbursement dispute.
How Does DCAA Review DBA Premiums in an Incurred Cost Audit?
On cost-reimbursement contracts, the Allowable Cost and Payment clause, FAR 52.216-7, controls how the contractor gets paid. It requires an annual incurred cost submission, commonly called the incurred cost proposal. The submission is due within six months after the end of the contractor's fiscal year under FAR 52.216-7(d)(2).
DCAA audits that submission to settle final direct costs and indirect rates. The DBA premium shows up in one of two places. It appears as a direct cost charged straight to the overseas contract, or inside an indirect pool like fringe or overhead that spreads across many contracts. Where it sits drives how the auditor tests it.
The auditor runs the premium through three FAR gates. Reasonableness under FAR 31.201-3 asks whether a prudent business person would have paid that amount. Allocability under FAR 31.201-4 asks whether the cost benefits the contract it is charged to. Allowability under FAR 31.205-19 confirms the insurance category is payable at all.
Expect document requests. The auditor wants the policy declarations page, the premium invoices, proof of payment, and the basis for any allocation. If the premium is charged direct, the auditor checks that the policy actually covers the employees on that contract and that period of performance.
Direct charging is where allocation errors surface. A single DBA policy often covers several contracts and task orders at once. If the contractor books the whole premium to one cost-plus contract, the auditor will question the share that belongs elsewhere. The premium must follow the benefit.
Double counting is the mirror problem. If a contractor charges the DBA premium as a direct cost and also loads a piece of the same insurance into an indirect pool, the government pays twice. Auditors watch for this pattern closely on flexibly priced overseas work.
None of this questions whether DBA coverage existed. It questions the number. For a claims investigator, the audit file is a gift, because it forces the contractor to document the exact policy, carrier, and dates behind the premium.
The DCAA Contract Audit Manual guides these reviews, but the governing authority is the FAR. When an auditor questions a DBA premium, the citation is almost always a cost principle in FAR Part 31, not an insurance regulation. That is why the fight plays out on allowability and allocation, not on coverage law.
Where Do DCAA Auditors Push Back on DBA Premiums?
Four pressure points drive most DCAA audit DBA insurance premium allowability cost reimbursement disputes. They are reasonableness of the rate, allocation across contracts, credits for refunds and dividends, and recoveries under the War Hazard Compensation Act. The first two turn on how the premium was priced and charged.
Reasonableness is the sharpest edge. DBA insurance is open-rated, which means carriers set premiums by the risk rather than a fixed government schedule. During the Iraq and Afghanistan surge years, rates on high-risk labor climbed far above ordinary workers' compensation manual rates. Auditors ask whether the contractor accepted an inflated rate without shopping the market.
A prudent contractor documents its rate. It keeps competing quotes, broker correspondence, and the loss experience that justified the premium. When that support is thin, the auditor benchmarks the rate against market data and questions the excess. The wide spread in historic DBA pricing, traced in the true cost of DBA insurance and premium trends since 2010, is exactly why reasonableness gets contested.
Allocation is the second pressure point. DBA premiums are frequently charged as a direct cost to the contract that generated the overseas headcount. That is correct only when the policy maps to that contract. When one master policy covers a portfolio, the premium must be prorated by a rational base such as covered payroll or headcount.
Auditors test the base. If a contractor charged the full premium to a single cost-plus contract while other contracts shared the same policy, the questioned cost is the misallocated share. The employees covered, the payroll base, and the period of performance all have to line up with the charge.
Retrospective rating complicates both tests. Many large DBA programs use experience-rated or retrospective premiums that adjust after the policy year based on actual losses. An initial premium can rise or fall once claims mature. That later adjustment has to flow through to the contract cost, up or down.
These are not coverage arguments. They are cost-accounting arguments about a policy that plainly existed. If you are trying to confirm which carrier insured a contractor on a specific vehicle, ClaimTrove traces the employer, the awarding agency, and the carrier tied to that contract period in one search, so you can start from the vehicle instead of guessing.
How Do Premium Refunds and War Hazard Recoveries Flow Back to the Government?
The credit rules are where the biggest dollars hide. FAR 31.201-5 states the principle plainly. When the contractor receives a refund, rebate, allowance, or other credit relating to an allowable cost, the government gets its proportionate share back.
DBA premiums generate exactly these credits. Experience-rated policies issue return premiums when losses come in low. Mutual and group programs pay dividends. If the government reimbursed the original premium, it is entitled to the credit when money comes back to the contractor. Auditors look for return premiums that were pocketed rather than passed through.
This is not a hypothetical risk. Federal oversight found a large-scale failure of exactly this kind in the Army Corps DBA insurance program. A 2011 SIGAR audit reported that $58.5 million in DBA insurance refunds was never returned to the government, according to ClaimTrove's SIGAR report data. The pattern of program-level problems is documented further in what SIGAR audits revealed about DBA insurance fraud in Afghanistan.
The Army Corps ran a mandatory DBA program with a single carrier for years before it ended. When that program closed and the market reopened, the credit and refund mechanics changed with it. The coverage consequences of that shift are traced in how the end of the Corps mandatory program fractured carrier identification.
The War Hazard Compensation Act adds a second recovery channel. Under 42 U.S.C. 1704, a DBA carrier that pays benefits for a war-risk injury can seek reimbursement from the federal government. When that reimbursement arrives, it reduces the carrier's net loss on the policy.
That matters for premium reasonableness and credits. If a carrier recovers war-hazard losses from the Treasury, the loss experience that justified a high premium looks different after the fact. Auditors and contracting officers weigh those recoveries when they test whether the net cost to the government was reasonable.
For your purposes as a claims investigator, these mechanics leave tracks. Refund records, retrospective adjustments, and War Hazard reimbursement filings all name the carrier and the policy period. Each one is another way to confirm who was actually on the risk.
What Does the Audit Picture Mean for Your DBA Coverage Investigation?
Start with contract type, because it decides whether the premium is even visible. On a cost-reimbursement contract, the DBA premium is a separately reimbursed, separately audited line. On a firm-fixed-price contract, it is buried in the price and never itemized to the government.
That single fact changes your evidence hunt. A cost-type vehicle leaves an incurred cost trail with policy numbers, carriers, and dates. A fixed-price vehicle hides the same information inside the contractor's own records. The split between these worlds is laid out in who really pays the DBA premium on cost-plus versus fixed-price contracts.
The practical takeaway from DCAA audit DBA insurance premium allowability cost reimbursement questions is simple for a claims investigator. Every allowability fight is anchored to a specific policy, carrier, and period of performance. The auditor forces the contractor to name them. You want the same three facts.
Allocation disputes are especially useful. When an auditor questions how a premium was split across contracts, the underlying record shows every contract and task order the policy touched. That is a map of coverage across a contractor's portfolio, not just one claim.
Credit and refund records help too. A return premium or a retrospective adjustment ties a dollar figure to a policy year and a carrier. Even a decades-old adjustment can confirm which carrier was on the risk when your client was injured.
Keep the timeline in mind as you work. Premiums are set before the policy year, adjusted after it, and audited months later when the incurred cost submission is due. A carrier can change between award and audit. Anchor every finding to the injury date, then match the policy period that actually covered it.
None of this replaces the coverage evidence itself. It points you to it. The audit framework tells you the premium existed, who set it, and which contract it belonged to, and those threads lead to the carrier.
When you need to close the loop, start from the contract vehicle. ClaimTrove cross-references federal contract awards, FOIA coverage filings, and legal decisions to trace the employer and the carrier tied to a given contract period. Run the vehicle, and let the data name the carrier instead of chasing it invoice by invoice.