GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
11 / ISO 20022 & CBPR+12 MIN

Settlement method: INGA versus INDA

Two questions decide the whole thing: which bank holds the account in the transfer currency, and is that bank sending this message or receiving it?

NOT STARTED

L0 Explain simply

Analogy: whoever holds the shared tab settles it. Picture two friends who keep a running tab with each other rather than paying cash every time. Whichever one of them holds the tab is the one who actually marks an item as settled — the other friend just tells them what to add. A correspondent banking relationship works the same way: when Bank Alfa holds Meridian Bank's account in a given currency, Bank Alfa is the one holding the tab, and it is Bank Alfa's own books — not a message travelling between them — where the money genuinely moves. The settlement method on a payment message is just a label saying which of the two banks is holding the tab for this particular leg, and whether they were the one sending the message or the one receiving it.

L1 Core concepts

Two questions decide the settlement method for one payment leg. First: which bank is the account servicing institution — the one holding the account, in the transfer currency, for the other? (This is exactly the nostro/vostro relationship: the bank whose books the account sits in is servicing it for its correspondent.) Second: on this particular message, is that account-servicing bank the instructing agent or the instructed agent? INGA (INstructinG Agent) means the account-servicing bank is the one sending the message — so settlement already happened the moment it sent it. INDA (INstructeD Agent) means the account-servicing bank is the one receiving the message — so settlement has not happened yet; it happens only when that bank processes what arrived.

L2 Practitioner view

The practical weight of this is timing, not paperwork. If a message arrives with settlement method INGA, the receiving bank is being told about money that has, from the sender's side, already moved — the sender settled by debiting or crediting its own books before the message was even sent. If it arrives with INDA, nothing has moved yet on either side; settlement is the very next thing the receiving bank has to do, by posting to the account it holds for its correspondent. This distinction is exactly why a bank cannot always safely credit a beneficiary the instant a payment message lands — under INDA, crediting before actually posting the settlement entry is crediting ahead of the money.

L3 Technical details

Illustrative pair of relationships: Bank Alfa holds Meridian Bank's EUR account (Meridian's nostro, Bank Alfa's vostro); Meridian Bank holds Bank Alfa's USD account (Bank Alfa's nostro, Meridian's vostro). For a EUR payment from Bank Alfa to Meridian: Bank Alfa is account-servicing and is sending the message, so settlement method is INGA. For a EUR payment the other way, Meridian to Bank Alfa: Bank Alfa is still account-servicing (nothing about the currency relationship changed), but now it is receiving the message, so settlement method is INDA. Swap to a USD payment and the account-servicing bank flips to Meridian — so a USD message from Meridian to Bank Alfa is INGA, and a USD message from Bank Alfa to Meridian is INDA. The direction of the money and the direction of who-holds-the-account are two separate questions, and both matter.

L4 Standards & sources

Settlement Method (SttlmMtd) is a defined element of the ISO 20022 pacs message Group Header, drawn from an external code list that also includes COVE (settled by a separate cover payment) and CLRG (settled through a clearing and settlement mechanism, not a bilateral account) — CBPR+'s correspondent-banking profile scopes its core usage to INDA, INGA and COVE, since CLRG belongs to the market-infrastructure world covered by the sister HVPS+ guidelines. The same INGA/INDA logic later decides which message a bank is even allowed to send if a payment cannot be completed: whether a leg has already settled by the account-servicing rule above determines the choice between rejecting a payment and returning one, which the next topic in this sequence takes on directly.

Sources & standards2
  1. Official requirement

    ISO 20022 Catalogue of messagesISO 20022 Registration Authority · GroupHeader/SettlementMethod external code list (SettlementMethod1Code): INDA, INGA, COVE, CLRG

    Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site. · Checked 2026-07-12

    Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.

  2. Scheme-specific rule

    Cross-Border Payments and Reporting Plus (CBPR+) usage guidelinesSwift (CBPR+ working group) · settlement method values in scope for the correspondent-banking (CBPR+) profile

    Defines how ISO 20022 messages (including pacs.008, pacs.009, pacs.002, pacs.004, and camt investigation messages) are used and validated for cross-border payments on the Swift network. · Checked 2026-07-18

    Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.

Sources for this topic3
  1. Official requirement

    ISO 20022 Catalogue of messagesISO 20022 Registration Authority · GroupHeader/SettlementMethod element and SettlementMethod1Code external code list

    Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site. · Checked 2026-07-12

    Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.

  2. Scheme-specific rule

    Cross-Border Payments and Reporting Plus (CBPR+) usage guidelinesSwift (CBPR+ working group) · settlement method values in scope for CBPR+ correspondent-banking traffic

    Defines how ISO 20022 messages (including pacs.008, pacs.009, pacs.002, pacs.004, and camt investigation messages) are used and validated for cross-border payments on the Swift network. · Checked 2026-07-18

    Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.

  3. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: Bank Alfa and Meridian Bank's bilateral EUR/USD correspondent relationship is an invented illustration; real correspondent networks involve many currencies and often more than one correspondent per currency.

    Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.

Deepest material on this page: L4 Standards & sources. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.

COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.
WHAT ARE YOU SHARING?

Public discussion

LOADING

Loading the discussion…