Narrative
PEFIGB22 notifies all institutions of how it expects AUD and ZAR payments to be settled, using an MT 670 Standing Settlement Instruction (SSI) Update Notification Request message to SWIFT, which is forwarded as an MT 671 Standing Settlement Instruction (SSI) Update Notification message to all SWIFT institutions. Each SSI recipient sets up the cash settlement information in its database.
The AUD correspondent of PEFIGB22 is BANKAU2L, account number 555555.
The ZAR correspondent of PEFIGB22 is JANIZAJJ, account number 777777.
Subsequently, BDAPGB22 makes an AUD payment to PEFIGB22 via its AUD correspondent. BDAPGB22 uses BANKAU2L as its AUD correspondent (the same as PEFIGB22).
And subsequently, WWYMGB22 makes a ZAR payment to PEFIGB22 via its ZAR correspondent. WWYMGB22 uses BANKZAJJ as its ZAR correspondent.
Information Flow
Message 1 MT 670 Standing Settlement Instruction (SSI) Update Notification Request:
 Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Start of Block |
|
| Sender's Message Reference |
|
| Function of the message |
|
| Start of Block |
|
| SSI Recipient Indicator |
|
| End of Block |
|
| Submitting Party (Sender) |
|
| Contact Person |
|
| SSI Update Type Indicator |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI |
|
| SSI Reference - optional |
|
| Currency of the SSI |
|
| Effective Date |
|
| Market Area Indicator |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI |
|
| SSI Reference - optional |
|
| Currency of the SSI |
|
| Effective Date |
|
| Market Area Indicator |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
| Note: |
In this scenario, PEFIGB22 is both the Sender of the SSI (submitting party) and the beneficiary and therefore appears in the message twice. |
On receipt of the MT 670, SWIFT creates an MT 671 and forwards it to all SWIFT users. The MT 671 is the same as the MT 670, except it does not have field :22H::SSIR//ALLL.
Message 2 MT 202 General Financial Institution Transfer
Using data in its SSI database, BDAPGB22 sends an MT 202 to its AUD correspondent to pay the AUD amount:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Transaction Reference Number |
|
| Related Reference |
|
| Value Date, Currency Code, Amount |
|
| Beneficiary Institution and its account at Receiver |
PEFIGB22 |
The Receiver of the MT is BDAPGB22's AUD correspondent. This bank is also the AUD correspondent of PEFIGB22.
Message 3 MT 202 General Financial Institution Transfer
Using data in its SSI database, WWYMGB22 sends an MT 202 to its ZAR correspondent to pay the ZAR amount:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Transaction Reference Number |
|
| Related Reference |
|
| Value Date, Currency Code, Amount |
|
| Account With Institution (also known as receiving agent) |
|
| Beneficiary Institution and its account at Account With Institution |
PEFIGB22 |
Narrative
PEFIGB22 has notified its trade counter-party BDAPGB22 of how it expects AUD to be settled, using an MT 670 Standing Settlement Instruction (SSI) Update Notification Request message to SWIFT, which is forwarded as an MT 671 Standing Settlement Instruction (SSI) Update Notification message to BDAPGB22. BDAPGB22 sets up the cash settlement information in its database.
Subsequently, PEFIGB22 does a deal with BDAPGB22, and buys AUD. PEFIGB22 has JANIAU2X as its AUD correspondent, account 999999. (BDAPGB22 uses BANKAU2X as its AUD correspondent.)
Information Flow
Message 1 MT 670 Standing Settlement Instruction (SSI) Update Notification Request:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Start of Block |
|
| Sender's Message Reference |
|
| Function of the Message |
|
| Start of Block |
|
| SSI Recipient |
|
| End of Block |
|
| Submitting Party (Sender) |
|
| Contact Person |
|
| SSI Update Type Indicator |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI |
|
| SSI Reference - optional |
|
| Currency of the SSI |
|
| Effective Date |
|
| Effective Date Indicator - the SSI must be applied to all outstanding trades |
|
| Market Area Indicator |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
| Note: |
In this scenario, PEFIGB22 is both the Sender of the SSI (submitting party) and the beneficiary and therefore appears in the message twice. |
On receipt of the MT 670, SWIFT creates an MT 671 and forwards it to the party identified as 95P SSIR (SSI Recipient). The MT 671 is the same as the MT 670, except it does not have field :95P::SSIR//.
Message 2 MT 300 Foreign Exchange Confirmation - Extract:
Using data in its SSI database, BDAPGB22 sends back its MT 300 to PEFIGB22 confirming that it will pay the AUD to PEFIGB22's AUD correspondent in favour of PEFIGB22's account.
Only mandatory subsequence B2 Amount Sold is shown:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Currency, Amount |
|
| Receiving Agent and account of Beneficiary at Receiving Agent |
JANIAU2X |
| Beneficiary Institution |
|
Message 3 MT 202 General Financial Institution Transfer:
Using data in its SSI database, the broker BDAPGB22 sends an MT 202 to its AUD correspondent to pay the AUD amount:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message type |
|
| Receiver |
|
| Transaction Reference Number |
|
| Related Reference |
|
| Value Date, Currency Code, Amount |
|
| Account With Institution (also known as receiving agent) |
|
| Beneficiary Institution and its account at Account with Institution |
PEFIGB22 |
Narrative
PEFIGB22 has notified its broker BDAPGB22 of how it expects AUD to be settled for trades carried out on behalf of Fund A, using an MT 670 Standing Settlement Instruction (SSI) Update Notification Request message to SWIFT, which is forwarded as an MT 671 Standing Settlement Instruction (SSI) Update Notification message to BDAPGB22. BDAPGB22 sets up the cash settlement information in its database.
Subsequently, Fund A uses fund manager PEFIGB22 to carry out a deal with BDAPGB22 and buys AUD. Fund A's custodian is CUSTGB22, its account at the custodian is 111111. The custodian, CUSTGB22, has JANIAU1L as its AUD correspondent, account 222222. (BDAPGB22 uses WWYMAU1L as its AUD correspondent.)
Information Flow
Message 1 MT 670 Standing Settlement Instruction (SSI) Update Notification Request:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Start of Block |
|
| Sender's Message Reference |
|
| Function of the Message |
|
| Start of Block |
|
| SSI Recipient |
|
| End of Block |
|
| Submitting Party (Sender) |
|
| SSI Update Type Indicator |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI |
|
| SSI Reference - optional |
|
| Currency of the SSI |
|
| Effective Date |
|
| Effective Date Indicator - the SSI must be applied to all future trades |
|
| Market Area Indicator |
|
| Start of Block |
|
| Intermediary |
|
| End of Block |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| Cash Account (Account With Institution's account at Intermediary) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
On receipt of the MT 670, SWIFT creates an MT 671 and forwards it to the party identified as 95P SSIR (SSI Recipient). The MT 671 is the same as the MT 670, except it does not have field :95P::SSIR//.
Message 2 MT 300 Foreign Exchange Confirmation - Extract:
Using data in its SSI database, BDAPGB22 sends back its MT 300 to PEFIGB22 confirming that it will pay the AUD to the PEFI's AUD correspondent in favour of the fund's account at the custodian.
Only the mandatory subsequence B2 Amount Sold is shown and the identification of the fund:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Fund/Beneficiary Institution |
|
| Currency, Amount |
|
| Intermediary and account of Receiving Agent at Intermediary |
JANIAU1L |
| Receiving Agent and account of Beneficiary at Receiving Agent |
CUSTGB22 |
Message 3 MT 202 General Financial Institution Transfer:
Using data in its SSI database, the broker BDAPGB22 sends an MT 202 to its AUD correspondent to pay the AUD amount:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message type |
|
| Receiver |
|
| Transaction Reference Number |
|
| Related Reference |
|
| Value Date, Currency Code, Amount |
|
| Intermediary |
|
| Account With Institution and its account at Intermediary |
CUSTGB22 |
| Beneficiary Institution and its account at Account With Institution |
Fund A |
Narrative
PEFIGB22, London, also manages SSIs for PEFIIE2D (Dublin) and has notified its trade counter-party, BDAPGB22, of how it expects AUD to be settled for trades with PEFIIE2D, using an MT 670 Standing Settlement Instruction (SSI) Update Notification Request message to SWIFT, which is forwarded as an MT 671 Standing Settlement Instruction (SSI) Update Notification message to BDAPGB22. BDAPGB22 sets up the cash settlement information in its database.
Subsequently, PEFIIE22, does a deal with BDAPGB22 (Trading Party B) and buys AUD. PEFIIE2D has JANIAU2X as its AUD correspondent, account 444444. (BDAPGB22, uses BANKAU2X as its AUD correspondent.)
Information Flow
Message 1 MT 670 Standing Settlement Instruction (SSI) Update Notification Request:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Start of Block |
|
| Sender's Message Reference |
|
| Function of Message |
|
| Start of Block |
|
| SSI Recipient |
|
| End of Block |
|
| Submitting Party (Sender) |
|
| Trade Party |
|
| SSI Update Type Indicator |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI |
|
| SSI Reference - optional |
|
| Currency of the SSI |
|
| Effective Date |
|
| Effective Date Indicator - the SSI must be applied to all outstanding trades and they must be reconfirmed |
|
| Market Area Indicator |
|
| Start of Block |
|
| Account With Institution (also known as Receiving agent) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
On receipt of the MT 670, SWIFT creates an MT 671 and forwards it to the party identified as 95P SSIR (SSI Recipient). The MT 671 is the same as the MT 670, except it does not have field :95P::SSIR//.
Message 2 MT 300 Foreign Exchange Confirmation - Extract:
Using data in its SSI database, BDAPGB22 sends back its MT 300 to PEFIIE2D confirming that it will pay the AUD to PEFIIE2D's AUD correspondent in favour of PEFIIE2D's account.
Only the mandatory subsequence B2 Amount Sold is shown:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Currency, Amount |
|
| Receiving Agent and account of Beneficiary at Receiving Agent |
JANIAU2X |
| Beneficiary Institution |
|
Message 3 MT 202 General Financial Institution Transfer:
Using data in its SSI database, the broker BDAPGB22 sends an MT 202 to its AUD correspondent to pay the AUD amount:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message type |
|
| Receiver |
|
| Transaction Reference Number |
|
| Related Reference |
|
| Value Date, Currency Code, Amount |
|
| Account With Institution (also known as receiving agent) |
|
| Beneficiary Institution and its account at Account With Institution |
PEFIIE2D |
Narrative
PEFIGB22, London, also manages SSIs for PEFIIE2D (Dublin) and has notified its trade counter-party, BDAPGB22, of how it expects AUD to be settled for trades carried out by PEFIIE2D on behalf of Fund A, using an MT 670 Standing Settlement Instruction (SSI) Update Notification Request message to SWIFT, which is forwarded as an MT 671 Standing Settlement Instruction (SSI) Update Notification message to BDAPGB22. BDAPGB22 sets up the cash settlement information in its database.
Subsequently, Fund A using fund manager, PEFIIE2D, does a deal with BDAPGB22 and buys AUD. Fund A's custodian is CUSTGB22, its account at the custodian is 111111. The custodian, CUSTGB22, has JANIAU2X as its AUD correspondent, account 222222. (BDAPGB22 uses BANKAU2X as its AUD correspondent.)
Information Flow
Message 1 MT 670 Standing Settlement Instruction (SSI) Update Notification Request:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Start of Block |
|
| Sender's Message Reference |
|
| Function of Message |
|
| Start of Block |
|
| SSI Recipient |
|
| End of Block |
|
| Submitting Party (Sender) |
|
| Trade Party |
|
| SSI Update Type Indicator |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI |
|
| SSI Reference - optional |
|
| Currency of the SSI |
|
| Effective Date |
|
| Effective Date Indicator - the SSI must be applied to all future trades |
|
| Market Area Indicator |
|
| Start of Block |
|
| Intermediary |
|
| End of Block |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| Cash Account (account of Account With Institution at Intermediary) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
On receipt of the MT 670, SWIFT creates an MT 671 and forwards it to the party identified as 95P SSIR (SSI Recipient). The MT 671 is the same as the MT 670, except it does not have field :95P::SSIR//.
Message 2 MT 300 Foreign Exchange Confirmation - Extract:
Using data in its SSI database, BDAPGB22 sends back its MT 300 to PEFIIE2D confirming that it will pay the AUD to PEFI's AUD correspondent in favour of the fund's account at the custodian.
Only the mandatory subsequence B2 Amount Sold is shown and the identification of the fund:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Fund/Beneficiary Institution |
|
| Currency, Amount |
|
| Intermediary and account of Receiving Agent at Intermediary |
JANIAU2X |
| Receiving Agent and account of Beneficiary at Receiving Agent |
CUSTGB22 |
Message 3 MT 202 General Financial Institution Transfer
Using data in its SSI database, the broker BDAPGB22 sends an MT 202 to its AUD correspondent to pay the AUD amount:
| Explanation |
Format |
|---|---|
| Sender (broker) |
|
| Message type |
|
| Receiver (broker's AUD correspondent) |
|
| Transaction Reference Number |
|
| Related Reference |
|
| Value Date, Currency Code, Amount |
|
| Intermediary |
|
| Account With Institution and its account at Intermediary |
CUSTGB22 |
| Beneficiary Institution and its account at Account With Institution |
Fund A |
Narrative
JANISESK, Stockholm, manages SSIs for JANIFI22 (Helsinki) and JANIDKKK (Copenhagen) and have the same AUD correspondent and account. JANISESK has notified its trade counter-party, BDAPGB22, of how it expects AUD to be settled for their trades, using an MT 670 Standing Settlement Instruction (SSI) Update Notification Request message to SWIFT, which is forwarded as an MT 671 Standing Settlement Instruction (SSI) Update Notification message to BDAPGB22. BDAPGB22 sets up the cash settlement information in its database.
Subsequently, JANIFI22, Finland, does a deal with BDAPGB22 and buys AUD. JANI has WWYMAU2X as its AUD correspondent, account 777777. BDAPGB22, uses BANKAU2X as its AUD correspondent.
Information Flow
Diagram 1 - SSI
Diagram 2 - Settlement parties and payment
Message 1 MT 670 Standing Settlement Instruction (SSI) Update Notification Request:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Start of Block |
|
| Sender's Message Reference |
|
| Function of Message |
|
| Start of Block |
|
| SSI Recipient |
|
| End of Block |
|
| Submitting Party (Sender) |
|
| SSI Update Type Indicator |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI |
|
| SSI Reference - optional |
|
| Currency of the SSI |
|
| Effective Date |
|
| Effective Date Indicator - the SSI must be applied to all future trades |
|
| Market Area Indicator |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
On receipt of the MT 670, SWIFT creates an MT 671 and forwards it to the party identified as 95P SSIR (SSI Recipient). The MT 671 is the same as the MT 670, except it does not have field :95P::SSIR//.
Message 2 MT 300 Foreign Exchange Confirmation - Extract:
Using data in its SSI database, BDAPGB22 sends back its MT 300 to JANIFI22 confirming that it will pay the AUD to JANIFI22's AUD correspondent in favour of JANI's account.
Only the mandatory subsequence B2 Amount Sold is shown:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Currency, Amount |
|
| Receiving Agent and account of Beneficiary at Receiving Agent |
WWYMAU2X |
| Beneficiary Institution |
|
Message 3 MT 202 General Financial Institution Transfer:
Using data in its SSI database, the broker BDAPGB22 sends an MT 202 to its AUD correspondent to pay the AUD amount:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message type |
|
| Receiver |
|
| Transaction Reference Number |
|
| Related Reference |
|
| Value Date, Currency Code, Amount |
|
| Account With Institution (also known as receiving agent) |
|
| Beneficiary Institution and account of Beneficiary at Account With Institution |
JANIFI22 |
Narrative
PEFIGB22 has notified its broker dealer, BDAPGB22 of how its expects securities trades to be settled, when the cash (GBP) has to be settled separately, using an MT 670 Standing Settlement Instruction (SSI) Update Notification Request message to SWIFT, which is forwarded as an MT 671 Standing Settlement Instruction (SSI) Update Notification message to all SWIFT institutions. BDAPGB22 sets up the cash settlement information in its database.
Subsequently, PEFIGB22 places an order to sell equities, the payment indicator is FREE (cash is settled separately from the securities).
PEFIGB22's cash agent is JANIGB22, account number 666666. JANIGB22's sort code is 121212. BDAPGB22 uses WWYMGB22 as its cash agent.
Information Flow
Message 1 MT 670 Standing Settlement Instruction (SSI) Update Notification Request:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Start of Block |
|
| Sender's Message Reference |
|
| Function of Message |
|
| Start of Block |
|
| SSI Recipient |
|
| End of Block |
|
| Submitting Party (Sender) |
|
| Contact Person |
|
| SSI Update Type Indicator |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI |
|
| SSI Reference - optional |
|
| Currency of the SSI |
|
| Effective Date |
|
| Effective Date Indicator - the SSI must be applied to all future trades |
|
| Market Area Indicator |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| Account With Institution's sort code |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
| Note: |
In this scenario, PEFIGB22 is both the sender of the SSI (submitting party) and the beneficiary and therefore appears in the message twice. |
On receipt of the MT 670, SWIFT creates an MT 671 and forwards it to the party identified as 95P SSIR (SSI Recipient). The MT 671 is the same as the MT 670, except it does not have field :95P::SSIR//.
Message 2 MT 202 General Financial Institution Transfer
Using data in its SSI database, BDAPGB22 sends an MT 202 to its cash agent to pay the GBP amount:
| Explanation |
Format |
|---|---|
| Sender |
|
| Message type |
|
| Receiver |
|
| Transaction Reference Number |
|
| Related Reference |
|
| Value Date, Currency Code, Amount |
|
| Account With Institution (also known as receiving agent)
(1) |
|
| Beneficiary Institution and its account at Account With Institution |
PEFIGB22 |
(1) The account with institution has been identified with a BIC using 57A. If a sort code is to be specified, then 57D is used.
In the past PEFIGB22 has notified BDAPGB22 of how it expects its AUD, USD, CAD and ZAR to be paid.
PEFIGB22 now re-confirms to BDAPGB22 its SSIs using an MT 670 Standing Settlement Instruction (SSI) Update Notification Request message to SWIFT, which is forwarded as an MT 671 Standing Settlement Instruction (SSI) Update Notification message to BDAPGB22.
PEFIGB22 uses the following correspondents:
AUD - BANKAU2L, account number 555555
USD - JANIUS33, account 666666
CAD - WWYMCATT, account 777777
ZAR - JANIZAJJ, account 888888
Information Flow
Message 1 MT 670 Standing Settlement Instruction (SSI) Update Notification Request
| Explanation |
Format |
|---|---|
| Sender |
|
| Message Type |
|
| Receiver |
|
| Start of Block |
|
| Sender's Message Reference |
|
| Function of Message |
|
| Start of Block |
|
| SSI Recipient |
|
| End of Block |
|
| Submitting Party (Sender) |
|
| SSI Update Type Indicator |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI
(1) |
|
| Currency of the SSI |
|
| Effective Date |
|
| Market Area Indicator |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI
(1) |
|
| Currency of the SSI |
|
| Effective Date |
|
| Market Area Indicator |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI
(1) |
|
| Currency of the SSI |
|
| Effective Date |
|
| Market Area Indicator |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
| Start of Block |
|
| Purpose of the SSI
(1) |
|
| Currency of the SSI |
|
| Effective Date |
|
| Market Area Indicator |
|
| Start of Block |
|
| Account With Institution (also known as receiving agent) |
|
| End of Block |
|
| Start of Block |
|
| Beneficiary |
|
| Cash Account (Beneficiary's account at Account With Institution) |
|
| End of Block |
|
| End of Block |
|
(1) For those situations in which a submitting party wants to send out a 'list' of all its SSIs, then the code RECO is used at the individual SSI level.
