2.13.3.1 SWIFT Routing

This task provides information on SWIFT routing.

• The Current Existing screen SWIFT Entity Maintenance is used to maintain DN address for SWIFT Entities.
• To support Routing of UH/Transaction SWIFT message. The Mapped Entity Type LOV has been enhanced to display a new Entity Type ‘Z – Agency Branch Module’ and Mapped Entity ID LOV has been enhanced to list all Agency Branch Module ID of the current FMG module.
• The user needs to choose Entity Type – S [Installation ID], pick the Installed Entity ID from LOV and map the associated Agency Branch Module ID to identify DN address in Unitholder SWIFT message Processing.
• DN address used for Agency branch module cannot be duplicated for another Installation [Entity Type- S]. Incoming SWIFT message coming into the system will have the tags <Requestor> and <Responder>. The <Responder> tag is the DN address of the specific module in which the message is processed.
• The DN address mentioned in the <Responder> tag to be searched in the DN addresses maintained in the system for SWIFT Entity Type S.
• Once the DN address is matched with maintained list, Systems will identify Module ID from the maintenance and process the Unitholder records.
• If there is no module mapping found for DN address, then the system will reject the message.
• During Unit holder creation as part of Swift Processing, AMC ID/Distributor ID field is to be derived from the value of AccountServicer <AcctSvcr><AnyBIC> tag.
• If the value derived from Account servicer is not matching with entities maintained in the system, then system will raise the error.
• If there is no AccountServicer <AcctSvcr> tag as part of incoming message, then the system will derive the value of AMC ID/Distributor ID field as below Transaction Processing:

  Table 2-18 Installation Type and Value

  Installation Type	Value of AMC ID/Distributor ID
  AMC	Default AMC ID
  Distributor	Default Distributor ID/ Agent code

• Agency Branch Module ID derivation for Transaction is based on Client Country Parameterization.
• The Client country SWIFTTXNAGENT is available in the system and if client country is ON, then system will derive the DN address using Receiver DN and same will be used for transaction processing. If DN address is not matching with maintenance available, then system will raise the error.
• If the client country is switched OFF, then the system will use the UH module to process the transaction.