DBA, VA Benefits, and Longshore Coordination: How to Avoid the Offset Traps That Cost Your Client Thousands

Your client was a former Army logistics specialist who took a contractor job in Kabul. He blew out his knee on a forklift at Bagram in 2017, filed a DBA claim, and is already collecting VA disability for a service-connected back condition from his active-duty years. Now the DBA carrier sends you a letter claiming a credit against future indemnity. Your client thinks his VA check is at risk. Is it?

This is the question that separates attorneys who understand benefit coordination from those who learn it the hard way. The answer is usually no, the VA benefit is safe, but the path to that answer runs through three different statutory schemes that interact in ways most claimants never see coming. The Defense Base Act, VA disability compensation, and the Longshore and Harbor Workers' Compensation Act each have their own offset logic. Get the interaction wrong and you either leave money on the table or set your client up for an unexpected carrier credit that wipes out months of benefits.

The stakes are concrete. Across the 5,022 OALJ and BRB decisions in our database, offset and credit disputes surface repeatedly, and they almost always involve a benefit stream the claimant assumed was untouchable. This article walks through where DBA, VA, and Longshore benefits collide, where the offsets actually bite, and how to model the math before the carrier does it for you.

How Does the DBA Borrow Its Offset Rules From the Longshore Act?

The Defense Base Act does not stand alone. It is a coverage extension. Under 42 U.S.C. 1651, the DBA applies the substantive provisions of the Longshore and Harbor Workers' Compensation Act to civilian employees working on overseas military bases and government contracts. That single fact drives nearly every offset question you will face.

Because the DBA incorporates the LHWCA, your client's overseas injury claim is adjudicated under Longshore rules. The same compensation formulas, the same average weekly wage calculation, the same Section 8 disability classifications. When you read a DBA decision, you are reading Longshore law applied to a contractor in Iraq instead of a stevedore in Baltimore.

This matters for offsets in two ways. First, the LHWCA's own credit provisions, like the Section 3(e) credit for benefits paid under another workers' compensation law, flow directly into DBA claims. Second, the LHWCA contains no general offset against VA disability compensation, and that absence is itself the key to protecting your client's VA check.

Understanding the borrowed framework also clarifies why carrier behavior in DBA cases mirrors Longshore practice. The carrier handling an overseas claim is operating under the same statute it would use for a domestic harbor worker. If you have worked Longshore cases, the procedural posture will feel familiar. If you have only worked DBA, recognizing the Longshore parentage tells you which precedents to pull.

One trap here is concurrent employment. When a contractor worked for more than one employer or under stacked contracts, the average weekly wage and the responsible carrier both become contested. We cover this in depth in our breakdown of concurrent employment and DBA claims when your client worked for multiple employers overseas, and the coordination question gets harder when each employer carried a different carrier.

Does VA Disability Compensation Offset a DBA Award?

This is the question clients ask first, and the answer reassures them. VA disability compensation and DBA benefits are generally separate, non-offsetting streams. They compensate different things and arise from different legal relationships.

VA disability compensates service-connected conditions tied to military service. DBA compensates a work injury sustained as a civilian contractor employee. When your client was injured on the forklift in 2017, that injury had nothing to do with his earlier active-duty back condition. Two distinct causes, two distinct benefit systems, no statutory offset between them.

The carrier in our opening scenario is likely overreaching, or confusing VA benefits with something else. There is no general provision in the DBA or the incorporated LHWCA that lets a carrier reduce indemnity dollar-for-dollar against a VA disability check. The veteran earned that VA benefit through service, not through the contractor job.

The exception worth flagging involves the same body part. If the DBA injury aggravates a condition the VA already rates, you can face apportionment and causation fights, not a clean offset but a dispute over what portion of the disability the work injury actually caused. That is a medical-legal battle, not an arithmetic one, and it turns on the treating physician's opinion and the AWW math.

A second nuance: VA benefits can become relevant as evidence. A 40 percent VA rating for a knee will be cited by the carrier's defense to argue pre-existing impairment. That is not an offset, but it shapes the disability percentage and the value of the DBA claim. You manage it the same way you manage any causation dispute, with strong medical evidence and a clear timeline.

Before you concede any reduction, confirm exactly what the carrier is claiming a credit for. The letter rarely cites a statute. Reading the carrier's actual offset position in a specific claim, the periods, the amounts, the source benefit, requires pulling the underlying decision and coverage records, which is precisely where most attorneys are flying blind.

Where Do the Real DBA Offsets Actually Bite?

If VA disability is generally safe, where does coordination cost your client real money? Four places, and none of them involve the VA.

Social Security disability and retirement. The LHWCA, and therefore the DBA, coordinates with Social Security through the framework that governs combined disability benefits. When your client collects both, the combined total is capped at 80 percent of average current earnings under 42 U.S.C. 424a, and the excess reduces the Social Security check. Because the federal LHWCA contains no reverse-offset provision, it is the SSDI benefit that the Social Security Administration reduces, not the carrier's DBA compensation. This is the offset clients most often miss because they think of SSDI as untouchable.

Third-party recoveries. Under Section 33 of the LHWCA, if your client recovers from a negligent third party, the carrier holds a lien and a credit against future compensation. An overseas injury caused by a defective piece of equipment can produce a product-liability claim, and the carrier will assert its credit. The dual capacity doctrine can change who counts as a third party when the employer also manufactured the equipment, which directly affects the credit math.

Concurrent state workers' compensation. Section 3(e) of the LHWCA gives the carrier a credit for amounts paid under a state workers' compensation law for the same injury. If your client filed in a state forum first, those payments reduce the DBA exposure.

War Hazards Compensation Act reimbursement. For war-zone injuries, the WHCA lets the carrier seek Treasury reimbursement, which does not reduce your client's benefit but changes the carrier's incentives during settlement. A carrier expecting WHCA reimbursement negotiates differently.

Each of these offsets requires you to know the carrier's identity and the policy details before you can model the exposure. The credit a carrier asserts depends on the policy period, the responsible carrier at the time of injury, and whether a TPA is muddying the picture. When you are trying to challenge a carrier's Section 8(f) transfer position, the same carrier-identification work underpins your offset analysis.

How Does the Section 8(f) Special Fund Change the Coordination Math?

Section 8(f) of the LHWCA, fully applicable in DBA cases, lets a carrier shift liability for permanent disability to the Special Fund after 104 weeks when a pre-existing condition combined with the work injury to produce a greater disability. For your veteran client with a prior VA-rated condition, 8(f) is squarely in play.

Here is where VA disability re-enters the picture, not as an offset but as evidence. A documented service-connected condition is exactly the kind of pre-existing, manifest disability that supports an 8(f) transfer. The carrier will use your client's VA rating to argue the prior condition was serious, permanent, and a hindrance to employment, the three classic 8(f) elements.

This creates a strategic tension. The VA rating that protects your client's separate VA check can simultaneously help the carrier offload liability to the Special Fund. That transfer does not reduce your client's benefit, the Special Fund pays instead of the carrier, but it changes who you are litigating against and how settlement value is calculated.

For the claimant attorney, 8(f) is usually neutral-to-favorable because the benefit keeps flowing. The carrier cares intensely because it caps its exposure at 104 weeks. Understanding this asymmetry lets you negotiate from a position of clarity. If the carrier is desperate for an 8(f) transfer, that desperation is leverage in settlement.

The mechanics of contesting or supporting an 8(f) application, the documentation, the timing, the DOL's role, are detailed in our Section 8(f) transfer playbook. The coordination point to remember: a VA-rated condition is a double-edged document, protecting one benefit while enabling a liability shift on another.

What Does a Clean Coordination Workflow Look Like?

Coordinating three benefit systems is a process, not a single calculation. Here is the sequence that prevents surprises.

Step one: map every benefit stream. List what your client receives and from whom. VA disability, SSDI or SSA retirement, any state WC, any third-party claim, and the DBA indemnity itself. Each row is a potential coordination point. The LS-203 you file is the anchor document, and reading it correctly matters. Our field-by-field guide to the LS-203 form walks through what each entry tells you about the claim's posture.

Step two: identify the carrier and policy period. Every offset analysis depends on knowing which carrier was on the risk at the time of injury and what TPA administers the claim. Among the 154,886 coverage card records and 2,468 employer-carrier mappings in our data, carrier assignments shift every few years for most contractors, so the carrier at injury date is rarely the carrier you would guess.

Step three: classify each offset. Sort the streams into offsetting (SSDI, state WC, third-party) and non-offsetting (VA disability). This single sort answers most client questions and tells you where the real exposure sits.

Step four: model the AWW and the disability percentage. Because the DBA borrows Longshore math, the average weekly wage drives everything. Concurrent employment, overtime, and per diem treatment all affect the number, and the number affects every offset downstream.

Step five: anticipate the vocational fight. Permanent partial and permanent total disability turn on residual earning capacity, which means a vocational rehabilitation expert often decides the case value. Choosing that expert well, covered in our guide to selecting a vocational rehabilitation expert for DBA claims, shapes the settlement that all the offsets then apply against.

Run this workflow before the carrier sends its first credit notice, not after. The attorney who has already modeled the offsets controls the settlement conversation. The attorney who is reacting to a carrier's credit letter is negotiating from behind.

How Do You Pressure-Test the Carrier's Offset Position?

Carriers assert credits aggressively and cite statutes vaguely. Your job is to make them prove every dollar. Three checks expose most overreach.

First, demand the statutory basis. A credit against VA disability has no foundation in the DBA or LHWCA. If the carrier claims one, ask for the provision in writing. The silence that follows is often the end of the dispute.

Second, verify the periods and amounts. A Section 3(e) state WC credit only applies to the same injury and the same period. A third-party credit under Section 33 only reaches the net recovery after attorney fees and costs. Carriers routinely overstate both. Reconstructing the actual numbers requires the underlying payment and decision records.

Third, confirm carrier identity and continuity. If the policy changed hands during the claim, the credit one carrier asserts may belong to a different carrier's period, or may not survive the transition at all. This is where carrier-family resolution and TPA mapping decide the outcome, and it is the hardest piece to do from public records alone.

ClaimTrove pulls the carrier, employer, contract, and decision data behind every one of these checks in seconds. Instead of guessing which carrier was on the risk in FY2017 or hunting through scattered OALJ PDFs for the offset language, you run one investigation and get the carrier identification, the coverage history, and the relevant decisions in a single report. Run your client's investigation on ClaimTrove and walk into the offset conversation already knowing what the carrier knows.

Benefit coordination is not where DBA cases are won on paper. It is where they are quietly lost when an attorney concedes a credit that the statute never authorized. Model the math first, verify the carrier, and make the carrier prove the rest.