Clearing Cycle

Overview

A clearing cycle is a scheduled sequence in which a payment system receives instructions, validates and groups them, calculates obligations, and prepares outputs for settlement. A system can run one or many cycles per business or calendar day.

For Clearing Cycle, the concept separates instruction exchange and obligation calculation from final settlement, with timing, netting, liquidity, legal finality, settlement asset, participant roles, and failure procedures defined by the relevant system. The source-of-truth record should preserve starting event, timezone, calendar, cutoff, expected duration, maximum age, completion timestamp, obligation, and participant for Clearing Cycle, including the handoff to Clearing . For Clearing Cycle, the most consequential risks are unmatched records, incorrect obligation calculation or netting, liquidity shortfalls, participant default, wrong settlement assets, failed cycles, duplicated instructions, cross-currency exposure, time-zone mismatch, and claiming finality before the governing system provides it. The implementation should identify the obligation, participants, settlement asset, accounts or addresses, value date, liquidity source, posting sequence, and evidence of finality.

Clearing Cycle should remain distinct from Clearing and Payment Clearing, 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 Clearing Cycle, this point supports the definition’s focus on clearing cycle is a scheduled sequence in which a payment system receives instructions, validates and groups them, calculates.

Controls should validate instructions, funding, destination, currency or asset, cutoffs, and participant positions before treating a settlement step as complete. For Clearing Cycle, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Clearing Cycle should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome.