What Are the System Requirements for Stop-Loss Claim Reporting?

What are specific and aggregate stop-loss coverages?

According to the National Association of Insurance Commissioners (NAIC), specific stop-loss reimburses the plan when one covered person's eligible claims exceed a specific deductible within the policy period. Aggregate stop-loss reimburses the plan when the group's total eligible claims exceed the aggregate attachment point. These two coverages are distinct but are typically purchased together from a single carrier.

Specific coverage focuses on individual risk. The claims system must accumulate one person's eligible claims across all covered categories, including pharmacy, and flag when totals approach the deductible. Aggregate coverage focuses on group risk. The system must total the group's eligible paid claims periodically, strictly netting out excluded items.

Claims reimbursed under specific coverage are excluded from the aggregate accumulation, requiring the claims system to maintain two separate running calculations.

What does the carrier need reported for stop-loss claims?

Carriers require strict adherence to the policy's reporting schedule. This schedule is a binding contract term, not an administrative guideline. The claims system must generate four distinct types of data for the carrier.

• Aggregate stop-loss report: A routine, periodic summary of the group's paid claims against the attachment point.
• Specific stop-loss notice: An event-driven alert sent when an individual claimant approaches the notification trigger.
• Reimbursement claim: A formal filing with supporting evidence submitted when a claimant crosses the specific deductible.
• Large claimant disclosure: A renewal statement detailing known conditions that the carrier uses to price the subsequent year's coverage.

Missing the renewal disclosure timeline is highly risky. It is the one report where a TPA omission can legally alter the terms of coverage after the fact.

What triggers a specific stop-loss notice?

The Self-Insurance Institute of America (SIIA) notes that specific notice triggers are defined by the policy. They serve to let the carrier open a file and manage the case before it becomes fully reimbursable.

A specific stop-loss notice is typically triggered by one of three events

• A claimant's eligible claims reach a stated percentage of the specific deductible.
• A claimant is diagnosed with a condition matching the policy's trigger list.
• The TPA becomes aware of an admission or prior authorization likely to exceed the deductible.

Each trigger demands distinct system capabilities. The deductible-share trigger requires recalculation during every check run. The diagnosis trigger requires real-time comparison of incoming ICD codes against the policy list. The awareness trigger requires integration between prior authorization records and the stop-loss reporting desk.

What is the difference between a paid versus incurred contract basis?

A claim is incurred on the date of service and paid on the date the plan disperses funds. The paid versus incurred contract basis dictates which of these dates must fall within the active policy period for the claim to be covered.

• Incurred and Paid: Covers claims incurred and paid entirely within the policy period.
• Run-in: Covers claims incurred before the period began, but paid during the period.
• Run-out: Covers claims incurred during the period, but paid within a specified window after it ends.
• Paid: Covers claims paid during the period, regardless of the service date.

This basis dictates exactly what the claims system must report. A claim filed under an incurred-and-paid contract must clearly document both dates on every line item. If a plan changes its contract basis at renewal, claims can easily fall into coverage gaps. A claims system that only logs the paid date cannot properly support anything other than a paid contract.

What is stop-loss lasering, and how does it impact systems?

Stop-loss lasering is an underwriting practice where the carrier assigns a higher specific deductible, or a complete exclusion, to a named individual with a known, high-cost condition. This allows the group's standard deductible to remain lower for the rest of the members. However, certain state insurance regulations restrict or prohibit lasering on policies they govern.

For a claims system, a laser acts as a secondary threshold. The lasered individual must accumulate against their customized deductible, while the rest of the group accumulates against the standard specific deductible.

If a claims system can only support one specific deductible per group, administrators are forced to track lasered individuals manually on spreadsheets. Manual tracking is the most common cause of late notices and missed reimbursements.

What stop-loss claim filing documentation is required?

Filing a specific claim requires rigorous proof that each charge was eligible, paid, and properly adjudicated. The carrier audits the plan's administration alongside its math.

Standard stop-loss claim filing documentation includes

• Claim line details with incurred and paid dates.
• Explanations of Benefits (EOBs).
• Itemized facility bills, if requested by the carrier.
• Proof of the claimant's active eligibility on the date of service.
• The specific plan document provisions used to adjudicate the claim.
• The status of any subrogation, coordination of benefits, or recoveries.

Recoveries must be netted against the reimbursement. A carrier can legally decline a claim if it was paid outside plan terms, issued to an ineligible member, or lacked required prior authorization. A robust adjudication record is essential to prove the claim holds up to scrutiny.

Why does late reporting increase TPA stop-loss exposure?

A late or incomplete report directly creates TPA stop-loss exposure. Administrative services agreements generally hold the TPA contractually responsible for accurate and timely stop-loss reporting. Policies mandate that complete filings and timely notices are strict conditions for reimbursement.

When a carrier denies a claim because a specific notice was missed or a filing arrived past the deadline, the expected reimbursement is lost. Because the sponsor expected those funds, they will look to the administrator who processed the claim to cover the deficit.

Similarly, failing to execute a complete large claimant disclosure at renewal exposes the plan to retroactive lasering or contested terms. In both scenarios, the financial liability stems from the claims system holding data that the stop-loss desk failed to report on time.

How should a claims system handle stop-loss claim reporting?

To succeed, a claims system must house per-claimant accumulations by both incurred and paid dates, family linkages, policy period boundaries, customized laser deductibles, and coordination-of-benefits netting. Because few legacy systems centralize all these elements, many TPA stop-loss desks rely heavily on external spreadsheets.

The most critical intervention point is the check run. Every check run should automatically recalculate claimant accumulations, compare them against policy triggers, and output a list of required notices before funds are dispersed.

Daybook Health manages the process from adjudication to the check run in a self-funded plan, ensuring high-fidelity data capture. By delivering a check run prepared with every stop-loss notice listed, Daybook allows the TPA's stop-loss desk to simply execute the notice and the filing, keeping the administrator compliant and the sponsor protected.