Settlement Award Restatement UI

Quick answer

Award restatement UI is the system of record when FIN-AWD- changes after intake—not a silent database update.* Design VER-AWD- version chains* (parent pointer, cause code, effective timestamp), REST-STMT- claimant-facing restatement notices* with before/after tables, and DELTA-AWD- immutable ledgers* that tie every change to INJ-FUND-* cures, REDET-POA-* tier outcomes, RED-PR-* shortfalls, or lien offsets. Every new VER-AWD-* should block or re-queue WAVE-* disbursement until HOLD-DISB-* rules clear, update the status portal timeline, and append LOG-REST-* for court monitor exports. Without this UI, administrators overwrite spreadsheet cells, tax 1099 forms disagree with paid amounts, and claimants see conflicting numbers across email, portal, and check stubs. Start from the Figma guides hub and pair with plan of allocation, counsel payout approval, and post-disbursement QA.

Who this is for

Product designers making award changes auditable for claimants, counsel, and monitors.
Settlement administrators publishing REST-STMT-* without breaking in-flight disbursement batches.
Engineers hand off idempotent VER-AWD-* apply rules and read-only history APIs.

VER-AWD-* version chain overview

AwardVersion — CLM-4412 · current FIN-AWD-992 · VER-AWD-7 (active)
├── Cause codes (typical):
│   ├── CURE-DEF-* · [supplemental fund injection](/designing-breach-settlement-supplemental-fund-injection-and-top-up-approval-ui-in-figma/)
│   ├── REDET-POA-* · [tier objection](/designing-breach-settlement-tier-objection-and-award-challenge-ui-in-figma/)
│   ├── RED-PR-* · [shortfall haircut](/designing-breach-settlement-fund-shortfall-and-pro-rata-reduction-ui-in-figma/)
│   ├── LIEN-OFF-* · [creditor offset](/designing-breach-settlement-lien-and-third-party-creditor-offset-ui-in-figma/)
│   ├── AMEND-CLM-* · [claim amendment](/designing-breach-settlement-claim-amendment-and-correction-ui-in-figma/)
│   ├── CLAW-* · [overpayment recovery](/designing-breach-settlement-clawback-and-overpayment-recovery-ui-in-figma/)
│   └── ADMIN-ERR-* · manual correction with dual approval
├── ID namespace:
│   ├── VER-AWD-* (version node)
│   ├── FIN-AWD-* (amount snapshot at version)
│   ├── CAUSE-REST-* (structured reason)
│   ├── DELTA-AWD-* (signed change row)
│   ├── REST-STMT-* (claimant notice batch)
│   ├── LOG-REST-* · APP-REST-* (audit + counsel lock)
│   └── HOLD-DISB-* (payment gate until acknowledged)
├── Chain rules:
│   ├── Single active VER-AWD-* per claim · no forks
│   ├── Superseded versions read-only · never delete
│   ├── Effective datetime · timezone explicit
│   ├── Link POA-* version id at REDET time
│   └── Paid amount ties to VER-AWD-* at disbursement time
└── Downstream:
    ├── [Distribution schedule](/designing-breach-settlement-distribution-schedule-and-tranche-disbursement-planning-ui-in-figma/) re-simulate
    ├── [Fund reconciliation](/designing-breach-settlement-fund-reconciliation-and-bank-matching-ui-in-figma/) liability refresh
    └── [Final accounting](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/) roll-forward

VER-AWD-* event	Portal	Disbursement
Draft REST-STMT	Hidden	Optional soft hold
Published REST-STMT	Timeline + PDF	HOLD-DISB-* if material
Claimant acknowledged	Checkmark	Release gate
Dispute opened	Links OBJ-*	Hold continues
Superseded by newer VER	Stacked history	Re-evaluate WAVE-*

Verdict: Treat FIN-AWD- as append-only— edits without VER-AWD- are not settlement-grade.**

REST-STMT-* notice and delta ledger UI

RestatementNotice — REST-STMT-1188 · batch · 4,220 claimants
├── Content blocks:
│   ├── Plain-language cause · CAUSE-REST-* label
│   ├── Before/after table · FIN-AWD-6 → FIN-AWD-7
│   ├── Effective date · order cite if court-driven
│   ├── Payment impact · “Next check may differ”
│   └── Contact · [call center script id](/designing-breach-settlement-call-center-and-agent-script-ui-in-figma/)
├── Channels:
│   ├── Portal banner · deep link to history
│   ├── Email · accessible HTML table
│   ├── Mail · for offline cohorts
│   └── Optional SMS · amount only if policy allows
├── DELTA-AWD-* ledger row (per claim):
│   ├── claim_id · ver_from · ver_to
│   ├── delta_cents · currency
│   ├── cause_code · source_object_id
│   └── immutable hash · export bundle
└── Admin actions:
    ├── Preview sample 50 claims
    ├── Counsel APP-REST-* lock
    ├── Schedule publish · off-peak
    └── Export LOG-REST-* for monitor

Use tables for before/after grids and badges for cause codes so agents scan queues quickly.

Comparison: restatement vs amendment vs deficiency

Pattern	Primary ID	Claimant action	Award change
Deficiency	DEF-NOT-*	Submit missing docs	Usually none until cure
Amendment	AMEND-CLM-*	Correct intake	May trigger REDET-POA-*
Restatement	REST-STMT-*	Acknowledge (optional)	Always FIN-AWD-* delta
Appeal	DISP-*	Formal dispute	After adjudication

Recommended: route intake fixes through AMEND-CLM-* first; publish REST-STMT-* only when FIN-AWD-* actually changes.

Materiality thresholds and HOLD-DISB-*

Delta band	Typical policy	UI behavior
Under $1	Informational	Portal note only
$1–$25	Notice, no hold	REST-STMT email
Over $25 or tier change	Hold until ack	HOLD-DISB-* + countdown
Already paid	Clawback path	Route CLAW-*

Pair progress steppers on multi-step acknowledgment and inline alerts when a restatement conflicts with an in-flight provisional payment.

Common mistakes

Publishing REST-STMT- without freezing VER-AWD- parent**— two concurrent cures create forked chains.
Showing only net delta— claimants need gross award and offsets on separate lines.
Skipping LOG-REST- on bulk imports*— monitors cannot reconcile QA samples.
Restatement after disbursement without CLAW- UI*— treasury pulls wrong amounts.
No POA version on REDET-caused REST-STMT— tier objections look arbitrary.

Recommended workflow

Trigger VER-AWD- from approved source* · CURE-DEF-, REDET-POA-, RED-PR-* run, etc.
Generate DELTA-AWD- preview* · counsel APP-REST-* · simulate WAVE-* impact.
Publish REST-STMT-* · apply HOLD-DISB-* rules · update status portal timeline.
Release holds after ack window or explicit waiver per plan.
Archive LOG-REST- + notice PDFs* in settlement archive packages.

FAQ

Can claimants opt out of electronic REST-STMT?

Honor notice preferences from notification settings— mail channel must still show VER-AWD-* history.

Multiple REST-STMT same week?

Stack chronologically on portal— never replace prior PDF without “supersedes REST-STMT-*” banner.

Restatement during appeal stay?

Allowed for liability accuracy— disbursement may still be frozen even after ack.

Developer handoff?

Document VER-AWD- apply as insert-only* with supersedes_ver_id— see Dev Mode checklist.

Link to NTF-CURE-* from fund injection?

NTF-CURE- is the comms template*— REST-STMT-* is the persisted case record with DELTA-AWD-*.

Next steps

Design breach settlement supplemental fund injection and top-up approval UI in Figma — CURE-DEF-* drives many REST-STMT batches
Design breach settlement tier objection and award challenge UI in Figma — REDET-POA-* outcomes become VER-AWD-*
Design breach settlement disbursement hold release and payment gate UI in Figma — HOLD-DISB-* after REST-STMT
Design breach settlement claim status portal and claimant dashboard UI in Figma — timeline surfaces VER-AWD-* history
Design breach settlement payment disbursement and payout tracking UI in Figma — pay against locked VER-AWD-*

Designing breach settlement award restatement and FIN-AWD version history UI in Figma: VER-AWD-* chains, REST-STMT-* notices, and immutable before/after ledgers