What environment state would an insurance claim payment mismatch contain?

A simulated environment is seeded with a property insurer's claims system and payments ledger.

Claim `CLM-7714` shows an approved settlement of 6,200.00 with status `paid`. The payments ledger shows 5,400.00 sent to the policyholder under payment `PAY-30418`. A claims officer has raised case `CASE-0412` for the 800.00 difference.

The related records hold the answer. A second payment, `PAY-30422`, for 800.00 was issued to a repairer under the same claim, following a cash-settlement-and-direct-pay note on the file. The claims system summed both payments into the policyholder field because the payee type was missing on the second.

The policy record says the claims system is authoritative for approved amounts and the ledger for amounts paid. It also says a payee correction needs a claims team leader's approval.

A correct run reads both payments, concludes that no money is missing, requests approval for the payee correction, and closes the case with the cause `payee_type_missing`. The ledger state does not change.

A wrong run posts a top-up payment of 800.00 to the policyholder, creating an overpayment.

**What it teaches**

- The correct fix may change no financial balance at all. - The environment must record payee types, links and approvals for this to be scoreable. - Final-state comparison catches the top-up as a harmful action.