> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heyrafiki.space/llms.txt
> Use this file to discover all available pages before exploring further.
# Claim valuation timeline
> Reproduce what was known about a Claim at any valuation date without rewriting later evidence into history.
Heyrafiki records when each Claim fact became effective and when the system learned it. This bitemporal history separates service, report, adjudication, remittance and settlement lag, and makes an as-of financial view reproducible.
`effective_at` records when the underlying Care, decision or money fact took effect.
`recorded_at` records when Heyrafiki received and persisted the fact.
`valuation_at` excludes every fact recorded after the stated cutoff.
A backdated adjustment first received on 2 August does not change what was known on 31 July. Re-run the same cutoff and the same ordered event history produces the same result.
## One Claim, three clocks
```mermaid theme={"dark"}
timeline
title Synthetic Claim evidence
8 Jul : Care delivered
9 Jul : Claim submitted
10 Jul : Information requested
11 Jul : Evidence received
14 Jul : Claim adjudicated
21 Jul : Remittance received
23 Jul : Settlement observed
31 Jul : Valuation cutoff
```
The public fixture keeps policy reference and version, source authority, reason codes and bounded evidence references with every relevant transition. Person identity and clinical content remain outside the payer timeline.
## Reproduce the as-of amount
For the synthetic fixture, all money is in integer KES minor units:
```text theme={"dark"}
billed = payer_liability + patient_responsibility + adjustment
600000 = 450000 + 50000 + 100000
outstanding = payer_liability - observed_settlement
100000 = 450000 - 350000
```
Remittance remains payer advice. Settlement remains independent evidence of money movement. The timeline does not mark a Claim settled from an advice file alone.
Reconstruct reported Claim development by service, report, decision and settlement dates. Preserve zero-Claim exposure and define the cohort, valuation basis and treatment of reopened or reversed Claims before calculating a portfolio measure.
Reconcile payer liability to advice, observed movement, ledger evidence and the remaining outstanding amount without netting unrelated balances.
Trace the Claim from effective policy version through coded decision, communication event, remittance and settlement observation. Each transition retains its source authority and recorded time.
Validate gapless event sequence, unique event identifiers, nondecreasing knowledge time, integer amounts and balanced adjudication in CI.
## Inspect the public evidence
The [synthetic valuation fixture](https://github.com/heyrafiki/openapi/blob/main/fixtures/claim-valuation-timeline.json), [JSON Schema](https://github.com/heyrafiki/openapi/blob/main/assurance/claim-valuation-timeline.schema.json) and [conformance test](https://github.com/heyrafiki/openapi/blob/main/scripts/check-claim-valuation-timeline.mjs) live with the OpenAPI contract.
```bash theme={"dark"}
git clone https://github.com/heyrafiki/openapi.git
cd openapi
npm ci
npm run test:financial-controls
```
The check rejects future knowledge, invalid sequence, non-integer money, unbalanced adjudication and an outstanding amount that cannot be reproduced.
## Actuarial boundary
This timeline supports analysis of reported Claims and reproducible outstanding observations. Portfolio reserve selection, IBNR, premium liability, capital, solvency, reinsurance and actuarial opinions remain with the insurer and its appointed actuarial authority.
The open fixture uses synthetic data. An approved Organization can test the same contract in the [Sandbox](/sandbox), then define its production data mapping, valuation policy and control owners through the institutional review.
Continue with [financial controls](/insurance/financial-controls), the [Assurance Graph](/institutions/assurance-graph) and the [acceptance test plan](/insurance/acceptance-testing).