When “Business Days” Keep People Waiting Longer for Their Money

What this evaluation covers

These canonical Entity references identify the products, systems, organizations, units, and other durable subjects covered by this Evaluation. Inclusion does not by itself establish responsibility or credit.

Public-eligible organizations, products, services, departments, and workflows in this Evaluation's scope. Inclusion identifies subject and provider context only; it does not by itself establish responsibility, internal ownership, fault, motive, or prevalence.

Subject entities

First Citizens Bank-Integrated Zelle P2P Transfer Flow— Service
First Citizens Bank— Banking organization

Evaluation scope

Business-day gating in consumer funds-availability processes. Separate from the number of processing cycles required and from attribution to any particular institution or rail.

Question being evaluated

When financial availability depends on business-day processing, what constraint prevents progress during excluded calendar periods, who controls it, what burden results, and what mitigation is available?

Current findings

What works well or deserves recognition

Recorded first-party timing material provides business-day timing disclosure for at least the documented mechanism. That is limited positive evidence of stated timing, not evidence that the calendar-time consequence, available control, mitigation, or actual delivery is adequately communicated in every context.

Difficulties and opportunities to improve

The documented occurrence shows that excluding weekends or holidays from processing can enlarge the real calendar interval during which a person lacks usable funds even though financial obligations and human needs continue. Where calendar-time effects, status, control, and mitigation are not sufficiently visible, the user bears added liquidity, planning, and coordination burden.

Mixed or conditional findings

Legitimate technical, legal, fraud, settlement, staffing, or operational constraints may exist. Necessity, proportionality, responsibility, disclosure, control, and mitigation remain evidence questions rather than presumed failures.

Evidence coverage and limits

Current public evidence includes one delayed-transfer Incident plus first-party timing material relevant to the business-day mechanism. The evidence does not establish prevalence, a shared backend cause across institutions, or the necessity of every excluded-calendar-period delay.

How the evidence connects

One public Incident contributes evidence to this mechanism Evaluation. Evidence relationships are not votes and do not establish prevalence. Additional incidents, official constraint evidence, and counterexamples can strengthen, narrow, challenge, or contextualize the current Evaluation.

Supporting incidents

• UXR-2026-0809-0001: Immediate Debit, Delayed Credit: Consumer Funds Availability Asymmetry

Related Evaluations

• UXR-EVAL-0002: When Money Leaves Before the Recipient Can Use It

Agency dimensions

Acceptance / benchmark test

Measure institutional processing days and actual elapsed calendar time, identify who controls the gating rule and why, and test whether calendar-time effects, status, preserved control, provisional availability, cancellation, compensation, or other proportionate mitigation are meaningfully available.

Next observation or verification

Identify the actual constraint and controlling actor in additional mechanisms; test whether people receive calendar-time expectations before commitment; and collect counterexamples showing better visibility, preserved control, faster availability, or proportionate mitigation.