Programmability Is Eating Settlement

The argument

Settlement delay was once a safety margin. It gave institutions time to reconcile, check and correct before value moved with finality. A €300 million Siemens digital bond, settled in central bank money within minutes through the Bundesbank’s Trigger Solution, shows how quickly that margin is disappearing: a comparable issue a year earlier took two days. For retail flows, the BIS design for Project Nexus links national instant payment systems so that most cross-border payments can arrive within 60 seconds.

Programmable settlement attaches conditions to the payment itself. Pay the supplier when the bill of lading is verified. Release insurance funds when rainfall crosses a threshold. Disburse a subsidy when identity and eligibility checks pass. Reconciliation then happens when the payment is designed, instead of after it moves. The shift spans several forms of money: stablecoin networks for banks and fintechs, tokenised deposits explored in MAS Project Guardian, central bank digital currency pilots such as Brazil’s Drex, and interlinked instant payment systems that share ISO 20022 data.

The consequences fall on operating models. Manual reconciliation teams and batch settlement windows lose their purpose. Compliance moves to the start of a transaction, as pre-checks and attestations that travel with the funds. Treasury becomes event-driven, with funding, foreign exchange and collateral triggered by conditions instead of calendars. Control accrues to whoever certifies the facts that release money: identity providers, document verifiers and sources of risk data.

The risk surface moves with it. A wrong input now moves real money. Private programmable networks can recreate old silos unless they share data semantics. Supervisors need to read the rules behind each conditional payment, and systems need reversible states, liquidity backstops and human override for the cases code does not anticipate.

Key points

• Settlement measured in minutes removes the time that reconciliation, exception handling and float management were built around.
• Conditions attached to a payment move reconciliation from after the transaction to its design.
• Compliance shifts to the start of the transaction, and treasury shifts from calendar-driven to event-driven.
• Whoever certifies the data that triggers release, such as identity, documents or risk signals, gains a new control point.
• Shared data standards such as ISO 20022 decide whether programmable networks interoperate or form new silos.

Evidence and sources

• Siemens €300 million digital bond settled in minutes through the Bundesbank Trigger Solution (Ledger Insights, Markets Media)
• BIS Project Nexus design for cross-border payments within 60 seconds, and its ASEAN implementation track (BIS, Monetary Authority of Singapore)
• US move to T+1 equity settlement on 28 May 2024 (SEC)
• DTCC Project Ion processing over 100,000 equity transactions a day in a parallel DLT environment (DTCC)
• J.P. Morgan intraday repo on chain and Broadridge DLR with cash on chain (Business Wire, Euromoney, Markets Media)
• Global average remittance cost in the 4 to 6 per cent range (World Bank, Remittance Prices Worldwide)
• ISO 20022 as a common data language for payments (BIS)

Limits

• Figures and project status are as reported in August 2025.
• The essay’s dated forecasts for 2026, 2027 and 2028 are stated in the original as inferences from the direction of travel.