Austin Johnson
Head of Customer Success, Wellnecity
Would your leadership team be upset to learn that stoploss reimbursement was underpaid? Would they be happy to know that it was your diligent review that identified gaps in payment, that you then recovered?
It's the end of the calendar year and many stoploss contracts are completing their terms. Many contracts will be underpaid because the claims data have not been properly processed.
Why does this happen? In short, claims are complex, and vendors process data for lots of clients.
Example Root Causes of Stoploss Underpayment
Medical and Rx claims aggregation errors
Standalone stoploss carriers are dependent on the medical claims administrator (TPA/ASO) and the Pharmacy Benefit Manager to send them all eligible claims. When you have two vendors acting independently, claims aggregation errors often occur.
Run-out claims from prior administrators
Stoploss policies often include "run-out" claims that were incurred from a prior claims administrator. The prior carrier is not incentivized to send claims to stoploss. It is not unusual for 6-month (or indefinite!) data lags for these "run-out" claims.
Year-end processing delays
The seasonal increase in claims at year-end overwhelms claims administrators — stoploss-eligible claims incurred at year-end are often not processed in time to meet the stoploss reimbursement terms. Watchful plan sponsors can find missed reimbursement opportunities that were incurred and received by the TPA/ASO but were not paid until the next calendar year, when the stoploss deductible has been reset to zero.