Frequently asked questions.

Claims platform modules and other stop loss tools track medical stop loss and generate reports. But the work is still manual and still in spreadsheets.

Korva does most of that work. Our AI agents read each policy and plan document as written, including the complex edge cases: lasers, exclusions, irregular contract basis, percentage of savings caps, you name it. Every claim line is checked against both documents, and the filing is built from what it finds.

Rules engines can’t do that, because no two policies are worded the same. When something doesn’t resolve cleanly, Korva flags it for your team to review. And every carrier exchange teaches Korva what that carrier questions and why, so each filing gets cleaner than the last.

Sort of. Korva prepares the complete filing and your stop loss team reviews, adjusts, and approves it. Nothing goes to the carrier without human review.

After adjudication. Korva ingests your adjudicated claims and other plan expenses, so a member or group crossing a threshold surfaces that day instead of weeks or even months later.

All of them. Specific and aggregate, aggregating specific deductibles, lasers, monthly accommodation, and level funded groups. If a group has something we haven’t seen, we want to see it.

Yes. Policies are uploaded to the portal for Korva to read and pull the terms that drive everything downstream: deductibles, lasers, exclusions, contract basis.

Yes. Korva knows which supporting documents each carrier will ask for: accident detail forms, work status forms, itemized bills. It asks for what’s missing before the filing goes out, not after the carrier sends it back.

It depends! Claims platforms, PBM portals, or a file sent via email. Whatever your team already does, Korva works with it.

Yes. Specific, aggregate, and high-cost claimant reports come standard, plus custom reports. Pull them on demand or send them on a schedule.