Settlement finality — why T+0 is not the point

Speed is not certainty

The most accessible promise of tokenisation is also one of its least complete: a trade agreed today can settle today. The appeal is obvious. Shorter settlement can reduce the period during which one party depends on another to deliver. It can also make ownership records easier to reconcile. But a clock measures elapsed time, not the quality of the rights exchanged. A transaction can be fast, technically irreversible and legally uncertain. For institutional capital, that combination is not modernisation. It is an unfamiliar form of exposure.

Settlement finality asks a different question from settlement speed. It concerns the point at which a transfer becomes unconditional and cannot be unwound under the applicable arrangements and law. Technical confirmation may help establish that point, but does not establish it by itself. The relevant evidence can include the governing documents, the authoritative ownership register, the rules of the settlement system and the treatment of insolvency. A ledger entry matters because of what it effects, not merely because it persists.

That distinction becomes especially important when a token represents an interest in something outside the network. A building, loan or infrastructure vehicle does not become subject only to software because its ownership interests are recorded digitally. Its governing law, contractual restrictions and enforcement arrangements remain. Faster transfers must fit within those arrangements rather than obscure them.

Two assets, several dependencies

A purchase involves more than the asset being acquired. There is also the payment asset, and both sides require scrutiny. A token representing a security might transfer cleanly while the payment depends on a separate bank process. Alternatively, a digital payment instrument might move immediately while the underlying ownership record requires further action. Calling either arrangement instantaneous can conceal the point at which the buyer has paid but does not yet hold an enforceable interest.

Delivery versus payment is intended to address this principal risk by making the transfer of securities conditional on payment, and vice versa. In a tokenised structure, that linkage may be implemented through shared infrastructure or coordinated systems. Neither approach removes the need to examine failure conditions. What happens if one system pauses, if an instruction expires, or if the cash instrument becomes unavailable? The design should explain where assets sit while an exception is resolved and who has authority to intervene.

The nature of cash matters as much as its availability. Commercial bank money, central bank money and privately issued digital instruments bring different legal claims and operational dependencies. A familiar label is not a substitute for understanding redemption, access and insolvency treatment. Institutions need to know which entity owes them money at each stage, in which currency, and under what conditions that obligation is discharged.

The useful question is not how quickly a token moves, but when each party can safely rely on what it has received.

Liquidity has a timetable

Immediate settlement can reduce outstanding counterparty exposure, yet it can also require participants to have cash and securities ready earlier. That is not a defect, but it is a trade-off. Arrangements that allow obligations to be netted can reduce the amount of liquidity needed across a portfolio of transactions. Replacing them with individually prefunded transfers may exchange one kind of risk for another. The comparison must include funding demands, not just processing speed.

This matters in private markets, where assets are not necessarily traded frequently and investors may coordinate subscriptions, capital calls and treasury movements across several accounts. A family office does not gain much from a rapid transfer window if its payment authorisations or banking arrangements cannot support it. A fund may value a predictable settlement cycle more highly than continuous availability. The appropriate timetable follows the participants and the instrument, rather than a technological ideal.

Continuous operation also raises questions about staffing and oversight. A network may accept instructions outside ordinary business hours while administrators, custodians or banks are unavailable. Someone must define which events are effective immediately, which are queued and which can be suspended. An institution should not discover during an exception that the infrastructure operates continuously but its contractual support does not.

Design for the difficult day

The strongest settlement design starts with an account of failure. It describes the consequences of an incorrect transfer, compromised credentials, a contested instruction and the insolvency of a service provider. It distinguishes between correcting a record and reversing a legally effective transaction. Those are not always the same action. An immutable history can document a mistake without determining how the resulting rights should be repaired.

Governance therefore belongs inside the technical specification. Who may pause transfers? Which evidence supports a correction? Can an administrator update an authoritative register independently of the token record? How are affected holders notified? These questions are sometimes presented as compromises with decentralisation. For regulated financial claims, they are more usefully understood as questions about accountability. Powers should be limited, disclosed and capable of being exercised under a clear process.

For a pre-launch arranger such as Democratize, the editorial implication is straightforward: settlement deserves to be assessed as a chain of legal and operational dependencies. The ambition should be a transfer process that professional investors can examine, price and trust. A shorter cycle may follow from that work, but it is not the evidence that the work has been done.

T+0 can be a useful outcome where the cash, asset and participants are ready. It should not become a slogan that displaces the harder inquiry. Better settlement means knowing what has transferred, when it became effective and what remains exposed if the system stops. Speed is valuable only once those answers are dependable. The distinction should shape procurement, documentation and operational testing from the outset.

Information, not advice.