End-of-Day (EOD) Batch Processing Failure

Root Cause & Remediation

Insufficient batch processing window due to data volume growth, failed dependency job (e.g. market data feed, FX rate upload), database deadlock during ledger posting, or a code regression in the batch job introduced by a recent release.

Remediation steps

1. 1Identify the failed step in the batch orchestration tool (Control-M, Autosys, or equivalent) and assess rerun feasibility.
2. 2Notify the Head of Operations and CFO of the delay and estimated impact on opening balance availability.
3. 3Implement manual workarounds for time-critical processes (e.g. manual position reconciliation for regulatory deadlines).
4. 4If rerun will exceed the business-open deadline, activate the batch failure contingency plan (may involve partial balance publication).
5. 5Post-incident: implement batch job SLA monitoring with automated alerts when jobs exceed 80% of their allocated window.

DORA Risk Matrix

Likelihood

Medium

Blast radius

Affects all retail and corporate clients whose balances or statements rely on the overnight posting run. Regulatory position reports to the NCA may also be delayed.

CIF impact

Account balance display, daily position reporting, and settlement obligations are the primary CIF-adjacent functions. Direct economic loss accrues if settlement obligations are missed.

Analyst notes

Batch failures are a classic legacy banking incident. They routinely breach the CIF downtime threshold when the failure is not resolved before business open (typically a 6-8h window). Missed settlement obligations can rapidly generate direct economic losses exceeding the €100,000 threshold under Art. 9(6) of Reg. 2024/1772.