Settlement Calendar

Overview

A settlement calendar defines the business days, holidays, cutoffs, processing windows, and value dates used to determine when obligations can settle. It may differ by country, currency, institution, market, and payment rail. Cross-border and multicurrency payments may depend on several calendars at once, while digital-asset networks may operate continuously even when banks, custodians, or treasury teams do not.

A system may roll the date forward, backward, or reject it according to the governing agreement. For Settlement Calendar, operational review should test incorrect obligations, liquidity shortfalls, participant default, wrong settlement assets, premature finality, and unreconciled movements. The implementation should identify the obligation, participants, settlement asset, accounts or addresses, value date, liquidity source, posting sequence, and evidence of finality.

Settlement Calendar should remain distinct from Settlement and Settlement Asset, because each can represent a different stage, record, control, or financial outcome.

Important failure modes include insufficient liquidity, duplicate instructions, wrong settlement assets, delayed delivery, participant default, unmatched evidence, and premature claims of finality. For Settlement Calendar, this point supports the definition’s focus on settlement calendar defines the business days, holidays, cutoffs, processing windows, and value dates used to determine when obligations.

The calendar should be versioned and applied with an explicit timezone. Scheduling, pricing, interest, statements, and reconciliation should all use the same approved calendar logic and preserve the originally requested date alongside the actual settlement date. Controls should validate instructions, funding, destination, currency or asset, cutoffs, and participant positions before treating a settlement step as complete. For Settlement Calendar, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Settlement Calendar should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome.