2.22.1 Tags in Messages

This topic provides information on Redemption Bulk Order and its tags in messages.

Message Identification

Table 2-52 Message Identification

Field	Description	Attributes
Message Identification	This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages. This number is used for storage and reference.	Mandatory
Reference	Incoming: This number is used for storage and reference. Outgoing: This will be generated by the system and will be unique for group of transactions in a fund.	Mandatory
Creation Date Time	This is applicable for incoming and outgoing message. This is the message generation date time.	Optional

Pool Reference

Table 2-53 Pool Reference

Field	Description	Attributes
Pool Reference	This is a collective reference to identify set of messages.	Optional
Reference	Incoming: This number is used for storage. Outgoing: If a set of orders is to be broken, system will assign a common reference number to multiple messages.	Mandatory

Bulk Order Details

Table 2-54 Bulk Order Details

Field	Description	Attributes
Bulk Order Details	Specify the details.	Mandatory
Financial Instrument Details	This tag provides details to identify a fund.	Mandatory
Identification	The fund can be identified based on the ISIN, Alternate Identification, RIC, Ticker Symbol, Bloomberg, CTA or Common. Incoming: FCIS supports identification based on the ISIN or Ticker Symbol. For other options, it will use the UDF mapping relevant for this tag. Outgoing: FCIS sends out the fund ISIN.	Mandatory
Individual Order Details	Specify the details.	(Mandatory / Repetitive)
Order Reference	This is a unique identifier for an order, as assigned by the instructing party. Incoming - This will be stored as part of SWIFT transaction log with corresponding FCIS transaction number. Outgoing - This will be the Transaction Number generated by FCIS.	Mandatory
Investment Account Details	Specify the details.	Mandatory
Account Identification  Proprietary  Identification	This tag is to identify an investor’s account. However, incase of a service provider installation, priority would be given to OwnerDetails tag to get the identification type and identification number. Incoming: The system uses the relevant UDF mapping for this tag. Outgoing: The system uses the relevant UDF mapping for this tag.	Mandatory
Beneficiary Details	Specify the details.	Optional
Other Identification  Identification	Incoming: This would map to the Identification Number of the Unit holder.	Mandatory
Other Identification  Identification Type	Incoming : FCIS uses data mapping to find the Unit holder account type.	Mandatory
Choice for Units / Net Amount/Holdings Redemption Rate	Incoming: The system determines the Transaction Mode and Value depending on the element available. If the field ‘NetAmt’ is provided, the mode of transaction will be ‘Net’. The value here would be in the currency provided as an attribute of the tag. FCIS will give priority to the tag ‘GrossAmount’ while processing the message. If the same is available, the transaction will be considered ‘Gross’. Outgoing : Values of the outgoing message will depend on the transaction mode. Net Amount transactions in FCIS, will be reported in the field ‘NetAmt’. The transaction currency will be passed as tag attribute. However, if the transaction is ‘Gross’, the same will be reported under the optional tag ‘GrossAmount’ as well as the tag ‘NetAmt’, as this is mandatory.	Mandatory
Gross Amount	Incoming: If a value is provided in this field the transaction will be considered as a gross amount transaction. The transaction currency would be defaulted to the currency code provided in the attribute. Outgoing: If the tag ‘GrossOrNet’ carries the value ‘G’, the amount will be passed under this tag. The transaction currency will be passed as a tag attribute.	Optional
Foreign Exchange Details	This is information related to currency exchange or conversion. Incoming: If the Transaction Currency is different from the Fund Base currency, FCIS will use the information provided to override the exchange rate. The Exchange Rate Source will be defaulted from the Bulk Transaction Maintenance for the bulk client ‘SWIFT’. Outgoing : If the transaction is a cross currency transaction, the exchange rate details will be provided in the message. The following sub tags are mandatory: Unit Currency: This will be the transaction currency Quoted Currency: This will be the fund base currency Exchange Rate: This will be the exchange rate for the transactions	Optional
Physical Delivery Indicator	This tag indicates whether or not the financial instrument is to be physically delivered. Outgoing: This indicator will depend on whether or not fund is scrip based.	Mandatory
Payment Instrument Choice	The payment instruments can be cheque, credit transfer, direct debit, and investment account or payment card. FCIS would not support cheque, payment card as mode of payment in the current release for outgoing orders. However, for incoming orders FCIS would support these payment modes and ignore the fields that are not currently supported. If payment instrument details are not provided, FCIS would use default bulk transaction setup for “SWIFT”.	Optional
Cash Settlement Date	Incoming/Outgoing – Both, the Incoming and Outgoing indicators, will be the Transaction Settlement Date.	Optional
Payment Instrument	The payment instruments can be cheque, credit transfer, direct debit, investment account or payment card. FCIS would not support cheque, payment card as mode of payment in the current release for outgoing orders. However, for incoming orders FCIS would support these payment modes and ignore the fields that are not currently supported. If payment instrument details are not provided, FCIS would use default bulk transaction setup for “SWIFT”.	Optional
Credit Transfer Details	Specify the details	(Mandatory / Choice)
Reference	Incoming/Outgoing: This will be the TransactionReferenceNumber	Optional
Creditor Details  Account Identification  Identification	FCIS supports DomesticAccount based identification. Incoming: The details available for DomesticAccount will be used in conjunction with the element details of the tag FirstAgent to determine the Unit Holder bank details available in FCIS. FCIS will check if the account number mentioned is valid for the transaction currency. If not, these account details will be considered as third party payment details. Outgoing: If the transaction payment mode is money transfer, the account details will be provided for the transaction. Money transfer direct debit will not be applicable for this tag.	Mandatory
Creditor Details  Account Identification  Name	This is the name of the account. It provides additional means of identification. Outgoing: This will be the TransferAccountHolderName of the transaction.	Optional
Creditor Details  Final Agent	FCIS supports BIC and Proprietary Identification based identification. Incoming: If BIC is provided, the system will get the relevant bank information, if available. FCIS will use the Bank Code, Account Number and Transaction Currency to get the banking details for the Unit Holder. If ProprietaryIdentification is provided, the UDF mapping for the field will be used to determine the bank. This will be a set of other information fields applicable for entity type ‘Bank’. If these bank account details do not match with unit holders banking details, the transaction will be captured as the third party payment details, provided the bank entity information is setup in FCIS. Outgoing: As FCIS is capable of supporting the elements BIC and ProprietaryIdentification, the SWIFT UDF mapping will be used to determine the element that client would want to send.	Mandatory
Cheque Details	Outgoing: This tag will be passed for transactions with payment mode as ‘Cheque’. FCIS will support PayeeIdentification (BIC / ProprietaryIdentiification) to identify the unit holder receiving the payment proceeds. SWIFT UDF mapping will be provided.	(Mandatory / Choice)
Account Details	Specify the details	(Mandatory / Choice)
Account Identification  Proprietary  Identification	Incoming : This will be the bank account number of the unit holder. This number will be used in conjunction with the element Type  Structured i.e., the bank account type, to get the bank details of unit holder. Outgoing : If the bank details selected for the transaction is a CPF accounts (CPFOA, CPFSA, ASPFOA, ASPFSA or SRS), the system will provide the structured account type information under this element.	Mandatory
Type  Structured	For more information on the strcutured codes, refer Table 2-55.	Mandatory

Table 2-55 Structured codes

Structured codes	FCIS Map
CASH	No mapping
CPFO	CPFOA
CPFS	CPFSA
OTHR	ASPFOA / ASPFSA
SRSA	SRS