Day & period close¶
A bank runs on a logical business date, not the wall clock. End-of-day closes the current day and rolls to the next; start-of-day opens it. This page covers both, plus reporting and regulatory returns.
Where: the Reporting & Close group.
End of day¶
Reporting & Close → End of Day is a live monitor. The left pane shows the current run as a vertical list of steps, each with a status (pending, running, completed, skipped, failed), a processed count and any inline error, plus a progress bar and the current and next business dates. The right pane is the run history.
- Run EOD (
eod:run) accrues interest, capitalises at month-end, then rolls the date. It confirms first, then polls while running. - Resume: a run that has been stuck for over 30 minutes is flagged; a watchdog resumes it, and Run EOD resumes idempotently from the first unfinished step. While a close runs, new input is refused (the console shows a Locked state).
- Automatic close: a per-institution schedule (a time and zone) can close the day automatically; it is seeded on, at 20:00.
- Catch up advances the business day through repeated end-of-day/start-of-day cycles up to a
target date, used to clear a backlog after downtime (needs both
eod:runandsod:run).
End-of-day is an ordered, idempotent, resumable pipeline. Among its steps: daily interest and penalty accrual and IFRS-9 provisioning; hold expiry, dormancy and commission sweeps; FX revaluation and AML monitoring; payment dispatch and clearing settlement; card and prepaid processing; treasury accrual; dispute SLA sweeps; notification dispatch; force-closing any open till; and, critically, two gates that can block the roll:
- Branch cash reconciliation: node cash against the GL. Any break blocks the close.
- Trial-balance check: the books must balance before the day can roll.
Month-end adds interest capitalisation, fee application and GL period close. A failed run is not auto-retried. A failed gate needs an operator to fix the cause, then Resume.
Start of day¶
Reporting & Close → Start of Day opens the new business day. It is a short job: resolve the business day (respecting the calendar: no activation on a non-processing day), run due standing orders and scheduled bulk payments, open the day, and fulfil any queued account and loan intents.
Reporting & regulatory returns¶
The Reporting & Close group also holds the financial and regulatory outputs (all read with
reporting:read):
- Reporting: trial balance, profit & loss, balance sheet and deposits, over a shared period / as-of picker, with drill-down when something is out of balance.
- Prudential: regulatory and prudential return exports.
- Library: run any report across domains and download it (CSV, XLSX, PDF, DOCX).
- Runs: an immutable register of every report that was run, with checksums.
- Schedules: recurring report generation with retained artifacts.
Who can view close
Viewing end-of-day needs reporting:read. Front-counter roles such as Teller deliberately do
not hold it. Running end-of-day needs eod:run.
Key terms¶
- Business date
- The logical accounting date the institution is operating on. Rolled by the date roll, which skips weekends and holidays per the calendar.
- Gate
- A check that must pass before the day can roll: branch cash reconciliation and the trial balance.
- Catch-up
- Advancing several business days in sequence to recover after downtime.
Roles that do this work¶
| Task | Permission | Typical role |
|---|---|---|
| View close | reporting:read |
Operations Officer, Controller |
| Run end-of-day | eod:run |
Financial Controller, System Administrator |
| Run start-of-day | sod:run |
Operations Officer |
| Read reports | reporting:read |
Finance Officer, Auditor |