figma guide

Designing breach settlement claims administrator fee and expense recovery UI in Figma: ADM-FEE-* schedules, EXP-* pass-through costs, and INV-* invoice approval

Design breach settlement claims administrator fee and expense recovery UI in Figma with ADM-FEE-* schedules, EXP-* pass-through costs, INV-* invoice approval, and ALLOC-* escrow recovery gates.

Published
Updated
Sep 14, 2026
Read time
8 min
Level
Intermediate

Quick answer

Administrator fee UI tracks pass-through settlement costs—not a hidden line item buried in counsel’s fee request. Design ADM-FEE- schedules* tied to court-approved compensation orders, EXP- pass-through costs* for notice vendors, call centers, IDV, and payment rails, and INV- invoice approval* workflows that debit escrow through ALLOC-* waterfalls before claim awards. Every ADM-FEE-* payment must reconcile to LOG-ADM-* audit entries and respect CAP-ADM-* fee caps from the settlement agreement. Without this UI, notice costs get double-billed, fee caps are exceeded silently, and final accounting cannot separate administrator compensation from class recovery. Start from the Figma guides hub and pair with attorney fee allocation, fund reconciliation, supplemental notice, and court monitor reporting.


Who this is for

  • Product designers building finance and vendor modules inside breach settlement administration platforms.
  • Claims administrators and settlement counsel who need transparent ADM-FEE-* tracking—not ad hoc expense spreadsheets.
  • Court monitors and fee objectors reviewing EXP-* categories before approving administrator compensation in fairness hearings.

Administrator fee lifecycle overview

AdminFeeProgram — ADM-SET992 · cap: $2,850,000 · Status: Accruing
├── Triggers:
│   ├── Court-approved administrator compensation order
│   ├── Settlement agreement fee schedule (hourly · percentage · hybrid)
│   ├── Pass-through vendor invoices (notice · payments · IDV · call center)
│   ├── Milestone fees (program launch · first disbursement · wind-down)
│   └── Successor administrator transition true-up
├── ID namespace:
│   ├── ADM-FEE-* (fee schedule line) · EXP-* (expense category)
│   ├── INV-* (vendor invoice) · APP-ADM-* (approval record)
│   ├── CAP-ADM-* (fee cap tracker) · LOG-ADM-* (audit log)
│   ├── LINK-ESC · LINK-DISB · LINK-NOT · LINK-ALLOC
│   ├── VAR-ADM-* (variance vs budget) · OBJ-ADM-* (objection hold)
│   └── RPT-ADM-* (court reporting package)
├── Expense categories:
│   ├── Notice: NOT-* vendor · postal · email · [supplemental campaigns](/designing-breach-settlement-supplemental-notice-and-renotice-campaign-ui-in-figma/)
│   ├── Claims processing: intake · [document upload](/designing-breach-settlement-claim-document-upload-and-evidence-management-ui-in-figma/) · [fraud detection](/designing-breach-settlement-duplicate-claim-detection-and-fraud-prevention-ui-in-figma/)
│   ├── Disbursement: payment rails · [returned payment](/designing-breach-settlement-returned-payment-and-reissue-ui-in-figma/) · bank fees
│   ├── Support: [call center](/designing-breach-call-center-and-agent-script-ui-in-figma/) · [status portal](/designing-breach-settlement-claim-status-portal-and-claimant-dashboard-ui-in-figma/)
│   ├── Compliance: [QA sampling](/designing-breach-settlement-post-disbursement-qa-and-audit-sampling-ui-in-figma/) · [external auditor](/designing-breach-settlement-external-auditor-access-and-read-only-review-portal-ui-in-figma/) · [tax reporting](/designing-breach-settlement-tax-reporting-and-1099-ui-in-figma/)
│   └── Technology: platform hosting · security · data retention
├── Workflow:
│   ├── Load ADM-FEE-* schedule from settlement agreement · set CAP-ADM-*
│   ├── Vendor submits INV-* · categorize EXP-* · attach supporting docs
│   ├── Counsel + administrator dual APP-ADM-* approval
│   ├── Check CAP-ADM-* headroom · OBJ-ADM-* hold if near cap
│   ├── Post to escrow BAL-ADM-* via [ALLOC-* priority](/designing-breach-settlement-claims-fund-escrow-and-interest-allocation-ui-in-figma/)
│   ├── Execute DISB-ADM-* wire · LOG-ADM-* entry
│   ├── Monthly RPT-ADM-* to [court monitor](/designing-breach-settlement-court-monitor-and-special-master-reporting-ui-in-figma/)
│   └── True-up at [final accounting](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/)
└── Outcomes:
    ├── Every dollar traceable: INV-* → EXP-* → DISB-ADM-*
    ├── Fee cap never exceeded without court order
    └── Objectors can audit pass-through vs profit margin
ADM-FEE-* stateCAP-ADM-* remainingDISB-ADM-* allowed
Budget open> 15% headroomStandard APP-ADM-*
Near cap< 15% headroomManager + counsel approval
At cap$0Court order required
OBJ-ADM- hold*FrozenNone until objection resolved
Wind-downFinal true-up onlyMilestone closeout fees
ClosedArchivedNone

Verdict: Pass-through EXP- must never flow through counsel FEE- buckets—separate ADM-FEE-* ledger or fee objections will conflate administrator costs with class counsel compensation.**


ADM-FEE-* schedule and CAP-ADM-* cap tracking UI

FeeSchedule — ADM-FEE-992-001 · type: hybrid · Status: Active
├── Schedule components:
│   ├── Base fee: fixed amount at program launch
│   ├── Variable: per-claim processed · per-DISB-* batch · per-NOT-* wave
│   ├── Hourly: staff time with rate card · task codes
│   ├── Percentage: rare · capped percentage of gross settlement
│   └── Successor admin: prorated handoff fee per transition order
├── CAP-ADM-* tracker:
│   ├── Court-ordered maximum · settlement agreement appendix
│   ├── Running total: approved INV-* + accrued but unbilled
│   ├── Reserve for estimated wind-down · QA · final accounting
│   ├── Alert at 85% · 95% · 100% thresholds
│   └── Override requires court order upload · LOG-ADM-* reason
├── Budget vs actual:
│   ├── EXP-* category budget from settlement budget exhibit
│   ├── VAR-ADM-* variance per category · month-over-month trend
│   ├── Forecast: projected cap breach date at current burn
│   └── Simulation: delay notice wave · reduce call center hours
└── Claimant visibility:
    ├── Status portal: aggregate "administration costs" line—no vendor names
    └── [Notice FAQ](/designing-breach-faq-and-notice-landing-page-ui-in-figma/) link to fee summary exhibit

Use tables for schedule line items, progress indicators for CAP-ADM-* burn-down, and badges for variance status.


INV-* invoice intake and EXP-* categorization UI

VendorInvoice — INV-992-8841 · vendor: NoticeCo · amount: $142,800 · Status: Pending approval
├── Intake fields:
│   ├── invoice_id (INV-*) · vendor_id · purchase order if required
│   ├── EXP-* category · settlement phase · related NOT-* or DISB-* batch
│   ├── Line items: quantity · unit rate · tax · pass-through flag
│   ├── Attachments: vendor PDF · delivery proof · contract SOW
│   ├── Duplicate INV-* detection · same vendor + amount + date
│   └── LINK to [supplemental notice](/designing-breach-settlement-supplemental-notice-and-renotice-campaign-ui-in-figma/) DEL-* proof if notice cost
├── Validation rules:
│   ├── Rate within contracted rate card · flag overage
│   ├── EXP-* must map to approved budget category
│   ├── Block if CAP-ADM-* insufficient without court order
│   ├── Require counsel APP-ADM-* for EXP-* > threshold
│   └── Split INV-* across multiple settlements if shared vendor
├── Approval chain:
│   ├── Administrator finance review · coding confirmation
│   ├── Settlement counsel APP-ADM-* · objector comment period if ordered
│   ├── Auto-route OBJ-ADM-* if class member filed fee objection
│   └── Dual sign-off before DISB-ADM-* generation
└── Rejection path:
    ├── Return to vendor with reason code · revision INV-* version
    ├── Dispute queue · LOG-ADM-* correspondence
    └── Escalate to [court monitor](/designing-breach-settlement-court-monitor-and-special-master-reporting-ui-in-figma/) if stale > 30 days

Pair with file upload UI for invoice attachments and forms for EXP-* categorization dropdowns.


DISB-ADM-* payment and escrow integration UI

AdminDisbursement — DISB-ADM-992-044 · INV-992-8841 · Status: Posted
├── Pre-flight checks:
│   ├── CAP-ADM-* headroom after this DISB-ADM-*
│   ├── BAL-ADM-* or BAL-FEE-* bucket per [ALLOC-* order](/designing-breach-settlement-claims-fund-escrow-and-interest-allocation-ui-in-figma/)
│   ├── STY-* block from [appeal UI](/designing-breach-settlement-appeal-and-mandamus-review-ui-in-figma/)
│   ├── RES-* hold from [QA finding](/designing-breach-settlement-post-disbursement-qa-and-audit-sampling-ui-in-figma/)
│   └── REC-ESC-* reconciliation current
├── Execution:
│   ├── Generate wire to vendor or administrator entity
│   ├── Mark INV-* paid · close APP-ADM-* record
│   ├── LOG-ADM-* immutable entry · tie to bank confirmation
│   ├── Feed [fund reconciliation](/designing-breach-settlement-fund-reconciliation-and-bank-matching-ui-in-figma/) BANK-*
│   └── Update RPT-ADM-* monthly rollup
├── 1099 handling:
│   ├── Administrator entity vs pass-through vendor
│   ├── Link [tax reporting UI](/designing-breach-settlement-tax-reporting-and-1099-ui-in-figma/) for vendor payments
│   └── Separate from claimant DISB-CLM-* tax logic
└── Objector visibility:
    ├── Redacted RPT-ADM-* export for [fairness hearing](/designing-breach-settlement-fairness-hearing-and-class-objection-ui-in-figma/)
    └── SCRUB-ADM-* remove vendor account numbers on public exhibits

Use modals for DISB-ADM-* confirmation when CAP-ADM-* is below 10% headroom.


OBJ-ADM-* fee objections and court review UI

FeeObjection — OBJ-ADM-992-003 · filer: class member · Status: Under review
├── Objection types:
│   ├── Excessive administrator compensation vs lodestar
│   ├── Pass-through billed without proof · duplicate INV-*
│   ├── Expense miscoded · should be defendant cost not class fund
│   ├── Cap breach · payment without court order
│   └── Successor admin transition fee dispute
├── Review workflow:
│   ├── Freeze affected DISB-ADM-* if OBJ-ADM-* targets specific INV-*
│   ├── Administrator response · attach supporting LOG-ADM-*
│   ├── Counsel reply · proposed reduction or affirmation
│   ├── [Court monitor](/designing-breach-settlement-court-monitor-and-special-master-reporting-ui-in-figma/) recommendation if special master appointed
│   └── Court order resolution · adjust CAP-ADM-* or reverse DISB-ADM-*
├── Claimant portal:
│   ├── Read-only fee summary exhibit · no live vendor invoices
│   └── Objection filing form if court-ordered comment period open
└── Integration:
    ├── Feed [final accounting](/designing-breach-settlement-final-accounting-and-court-closure-ui-in-figma/) fee exhibit
    └── Link [attorney fee OBJ-FEE-*](/designing-breach-settlement-attorney-fee-allocation-and-incentive-award-ui-in-figma/)— separate queues

Comparison: hourly vs per-claim vs hybrid administrator fees

DimensionHourly ADM-FEE-*Per-claim / per-DISB-*Hybrid (common)
Predictability for objectorsLow · requires timesheet auditHigh · formula-drivenMedium
Cap enforcementHard without task-code budgetsEasier · linear with volumeCAP-ADM-* on total
Vendor pass-throughSeparate EXP-* alwaysSeparate EXP-* alwaysBase + variable + EXP-*
Wind-down costOften underestimatedMay overpay if claims spike earlyMilestone + hourly closeout
Court preferenceLarge complex programsHigh-volume low-touchMost breach settlements
Best forMDL with shifting scopeStandard data-breach classEnterprise settlement platforms

Common mistakes

  1. Notice vendor INV- coded as counsel FEE-**— objectors cannot audit pass-through; court rejects fee petition.
  2. DISB-ADM- debits ESC-CLM- instead of BAL-ADM-***— claims pool depleted for admin costs; waterfall violation.
  3. CAP-ADM- checked only at invoice approval, not at accrual*— unbilled hours breach cap before wind-down.
  4. Duplicate INV- paid because vendor resubmitted after rejection*— duplicate detection must key on vendor + PO + amount.
  5. 1099 issued to administrator for pass-through vendor payment— tax reporting error; vendor gets 1099 directly.

  1. Load ADM-FEE- schedule and CAP-ADM-** from settlement agreement · configure EXP-* budget categories.
  2. Route vendor INV- through EXP- coding** · dual APP-ADM-* approval · check cap headroom.
  3. Post DISB-ADM- via ALLOC- priority** · reconcile to fund reconciliation monthly.
  4. Publish RPT-ADM- to court monitor* · handle OBJ-ADM-* holds promptly.
  5. True-up at final accounting · archive LOG-ADM-* · close CAP-ADM-*.

FAQ

Are administrator fees separate from class counsel fees?

Yes—always separate ADM-FEE- and FEE- ledgers.** Counsel fees use attorney fee allocation UI; administrator fees use this module.

Who approves pass-through notice costs?

Administrator codes INV-* · settlement counsel APP-ADM-* · large NOT-* waves may need pre-approval in settlement budget exhibit.

Can administrator fees continue during appeal stay?

Usually yes for ongoing admin— but DISB-ADM-* may need court order if STY-* freezes all fund outflows; check appeal UI STY-* scope.

Successor administrator mid-program?

Prorate ADM-FEE-* · transition INV-* for data migration · handoff milestone · new CAP-ADM-* sub-schedule per court order.

Fee cap exceeded— what happens?

Block new DISB-ADM-* · file cap increase motion · LOG-ADM-* freeze until court order uploaded.

Claimants see individual vendor invoices?

No— aggregate administration cost on status portal · detailed INV-* redacted in public exhibits · full detail in external auditor portal.


Next steps

Share on X

§ Keep reading

Related guides.