Why Does This Distinction Even Matter?
Every DBA attorney has encountered this problem. You pull up a DOL record, an OALJ decision, or an OWCP filing. The entity listed as handling the claim looks like the carrier. You draft your filing. Weeks later, you discover you named the wrong entity. The name in the record was a Third Party Administrator, not the insurance carrier.
TPAs administer claims. Carriers underwrite risk. These are fundamentally different roles, and confusing them costs attorneys time, delays benefits for injured workers, and creates procedural headaches that are entirely avoidable.
The problem is that federal records do not clearly distinguish between the two. A TPA name can appear in the same fields, the same documents, and the same case captions where you would expect to see the carrier. Unless you already know the difference, the records will not tell you.
What Exactly Does a TPA Do in DBA Claims?
A Third Party Administrator is a company hired by an insurance carrier to manage the operational side of claims. The TPA handles the paperwork. It processes medical bills. It coordinates with injured workers and their attorneys. It files documents with the Department of Labor.
What the TPA does not do is bear financial risk. The TPA does not write the insurance policy, collect premiums, or pay benefits out of its own reserves. That is the carrier's job. The TPA is a service provider, not an insurer.
Think of it this way: the carrier is the entity that owes the money. The TPA is the entity that manages the process of getting the money to the right place. When you file a DBA claim, you need to name the entity that owes the money.
Several large national claims management firms dominate the DBA third-party administration market. These companies each handle claims for multiple carriers simultaneously, which means seeing one of their names in a record tells you almost nothing about which carrier is actually on risk.
Where Do TPA Names Show Up in Federal Records?
TPA names infiltrate DBA records at every level. Understanding where they appear helps you spot them before they derail your research.
OALJ Decisions: Administrative Law Judge decisions frequently list the TPA as the employer/carrier representative. The decision caption may name the TPA alongside or instead of the actual carrier. In ClaimTrove's database of 5,000+ OALJ decisions, TPA names appear as party identifiers in a significant percentage of cases.
OWCP Correspondence: Because TPAs handle day-to-day communication with the DOL, their names and addresses appear on filed documents. An attorney reviewing OWCP records may see the TPA letterhead and assume it is the carrier.
DOL Case Summaries: The Department of Labor's annual case summary reports sometimes aggregate data using the claims administrator rather than the underlying carrier. This creates misleading statistics about carrier market share.
Informal Records: When employers respond to inquiries about their DBA coverage, they often provide the TPA's name and contact information rather than the carrier. The employer itself may not know the difference. HR departments deal with the TPA, not the carrier.
How Can You Tell If a Name Is a TPA or a Carrier?
The single most reliable method is checking the DOL's list of authorized DBA carriers. The Department of Labor publishes annual reports listing every insurance company authorized to write DBA coverage. If the name you found in a record does not appear on that list, it is almost certainly a TPA or some other non-carrier entity.
As of the most recent DOL authorization data, there are 637 carriers that have been authorized to write DBA coverage at some point. That is a large list, but it is finite and searchable. If your entity is not on it, you have your answer.
A second method is checking OWCP coverage cards. These filings, which employers submit to document their DBA insurance, typically list the actual underwriting carrier and policy number. Coverage cards are more reliable than case records because they are filed specifically to document the insurance relationship, not to manage a claim.
A third approach is looking at NAIC numbers. Every legitimate insurance carrier has a National Association of Insurance Commissioners number. TPAs do not. If the entity in your record has no NAIC number, it is not a carrier. NAIC numbers are also the key to mapping carrier family relationships where multiple subsidiary names belong to one parent group.
What Happens When You File Against the Wrong Entity?
Filing a DBA claim against a TPA instead of the carrier creates a cascade of problems. The most immediate is delay. The TPA will respond that it is not the carrier and cannot accept liability. You then need to identify the actual carrier and re-file.
In straightforward cases, this might cost you a few weeks. In complicated cases involving older injuries, corporate restructurings, or disputed coverage periods, the delay can stretch into months. During that time, the injured worker is not receiving benefits.
There is also a statute of limitations concern. DBA claims must be filed within specific time windows. If you spend weeks filing against the wrong entity and the limitations period is running, you could face a time-bar argument when you re-file against the correct carrier.
The financial cost to the law firm is real as well. Every hour spent untangling a TPA misidentification is an hour not spent on case development. For firms handling high volumes of DBA claims, these errors compound.
Why Do TPA-Carrier Relationships Change Over Time?
One of the trickiest aspects of TPA identification is that the relationships are not permanent. A carrier may use one TPA for several years, then switch to a different one. A TPA may lose a contract with one carrier and pick up business from another.
This means that even if you correctly identified a TPA-carrier relationship for a 2016 claim, that same TPA might be working for a completely different carrier by 2020. You cannot rely on historical mappings without verifying them against the specific time period of the injury you are investigating.
Our research across 30,000+ OWCP filings and 5,000+ OALJ decisions confirms that TPA-carrier pairings shift regularly. At least two major TPAs in the DBA market switched their primary carrier relationships during the 2015-2022 period. If you assumed the old relationship still held, you would name the wrong carrier.
How Does ClaimTrove Handle TPA Resolution?
ClaimTrove's investigation engine maintains a time-stamped database of known TPA-to-carrier mappings. When a TPA name appears in search results from any of the 18+ data sources the system queries, the engine flags it automatically.
The resolution process works in two steps. First, the system identifies the entity as a TPA rather than a carrier by checking it against the DOL authorized carrier list. Second, it looks up the TPA-carrier relationship for the specific time period of the injury, using verified data from OWCP filings and OALJ decisions.
The result is a carrier identification that accounts for temporal shifts in TPA relationships. Instead of seeing a TPA name and wondering who the real carrier is, you see the actual underwriting carrier with a confidence score based on the strength and recency of the underlying evidence. Try an investigation to see how TPA resolution works on a real case.
What Are the Warning Signs That You Are Looking at a TPA?
Several indicators suggest that a name in a DBA record is a TPA rather than a carrier:
- The name does not appear on DOL authorized carrier lists. This is the most definitive test. If the entity was never authorized to write DBA coverage, it cannot be the carrier.
- The name appears as a "claims administrator" or "adjuster" rather than "carrier" or "insurer." Some records use these labels, though not consistently.
- The same name appears across multiple carriers. If an entity name shows up in records involving several different carriers, it is likely a TPA that works for all of them.
- The entity has no NAIC number. Legitimate insurance carriers are registered with the NAIC. TPAs are not.
- The employer or HR department provides the name as their "insurance contact." Employers interact with TPAs, not carriers. When they give you a name, verify it independently.
Does This Problem Affect All DBA Claims Equally?
No. TPA confusion is most common in claims involving large defense contractors and government service providers. These employers typically have high volumes of DBA claims and outsource claims administration to TPAs as a matter of course.
Smaller employers with fewer DBA claims may handle administration in-house or work directly with the carrier. In those cases, the carrier name in the record is more likely to be the actual carrier.
The problem is also more acute for older claims. As time passes, TPA-carrier relationships change, companies merge, and institutional knowledge evaporates. A TPA name from a 2012 record may be especially misleading if you are researching it in 2026.
Claims in high-volume theaters like Afghanistan and Iraq are particularly susceptible. The sheer number of contractors, carriers, and TPAs operating in those regions during peak years created a tangled web of relationships that is difficult to unravel from public records alone. When you encounter a TPA in your investigation results, treat it as one of several red flags that signal your carrier identification needs additional verification.
What Should Your Research Workflow Look Like?
When you encounter a name in a DBA record that might be the carrier, run through this verification process:
- Check the DOL authorized carrier list. Is this entity authorized to write DBA coverage? If not, it is a TPA or other non-carrier entity.
- Search OWCP coverage cards. Coverage cards filed for the relevant employer and time period will list the actual carrier and policy number.
- Cross-reference OALJ decisions. Look at the full text of decisions involving the same employer. The decision may name both the TPA and the carrier in different sections.
- Verify the time period. Confirm that the carrier you identified was on risk at the time of the injury, not just at some point in the employer's history.
- Check for corporate family relationships. The carrier may be a subsidiary of a larger group. Make sure you are naming the correct legal entity within the family.
This manual process works. It is also time-consuming. For a single claim, expect to spend an hour or more if the records are ambiguous. For firms handling multiple DBA cases, building a structured 5-step carrier investigation workflow prevents the most common errors and reduces time per case significantly.
ClaimTrove automates this entire workflow across over 1 million records from 18+ federal data sources. The system runs all five verification steps simultaneously and returns results with source citations in under 30 seconds. Start your first investigation and see the difference automated TPA resolution makes.
Are There Other Entities That Get Confused With Carriers?
TPAs are the most common source of confusion, but they are not the only one. Brokers and agents also appear in DBA records and can be mistaken for carriers. A broker helps the employer purchase the DBA policy but does not underwrite the risk.
Carrier groups and holding companies create another layer of confusion. A parent company may appear in records even though the actual policy was written by a specific subsidiary. Filing against the parent instead of the subsidiary can create jurisdictional and procedural issues.
Surplus lines carriers and state-specific entities add further complexity. Some DBA policies are written through surplus lines markets, and the entity name on the policy may differ from the group name that appears in federal records.
The common thread is that DBA records were not designed for carrier identification. They were designed for claims administration, case management, and regulatory compliance. Using them for identification requires understanding the limitations of each record type and cross-referencing multiple sources to confirm the true carrier. The broader trend of defense contractor consolidation makes these family structures even harder to track over time.