Payments Academy
Deferred net settlement PAYMENT OPERATIONS STARTED LIVE 01 Deferred - often called DNS ACTIVE 02 Only - Because only net amounts settle QUEUED 03 Receiving banks - If that happens QUEUED 04 At the 4 in the afternoon - Bank A owes a net EUR 48 million and Bank B QUEUED 05 Customers of Bank C and Bank - paid on time, and the problem stays between QUEUED 06 Moving to three settlement cycles - day instead of one shortens the exposure QUEUED Deferred net settlement, often called DNS, is the model used by most retail payment systems. Step 1 of 6 Deferred net settlement STARTED Deferred often called DNS ACTIVE Only Because only net amounts settle QUEUED Receiving banks If that happens QUEUED At the 4 in the afternoon Bank A owes a net EUR 48 million and Bank B QUEUED Customers of Bank C and Bank paid on time, and the problem stays between QUEUED Moving to three settlement cycles day instead of one shortens the exposure QUEUED Deferred net settlement, often called DNS, is the model used by most retail payment systems.
Only net amounts settle PAYMENT OPERATIONS IN PROGRESS LIVE 01 Deferred - often called DNS DONE 02 Only - Because only net amounts settle ACTIVE 03 Receiving banks - If that happens QUEUED 04 At the 4 in the afternoon - Bank A owes a net EUR 48 million and Bank B QUEUED 05 Customers of Bank C and Bank - paid on time, and the problem stays between QUEUED 06 Moving to three settlement cycles - day instead of one shortens the exposure QUEUED Because only net amounts settle, the liquidity needed is a small fraction of the gross value processed. Step 2 of 6 Only net amounts settle IN PROGRESS Deferred often called DNS DONE Only Because only net amounts settle ACTIVE Receiving banks If that happens QUEUED At the 4 in the afternoon Bank A owes a net EUR 48 million and Bank B QUEUED Customers of Bank C and Bank paid on time, and the problem stays between QUEUED Moving to three settlement cycles day instead of one shortens the exposure QUEUED Because only net amounts settle, the liquidity needed is a small fraction of the gross value processed.
Receiving banks PAYMENT OPERATIONS IN PROGRESS LIVE 01 Deferred - often called DNS DONE 02 Only - Because only net amounts settle DONE 03 Receiving banks - If that happens ACTIVE 04 At the 4 in the afternoon - Bank A owes a net EUR 48 million and Bank B QUEUED 05 Customers of Bank C and Bank - paid on time, and the problem stays between QUEUED 06 Moving to three settlement cycles - day instead of one shortens the exposure QUEUED If that happens, the receiving banks may have already credited their customers but have not yet received the settlement funds. Step 3 of 6 Receiving banks IN PROGRESS Deferred often called DNS DONE Only Because only net amounts settle DONE Receiving banks If that happens ACTIVE At the 4 in the afternoon Bank A owes a net EUR 48 million and Bank B QUEUED Customers of Bank C and Bank paid on time, and the problem stays between QUEUED Moving to three settlement cycles day instead of one shortens the exposure QUEUED If that happens, the receiving banks may have already credited their customers but have not yet received the settlement funds.
At the 4 in the afternoon settlement PAYMENT OPERATIONS IN PROGRESS LIVE 01 Deferred - often called DNS DONE 02 Only - Because only net amounts settle DONE 03 Receiving banks - If that happens DONE 04 At the 4 in the afternoon - Bank A owes a net EUR 48 million and Bank B ACTIVE 05 Customers of Bank C and Bank - paid on time, and the problem stays between QUEUED 06 Moving to three settlement cycles - day instead of one shortens the exposure QUEUED At the 4 in the afternoon settlement, Bank A owes a net EUR 48 million and Bank B owes a net EUR 22 million, while Bank C is due a net EUR 55 million and Bank D is due a net EUR 15 million. Step 4 of 6 At the 4 in the afternoon settlement IN PROGRESS Deferred often called DNS DONE Only Because only net amounts settle DONE Receiving banks If that happens DONE At the 4 in the afternoon Bank A owes a net EUR 48 million and Bank B ACTIVE Customers of Bank C and Bank paid on time, and the problem stays between QUEUED Moving to three settlement cycles day instead of one shortens the exposure QUEUED At the 4 in the afternoon settlement, Bank A owes a net EUR 48 million and Bank B owes a net EUR 22 million, while Bank C is due a net EUR 55 million and Bank D is due a net EUR 15 million.
Customers of Bank C and Bank D PAYMENT OPERATIONS IN PROGRESS LIVE 01 Deferred - often called DNS DONE 02 Only - Because only net amounts settle DONE 03 Receiving banks - If that happens DONE 04 At the 4 in the afternoon - Bank A owes a net EUR 48 million and Bank B DONE 05 Customers of Bank C and Bank - paid on time, and the problem stays between ACTIVE 06 Moving to three settlement cycles - day instead of one shortens the exposure QUEUED The customers of Bank C and Bank D are paid on time, and the problem stays between the banks. Step 5 of 6 Customers of Bank C and Bank D IN PROGRESS Deferred often called DNS DONE Only Because only net amounts settle DONE Receiving banks If that happens DONE At the 4 in the afternoon Bank A owes a net EUR 48 million and Bank B DONE Customers of Bank C and Bank paid on time, and the problem stays between ACTIVE Moving to three settlement cycles day instead of one shortens the exposure QUEUED The customers of Bank C and Bank D are paid on time, and the problem stays between the banks.
Moving to three settlement cycles PAYMENT OPERATIONS COMPLETE LIVE 01 Deferred - often called DNS DONE 02 Only - Because only net amounts settle DONE 03 Receiving banks - If that happens DONE 04 At the 4 in the afternoon - Bank A owes a net EUR 48 million and Bank B DONE 05 Customers of Bank C and Bank - paid on time, and the problem stays between DONE 06 Moving to three settlement cycles - day instead of one shortens the exposure ACTIVE Moving to three settlement cycles a day instead of one shortens the exposure window from a full day to a few hours, which is a common upgrade when volumes grow. Step 6 of 6 Moving to three settlement cycles COMPLETE Deferred often called DNS DONE Only Because only net amounts settle DONE Receiving banks If that happens DONE At the 4 in the afternoon Bank A owes a net EUR 48 million and Bank B DONE Customers of Bank C and Bank paid on time, and the problem stays between DONE Moving to three settlement cycles day instead of one shortens the exposure ACTIVE Moving to three settlement cycles a day instead of one shortens the exposure window from a full day to a few hours, which is a common upgrade when volumes grow.

Key points of this lesson, in order.

0:00 / 3:29 Step 1 of 6

Deferred Net Settlement

Settlement Models, Lesson 3 of 7, Narration 3:29, D07 Clearing, settlement and liquidity

SettlementLiquidityClearing

What you will learn

Your objective. By the end of this lesson, you will be able to explain deferred net settlement. Deferred net settlement, often called DNS, is the model used by most retail payment systems.

Why it matters. An analyst documents three things for a DNS system.

Chapter objective: Learner compares gross settlement, net settlement, deferred net settlement, and real-time gross settlement, and explains finality, timing, and liquidity needs for each model. Learner practises this skill on realistic banking cases, explaining the reasoning clearly and using correct terminology throughout the work.

Key learning points

  • Deferred net settlement
  • Only net amounts settle
  • Receiving banks
  • At the 4 in the afternoon settlement
  • Customers of Bank C and Bank D
  • Moving to three settlement cycles

Key terms

Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.

Liquidity: Cash or assets that a bank can use immediately to meet payment obligations. Banks manage liquidity by forecasting inflows and outflows, funding nostro and settlement accounts, and using central bank...

Clearing: The process of exchanging payment instructions between banks and calculating what each bank owes the others.

Clearing and settlement timeline showing Deferred Net Settlement.

Practise this lesson

Exercise

Decide which settlement model fits the scenario in this lesson and explain why.

Use the settlement models, the liquidity trade-off and the finality rules in this lesson.

  1. What to do. Name the model, state when settlement becomes final, and explain what happens if the sending bank does not have enough liquidity.

Correct result. Real time gross settlement settles each payment individually in central bank money with immediate finality, but it needs liquidity for every payment. Deferred net settlement nets payments and settles the net position, which needs less liquidity but leaves settlement risk until the net settles.

Why. Settlement is where money actually moves. The model decides the risk, the liquidity need, and when the payment is truly final.

Check your understanding

Practice question

A payment system settles all of the day payments once, at 5pm, on a net basis. A customer payment sent at 9am is urgent. What should the bank tell the customer?

Takeaway and next step

What to remember

Moving to three settlement cycles a day instead of one shortens the exposure window from a full day to a few hours, which is a common upgrade when volumes grow.

Settle a payment like the one in this lesson and watch the liquidity and finality behaviour.

Open the T2/TIPS Simulator →

Builds on "Real Time Gross Settlement".

Transcript and full text

Show transcript

Deferred net settlement, often called DNS, is the model used by most retail payment systems. Payments are collected over a period, such as a few hours or a full day, netted together, and then settled as a single net amount at the end of that period. A bank that has sent more than it received pays its net debit, and a bank that has received more than it sent receives its net credit. Settlement typically happens once or a few times a day, rather than continuously. This is the model behind automated clearing houses and many national retail systems. The advantage of DNS is efficiency. Because only net amounts settle, the liquidity needed is a small fraction of the gross value processed. This makes DNS ideal for high volume, low value payments such as salaries, direct debits, bill payments and retail transfers, where individual payments are small and the cost of settling each one in real time would be disproportionate. The system can process millions of payments cheaply, and participants only need to fund their net position at the agreed settlement times. The disadvantage is timing risk. Between the moment a payment is cleared and the moment it settles, the sending bank could fail. If that happens, the receiving banks may have already credited their customers but have not yet received the settlement funds. Systems manage this with prefunding, collateral, loss sharing agreements and, in some cases, a guarantee from the central bank or the clearing house. Some DNS systems have moved to multiple settlement cycles per day, which shortens the exposure window and gives customers faster access to funds while keeping the liquidity benefits of netting. Run the numbers for one cycle. A retail system collects 2.4 million payments during the day with a gross value of EUR 6.3 billion. At the 4 in the afternoon settlement, Bank A owes a net EUR 48 million and Bank B owes a net EUR 22 million, while Bank C is due a net EUR 55 million and Bank D is due a net EUR 15 million. The debits add to EUR 70 million and the credits add to EUR 70 million, so the cycle balances exactly. Only EUR 70 million moves at settlement, against EUR 6.3 billion of customer payments, which is why the model is so cheap to run. Now suppose Bank A cannot fund its EUR 48 million net debit at 4 in the afternoon. In a well designed system the settlement still completes. The system draws on the prefund or collateral Bank A posted in advance, or on a loss sharing agreement under which the other participants cover the shortfall and recover it from Bank A later. The customers of Bank C and Bank D are paid on time, and the problem stays between the banks. An analyst documents three things for a DNS system. First, the cycle timetable. Collection cut off, net calculation, funding deadline, and settlement time, with the consequence of missing each one. Second, the funding forecast. Each participant's expected net position for the day, so treasury can arrange the money before the funding deadline instead of discovering the shortfall at three fifty-five in the afternoon. Third, the break procedure. If the system's net figure differs from a bank's own calculation, the difference is investigated before settlement, not after, because once the net amounts have moved, unwinding them is slow and expensive. Moving to three settlement cycles a day instead of one shortens the exposure window from a full day to a few hours, which is a common upgrade when volumes grow. DNS, which stands for Deferred Net Settlement, is the full name of the model taught in this lesson, and the two names refer to exactly the same thing. DNS is the abbreviation used in the Bank for International Settlements PFMI and in most central bank publications, while deferred net settlement is the descriptive name used in scheme rulebooks and in this course. There is no separate DNS system and no separate deferred net settlement system: they are one model with two names, and a learner who searches for either must arrive at this lesson. The reason both names persist is that the PFMI uses the abbreviation DNS for brevity, while operators and schemes prefer the full descriptive name because it tells a newcomer what the model does: settlement is deferred, and it is net. The abbreviation matters in practice because it appears in documents, in system names, and in conversations, and a professional who does not recognise it will be confused. The Faster Payments Service in the United Kingdom settles on a DNS basis, and its documentation refers to DNS cycles. The STEP2 system in Europe settles on a DNS basis, and the European Central Bank refers to it as DNS. The National Payments Corporation of India refers to DNS in its settlement documentation. When a business analyst writes a requirement that says the system settles on a DNS basis, every reader must understand that this means payments are exchanged through the day, netted at the cut-off, and settled as a single net amount, and that the alternative is RTGS, real-time gross settlement, where each payment settles individually. A worked example shows the DNS calculation again with the abbreviation used throughout. Four banks exchange payments in one DNS cycle. Bank A sends EUR 120 million and receives EUR 95 million, so its DNS 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 DNS settlement instruction from the operator to the central bank contains one line per bank: debit A EUR 25 million, credit B EUR 30 million, debit C EUR 5 million, no instruction for D. The total debits equal the total credits, EUR 30 million, and the settlement completes in a single batch. This is the DNS model in one paragraph. For a business analyst, the naming is a terminology subject. You must use the full name deferred net settlement the first time it appears in a document, followed by the abbreviation DNS in brackets, and then use DNS thereafter, because that is the convention in the PFMI and in central bank publications. You must also ensure that your glossary, your requirements, and your test cases all use the same name, because a test case that says DNS and a requirement that says deferred net settlement will be treated as two different things by a tester who does not know they are the same. Takeaway: DNS and deferred net settlement are one model, and this lesson is the single place where it is taught. Last reviewed 7 November 2026.

Deferred net settlement, often called DNS, is the model used by most retail payment systems. Payments are collected over a period, such as a few hours or a full day, netted together, and then settled as a single net amount at the end of that period. A bank that has sent more than it received pays its net debit, and a bank that has received more than it sent receives its net credit. Settlement typically happens once or a few times a day, rather than continuously. This is the model behind automated clearing houses and many national retail systems.

The advantage of DNS is efficiency. Because only net amounts settle, the liquidity needed is a small fraction of the gross value processed. This makes DNS ideal for high volume, low value payments such as salaries, direct debits, bill payments and retail transfers, where individual payments are small and the cost of settling each one in real time would be disproportionate. The system can process millions of payments cheaply, and participants only need to fund their net position at the agreed settlement times.

The disadvantage is timing risk. Between the moment a payment is cleared and the moment it settles, the sending bank could fail. If that happens, the receiving banks may have already credited their customers but have not yet received the settlement funds. Systems manage this with prefunding, collateral, loss sharing agreements and, in some cases, a guarantee from the central bank or the clearing house. Some DNS systems have moved to multiple settlement cycles per day, which shortens the exposure window and gives customers faster access to funds while keeping the liquidity benefits of netting.

Run the numbers for one cycle. A retail system collects 2.4 million payments during the day with a gross value of EUR 6.3 billion. At the 4 in the afternoon settlement, Bank A owes a net EUR 48 million and Bank B owes a net EUR 22 million, while Bank C is due a net EUR 55 million and Bank D is due a net EUR 15 million. The debits add to EUR 70 million and the credits add to EUR 70 million, so the cycle balances exactly. Only EUR 70 million moves at settlement, against EUR 6.3 billion of customer payments, which is why the model is so cheap to run. Now suppose Bank A cannot fund its EUR 48 million net debit at 4 in the afternoon. In a well designed system the settlement still completes. The system draws on the prefund or collateral Bank A posted in advance, or on a loss sharing agreement under which the other participants cover the shortfall and recover it from Bank A later. The customers of Bank C and Bank D are paid on time, and the problem stays between the banks.

An analyst documents three things for a DNS system. First, the cycle timetable. Collection cut off, net calculation, funding deadline, and settlement time, with the consequence of missing each one. Second, the funding forecast. Each participant's expected net position for the day, so treasury can arrange the money before the funding deadline instead of discovering the shortfall at three fifty-five in the afternoon. Third, the break procedure. If the system's net figure differs from a bank's own calculation, the difference is investigated before settlement, not after, because once the net amounts have moved, unwinding them is slow and expensive. Moving to three settlement cycles a day instead of one shortens the exposure window from a full day to a few hours, which is a common upgrade when volumes grow.

DNS, which stands for Deferred Net Settlement, is the full name of the model taught in this lesson, and the two names refer to exactly the same thing. DNS is the abbreviation used in the Bank for International Settlements PFMI and in most central bank publications, while deferred net settlement is the descriptive name used in scheme rulebooks and in this course. There is no separate DNS system and no separate deferred net settlement system: they are one model with two names, and a learner who searches for either must arrive at this lesson. The reason both names persist is that the PFMI uses the abbreviation DNS for brevity, while operators and schemes prefer the full descriptive name because it tells a newcomer what the model does: settlement is deferred, and it is net.

The abbreviation matters in practice because it appears in documents, in system names, and in conversations, and a professional who does not recognise it will be confused. The Faster Payments Service in the United Kingdom settles on a DNS basis, and its documentation refers to DNS cycles. The STEP2 system in Europe settles on a DNS basis, and the European Central Bank refers to it as DNS.

The National Payments Corporation of India refers to DNS in its settlement documentation. When a business analyst writes a requirement that says the system settles on a DNS basis, every reader must understand that this means payments are exchanged through the day, netted at the cut-off, and settled as a single net amount, and that the alternative is RTGS, real-time gross settlement, where each payment settles individually.

A worked example shows the DNS calculation again with the abbreviation used throughout. Four banks exchange payments in one DNS cycle. Bank A sends EUR 120 million and receives EUR 95 million, so its DNS 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 DNS settlement instruction from the operator to the central bank contains one line per bank: debit A EUR 25 million, credit B EUR 30 million, debit C EUR 5 million, no instruction for D. The total debits equal the total credits, EUR 30 million, and the settlement completes in a single batch. This is the DNS model in one paragraph.

For a business analyst, the naming is a terminology subject. You must use the full name deferred net settlement the first time it appears in a document, followed by the abbreviation DNS in brackets, and then use DNS thereafter, because that is the convention in the PFMI and in central bank publications. You must also ensure that your glossary, your requirements, and your test cases all use the same name, because a test case that says DNS and a requirement that says deferred net settlement will be treated as two different things by a tester who does not know they are the same. Takeaway: DNS and deferred net settlement are one model, and this lesson is the single place where it is taught. Last reviewed 7 November 2026.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.