Settlement cycle design: choosing when and how often to settle

A settlement cycle is the timetable that decides when payment obligations become final, and the choice of cycle is the single most important design decision in any clearing system. A cycle has three parameters: the cut-off time after which payments wait for the next cycle, the settlement window in which net positions are computed, and the settlement moment when central bank money actually moves. The operator chooses these parameters by balancing two opposing risks. Settling often reduces the exposure between participants but demands more liquidity, while settling rarely saves liquidity but lets exposures build up through the day. There is no universally correct answer, and the choice is a policy decision that the operator documents in the scheme rulebook. Why the cycle matters is that it determines how long a receiving bank waits before it can safely credit its customer in final funds. In a real-time gross settlement system such as Fedwire or T2, each payment settles individually in central bank money within seconds, so the receiving bank can credit the beneficiary immediately and the settlement risk is near zero. In a deferred net settlement system such as the UK Faster Payments Service or STEP2, payments are exchanged through the day and settled in a small number of net batches, so the receiving bank credits its customer before settlement and carries intraday exposure to the sending bank. The design question is always who bears the risk between the moment of credit and the moment of settlement. The parties involved are the participating banks, the clearing system operator, the central bank that holds the settlement accounts, and the scheme that writes the rulebook. The operator publishes the cycle timetable, collects payment files, computes net positions, and sends settlement instructions to the central bank. The central bank debits and credits the participants settlement accounts at the settlement moment. Each participant must hold enough liquidity in its settlement account to cover its net debit position, or arrange intraday credit against collateral. The Bank for International Settlements Principles for Financial Market Infrastructures, known as the PFMI, require the operator to manage this credit and liquidity risk explicitly. In practice a deferred net settlement cycle runs like this. During the exchange window, banks send payment instructions to the clearing system. At the cut-off, the system closes the cycle and computes each participant net position: the total value it owes minus the total value it is owed. A bank that sent more than it received has a net debit position and must fund it; a bank that received more has a net credit position and receives funds. The system then sends one settlement instruction per participant to the central bank, which debits the net debtors and credits the net creditors. The whole settlement typically completes in minutes, and the operator publishes a settlement report so each bank can reconcile its account. A worked example makes the numbers concrete. Suppose four banks exchange payments in one cycle. Bank A sends EUR 120 million and receives EUR 95 million, so its net position is a EUR 25 million debit. Bank B sends EUR 80 million and receives EUR 110 million, a EUR 30 million credit. Bank C sends EUR 60 million and receives EUR 55 million, a EUR 5 million debit. Bank D sends EUR 40 million and receives EUR 40 million, a net zero. The net debits total EUR 30 million and the net credits total EUR 30 million, so they balance exactly. Each bank moves only its net position, not the EUR 300 million of gross payments, which is why netting cuts liquidity needs by roughly ninety percent in a typical cycle. What happens when the cycle fails is the critical test of the design. If a net debtor cannot fund its position at the settlement moment, the operator must decide whether to delay settlement, exclude that bank's payments from the cycle and recompute the net positions, or draw on a default fund. Exclusion is the usual answer in retail systems: the failed bank's payments are removed, the net positions are recalculated, and settlement proceeds without it, but every other bank net position changes and some banks that expected a credit now owe money. The operator rulebook must state the exclusion procedure in advance, because recomputing under pressure with no agreed procedure is how a single failure becomes a systemic event. The operational and accounting implications are substantial. Each participant must forecast its net position before the cut-off, using its own payment queue and the expected receipts, and must pre-position liquidity or collateral. The operations team monitors the position through the day, and the treasury team manages the settlement account balance. On the ledger, each payment is booked when it is exchanged, but final settlement is only booked when the central bank confirms the debit or credit to the settlement account. A payment that is exchanged but not yet settled sits in a clearing account, and the reconciliation team must be able to explain every item in that account at the end of the day. For a business analyst, the settlement cycle is a requirements subject, not a background fact. When you write requirements for a new clearing system or a new participant connection, you must specify the cut-off times, the number of cycles per day, the settlement window, the funding deadline, the exclusion procedure, and the settlement reporting format. You must also specify what happens to payments that arrive after the cut-off, how the system handles a participant that misses its funding deadline, and how the operations team is alerted. The most common design mistake is to copy another system cycle without checking whether the liquidity profile and the risk appetite fit this participant population. Takeaway: a settlement cycle trades liquidity against risk, and the operator choice of cycle, cut-off and exclusion procedure is the risk policy of the system. Further reading: the BIS Principles for Financial Market Infrastructures (PFMI) for the credit and liquidity risk framework; the ECB TARGET services documentation for the cycle and account structure; the Bank of England CHAPS reference manual for the operating model and cut-off times. Last reviewed 7 November 2026.