Clearing and settlementالمقاصة والتسوية

Settlement (التسوية) is the moment money actually moves between two banks, long after the approval appeared on a screen. It has two routes, and what separates them is whether each amount moves on its own or is pooled with others first.

The first route is called real-time gross settlement, and the second is called net settlement (التسوية الصافية).

If netting is cheaper, why does gross settlement exist at all?

You learned in the payment lifecycle topic that gathering transactions and moving only the difference saves an enormous amount of liquidity. If it is that efficient, why is every payment not settled that way?

Because the saving has a price, and its name is waiting risk.

When a whole day of transactions is gathered and settled in the evening, you are assuming every bank will still be able to pay in the evening. All day long, unpaid debt accumulates between banks.

Now imagine a bank failing at three in the afternoon. Everyone who sent it transactions since morning, waiting for the evening settlement, is a creditor of an institution that will not pay. Those creditors may in turn fail to meet their own obligations, and the problem cascades. In crises this is called settlement risk.

Hence the practical split: large amounts settle one at a time and immediately, with no gathering and no waiting. That costs far more in liquidity, but it leaves no debt hanging for a single moment. Many small amounts are gathered and settled net, because the risk of one of them failing does not shake the system.

The rule is simply: the larger the amount, the less patience there is for waiting.

Gross means no offsetting

In real-time gross settlement, or RTGS (التسوية الإجمالية الفورية), the system processes every payment instruction separately and at its full value. If Bank A sends SAR 10 million to Bank B, the first bank's balance at the central bank falls and the second bank's balance rises by the same amount. The system does not wait for payments in the opposite direction and offset them.

This design suits a large securities payment or the funding of a corporate transaction. One failure in a high-value payment can transmit risk to other banks within minutes. RTGS therefore gives each payment a clear path and a defined settlement time.

Real time does not guarantee that every instruction executes immediately under all conditions. The sending bank needs enough liquidity in its central-bank account. The system may queue an instruction until an incoming payment or secured borrowing supplies that liquidity. It executes when the conditions and priority rules are satisfied.

Liquidity has an economic cost. Money reserved for settlement cannot be used elsewhere at the same moment. A bank treasurer therefore manages incoming and outgoing flows throughout the day rather than watching only the total value sent.

Net means paying the difference

In net settlement, the system collects many instructions before moving the final balance between banks. Suppose Bank A's customers send SAR 5 million to Bank B's customers while traffic in the opposite direction totals SAR 4 million. The banks do not need to settle SAR 9 million. Bank A pays a net SAR 1 million.

Netting can be bilateral between two banks or multilateral across all participants. Under multilateral netting, the system calculates each bank's position against the whole group. One bank ends as a net debtor and another as a net creditor, while thousands of offsetting transactions disappear from the final settlement payment.

This reduces the liquidity required. A retailer pays suppliers in the morning and receives customer sales later. A payroll application sends thousands of small credits while its banks receive other retail transfers in the opposite direction. Aggregation lets the system use offsetting instead of funding every movement separately.

Smaller net positions do not remove risk. A debtor bank may fail to pay its position when the cycle closes. The system then needs rules for collateral, limits, loss sharing, or recalculation. Closing times and default procedures are part of the financial design, not accounting details.

Finality (النهائية) is where the debt ends

Settlement finality means that a settled transfer is irrevocable under the system's rules, even if a commercial dispute arises later. Once a bank pays its final position in central-bank money, the obligation between the banks is discharged. A customer complaint does not automatically reverse that entry.

Finality does not prevent fraud recovery. A beneficiary bank can send a new transfer back, freeze an account under legal authority, or compensate a customer under its contract. These are later events, not deletion of the original settlement.

A risk manager needs to identify the exact point of finality. "Sent" may mean only that the customer's app accepted a request. It may mean the bank created a message. It may mean clearing calculated a position that has not yet been paid. A coloured status label is not enough to show who still bears the risk.

A batch window explains a missing salary

Your salary often begins as one row in a file containing many employees. The employer submits that file to its bank before a cut-off. The bank checks the account, names, and amounts before passing instructions to the relevant clearing route. The system then calculates bank positions in a scheduled window.

A file submitted after the cut-off may wait for the next cycle or the next business day. Even after clearing completes, the receiving bank may need to reconcile the file and post the credit to your account. The employer can therefore see an accepted payroll file while you still cannot see your salary.

The money is not lost between two servers. It is in a defined state between file acceptance, position calculation, settlement, and final account posting. A useful investigation starts with the file reference, cut-off time, clearing cycle, and receiving-bank status rather than a generic "processing" message.

That differs from a large RTGS transfer. A company buying property may request one payment during system operating hours because the seller will not transfer ownership before payment is final. Ten thousand salaries benefit from a low-cost batch even when it is tied to a time window.

Customer speed and bank speed can differ

Instant retail payment systems return a result in seconds and operate around the clock. The sender sees a debit, the beneficiary sees a credit, and both can treat the transaction as complete. The back-end design does not always have to mirror that experience literally.

Some systems settle every payment between banks immediately in central-bank money. Others give customers rapid finality while accumulating bank positions for later net settlement. In the second model, the scheme or a bank ensures that the beneficiary does not wait for a later settlement failure.

This hybrid model creates two benefits and one exposure. It gives customers retail speed and reduces interbank liquidity through netting. It also creates exposure between the moment funds become available to the beneficiary and the moment the debtor bank pays its position. Systems therefore impose participant limits, require collateral, and monitor positions during the day.

The word instant does not reveal the architecture. Two systems can provide the same customer experience while one settles each transaction separately and the other settles a net batch periodically. Ask when the payment is final for the customer, when it is final between banks, and who covers the gap.

Settlement layers in Saudi Arabia

SAMA, the Saudi Central Bank, oversees national payment and settlement infrastructure. The Saudi Arabian Riyal Interbank Express, SARIE, operates as the RTGS system for interbank riyal transfers. It also provides final settlement for connected systems, including obligations generated by mada, SADAD, and other clearing arrangements.

A card purchase at a shop does not necessarily cross RTGS as one individual transaction. mada carries large volumes of transaction messages and calculates obligations under its rules. Final positions then reach the settlement layer in central-bank money. The network accepting a card is therefore distinct from the place where the debt between banks ends.

Saudi Arabia launched the sarie instant payment system for low-value transfers in 2021. Customers can send eligible domestic transfers within seconds, around the clock, using an IBAN or permitted alternative identifier. The customer experience is simple, but banks still have to manage liquidity, finality, and operational resilience behind it.

Choosing the appropriate layer

Start with the payment's value, the consequence of failure, and when it needs to become final. A large financial-market payment needs fast certainty and an individual path. Salaries and small bills need scale efficiency. An instant retail transfer needs continuous availability and rules that protect interbank settlement.

Then separate four times in any payment product: customer acceptance, clearing, interbank settlement, and availability to the beneficiary. They may coincide or sit hours apart. "Where is my salary?" becomes answerable once you identify the layer, window, and state instead of relying on the single word transfer.