Settlement Glossary
Deferred net settlement (DNS)
Deferred net settlement offsets many payments against each other and settles only the net amounts at set times, saving liquidity but leaving participants exposed to settlement risk until the netting cycle completes.
Deferred net settlement, or DNS, is settlement by offset. Instead of settling every payment on its own, the system collects many payments, works out what each participant owes on balance, and settles only those net amounts at scheduled times. The CPMI defines it as a net settlement mechanism which settles on a net basis at the end of a predefined settlement cycle. The appeal is efficiency: far less money has to actually move, because most of the obligations cancel out.
The trade-off at the heart of settlement
DNS and real-time gross settlement are the two poles of payment system design, and each buys one thing at the price of the other. The BIS describes the DNS side directly: settling by netting at the end of the day significantly reduces the amount of money that needs to change hands, but it also gives rise to potential settlement risk. Deferred net settlement minimises the liquidity you need. Real-time gross settlement gives you immediate finality and no settlement risk. You cannot have both at their maximum in the same design, which is why systems sit at different points on the line between them.
The risk in DNS is concrete. Because final settlement is deferred, participants are exposed to each other in the meantime. If a participant fails before the netting settles, its payments may have to be unwound, which reshapes everyone else’s net positions. The BIS lays out how this can spread: a bank expecting incoming funds from the failed participant may then be unable to meet its own new obligation, and may fail in turn, potentially setting off a cascade. That scenario is not hypothetical; it shaped the redesign of major systems.
How modern systems manage it
The response has been to keep the liquidity benefit of netting while containing the risk. Systems apply net debit caps, require collateral against debit positions, and use pre-funding of positions. Many settle several times a day rather than only at day’s end, shrinking the window in which exposure builds up. Others adopt a hybrid design that blends net and gross settlement: CHIPS, once a pure end-of-day net system, moved to a hybrid model that keeps netting’s liquidity efficiency while settling continuously enough to cut the risk. Deferred net settlement still underpins major systems, including fast retail payment schemes, but almost always wrapped in these protections rather than left in its original end-of-day form.
Common questions
- What is deferred net settlement?
- It is a mechanism that settles on a net basis at the end of a predefined settlement cycle, in the words of the CPMI. Rather than settling each payment individually, the system offsets what participants owe each other and settles only the net balances at scheduled times, which greatly reduces the money that actually has to change hands.
- How is DNS different from RTGS?
- Deferred net settlement saves liquidity by netting obligations and settling the net amounts periodically, but it delays finality and carries settlement risk until the cycle completes. Real-time gross settlement settles every payment individually and immediately with no settlement risk, at the cost of needing liquidity for each gross payment. It is a trade-off between liquidity and risk.
- What happens if a bank fails before settlement in a DNS system?
- The payments involving the failed bank may have to be unwound, which changes the net positions of everyone else. As the BIS describes, another bank that was expecting incoming funds might then be unable to meet its new obligation, potentially setting off a cascade of failures. This is why DNS systems use safeguards such as net debit caps, collateral, and pre-funding.
Related terms
Sources
Last reviewed 2026-07-08