1. Life Insurance Management
  2. Features
  3. Claims and settlement
Feature · Claims and settlement

Claims and settlement

Assess a reported loss, retain the benefit decision and verify settlement.

OverviewClaim payments to verify
Life Insurance Management · Claims and settlement

Claim payments to verify

Claim payments

New
ClaimDecisionAmount USDPaid atProvider event IDVerified
CLM-97083CD-794421021 OctPEI-605No
CLM-55337CD-567174006 OctPEI-995No
CLM-85456CD-608782006 OctPEI-867No
CLM-49366CD-697026027 OctPEI-669No
CLM-18949CD-858992006 OctPEI-979No
6 of 6 records
PEI-605Claim payments · CP-11392
No
ClaimCLM-97083
DecisionCD-7944
Amount USD210
Paid at21 Oct
Example screen with sample data

What you can do

Follow a claim from loss to payment

A claim starts with a policy, claim number, loss date, report date, claimed amount and loss evidence. The assessment action works on a Reported claim. It moves an eligible claim to Assessment with an operation receipt or records a reasoned refusal. A claim decision separately states whether to approve, decline or request evidence, with the reason, authorized person, decision date and approved benefit amount.

A verified provider payment links both the claim and the approved decision. The settlement action marks the claim Settled and records an operation receipt. This sequence lets the team explain why a claim was paid and which external payment event supports the outcome. The approved benefit and verified amount can be compared from the linked records rather than inferred from a claim status alone.

How the work is organized

  • Loss report. Dates, amount and evidence place the reported event against its policy.
  • Decision. The authorized result and reason explain the benefit judgment.
  • Payment. The provider event and verification state connect the decision to settlement.

What to agree during setup

Agree who can prepare the claim record, who makes the benefit decision and which provider event establishes payment. Review a coverage line with a realistic exclusion and effective period so the assessor can compare the reported loss to the policy terms. Choose a claim with clear evidence and a separate reviewer. Decide who investigates a failed operation receipt, and have the reviewer inspect the persisted result before retrying. Keep the authority to decide a benefit distinct from the work of gathering loss evidence.

Check the handoff on an actual case

Start with a Reported claim attached to an issued policy. Confirm the loss date and coverage terms before assessment. Inspect the assessment receipt and its reason if the action refuses to proceed. For an eligible claim, record the authorized decision and approved benefit. Match a verified provider payment to that decision and claim, then check that settlement moved the claim to Settled and left a receipt. If a payment event is repeated, compare its event ID with the existing record before concluding a new payment occurred. The Auditor can trace the claim, decision, payment and operation result as one case.

What your team sees

  • Claims by loss date — Review reported losses and their changing assessment states.
  • Operations and results — Follow the recorded effect when an action needs reconciliation.

Follow the work through

Use claim assessment and settlement to rehearse a covered and a refused case. See reports for claim and payment questions.

What it keeps track of

Data model
Claims
Claims reported against issued policies.
Claim decisions
Authorized claim decisions and approved benefits.
Claim payments
Verified provider payments against approved benefits.
Policies
Life insurance policies and issuance state.
Policy coverages
Coverage lines attached to a policy.
Operation receipts
Idempotent operation receipts for guarded actions.

Who uses it

Permissions
Claims Examiner
Prepares the reported loss.
Authorized Underwriter
Reviews claim and payment evidence.
Auditor
Reads the decision and settlement trail.
Insurance Coordinator
Provides policy context.

Set up Life Insurance Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started