Financial systems take a holiday
Financial infrastructure turns out to be deeply constrained by holidays, time zones and legacy processes, even as other computer systems run 24/7. Commenters share war stories from banking and trading, explaining why settlement calendars, unpredictable public holidays, compliance checks and rare edge cases still require human oversight and batch windows, limiting instant payments and round-the-clock markets. Some point to SEPA instant transfers, crypto, and emerging 24/7 exchanges as evidence that continuous operation is possible, but note that regulatory, cultural and operational complexity—rather than pure technology—largely determines how fast finance can change.
Holiday-driven downtime & ops risk
- Holidays coincide with peak consumer activity but also settlement pauses, creating tension.
- Unplanned or short-notice holidays (presidential funerals, monarch deaths, typhoons, surprise “victory” days) are seen as worst-case for operations teams.
- Financial systems’ overnight batch cycles are described as fragile; failures or delays can cause cascading issues.
Why finance isn’t fully 24/7
- Several argue financial “plumbing” is far more constrained than email: settlement, risk controls, AML/KYC, and regulatory oversight often need humans.
- Others counter that most transactions are already straight‑through processed; only edge cases need humans, so more 24/7 service should be possible.
- Examples exist of weekend/instant payments and 24/7 trading (crypto, some banks, instant stock exchanges), suggesting it’s mostly inertia, cost, and low perceived demand.
Payment systems: regional contrasts
- EU’s SEPA Instant is highlighted as 24/7, near-instant, and widely mandated.
- In the US, instant transfers exist via systems like Zelle and newer FedNow, but coverage, limits, and usability differ from SEPA.
- Some note card networks, ATMs, and neobanks already operate continuously.
Calendars, holidays, and technical complexity
- “Business days” are considered a notoriously hard requirement: trading vs settlement calendars, per‑counterparty calendars, national vs supranational holidays (e.g., TARGET2), and city‑ or company‑specific days.
- Edge cases include saints’ days in Italy, school-only holidays, surprise mourning days, and Japan’s emperor-era date changes.
- Many teams resolve this with central calendar tables and manual yearly updates; handling last‑minute holidays remains hard.
- Contest and bus‑schedule anecdotes show how holiday rules, “observed” days, and religious calendars (Easter, Ramadan/Eid) quickly defeat naive algorithms.
Market structure & trading hours debates
- Some want stock markets open 24/7 to match other digital services and help people who work standard hours.
- Others defend limited hours to concentrate liquidity, protect smaller participants who can’t staff 24/7, and avoid more complexity.
- Alternatives proposed include shorter hours, daily auctions, or even extreme reductions; these are criticized as naïve by practitioners.
Reliability, legacy systems, and “nines”
- Discussion on “five nines” uptime: some think it’s already very high; others note large platforms may aim higher in practice.
- Legacy tech (EBCDIC, old mainframes) and compliance-heavy workflows are expected to persist for decades.