Payments and evidence

A claim payment records the amount paid, payment date, provider event identifier and verification state. It links to both the claim and the benefit decision. Claims Specialist can compare that event with the authorized benefit and the external provider record before marking it verified. A claim should not be treated as settled merely because someone entered an amount. The linked decision explains why the amount was authorized; the provider event is evidence that a payment occurred.

Policy attachments preserve a title, file, upload date, evidence type, visibility and uploader. They give the team a controlled place for documents used during policy and review work. Operation receipts document attempted external actions on a policy, including the key, expected revision, result, external reference and failure reason. Together these records help staff answer what was decided, what was sent, what came back and what still needs follow-up.

• Payment event. Claims Specialist links a provider event to its claim and claim decision, then checks amount and date.
• Policy evidence. Admin or Policy Operations uploads policy-related files with a clear title, type and visibility.
• Operation follow-up. Admin reviews failed or unresolved receipts by action and key before anyone repeats an external request.

Agree which payment service supplies the event identifier and who can verify a payout. Decide whether verification requires a provider confirmation or a finance reconciliation, and make that standard consistent across the team. An amount on a payment record does not by itself say that the insurer’s obligation is closed. The team should explicitly decide when a claim can move to settled and closed.

For attachments, agree who may use Internal and Shared visibility and what each means in the organization’s access policy. Name evidence types consistently enough to retrieve the right document during a review. For operation receipts, decide who handles Failed and needs review results and when a retry is permitted. The operation key and expected revision should be checked before recording another effect.

Claims Authorizer approves a benefit after assessing the reported loss. A payment service returns an event with a paid date, amount and identifier. Claims Specialist records that event under the same claim and decision, compares the amount with the approved benefit and checks the provider event before changing verification to Yes. The specialist then moves the claim through settlement and closure under the team’s rules.

Now consider an event whose amount differs from the authorized benefit. The specialist keeps the payment unverified and asks Claims Authorizer to resolve the difference. If a carrier operation associated with the policy has failed, Admin opens the receipt and reads its failure reason and external reference. Staff can explain both exceptions from their source records instead of relying on a status label alone.

• Payments to verify — Claims Specialist sees unverified claim payments with event identifiers and linked decisions.
• Failed operations — Admin sees unresolved policy operations and their reasons for follow-up.

See claim settlement and premium verification.