Standing Settlement Instruction Fields

Name	ALERT Field Name	Datatype	Max. Length	Definition
	A/C @ Depository (ID1)		35	The membership ID of the clearing agent at the depository. It is also referred to as the local market code identifier, such as a DTC participant number or a CHESS PID number, other than a BIC. You complete it for certain countries according to Securities Market Practice Group (SMPG) recommended guidelines. The name of this field changes to the relevant name for the local identifier when certain methods are selected. For US-DTC settlement instructions, ID1 (DTC #) is required and validated against DTC master files.
AC_No_at_Global_Custodian	A/C# @ Global Custodian	char	35	The number of the safekeeping or security account at the global custodian. For one level of clearing, the custodian is referred to and appears in the Local Agent data section, as he or she acts as the agent. For two levels of clearing, the global custodian should appear in the Custodian section, with the subcustodian’s information appearing in the Local Agent section. If a market-specific label is not available, the label is A/C @ Global Custodian. SWIFT uses the following labels to identify the parties: BUYR/SELL = Investment manager REAG/DEAG = Subcustodian/subagent/local agent RECU/DECU = Global custodian
AC_No_at_Local_Agent	A/C# @ Local Agent	char	35	The account number of the entity that has the account at the local agent. For two levels of clearing, this is the global custodian's account number at the subcustodian/subagent. If there is an intermediary, this would be the intermediary’s account number at the subcustodian/subagent/local agent. For foreign exchange instructions, this field contains the final beneficiary’s account number (that is, the account number at the global custodian). SWIFT uses the following labels to identify the parties: RECU/DECU = Global custodian REAG/DEAG = Subcustodian/subagent/local agent REI1/DEI1 = Intermediary
AC_Ref_1	A/C Ref 1	char	35	The first 35 characters of the fund/account name associated with the safekeeping or security account at the global custodian. For one level of clearing, the custodian is referred to and appears in the Subagent data section, as he or she acts as the agent. For two levels of clearing, the global custodian appears in the Custodian section, with the subcustodian's information appearing in the Local Agent section. SWIFT uses the following labels to identify the parties: RECU/DECU = Global custodian REAG/DEAG = Subcustodian/subagent/local agent BUYR/SELL = Investment manager
AC_Ref_2	A/C Ref 2	char	35	The second 35 characters of the fund/account name associated with the safekeeping or security account at the global custodian. For one level of clearing, the custodian is referred to and appears in the Local Agent data section, as he or she acts as the agent. For two levels of clearing, the global custodian appears in the Custodian section, with the subcustodian's information appearing in the Local Agent section. SWIFT uses the following labels to identify the parties: RECU/DECU = Global custodian REAG/DEAG = Subcustodian/subagent/local agent BUYR/SELL = Investment manager
Alternate_Cash_AC_No	Alternate Cash A/C #	char	35	The alternate cash account number of the global custodian, given to it by the next party in the settlement chain. For one level of clearing, the custodian is referred to and appears in the Local Agent data section, as he or she acts as the agent. For two levels of clearing, the global custodian should appear in the Custodian section, with the subcustodian's information appearing in the Local Agent section. SWIFT uses the following labels to identify the parties: RECU/DECU = Global custodian REAG/DEAG = Subcustodian/subagent/local agent BUYR/SELL = Investment manager
Alternate_Currency	Alternate Currency	char	3	The alternate currency if settlement takes place in a currency other than the one specified in the Payment Currency field. For example: US$ in Singapore. The sender of a SWIFT settlement instruction can use the value in this field to populate an indicator in a message. It instructs the recipient (custodian) to buy (FXIB) or sell (FXIS) the currency necessary to settle the trade.
Cash_AC_no	Cash A/C#	char	35	The cash account number of the global custodian, given to it by the next party in the settlement chain. For one level of clearing, the custodian is referred to and appears in the Local Agent data section, as he or she acts as the agent. For two levels of clearing, the global custodian should appear in the Custodian section, with the subcustodian's information appearing in the Local Agent section. For foreign exchange instructions, this field contains the account number at the local agent. SWIFT uses the following labels to identify the parties: RECU/DECU = Global custodian REAG/DEAG = Subcustodian/subagent/local agent BUYR/SELL = Investment manager
Corresp_Address_1	Correspondent Address 1	char	35	When the Correspondent Relationship field is set to Correspondent (C), these are the first 35 characters of the street of the cash correspondent bank. The global custodian chooses a cash correspondent bank when it does not clear cash through the subcustodian. (The cash correspondent bank is known as the ACCW by SWIFT.) When the Correspondent Relationship field is set to Subagent (S), these are the first 35 characters of the first intermediary's street. (The first intermediary is known as the REI1/DEI1 by SWIFT.)
Corresp_Address_2	Correspondent Address 2	char	35	When the Correspondent Relationship field is set to Correspondent (C), these are the second 35 characters of the street of the cash correspondent bank. The global custodian chooses a cash correspondent bank when it does not clear cash through the subcustodian. (The cash correspondent bank is known as the ACCW by SWIFT.) When the Correspondent Relationship field is set to Subagent (S), these are the first 35 characters of the first intermediary's street. (The first intermediary is known as the REI1/DEI1 by SWIFT.)
Corresp_BIC	Correspondent BIC	char	11	When the Correspondent Relationship field is set to Correspondent (C), this is the BIC of the cash correspondent bank. The global custodian chooses a correspondent bank when it does not settle cash through the subcustodian. (The cash correspondent bank is known as the ACCW in SWIFT.) When the Correspondent Relationship field is set to Subagent (S), this is the BIC of the first intermediary. (The first intermediary is known as the REI1/DEI1 by SWIFT.)
Corresp_Cash_A_No	Correspondent Cash A/C#	char	35	Can be used only if the Correspondent Relationship field is set to Correspondent (C). In this case, it is the global custodian's cash account number at the cash correspondent bank. The global custodian chooses the cash correspondent bank when it does not clear cash through the subcustodian. For foreign exchange instructions, this field contains the beneficiary’s account number at the intermediary (when three parties are involved). The cash correspondent bank is known as the ACCW by SWIFT. The global custodian is known as the RECU/DECU by SWIFT.
Corresp_City	Correspondent City	char	35	When the Correspondent Relationship field is set to Correspondent (C), this is the city of the cash correspondent bank. The global custodian chooses the cash correspondent bank when it does not clear cash through the subcustodian. (The cash correspondent bank is known as the ACCW by SWIFT.) When the Correspondent Relationship field is set to Subagent (S), this is the first intermediary's city. (The first intermediary is known as the REI1/DEI1 by SWIFT.)
Corresp_Country	Correspondent Country	char	2	When the Correspondent Relationship field is set to Correspondent (C), this is the country of the cash correspondent bank. The global custodian chooses the cash correspondent bank when it does not clear cash through the subcustodian. (The cash correspondent bank is known as the ACCW by SWIFT.) When the Correspondent Relationship field is set to Subagent (S), this is the first intermediary's country. (The first intermediary is known as the REI1/DEI1 by SWIFT.)
Corresp_Locality	Correspondent Locality	char	35	When the Correspondent Relationship field is set to Correspondent (C), this is the state or province of the cash correspondent bank. The global custodian chooses the cash correspondent bank when it does not clear cash through the subcustodian. (The cash correspondent bank is known as the ACCW by SWIFT.) When the Correspondent Relationship field is set to Subagent (S), this is the first intermediary's state or province. SWIFT refers to the first intermediary as REI1/DEI1.
Corresp_Name_1	Correspondent Name 1	char	35	When the Correspondent Relationship field is set to Correspondent (C), these are the first 35 characters of the name of the cash correspondent bank. The global custodian chooses the cash correspondent bank when it does not clear cash through the subcustodian. (The cash correspondent bank is known as the ACCW by SWIFT.) When the Correspondent Relationship field is set to Subagent (S), these are the first 35 characters of the name of the first intermediary. SWIFT refers to the first intermediary as REI1/DEI1.
Corresp_Name_2	Correspondent Name 2	char	35	When the Correspondent Relationship field is set to Correspondent (C), these are the second 35 characters of the name of the cash correspondent bank. The global custodian chooses the cash correspondent bank when it does not clear cash through the subcustodian. (The cash correspondent bank is known as the ACCW by SWIFT.) When the Correspondent Relationship field is set to Subagent (S), these are the second 35 characters of the name of the first intermediary. SWIFT refers to the first intermediary as REI1/DEI1.
Corresp_Post_Code	Correspondent Post Code	char	15	When the Correspondent Relationship field is set to Correspondent (C), this is the post code, zip code, etc. of the cash correspondent bank. The global custodian chooses the cash correspondent bank when it does not clear cash through the subcustodian. (The cash correspondent bank is known as the ACCW by SWIFT.) When the Correspondent Relationship field is set to Subagent (S), this is the first intermediary's post code, zip code, and so on. SWIFT refers to the first intermediary as the REI1/DEI1.
Relationship	Correspondent Relationship	char	1	Defines the party details stored in the Correspondent fields. Can be set either to C (Correspondent), which indicates a cash correspondent in the settlement chain, or S (Subagent), which indicates an intermediary in the settlement chain. For example, it could be used to allow for the listing of a cash correspondent or another subcustodian level.
Corresp_Sec_AC_No	Correspondent Security A/C#	char	35	Can be used only if the Correspondent Relationship field is set to Subagent (S). For three levels of clearing, this is the security account number of the global custodian with their intermediary. The first intermediary is known as the REI1/DEI1 by SWIFT. The subcustodian/subagent or clearing agent is known as the REAG/DEAG by SWIFT.
Custodian_Address_1	Custodian Address 1	char	35	The first 35 characters of the global custodian bank's street. SWIFT refers to the global custodian as the RECU/DECU or BENM. For one level of clearing, the global custodian information must be left blank. In this scenario, the subagent is the same entity as the global custodian; therefore, data must be entered only in the Local Agent fields
Custodian_Address_2	Custodian Address 2	char	35	The second 35 characters of the global custodian bank's street. SWIFT refers to the global custodian as the RECU/DECU or BENM. For one level of clearing, the global custodian information must be left blank. In this scenario, the subagent is the same entity as the global custodian; therefore, data must be entered only in the Local Agent fields.
Custodian_BIC	Custodian BIC	char	11	The global custodian bank's BIC. SWIFT refers to the global custodian as the RECU/DECU or BENM. For one level of clearing, the global custodian information must be left blank. In this scenario, the subagent is the same entity as the global custodian; therefore, data must be entered only in the Local Agent fields
Custodian_City	Custodian City	char	35	The global custodian bank's city. SWIFT refers to the global custodian as the RECU/DECU or BENM. For one level of clearing, the global custodian information must be left blank. In this scenario, the subagent is the same entity as the global custodian; therefore, data must be entered only in the Local Agent fields.
Custodian_Country	Custodian Country	char	2	The global custodian bank's country. SWIFT refers to the global custodian as the RECU/DECU or BENM. For one level of clearing, the global custodian information must be left blank. In this scenario, the subagent is the same entity as the global custodian; therefore, data must be entered only in the Local Agent fields
Custodian_Locality	Custodian Locality	char	35	The global custodian bank's state or province. SWIFT refers to the global custodian as the RECU/DECU or BENM. For one level of clearing, the global custodian information must be left blank. In this scenario, the subagent is the same entity as the global custodian; therefore, data must be entered only in the Local Agent fields
Custodian_Name_1	Custodian Name 1	char	35	The first 35 characters of the global custodian bank's name. SWIFT refers to the global custodian as the RECU/DECU or BENM. For one level of clearing, the global custodian information must be left blank. In this scenario, the subagent is the same entity as the global custodian; therefore, data must be entered only in the Local Agent fields.
Custodian_Name_2	Custodian Name 2	char	35	The second 35 characters of the global custodian bank's name. SWIFT refers to the global custodian as the RECU/DECU or BENM. For one level of clearing, the global custodian information must be left blank. In this scenario, the subagent is the same entity as the global custodian; therefore, data must be entered only in the Local Agent fields
Custodian_Post_Code	Custodian Post Code	char	15	The global custodian bank's post code, zip code, and so on. SWIFT refers to the global custodian as the RECU/DECU or BENM. For one level of clearing, leave the global custodian information blank. In this scenario, the subagent is the same entity as the global custodian. Therefore, enter data only in the Local Agent fields
ID_2	ID 2	char	35	Another means of identification used by a depository, such as a DTC Agent ID number or a CHESS HID number. The name of this field changes to the relevant name for the local identifier when certain methods are selected. For US-DTC settlement instructions, ID 2 (Agent ID) is required and validated against DTC master files.
ID_3	ID 3	char	35	Another means of participant identification used by a depository, such as a DTC Institution ID number. The name of this field changes to the relevant name for the local identifier when certain methods are selected. For US-DTC settlement instructions, ID 3 (Inst/Broker ID) is required and validated against DTC master files.
ID_4	ID 4	char	35	Another means of identification that a depository can use. Only applicable in settlement instructions for India and Brazil when the method is one of the following: Central Depository Services Ltd. (INCSD) National Securities Depository Ltd. (NSDL) The Reserve Bank of India (RBI) Companhia Brasilieira de Liquidacao e Custodia (BOVESPA). This field is not available if you use DTD version 6 or less.
ID_5	ID 5	char	35	Another means of identification used by a depository. Only applicable in settlement instructions for India and Brazil when the method is one of the following: Central Depository Services Ltd. (INCSD) National Securities Depository Ltd. (NSDL) Reserve Bank of India (RBI) Companhia Brasilieira de Liquidacao e Custodia (BOVESPA). This field is not available if you use DTD version 6 or less.
Institution_BIC	Institution/Executing Broker BIC	char	11	The BIC of the investment manager. The investment manager is known as the BUYR/SELL by SWIFT
Institution_Contact	Institution/Executing Broker Data Contact	char	35	The name of the contact at the investment manager.
Institution_Name	Institution/Executing Broker Data Name	char	70	The name of the investment manager. This field is not available if you use DTE version 6 or less.
Institution_Phone	Institution Phone	char	20	The telephone number of the contact at the investment manager.
IP_1_AC_No	Interested Party 1 A/C#	char	12	The first interested party’s account number when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_1_BIC	Interested Party 1 BIC	char	11	The first interested party’s BIC when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_1_Contact	Interested Party 1 Contact	char	35	The first interested party’s contact name when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_1_ID	Interested Party 1 ID	char	8	The first interested party’s ID when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_1_Name	Interested Party 1 Name	char	70	The first interested party’s name when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_1_Phone	Interested Party 1 Phone	char	20	The first interested party’s phone number when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_1_Special_Instr_1	Interested Party 1 Spec Instr 1	char	35	The first interested party’s special instructions when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_1_Special_Instr_2	Interested Party 1 Spec Instr 2	char	35	The first interested party’s additional special instructions when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_2_AC_No	Interested Party 2 A/C#	char	25	The second interested party’s account number when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_2_BIC	Interested Party 2 BIC	char	11	The second interested party’s BIC when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_2_Contact	Interested Party 2 Contact	char	35	The second interested party’s contact name when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_2_ID	Interested Party 2 ID	char	8	The second interested party’s ID when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_2_Name	Interested Party 2 Name	char	70	The second interested party’s name when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_2_Phone	Interested Party 2 Phone	char	20	The second interested party’s phone number when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_2_Special_Instr_1	Interested Party 2 Spec Instr 1	char	35	The second interested party’s special instructions when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_2_Special_Instr_2	Interested Party 2 Spec Instr 2	char	35	The second interested party’s additional special instructions when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_3_AC_No	Interested Party 3 A/C#	char	25	The third interested party's account number when DTC is used as the clearing method. Used to send trade confirmations by DTC. The Interested Party 3 BIC and Interested Party 3 Name fields may also be used to specify the party to whom DTCC should sent MT54X messages, if the following are true: The investment manager is using DTCC settlement notification. This is a different party from the party specified in the Custodian BIC field or the Local Agent BIC field. In this case, leave all Interested Party 3 fields (other than BIC and Name) blank.
IP_3_BIC	Interested Party 3 BIC	char	11	The third interested party's BIC when DTC is used as the clearing method. Used to send trade confirmations by DTC. The Interested Party 3 BIC and Interested Party 3 Name fields may also be used to specify the party to whom DTCC should sent MT54X messages, if the following are true: The investment manager is using DTCC settlement notification This is a different party from the party specified in the Custodian BIC field or the Local Agent BIC field. In this case, leave all Interested Party 3 fields (other than BIC and Name) blank.
IP_3_Contact	Interested Party 3 Contact	char	35	The third interested party’s contact name when DTC is used as the clearing method. Used to send trade confirmations by DTC. The Interested Party 3 BIC and Interested Party 3 Name fields may also be used to specify the party to whom DTCC should sent MT54X messages, if the following are true: The investment manager is using DTCC settlement notification This is a different party from the party specified in the Custodian BIC field or the Local Agent BIC field. In this case, leave all Interested Party 3 fields (other than BIC and Name) blank.
IP_3_ID	Interested Party 3 ID	char	8	The third interested party’s ID when DTC is used as the clearing method. Used to send trade confirmations by DTC. The Interested Party 3 BIC and Interested Party 3 Name fields may also be used to specify the party to whom DTCC should sent MT54X messages, if the following are true: The investment manager is using DTCC settlement notification This is a different party from the party specified in the Custodian BIC field or the Local Agent BIC field. In this case, leave all Interested Party 3 fields (other than BIC and Name) blank.
IP_3_Name	Interested Party 3 Name	char	70	The third interested party’s name when DTC is used as the clearing method. Used to send trade confirmations by DTC. The Interested Party 3 BIC and Interested Party 3 Name fields may also be used to specify the party to whom DTCC should sent MT54X messages, if the following are true: The investment manager is using DTCC settlement notification This is a different party from the party specified in the Custodian BIC field or the Local Agent BIC field. In this case, leave all Interested Party 3 fields (other than BIC and Name) blank.
IP_3_Phone	Interested Party 3 Phone	char	20	The third interested party’s phone number when DTC is used as the clearing method. Used to send trade confirmations by DTC. The Interested Party 3 BIC and Interested Party 3 Name fields may also be used to specify the party to whom DTCC should sent MT54X messages, if the following are true: The investment manager is using DTCC settlement notification This is a different party from the party specified in the Custodian BIC field or the Local Agent BIC field. In this case, leave all Interested Party 3 fields (other than BIC and Name) blank.
IP_3_Special_Instr_1	Interested Party 3 Spec Instr 1	char	35	The third interested party’s special instructions when DTC is used as the clearing method. Used to send trade confirmations by DTC.
IP_3_Special_Instr_2	Interested Party 3 Spec Instr 2	char	35	The third interested party's additional special instructions when DTC is used as the clearing method. Used to send trade confirmations by DTC.
Participant_Name_1	Participant Name 1	char	35	The first 35 characters of the name of the member/participant in ID 1, also known in SWIFT as the REAG/DEAG.
Participant_Name_2	Participant Name 2	char	35	The second 35 characters of the name of the member/participant in ID 1, also known in SWIFT as the REAG/DEAG.
Payment_Currency	Payment Currency	char	3	The currency in which settlement takes place.
PSET	Place of Settlement	char	11	The central depository's BIC, known as the PSET by SWIFT. Per the SMPG, use the stock exchange BIC when no CSD exists in a market. Use Country Code only for physical settlements. Country Code is the same as the country in the Country-Security-Method combination, but requires the ISO country format.
Reg_Address_1	Registration Address 1	char	35	The first 35 characters of the beneficial owner's street. It is part of the post-settlement process and is utilized when the subcustodian is settling securities in physical form. SWIFT refers to the subcustodian as the REAG/DEAG
Reg_Address_2	Registration Address 2	char	35	The second 35 characters of the beneficial owner's street. It is part of the post-settlement process and is utilized when the subcustodian is settling securities in physical form. SWIFT refers to the subcustodian REAG/DEAG.
Reg_BIC	Registration BIC	char	11	The beneficial owner’s BIC.
Reg_City	Registration City	char	35	The beneficial owner's city. It is part of the post-settlement process and is utilized when the subcustodian is settling securities in physical form. SWIFT refers to the subcustodian as the REAG/DEAG.
Reg_Country	Registration Country	char	2	The beneficial owner's country. It is part of the post-settlement process and is utilized when the subcustodian is settling securities in physical form. SWIFT refers to the subcustodian as the REAG/DEAG.
Reg_Locality	Registration Locality	char	35	The beneficial owner's state or province. It is part of the post-settlement process and is utilized when the subcustodian is settling securities in physical form. SWIFT refers to the subcustodian as the REAG/DEAG.
Reg_Name_1	Registration Name 1	char	140	The beneficial owner name of the securities held at the depository when omnibus accounts are not permitted or used. It is part of the post-settlement process and is utilized when the subcustodian is settling securities in physical form. SWIFT refers to the subcustodian as the REAG/DEAG.
Reg_Post_Code	Registration Post Code	char	15	The beneficial owner's post code, zip code, or equivalent. It is part of the post-settlement process and is utilized when the subcustodian is settling securities in physical form. SWIFT refers to the subcustodian as the REAG/DEAG.
Settlement_Contact	Settlement Contact	char	35	The name of the contact at the subcustodian (one level of clearing) or at the global custodian (two or more levels of clearing). The subcustodian is known as the REAG/DEAG by SWIFT. The global custodian is known as the RECU/DECU by SWIFT.
Settlement_Phone	Settlement Phone	char	20	The phone number of the contact at the subcustodian (one level of clearing) or at the global custodian (two or more levels of clearing). The subcustodian is known as the REAG/DEAG by SWIFT. The global custodian is known as the RECU/DECU by SWIFT.
Special_Instr_1	Special Instr 1	char	35	Special instructions related to the settlement contact from the Settlement Contact and Settlement Phone fields. Can also be used for any other miscellaneous information relating to the settlement not entered elsewhere in the instruction.
Special_Instr_2	Special Instr 2	char	35	Additional special instructions related to the settlement contact from the Settlement Contact and Settlement Phone fields. Can also be used for any other miscellaneous information relating to the settlement not entered elsewhere in the instruction.
Lca_AC_Ref_1	Local A/C Ref 1	char	35	The first 35 characters of the account name of the entity that has the account at the local agent. For one level of clearing, leave the global custodian information blank. For two levels of clearing, it is the name of the global custodian's account at the subcustodian/subagent/local agent. If there is an intermediary, it is the intermediary’s account at the subcustodian/subagent/local agent. SWIFT uses the following labels to identify the parties: RECU/DECU = Global custodian REAG.DEAG = Subcustodian/subagent/local agent REI1/DEI1 = Intermediary
Lca_AC_Ref_2	Local A/C Ref 2	char	35	The first 35 characters of the account name of the entity that has the account at the local agent. For one level of clearing, leave the global custodian information blank. For two levels of clearing, it is the name of the global custodian's account at the subcustodian/subagent/local agent. If there is an intermediary, it is the intermediary’s account at the subcustodian/subagent/local agent. SWIFT uses the following labels to identify the parties: RECU/DECU = Global custodian REAG.DEAG = Subcustodian/subagent/local agent REI1/DEI1 = Intermediary
Lca_Agent_Address_1	Local Agent Address 1	char	35	The first 35 characters of the local agent’s street. It is the entity that will settle the transaction at the depository. (The local agent is known as the REAG/DEAG by SWIFT.) Key subagent information must always be populated because this is the entity that settles the transaction at the depository.
Lca_Agent_Address_2	LocalAgent Address 2	char	35	The second 35 characters of the local agent’s street. It is the entity that will settle the transaction at the depository. SWIFT refers to the local agent as the REAG/DEAG. Key subagent information must always be populated because this is the entity that settles the transaction at the depository.
Lca_Agent_BIC	Local Agent BIC	char	11	The local agent's BIC. This is the entity that will settle the transaction at the depository. SWIFT refers to the local agent is known as the REAG/DEAG. Key subagent information must always be populated because this is the entity that will settle the transaction at the depository.
Lca_Agent_City	Local Agent City	char	35	The local agent's city. This is the entity that will settle the transaction at the depository. SWIFT refers to the local agent as the REAG/DEAG. Key subagent information must always be populated because this is the entity that will settle the transaction at the depository.
Lca_Agent_Country	Local Agent Country	char	2	The clearing agent's country. This is the entity who will settle the transaction at the depository. SWIFT refers to the clearing agent as the REAG/DEAG. Key subagent information must always be populated because this is the entity that will settle the transaction at the depository.
Lca_Agent_Locality	Local Agent Locality	char	35	The local agent's state or province. This is the entity that will settle the transaction at the depository. SWIFT refers to the local agent as the REAG/DEAG. Key subagent information must always be populated because this is the entity that will settle the transaction at the depository.
Lca_Agent_Name_1	Local Agent Name 1	char	35	The first 35 characters of the local agent’s name. This is the entity that will settle the transaction at the depository. (The local agent is known as the REAG/DEAG by SWIFT.) Key subagent information must always be populated because this is the entity that will settle the transaction at the depository.
Lca_Agent_Name_2	Local Agent Name 2	char	35	The second 35 characters of the local agent’s name. This is the entity that will settle the transaction at the depository. SWIFT refers to the local agent as the REAG/DEAG. Key subagent information must always be populated because this is the entity that will settle the transaction at the depository.
Lca_Agent_Post_Code	Local Agent Post Code	char	15	The local agent's post code, zip code, or equivalent. This is the entity that will settle the transaction at the depository. SWIFT refers to the local agent as the REAG/DEAG. Key subagent information must always be populated because this is the entity that will settle the transaction at the depository.