Settlement Contested Claim Escrow UI

Quick answer

Contested claim escrow UI ring-fences dollars while tier fights, fraud holds, or subclass objections stay open—not a generic “pending” badge on the status portal. Design RES-CLM- per-claim holdbacks*, DIS-ESC- aggregate dispute pools* for class-wide objections, and REL- release workflows* that require counsel approval, court order, or appeal exhaustion before funds move to disbursement. Every RES-CLM-* must tie to LINK-OBJ-, LINK-APP-, or FRAUD-HOLD-* reason codes and respect STY- appeal stays* and provisional payment caps. Without this UI, administrators pay disputed claims and claw back later, or leave escrow opaque until final accounting fails court review. Start from the Figma guides hub and pair with disputes and appeals, fraud detection, distribution schedule, and fund reconciliation.

Who this is for

Product designers building reserve accounting and dispute modules inside breach settlement administration platforms.
Settlement administrators who must segregate contested dollars from escrow interest allocation and tranche planning.
Class counsel defining when RES-CLM-* converts to paid DISB-* versus returned to the common fund.

Contested reserve lifecycle overview

DisputeReserveProgram — DIS-ESC-992 · pool: $4.2M · Status: 318 RES-CLM-* active
├── Triggers:
│   ├── Open [DIS-APPEAL-*](/designing-breach-settlement-claims-dispute-and-appeals-ui-in-figma/) on CLM-*
│   ├── Tier reclassification pending · FIN-AWD-* not locked
│   ├── FRAUD-HOLD-* or duplicate merge in progress
│   ├── [Lien dispute](/designing-breach-settlement-lien-and-third-party-creditor-offset-ui-in-figma/) blocks net release
│   ├── Class [objection](/designing-breach-settlement-fairness-hearing-and-class-objection-ui-in-figma/) affects subclass bucket
│   └── Court order requires RES-CLM-* until ruling
├── ID namespace:
│   ├── RES-CLM-* (claim-level holdback)
│   ├── DIS-ESC-* (pooled dispute escrow sub-account)
│   ├── REL-* (release authorization record)
│   ├── OBJ-* (objection link) · APP-* (appeal link)
│   ├── AMT-RES-* · AMT-REL-* · BAL-RES-* (running reserve balance)
│   └── LOG-RES-* (immutable reserve audit trail)
├── Reserve rules (plan-driven):
│   ├── Full hold: 100% of FIN-AWD-* or EST-AWD-*
│   ├── Partial hold: net after [PROV-DISB-*](/designing-breach-settlement-provisional-payment-and-interim-distribution-ui-in-figma/) only
│   ├── Interest accrual: to common fund vs claimant-specific · plan flag
│   ├── Auto-release timer: never default without counsel flag
│   └── Cross-claim offset: blocked unless plan permits
├── Workflow:
│   ├── Flag CLM-* contested · compute AMT-RES-*
│   ├── Move cash to DIS-ESC-* ledger · update [reconciliation](/designing-breach-settlement-fund-reconciliation-and-bank-matching-ui-in-figma/)
│   ├── Block TRN-DISB-* queue inclusion
│   ├── Resolve dispute · create REL-* with approvers
│   ├── Release to disbursement or reallocate to subclass pool
│   └── Archive LOG-RES-* for [external auditor](/designing-breach-settlement-external-auditor-access-and-read-only-review-portal-ui-in-figma/)
└── Outcomes:
    ├── Uncontested claims pay on schedule
    ├── Contested dollars visible on court monitor dashboard
    └── No silent reclassification of RES-* as “paid”

RES-CLM-* state	Disbursement queue	Claimant portal copy
Active hold	Excluded	“Award reserved pending review”
Partial release	Net balance only	Itemized REL-* line
Full release	Eligible TRN-DISB-*	Standard paid path
Reallocated	N/A · subclass	Notice + FAQ link
STY- frozen*	Block REL-*	Appeal stay banner

Verdict: RES-CLM- must never share a bank sub-account with unrestricted WAVE- cash without ledger tagging— auditors treat commingling as a material weakness.**

RES-CLM-* creation and AMT-RES-* calculation UI

ClaimReserve — RES-CLM-992-8841 · CLM-4412 · AMT-RES-*: $3,200 · Status: Active
├── Amount basis:
│   ├── FIN-AWD-* when finalized but disputed
│   ├── EST-AWD-* when dispute precedes final tier
│   ├── NET-AWD-* after lien preview · hold gross if OFF-* contested
│   ├── Exclude already paid PROV-DISB-* from hold if plan allows partial pay
│   └── Round per currency · no float drift vs escrow
├── Reason codes (required):
│   ├── OBJ-TIER-* · OBJ-DOC-* · OBJ-IDV-*
│   ├── FRAUD-REV-* · DUP-MERGE-*
│   ├── LIEN-DIS-* · SUBCLASS-*
│   └── CRT-ORD-* (court-ordered hold)
├── Linked records:
│   ├── LINK-CLM-* · LINK-DIS-APPEAL-* · LINK-FRAUD-*
│   ├── LINK-LIEN-* · LINK-STY-* when appeal stay partial
│   └── Attachments from [document upload](/designing-breach-settlement-claim-document-upload-and-evidence-management-ui-in-figma/)
├── Admin actions:
│   ├── Increase/decrease AMT-RES-* · LOG-RES-* + counsel note
│   ├── Split RES-* across subclass buckets · SUB-ALLOC-*
│   ├── Convert to DIS-ESC-* pool contribution (class-wide)
│   └── Cannot delete RES-* · only release or reclassify
└── Claimant view:
    ├── Plain language reason · not internal OBJ-* codes only
    ├── Expected timeline · link [status portal](/designing-breach-settlement-claim-status-portal-and-claimant-dashboard-ui-in-figma/)
    └── [Call center script](/designing-breach-call-center-and-agent-script-ui-in-figma/) snippet ID for RES-* FAQs

Use badges for hold severity, tables for multi-claim DIS-ESC-* rollups, and modals for AMT-RES-* adjustments with mandatory justification.

DIS-ESC-* pool management and subclass segregation UI

DisputePool — DIS-ESC-992-SUB-A · balance: $890,400 · claims: 412 · Status: Open
├── Pool types:
│   ├── Class-wide objection reserve (fairness hearing)
│   ├── Subclass SUB-* buckets · pro rata fights
│   ├── Fraud investigation pool · FRAUD-ESC-*
│   ├── Lien litigation pool · LIEN-ESC-*
│   └── Appeal stay holdback · STY-ESC-* pair with [appeal UI](/designing-breach-settlement-appeal-and-mandamus-review-ui-in-figma/)
├── Inflows:
│   ├── New RES-CLM-* transfers from master escrow
│   ├── Interest allocation per [ALLOC-* rules](/designing-breach-settlement-claims-fund-escrow-and-interest-allocation-ui-in-figma/)
│   ├── Clawback recoveries routed to pool
│   └── Cy pres or residual redirect if plan allows
├── Outflows (blocked until REL-*):
│   ├── Release to claimant DISB-*
│   ├── Reallocation to uncontested subclass
│   ├── Fee holdback for [administrator expense](/designing-breach-settlement-claims-administrator-fee-and-expense-recovery-ui-in-figma/)
│   └── Return to common fund after objection denied
├── Reporting:
│   ├── RPT-RES-* monthly · aging buckets 30/60/90+
│   ├── Court monitor view · separate from paid WAVE-* totals
│   └── [QA sampling](/designing-breach-settlement-post-disbursement-qa-and-audit-sampling-ui-in-figma/) on REL-* approvals
└── Integration:
    ├── [Distribution schedule](/designing-breach-settlement-distribution-schedule-and-tranche-disbursement-planning-ui-in-figma/) shows reduced available tranche
    └── [Tax reporting](/designing-breach-settlement-tax-reporting-and-1099-ui-in-figma/) waits for release event when required

DIS-ESC-* dashboards should mirror SLA-style trust metrics for reserve aging—not marketing charts that hide stuck RES-CLM-* counts.

REL-* release authorization and dispute resolution UI

ReleaseRecord — REL-992-4412 · RES-CLM-8841 · AMT-REL-*: $3,200 · Status: Pending counsel
├── Release paths:
│   ├── Dispute withdrawn · auto-suggest REL-* · still needs approver
│   ├── Appeal exhausted · STY-* cleared · link APP-OUT-*
│   ├── Court order REL-CRT-* · upload PDF · immutable hash
│   ├── Fraud cleared · FRAUD-HOLD-* removed · dual approval
│   ├── Partial release after tier split · FIN-AWD-* updated
│   └── Reallocate to pool · no claimant DISB-* · SUB-REALLOC-*
├── Approval chain:
│   ├── Administrator ops · threshold T1
│   ├── [Counsel review](/designing-breach-settlement-counsel-review-and-payout-approval-ui-in-figma/) · threshold T2
│   ├── Court monitor notify-only vs co-sign · plan driven
│   └── Block if [deficiency](/designing-breach-settlement-deficiency-notice-and-claim-cure-ui-in-figma/) reopened
├── Execution:
│   ├── Debit DIS-ESC-* · credit disbursement staging
│   ├── Enqueue TRN-DISB-* · respect [lien offset](/designing-breach-settlement-lien-and-third-party-creditor-offset-ui-in-figma/)
│   ├── Update portal · remove reserve banner
│   └── LOG-RES-* closure reason · link REL-*
└── Failure modes:
    ├── REL-* approved but STY-* still active · hard block
    ├── Double REL-* same RES-* · idempotency key
    └── Amount mismatch vs FIN-AWD-* · force REC-* path

Pair REL-* with session re-auth for high-dollar releases and audit log entries for every approver action.

Comparison: per-claim RES-CLM-* vs pooled DIS-ESC-*

Dimension	RES-CLM-* holdback	DIS-ESC-* pool
Granularity	Single CLM-*	Many claims / subclass
Best for	Appeal, fraud, tier fight	Class objection, fairness stay
Claimant messaging	Specific reserve amount	Often “class-wide delay”
Interest treatment	Claimant-specific possible	Usually common fund
Release unit	REL-* per claim	Bulk REL-BATCH-*
Reconciliation	Simple tie to CLM-*	Requires pool ledger

Common mistakes

Marking claim “paid” while RES-CLM- active*— portal shows green check; REL-* never happened.
No reason code on RES-*— support and auditors cannot explain hold duration.
Releasing RES- during STY- without scope check**— partial stay allows some subclasses only.
Commingling DIS-ESC- with operating cash*— fund reconciliation breaks.
PROV-DISB- after full RES-**— plan may forbid advances on contested awards.

Recommended workflow

Define reserve triggers and pool structure in settlement plan · map OBJ-* to RES-* vs DIS-ESC-*.
Auto-create RES-CLM- on dispute flags* · block disbursement queues · notify claimant with FAQ.
Age RES- in RPT-RES-** · escalate 90+ day holds to counsel queue.
Process REL- with approval chain* · execute TRN-DISB-* or reallocate · update reconciliation.
Close RES- in final accounting* with zero unexplained DIS-ESC-* balance.

FAQ

Can claimants earn interest while RES-CLM-* is active?

Plan-specific— UI must show accrual rules and whether interest releases with REL-* or stays in common fund.

What if dispute reduces FIN-AWD-* below PROV-DISB-*?

Route to clawback— RES-* does not erase over-advance obligation.

Partial release during active appeal?

Only if STY-SCOPE- permits*— default block REL-* until appeal exhausted.

How do reserves interact with UCF escheatment?

Unreleased RES- is not UCF*— escheat workflows apply after REL-* failed delivery, not during dispute hold.

External auditor view of RES-*?

Read-only DIS-ESC- ledger* via auditor portal— no REL-* actions.

Deceased claimant with open RES-*?

Freeze REL-* until heir designation completes.

Next steps

Design breach settlement claims dispute and appeals UI in Figma — triggers RES-CLM-*
Design breach settlement payment disbursement and payout tracking UI in Figma — post-REL-* execution
Design breach settlement fund reconciliation and bank matching UI in Figma — DIS-ESC-* ledger
Design breach settlement provisional payment and interim distribution UI in Figma — partial pay vs full hold
Design breach settlement claim status portal and claimant dashboard UI in Figma — reserve messaging

Designing breach settlement contested claim escrow and dispute reserve UI in Figma: RES-CLM-* holdbacks, DIS-ESC-* pools, and REL-* release workflows