Liquidity signals should arrive before settlement incidents

Volume is not capacity

A participant can be processing successfully while its settlement position is deteriorating. A dashboard that celebrates throughput without showing liquidity exposure can look healthy immediately before an operational constraint.

The control plane receives participant settlement-balance snapshots and evaluates them against configured thresholds. The goal is not a prettier balance screen. It is enough lead time to intervene before liquidity stress becomes service interruption or settlement failure.

Operating principleObserve the ability to continue, not only the activity already completed.

Thresholds need operating meaning

A threshold is useful only when its zone maps to ownership and action. Warning may trigger participant contact. Critical may trigger escalation, more frequent observation, or scheme controls. The record should preserve the balance, threshold, classification, participant, and time that justified the response.

Thresholds also need governance. Different participants can have different operating profiles, and any change to a financially significant limit should be permissioned and auditable.

• Separate informational, warning, and critical zones.
• Attach an escalation owner and response expectation to each zone.
• Preserve threshold changes and the evidence behind an alert.
• Connect intraday signals to later NSI and RTGS settlement artifacts.

Close the loop with settlement evidence

Liquidity monitoring and settlement files should not live as unrelated tools. Participant balances, net obligations, detail files, and final settlement outputs describe the same risk across time.

When the control plane joins them, operations can move from an early signal to participant follow-up and, finally, to reconciled settlement evidence without losing context.