SWIFT, Payment Systems, Reconciliation and Settlement Risk - Article

Introduction

Cross-border payment processing involves more than simply sending money from one bank to another.

A typical international payment may involve:

• the customer's bank;

• one or more correspondent banks;

• a payment messaging network;

• Nostro or Vostro accounts;

• domestic or international payment systems; and

• reconciliation after settlement.

For CAIIB, the important concepts are SWIFT, payment messaging, actual settlement, reconciliation and settlement risk.

The most important distinction is:

SWIFT generally communicates financial instructions; it does not itself mean that funds have been finally settled.

SWIFT describes itself as a secure financial messaging service connecting financial institutions. Actual settlement takes place through accounts and payment or settlement systems.

This distinction is particularly important in case-study questions because a valid or authenticated message does not automatically prove that funds have been received or finally settled.

Learning Objectives

After studying this topic, you should be able to:

• explain the role of SWIFT in international banking;

• distinguish a payment message from actual settlement;

• understand how payment systems and correspondent accounts interact;

• identify important SWIFT-related operational controls;

• explain Nostro and transaction reconciliation;

• identify principal, liquidity and operational settlement risks;

• understand how Payment-versus-Payment reduces FX settlement risk; and

• analyse common CAIIB case-study situations.

1. What Is SWIFT?

SWIFT stands for the Society for Worldwide Interbank Financial Telecommunication.

It provides secure financial messaging services that allow banks and other financial institutions to exchange structured financial information.

A SWIFT message may contain information relating to:

• customer payments;

• bank-to-bank payments;

• foreign exchange transactions;

• trade finance;

• securities transactions;

• account statements;

• confirmations; and

• other financial activities.

The network standardises communication so that financial institutions in different countries can understand and process instructions consistently.

2. SWIFT Message Is Not the Same as Movement of Money

This is one of the most important CAIIB distinctions.

Assume an Indian bank sends an instruction to its US correspondent to pay USD to a beneficiary.

The payment process may involve:

1. the Indian bank creating the payment instruction;

2. transmission of financial information through SWIFT;

3. the correspondent bank receiving and processing the instruction;

4. debit to the Indian bank's Nostro account;

5. settlement through the relevant payment infrastructure; and

6. credit reaching the beneficiary bank or customer.

The SWIFT message supports communication.

The Nostro/Vostro account and payment infrastructure support settlement.

Therefore:

Message sent ≠ money finally received

and

Message authenticated ≠ settlement completed

This distinction can determine the correct answer in a case study.

3. Current SWIFT Message Standard: ISO 20022

Older banking material frequently refers to traditional SWIFT MT messages, such as MT-based payment instructions.

The cross-border payment environment has now materially changed.

SWIFT states that the coexistence period between traditional MT and ISO 20022 messaging for cross-border payment instructions ended on 22 November 2025. ISO 20022 is now the standard for cross-border payment instructions under the CBPR+ framework, although certain other MT reporting and non-instruction message types may continue during their respective transition arrangements.

ISO 20022 provides richer and more structured payment data, supporting:

• better straight-through processing;

• improved reconciliation;

• greater automation;

• improved compliance processing; and

• reduced manual intervention.

4. Payment System versus Messaging System

A messaging system communicates instructions and information.

A payment or settlement system processes monetary obligations according to its rules and enables settlement between participants.

This distinction can be understood as follows:

For example, India's RTGS settles transactions individually and continuously in real time. Since settlement occurs in RBI's books, RBI states that RTGS payments are final and irrevocable.

NEFT works differently. Transactions are processed through batches, with the RBI processing centre preparing bank-wise accounting entries and forwarding remittance messages to beneficiary banks.

The practical lesson is not to treat every payment network in the same manner.

5. Gross Settlement and Net Settlement

Payment systems may broadly settle obligations using gross or net approaches.

Gross Settlement

Each transaction is settled individually.

RTGS is the important Indian example.

RBI defines RTGS as continuous, real-time settlement of fund transfers individually on a transaction-by-transaction basis without netting.

Net Settlement

Multiple obligations may be accumulated and offset before the resulting net obligations are settled.

Netting reduces the amount of liquidity required for settlement but creates different timing and risk considerations.

For CAIIB, remember:

Gross = transaction by transaction

Net = obligations offset before settlement

The Payment and Settlement Systems Act provides legal recognition to matters including netting and settlement finality in authorised payment systems in India.

6. How SWIFT and Nostro Accounts Work Together

Assume:

• Bank A is an Indian bank.

• Bank B is Bank A's USD correspondent in New York.

• Bank A maintains a USD Nostro account with Bank B.

• An Indian importer instructs Bank A to pay a US exporter.

A simplified flow is:

Customer Instruction → Bank A's Accounting/CBS → SWIFT Payment Instruction → Bank B → Debit Bank A's Nostro → Payment System/Beneficiary Bank → Exporter

Two records are important:

Internal Record

Bank A records what it believes should have happened.

External Correspondent Record

Bank B records what actually passed through Bank A's Nostro account with Bank B.

These records must be reconciled.

7. Why Reconciliation Is Critical

Reconciliation means comparing two independently maintained records to identify whether transactions and balances agree.

In correspondent banking, important reconciliations include:

• SWIFT messages against CBS or accounting entries;

• Nostro statements against internal Nostro records;

• payment confirmations against transactions initiated;

• incoming funds against expected receipts; and

• outstanding entries against supporting documents.

Reconciliation helps identify:

• unauthorised payments;

• duplicate payments;

• missed accounting entries;

• incorrect amounts;

• wrong value dates;

• correspondent charges;

• returned transactions;

• messages created without accounting entries; and

• accounting entries for which no valid external payment exists.

8. RBI's Important SWIFT-Related Operational Controls

RBI's supervisory action against banks for SWIFT-control deficiencies highlights several important controls relevant to CAIIB.

RBI identified major control expectations relating to:

• avoiding uncontrolled direct creation of payment messages in the SWIFT environment;

• Straight Through Processing between CBS/accounting systems and SWIFT;

• segregation between users handling transactions in CBS and users operating the SWIFT environment;

• independent reconciliation of SWIFT logs with corresponding CBS/accounting entries;

• additional approval for payment messages above prescribed internal thresholds; and

• timely Nostro reconciliation.

These controls address a basic risk:

A payment message should not exist independently of a properly authorised and accounted banking transaction.

9. Straight Through Processing

Straight Through Processing (STP) means processing a transaction electronically through connected systems with little or no manual re-entry.

In a well-integrated environment:

Authorised Transaction in CBS → Data Flows to Payment/Messaging System → Message Generated → Processing Continues

STP reduces:

• manual data entry;

• duplication of work;

• keying errors;

• differences between systems; and

• opportunities for unauthorised message creation.

However, STP does not remove the need for:

• authorisation;

• maker-checker controls;

• access security;

• sanctions and compliance screening;

• exception handling; and

• independent reconciliation.

Automation reduces certain risks but does not eliminate control responsibility.

10. SWIFT-to-CBS Reconciliation

Consider the following case:

An employee creates an outward SWIFT payment instruction for USD 200,000.

No corresponding customer debit or authorised treasury transaction exists in the bank's CBS.

If the SWIFT system and CBS are not independently reconciled, the unauthorised transaction may remain undetected until the Nostro account is debited.

The correct control is to compare:

SWIFT output/logs

with

corresponding authorised CBS/accounting entries.

RBI specifically highlighted independent reconciliation of SWIFT logs with CBS/accounting entries as an important operational control.

This is different from Nostro reconciliation.

11. Nostro Reconciliation

Nostro reconciliation compares:

Bank's internal Nostro records

with

Correspondent bank's actual account statement.

Suppose Bank A records an expected USD 100,000 Nostro debit.

The correspondent statement shows USD 102,000.

The USD 2,000 difference must be investigated.

Possible causes include:

• correspondent charges;

• wrong payment amount;

• duplicate debit;

• incorrect internal posting; or

• another transaction booked to the account.

An unreconciled item should not simply remain outstanding indefinitely.

The longer an unexplained item remains unresolved, the greater the possibility of:

• financial loss;

• fraud;

• inaccurate liquidity position;

• wrong profit or loss;

• customer dispute; or

• settlement failure.

12. SWIFT Reconciliation versus Nostro Reconciliation

These are commonly confused.

A payment may successfully pass the SWIFT-CBS reconciliation but still produce a Nostro reconciliation difference.

Therefore, one control cannot replace the other.

13. What Is Settlement Risk?

Settlement risk is the risk that a transaction does not settle as expected.

In foreign exchange transactions, this risk becomes especially important because two currencies must usually be delivered.

For example:

Bank A sells USD to Bank B and buys EUR.

Bank A sends USD.

Before Bank A receives EUR, Bank B fails.

Bank A may lose the USD principal while not receiving the EUR purchased.

This is a major form of FX principal risk.

The Basel framework identifies FX settlement-related risks including principal risk, replacement-cost risk and liquidity risk.

14. Major Types of Settlement-Related Risk

Principal Risk

The risk of paying away the currency sold but not receiving the currency purchased.

This can expose the bank to the full principal amount, not merely the profit on the trade.

Replacement Cost Risk

A counterparty may default before settlement is completed.

The bank may then have to replace the transaction in the market at a less favourable rate.

The loss is linked to the changed market value of the transaction.

Liquidity Risk

A counterparty may eventually pay but not at the expected time.

The bank may need to obtain funds elsewhere to meet its own obligations.

Operational Risk

Settlement may fail because of:

• incorrect instructions;

• system failure;

• wrong account details;

• missed cut-off time;

• incorrect value date;

• inadequate controls; or

• processing error.

Credit Risk

A correspondent or counterparty may become unable to meet its obligation.

These risks can overlap in a real transaction.

15. Payment-versus-Payment

A major method of reducing FX principal settlement risk is Payment-versus-Payment (PvP).

Under PvP, final settlement of one currency occurs if and only if final settlement of the other currency also occurs.

The objective is to avoid the situation where one bank irrevocably pays one currency but never receives the other.

The BIS/CPMI identifies PvP as a major mechanism for reducing FX settlement risk.

16. Settlement Finality

Settlement finality means that settlement has reached the stage at which the transfer becomes final according to the rules and applicable law governing the payment system.

This is important because banks need certainty about when an obligation has been discharged.

For example, RBI states that RTGS payments are final and irrevocable because settlement takes place in RBI's books.

Do not confuse:

• payment instruction created;

• instruction transmitted;

• instruction accepted for processing;

• account debited; and

• final settlement.

These may represent different stages of a transaction.

17. Practical Case Study: Message Sent but Nostro Not Debited

A branch tells a customer that an international payment has been completed because the SWIFT message was successfully transmitted.

Later, the correspondent bank reports that the transaction could not be settled because the Nostro account did not have sufficient funds.

Correct Analysis

The branch's conclusion was incorrect.

Successful message transmission proves that the instruction was communicated through the messaging channel.

It does not necessarily establish final settlement.

The bank should verify:

• correspondent processing status;

• Nostro debit;

• settlement confirmation; and

• beneficiary-side outcome.

The case tests the distinction between messaging and settlement.

18. Practical Case Study: SWIFT Message Without CBS Entry

A treasury employee notices a high-value outgoing SWIFT message, but no corresponding transaction appears in the accounting system.

Correct Analysis

This is a serious control exception.

The bank should investigate immediately because the message may represent:

• an unauthorised transaction;

• failure of system integration;

• incorrect accounting;

• processing outside approved procedures; or

• another operational irregularity.

RBI's SWIFT controls emphasise STP, segregation of duties and independent reconciliation between SWIFT logs and CBS/accounting records.

The correct response is not to wait for the customer to complain or for the Nostro statement to arrive.

19. Practical Case Study: Nostro Difference

The internal books show a USD 5 million Nostro balance, while the correspondent statement shows USD 4.8 million.

Correct Analysis

The difference of USD 0.2 million is a reconciliation exception.

The bank should identify the individual unmatched entries rather than merely adjusting the internal balance to agree with the correspondent statement.

The investigation should check:

• unposted transactions;

• duplicate transactions;

• charges;

• value-date differences;

• returned payments; and

• unauthorised entries.

A balancing entry without investigation may hide the real operational problem.

20. Practical Case Study: Two Currency Legs

Bank A sells USD 10 million against EUR to Bank B.

Bank A irrevocably releases USD in the morning.

EUR is expected several hours later.

Bank B fails before delivering EUR.

Correct Analysis

Bank A is exposed to principal settlement risk because it has delivered the currency sold without receiving the currency purchased.

The important issue is not merely exchange-rate movement.

The bank may lose the full amount already delivered.

A PvP settlement mechanism would substantially reduce this type of principal risk by linking settlement of both currencies.

21. Practical Case Study: Delayed Receipt but No Default

Bank A expects USD funds from a counterparty by a specified value date.

The funds are delayed for several hours.

Bank A must borrow USD to meet another payment obligation.

The counterparty eventually pays in full.

Correct Analysis

The major immediate problem is liquidity risk.

Bank A has not necessarily suffered principal loss, because the counterparty eventually paid.

However, it may incur:

• borrowing cost;

• overdraft cost;

• operational disruption; or

• reputational consequences.

The word delay is important in distinguishing liquidity risk from outright principal loss.

22. Controls for Safe Payment and Settlement Operations

A bank should maintain layered controls covering the full payment lifecycle.

Important controls include:

• authorised transaction initiation;

• maker-checker or appropriate approval controls;

• segregation of duties;

• restricted system access;

• integration between accounting and payment messaging systems;

• independent SWIFT-CBS reconciliation;

• timely Nostro reconciliation;

• sufficient Nostro funding;

• monitoring of payment cut-off times;

• counterparty and correspondent limits;

• exception monitoring;

• investigation of outstanding reconciliation items; and

• use of risk-reducing settlement mechanisms where appropriate.

The important CAIIB principle is:

No single control is sufficient.

Authentication protects messaging.

Reconciliation detects mismatches.

Liquidity management supports settlement.

Counterparty controls address credit exposure.

PvP reduces FX principal settlement risk.

23. CAIIB Exam Focus

SWIFT Is Messaging, Not Settlement

If a case says that the SWIFT message was transmitted successfully, do not automatically conclude that settlement is complete.

Identify Which Reconciliation Has Failed

Ask what is being compared:

• SWIFT vs CBS → messaging/accounting control;

• Nostro books vs correspondent statement → settlement/account reconciliation.

Understand STP

STP reduces manual intervention and enables data to flow between systems, but it does not remove the need for authorisation and independent controls.

Read Risk Words Carefully

Look for keywords such as:

“Paid but did not receive” → Principal risk

“Counterparty defaults before settlement and trade must be replaced” → Replacement-cost risk

“Payment delayed and bank must borrow funds” → Liquidity risk

“Wrong details/system/process failure” → Operational risk

Distinguish RTGS from Net Settlement

RTGS settles transactions individually and continuously rather than accumulating them for net settlement.

Remember the Current ISO 20022 Position

From 22 November 2025, ISO 20022 became the standard for SWIFT cross-border payment instructions under the CBPR+ framework.

Historical questions may still use MT terminology.

24. Common Exam Traps

Trap 1: “SWIFT Transfer Completed” Means Beneficiary Received Funds

Incorrect.

The SWIFT message and final settlement are different stages.

Trap 2: Nostro Reconciliation and SWIFT Reconciliation Are the Same

Incorrect.

They compare different records and control different risks.

Trap 3: Authentication Removes the Need for Reconciliation

Incorrect.

Even an authenticated message may be incorrect, unauthorised internally or inconsistent with the accounting records.

Trap 4: STP Means No Human Control Is Required

Incorrect.

STP reduces manual processing but does not eliminate authorisation, access controls, exception handling or reconciliation.

Trap 5: Settlement Risk Means Only Counterparty Credit Risk

Incorrect.

Settlement-related risks may include principal, replacement-cost, liquidity and operational risks.

Trap 6: Delayed Receipt Always Means Principal Loss

Incorrect.

A delay may primarily create liquidity risk if payment is eventually received.

Trap 7: FX Loss Is Limited to Exchange-Rate Difference

Incorrect in a principal-risk case.

If one currency has been irrevocably delivered but the other is never received, exposure may involve the full principal delivered.

Trap 8: PvP Removes Every Risk in an FX Transaction

Incorrect.

PvP is particularly important for reducing principal settlement risk. Other risks such as operational, liquidity, legal and counterparty risks still require separate management.

Trap 9: All SWIFT Payment Instructions Still Use Traditional MT Formats

Incorrect as a statement of the current position.

ISO 20022 became the required standard for cross-border payment instructions after the SWIFT coexistence period ended on 22 November 2025.

25. Memory Techniques

For payment processing, remember:

M–A–S–R

M – Message The instruction is communicated.

A – Account The relevant Nostro/Vostro or settlement account is affected.

S – Settlement The financial obligation is discharged.

R – Reconciliation Records are checked after processing.

For settlement risks, remember:

P–R–L–O

P – Principal risk

R – Replacement-cost risk

L – Liquidity risk

O – Operational risk

For the most important SWIFT exam rule, remember:

SWIFT tells; settlement pays.

This helps avoid the common mistake of treating transmission of a payment message as proof of final settlement.