Settlement Claim Amendment UI

Quick answer

Claim amendment UI lets class members fix errors on filed CLM- records—without reopening approved claims for fraud or allowing unlimited edits after payout.* Design a field-level edit matrix (what claimants change self-service vs what needs admin AMD-* review), a correction wizard with before/after diff preview, and an immutable audit trail every stakeholder can trust. Gate changes after approval and block amendments that affect payment amount without counsel workflow. Connect to settlement claims, claim status portal, payment disbursement, and disputes. Start from the Figma guides hub and pair with forms, audit log, and Dev Mode handoff.

Who this is for

Product designers building self-service correction flows—not unconstrained profile editing from consumer apps.
Settlement administrators reviewing name changes, tier corrections, and post-approval amendments at scale.
Class counsel defining which fields may change after approval and which require court notice.

Amendment lifecycle overview

ClaimAmendment — AMD-992-0033 · CLM-992-44102 · Field: mailing_address · Status: Auto-applied
├── Triggers:
│   ├── Claimant clicks "Correct information" on [status portal](/designing-breach-settlement-claim-status-portal-and-claimant-dashboard-ui-in-figma/)
│   ├── Admin initiates correction during [call center](/designing-breach-call-center-and-agent-script-ui-in-figma/) session
│   ├── Returned check or failed ACH forces address/bank update
│   └── Eligibility file update retroactively affects CLM-* tier
├── ID namespace:
│   ├── AMD-* (amendment request) · CLM-* (target claim)
│   ├── REV-* (admin review record when manual approval required)
│   └── AUD-* (audit log entry—append-only)
├── Outcomes:
│   ├── Auto-applied (low-risk fields, pre-approval)
│   ├── Admin approved (REV-* signed off)
│   ├── Denied with reason (claimant notified)
│   └── Escalated to DIS-* or counsel (amount-affecting changes)
└── Post-PAY-* rule: Block amount/name changes without stop-payment workflow

CLM-* state	Self-service edits	Admin review required
Draft / not submitted	All fields	None
Submitted, under review	Contact, mailing address	Name, SSN, DOB, tier
Approved, pre-payment	Address, phone, email	Name, payment method, amount
Payment initiated	None without stop	All material fields
Paid	Contact only	Name/legal changes via AMD-* + counsel

Verdict: Treat amendments as governed events, not form autosave—every change creates AMD-* and AUD-* records.

Field-level edit matrix

EditMatrix — Settlement: Acme · CLM-992-44102 · State: Approved pre-payment
├── Self-service (auto-apply AMD-*):
│   ├── Mailing address · Phone · Email · Notification language
│   └── Payment method (if PAY-* not yet sent)
├── Admin review (REV-* queue):
│   ├── Legal name change (marriage, typo with ID proof)
│   ├── SSN/DOB correction (eligibility impact)
│   ├── Claim tier / damages category change
│   └── [Minor](/designing-breach-settlement-minor-claimant-and-guardian-designation-ui-in-figma/) DOB correction
├── Blocked (claimant cannot edit):
│   ├── Settlement case ID · Original filing timestamp
│   ├── Approved payment amount (without dispute/counsel path)
│   ├── Fraud hold flags · Internal admin notes
│   └── [Opt-out](/designing-breach-settlement-opt-out-and-class-member-exclusion-ui-in-figma/) status (separate flow)
├── Evidence requirements:
│   ├── Name change → Government ID upload via [file upload](/designing-file-upload-and-drag-drop-ui-in-figma/)
│   ├── Address change → None pre-payment · Utility bill if post-return
│   └── Tier change → Supporting docs per settlement schedule
└── Display: Gray out blocked fields with tooltip "Contact administrator to change"

Publish the matrix in admin config—designers show disabled fields with explanation, not hidden fields that confuse claimants.

Claimant correction wizard

CorrectionWizard — CLM-992-44102 · Step 2 of 3 · Change: mailing_address
├── Step 1 — Select field to correct:
│   ├── List editable fields only (from EditMatrix)
│   ├── "Something else" → Contact support form (not free-text edit)
│   └── Warning banner if PAY-* in progress
├── Step 2 — Enter new value:
│   ├── Show current value (masked where sensitive)
│   ├── New value with same validation as original [claim form](/designing-breach-settlement-notice-and-victim-compensation-claims-ui-in-figma/)
│   ├── [Foreign address formats](/designing-breach-settlement-foreign-claimant-and-international-payment-ui-in-figma/) when FOR-* flagged
│   └── Optional: Upload supporting document
├── Step 3 — Review diff:
│   ├── Before / After side-by-side
│   ├── Impact notice: "This may delay payment by X days" if REV-* required
│   ├── Checkbox: "I certify this information is accurate"
│   └── Submit → AMD-* created
├── Post-submit states:
│   ├── Auto-applied → Success · Timeline updated on status portal
│   ├── Pending REV-* → "Under review" · SLA badge
│   └── Denied → Reason + appeal or [dispute](/designing-breach-settlement-claims-dispute-and-appeals-ui-in-figma/) link
└── Rate limit: Max 3 self-service AMD-* per field per 30 days (configurable)

Use progress steppers for the wizard—corrections are high-stakes; show clear steps.

Post-approval and payment change gates

PaymentChangeGate — CLM-992-44102 · PAY-992-44102 · Status: In transit · Amendment: blocked
├── Gate rules:
│   ├── PAY-* status = initiated/sent → Block name and bank AMD-* without stop
│   ├── Admin must initiate stop-payment or recall (out of scope for claimant UI—show contact CTA)
│   └── Check mailed → Address AMD-* updates re-mail logic only (admin)
├── Failed payment exception:
│   ├── ACH return → Auto-open ACT-* for bank correction (not full AMD-* review)
│   ├── Claimant updates via [payment wizard](/designing-breach-settlement-payment-disbursement-and-payout-tracking-ui-in-figma/)
│   └── New AMD-* auto-linked to return reason code
├── Amount-affecting changes:
│   ├── Never self-service after approval
│   ├── Admin AMD-* → Counsel notification · May require [dispute](/designing-breach-settlement-claims-dispute-and-appeals-ui-in-figma/)
│   └── Timeline shows "Amount under review" not new dollar value until final
└── [Deceased](/designing-breach-settlement-deceased-claimant-and-heir-designation-ui-in-figma/) / [minor](/designing-breach-settlement-minor-claimant-and-guardian-designation-ui-in-figma/) overlays:
    └── Payee changes route to HEI-* or GUA-* flows—not generic AMD-*

Show why amendment is blocked with specific next step—“Payment in transit. Contact us to stop and reissue” beats generic error.

Administrator amendment review console

AmendmentReviewConsole — 8 pending REV-* · 3 urgent (PAY-* hold)
├── Queue columns:
│   ├── AMD-* ID · CLM-* · Field changed · Submitted · SLA
│   ├── Risk score (internal only—not claimant facing)
│   └── Assigned reviewer
├── Review detail:
│   ├── Before/after diff · Uploaded evidence viewer
│   ├── Eligibility file cross-check (name/SSN/DOB changes)
│   ├── Related PAY-* / TAX-* impact flags
│   └── Prior AMD-* history on same CLM-*
├── Actions:
│   ├── Approve → Apply to CLM-* · AUD-* entry · Notify claimant
│   ├── Deny → Reason code · Claimant email · Optional appeal path
│   ├── Request more info → ACT-* on claimant portal
│   └── Escalate to counsel (amount/tier changes)
├── Bulk operations:
│   ├── Approve address corrections from returned mail batch
│   └── Export AMD-* log for [final accounting](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/)
└── Audit: amd_id · rev_id · reviewer_id · decision · applied_at · clm_snapshot_hash

Admin console shares patterns with privacy request queue—case-based review with SLA sorting.

Audit trail and correction history

AuditTrail — CLM-992-44102 · 4 amendments · View: Claimant-safe
├── Claimant-visible history (on status portal):
│   ├── "Mailing address updated" · Aug 10 · No before/after PII
│   ├── "Claim submitted" · Aug 1
│   └── "Payment method updated" · Aug 18
├── Admin-full history (internal):
│   ├── AMD-992-0033 · address · old_hash → new_hash · auto_applied
│   ├── AMD-992-0021 · phone · REV-992-0012 approved · reviewer jsmith
│   └── Immutable append-only · No delete · [Legal hold](/designing-compliance-exports-and-legal-hold-ui-in-figma/) respected
├── Export:
│   ├── Claimant PDF summary (counsel-approved fields only)
│   └── Admin CSV for court [final accounting](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/)
└── Integration: Same AUD-* patterns as [audit log UI](/designing-audit-log-and-security-activity-ui-in-figma/) but settlement-scoped

Claimants see that a change happened, not always what the old value was—reduces identity theft risk on shared screens.

Comparison: amendment UI vs adjacent settlement surfaces

Surface	Focus	This UI adds
Settlement claims	Initial CLM-* filing	Post-filing corrections
Status portal	Visibility	”Correct information” entry
Payment disbursement	PAY-* execution	Bank fix after return
Disputes	Eligibility fights	Factual corrections
Call center	Agent-assisted edits	Same AMD-* records as self-service

Handoff checklist (Dev Mode)

EditMatrix — settlement_id, clm_state_enum, field_name, edit_permission_enum (self/admin/blocked), evidence_required, rate_limit_days.
CorrectionWizard — amd_id (AMD-*), clm_id, field_name, old_value_hash, new_value, evidence_refs[], certification_at, submission_status.
PaymentChangeGate — clm_id, pay_id, pay_status_enum, amendment_allowed, block_reason_code, stop_payment_required.
AmendmentReviewConsole — rev_id (REV-*), amd_id, reviewer_id, decision_enum, denial_reason, applied_at, eligibility_check_result.
AuditTrail — aud_id (AUD-*), clm_id, amd_id, event_type, visible_to_claimant, timestamp, actor_type_enum (claimant/admin/system).

Common mistakes

Mistake	Why it hurts	Fix
Unlimited post-approval edits	Fraud · Double payment	EditMatrix by CLM-* state
No audit trail	Court accounting failure	Append-only AUD-* per change
Allow amount self-correction	Overpayment liability	Admin + counsel path only
Hide edit option on portal	Call center load	Prominent “Correct information”
Apply name change without ID	Wrong payee	REV-* + document upload
Same flow for HEI-/GUA-* changes	Legal invalid payee	Route to specialized flows
Show old SSN on diff screen	Privacy leak	Mask in claimant view
No rate limit on AMD-*	Abuse · Review flood	Per-field limits
Block all edits during review	Can’t fix typos blocking approval	Allow contact/address pre-approval
Email-only correction confirm	No portal record	Timeline event on status portal

Recommended workflow

Counsel defines EditMatrix per CLM-* state and settlement order before wireframes.
Design correction wizard with diff review and certification checkbox.
Add payment change gates integrated with PAY-* status from disbursement UI.
Build admin REV- review console* with eligibility cross-check and evidence viewer.
Implement claimant-safe audit trail on status portal; full trail in admin.
Connect failed payment returns to streamlined bank correction (not full REV-* unless flagged).

FAQ

Can claimants cancel a submitted claim instead of amending?

Separate withdrawal flow if order allows · Often equivalent to not claiming · May differ from opt-out · Do not conflate with AMD-*.

Typo in email—lost access to portal?

Admin identity verification · Call center or email OTP to new address after REV-* · Not instant self-service email change if account takeover risk.

Amendment after tax form submitted?

Name/SSN change may invalidate TAX-* · Block PAY-* · Require new W-9/W-8 · Show clear regen flow.

Multiple AMD-* on same day?

Allowed if different fields · Same field rate-limited · Admin queue merges duplicate REV-* when possible.

Court-ordered notice of material amendments?

Rare · Admin flags AMD-* requiring notice batch · Out of claimant UI scope but REV-* shows “Notice pending” status.

Next steps

Design breach settlement claim status portal and claimant dashboard UI in Figma — Entry point for corrections
Design breach settlement notice and victim compensation claims UI in Figma — Original CLM-* field validation
Design breach settlement payment disbursement and payout tracking UI in Figma — Bank correction after return
Design breach settlement claims dispute and appeals UI in Figma — When correction denied
Design audit log and security activity UI in Figma — Shared audit patterns

Designing breach settlement claim amendment and correction UI in Figma: editable fields, audit trail, and post-approval change gates