The Oracle FLEXCUBE Investor Servicing (FCIS) system provides the facility of processing incoming and outgoing messages at an AMC / Distributor installation, over the SWIFT (Society for Worldwide Inter bank Financial Telecommunication) network.
This chapter contains the following sections:
This section contains the following topics:
This section contains the following topics:
You will need to carry certain maintenances for the generation of SWIFT messages, in the ‘Swift Message Setup Maintenance Detail’ screen. This screen can be used to define parameters applicable for individual messages such as the trigger events, entities involved in the communication etc. You can invoke the ‘Swift Message Setup Maintenance Detail’ screen by typing ‘UTDSWMSG’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Note
Depending on the Message Type and Message Code that you select, certain fields will be displayed.
Select ‘New’ from the Actions menu in the Application tool bar or click new icon to enter the details of the Swift message setup maintenance.
Swift Details displays the following fields:
Message Reference Code
Alphanumeric; 35 Characters; Mandatory
Enter a unique reference number for the message.
Message Code
Alphanumeric; 3 Characters; Mandatory
Specify the message code.
Note
Certain other fields will be displayed in this screen, depending on the option you select against the field Message Code.
Medium
Mandatory
Select the option ‘In’ to indicate the message will be an incoming message. Select the option ‘Out’ to indicate the message is an outgoing message.
Note
Certain other fields will be displayed in this screen, depending on the option you select against the field Message Type.
Trigger Option
Optional
The trigger for generating the message may be an Auto or Manual. Select the appropriate option. from the drop-down list.
This field is enabled only if you have selected the ‘Medium’ as ‘OUT’.
Trigger Method
Optional
Select the trigger method from the drop-down list. The list displays the following values:
This field is enabled only if you have selected the ‘Trigger’ as ‘Auto’.
In case of event based messages the message will be generated on the occurrence of the event. For instance, if the event is End of Day, then the message will be generated as soon as the system completes the End of Day activity.
If the Trigger Method is Time Based, you can enter a specific business day, say 2nd working day of the month.
The system will automatically generate the SWIFT outgoing message as per the frequency or date mentioned if trigger is time-based. In case of time based setup the message will be generated on the occurrence of scheduled date and time. In case of event based setup the message will be generated on the occurrence of the event.
Generate Auth Transactions
Optional
Select ‘Yes’ from the drop-down list if an incoming transaction request should be created as an authorized transaction.
Note
This field will be enabled only if the Message Type is ‘IN’ and the Message Code is an Order or Cancellation message.
Confirm Outgoing Messages
Optional
Select ‘Yes’ from the drop-down list to indicate the message needs to be manually confirmed. This is applicable only to FCIS initiated messages only and not messages which are in response to SWIFT requests.
Note
This field will be displayed only if the Message Type is ‘OUT’.
Global Order
Optional
Global order are orders sent from distributors to AMC to subscribe on behalf of the distributor's customers. Select ‘Yes’ from the drop-down list to indicate a global order should be generated.
Note
This field will be enabled only if the Message Type is ‘OUT’ and the Message Code is a multiple order message.
Event Code
Alphanumeric; 20 Characters; Mandatory if the Trigger is ‘Event’
Select the event upon which the message should be generated.
Note
This field will be:
To Entity Type
Alphanumeric; 1 Character; Optional
Select the Entity Type for which the message will be generated.
Note
For all Message Codes other than ‘Price Report’ messages, the option ‘AMC’ will be displayed in this field. You will not be allowed to change the same.
To Entity ID
Alphanumeric; 1 Character; Optional
Select the entity for which the message is applicable.
Note
This field will be displayed only if the Message Type is ‘OUT’.
Split Required
Optional
Select if split is required or not from the drop-down list. The list displays the following values:
Max Length
Display
The system displays the message length as ISO20022 (100000) and ISO15022 (10000)
Frequency
Alphanumeric; 1 Character; Optional
Specify the frequency code. Alternatively, you can select the frequency code from the option list. The list displays all valid frequency code maintained in the system.
This field is enabled only if you have selected the ‘Trigger Method’ as ‘Time Based’.
Specific Date
Date Format; Optional
Select the specific date from the adjoining calendar.
Day
Optional
Select the day from the drop-down list.
Month
Optional
Select the month from the drop-down list.
Time (HH24:MI)
Time Format; Optional
Specify the time format.
Actual Run Date Time
Display
The system displays the actual run date and time.
Next Run Date Time
Display
The system displays the Next Run Date and time.
AMC ID
Alphanumeric; 12 Characters; Optional
Specify the AMC ID.
Legal Entity
Alphanumeric; 12 Characters; Optional
Specify the legal entity code.
Holiday Rule
Optional
Select the holiday rule from the drop-down list. The list displays the following values:
Split Message by Fund
Optional
Check this box to split the message by fund.\
This check box is enabled only for PriceReportV04 message, i.e., when price report is selected.
Applicable Ref Types
Alphanumeric; 2 Characters; Optional
For FCIS initiated orders, you can specify the Transaction Reference Types applicable to the outgoing message. The ones available for selection will be displayed in the adjoining option list. You can choose the appropriate one.
Ref Type Description
Display
Upon Selection of the applicable reference type, the description of the selected reference type gets displayed.
Applicable Account Types
Alphanumeric; 2 Characters; Optional
For FCIS initiated orders, you can specify the account types which are allowed. The ones available for selection will be displayed in the adjoining option list. You can choose the appropriate one.
Account Type Description
Display
Upon Selection of the applicable account type, the description of the selected account type gets displayed.
Click ‘Applicable UH Button’ to select one or multiple unitholder IDs / unitholder Names for which the outgoing message must be generated.
You can specify the following details:
Unit Holder ID
Alphanumeric; 12 Characters; Optional
Specify the unit holder ID. Alternatively, you can select the unit holder ID from the option list. The list displays all valid unit holder ID maintained in the system.
CIF Number
Alphanumeric; 12 Characters; Optional
Specify the CIF number. Alternatively, you can select the CIF number from the option list. The list displays all valid CIDF number maintained in the system.
Status
Optional
Select the status from the drop-down list. The list displays the following values:
UH Category
Alphanumeric; 2 Characters; Optional
Specify the unit holder category. Alternatively, you can select the unit holder category from the option list. The list displays all valid unit holder category maintained in the system.
A/C Operation Type
Optional
Select the account operation type from the drop-down list. The list displays the following details:
Module ID
Alphanumeric; 30 Characters; Optional
Specify the module ID. Alternatively, you can select the module ID from the option list. The list displays all valid module ID maintained in the system.
First Name
Alphanumeric; 105 Characters; Optional
Specify the first name.
Middle Name
Alphanumeric; 105 Characters; Optional
Specify the middle name.
Last Name
Alphanumeric; 105 Characters; Optional
Specify the middle name.
Identification Number
Alphanumeric; 50 Characters; Optional
Specify the identification number.
Reference Number
Alphanumeric; 12 Characters; Optional
Specify the reference number.
Investor Type
Optional
Select the investor type from the drop-down list. The list displays the following values:
Type Closed
Optional
Select the type closed from the drop-down list. The list displays the following values:
Tax ID
Alphanumeric; 50 Characters; Optional
Specify the tax ID.
Stop Account
Optional
Select if the account is stopped or not from the drop-down list. The list displays the following values:
AMC ID
Alphanumeric; 12 Characters; Optional
Specify the AMC ID. Alternatively, you can select the AMC ID from the option list. The list displays all valid AMC ID maintained in the system.
Date Of Birth
Date Format; Optional
Select the date of birth from the adjoining calendar.
Corporation Type
Alphanumeric; 3 Characters; Mandatory
Specify the corporation type. Alternatively, you can select the corporation type from the option list. The list displays all valid corporation type maintained in the system.
Select All
Optional
Check this box to select all the records.
Select all record in current page
Optional
Check this box to select all the records in current page.
Select ‘Search Unitholder’ button to display unit holder details.
Unitholder ID
Alphanumeric; 16 Characters; Mandatory
Specify the unit holder ID. Alternatively, you can select the unit holder ID from the option list. The list displays all valid unit holder ID maintained in the system.
UH Name
Display
The system displays the unit holder name for the selected unit holder ID.
The system will display the following details:
You can add single or all the records by clicking Add or Add All button. You can also remove all the record b clicking ‘Remove All’ button.
Click ‘Applicable Button’ to select one or multiple funds based on the search criteria.
You can specify the following details:
Fund ID
Alphanumeric; 6 Characters; Optional
Specify the fund ID. Alternatively, you can select fund ID from the option list. The list displays all valid fund ID maintained in the system.
Fund Name
Alphanumeric; 60 Characters; Optional
Specify the fund name. Alternatively, you can select fund name from the option list. The list displays all valid fund name maintained in the system.
Umbrella Fund
Optional
Select the umbrella fund from the drop-down list. The list displays the following values:
AMC ID
Alphanumeric; 12 Characters; Optional
Specify the AMC ID. Alternatively, you can select AMC ID from the option list. The list displays all valid AMC ID maintained in the system.
ISIN No
Alphanumeric; 12 Characters; Optional
Specify the ISIN Number. Alternatively, you can select ISIN number from the option list. The list displays all valid ISIN number maintained in the system.
Fund Ticker Symbol
Alphanumeric; 25 Characters; Optional
Specify the fund ticker symbol.
COE Enabled
Optional
Select if currency of Expression is enabled or not from the drop-down list. The list displays the following values:
Hedge Fund
Optional
Select if hedge fund is enabled or not from the drop-down list. The list displays the following values:
Select All
Optional
Check this box to select all the records.
Select all record in current page
Optional
Check this box to select all the records in current page.
Click ‘Search Fund’ button to display the fund details.
Fund ID
Alphanumeric; 6 Characters; Optional
Specify the fund ID. Alternatively, you can select the fund ID from the option list. The list displays all valid fund ID maintained in the system.
Fund Name
Display
The system displays the fund name for the selected fund ID.
The system will display the following details:
You can add single or all the records by clicking Add or Add All button. You can also revove all the record b clicking ‘Remove All’ button.
You can maintain only one record with default schema using ‘Default Schema’ in the ‘Module Creation’ table. These details are saved in FCISSCHEMALINKTBL.
If schema is not identified then the message will be routed to default schema from FCISSCHEMALINKTBL. Once the message is received, the system will check whether Related Reference or Previous Reference is available in the message. If it is available then the system will find the schema from mstm_msg_track table.
If Related Reference or Previous Reference is not available or cannot find schema from mstm_msg_track then the system will find the schema from DN address maintenance (based on the requester.
Whenever the following messages received in FCIS, the system will validate against the Fund cut-off time and apply the following logic:
If Cancellation request received after fund-cut off time:
If cancellation messages are received after fund cut-off time, then the system will reject the message by generating an Order Cancellation Status Report with the rejection code CUTO (Cut off time – Instruction has received after cut-off time).
If Cancellation request received within or before fund cut-off time:
If cancellation messages are received within or before fund cut-off time, then the system will accept the cancellation request required to be accepted and an Order Cancellation Status Report required to be generated with one of the following statuses:
The system will not generate the Confirmation Message until all the transactions in that Swift Bulk Order gets allotted. That is, if the Multiple Order contains 10 orders and only 8 orders got allotted then, the system will not generate the confirmation message immediately; rather it will generate after the rest of the 2 transactions get allotted.
The following Messages will be impacted:
The following messages are generated as per SWIFT message setup:
The system will receive <DeliveryTime> tag in the header section of the incoming message.The value of the Delivery Time will be stored in the system and during transaction creation this value will be used to determine the transaction date. If the tag DeliveryTime is not provided then system will consider the application date of that segment as the Transaction Date.
This value of Delivery Time and Date will be validated against the Fund Rule such as Transaction Cut Off etc. The dealing date for the transaction will be calculated based on the calculated transaction Date.
The <DeliveryTime> tag will be used in only Transaction upload related incoming messages such as SubscriptionBulkOrderV03, RedemptionBulkOrderV03, SwitchOrderV03, RedemptionOrderV03, SubscriptionOrderV03.
In case of other incoming messages such as OrderConfirmationStatusReportV01 this Delivery Time if passed will only be stored but will not be used in any kind of processing.
The <DeliveryTime> tag will contain the date and time of the time zone where the transaction will be uploaded. The time will be matched against the Application Date of that segment/Schema where the transaction is getting created and will be converted into local time. If the Delivery Date is back dated/future dated then the back dating/future dated rule will be applied.
The incoming message “OrderConfirmationStatusReportV01 (setr.057.001.01) will state the status of the order confirmation which was sent from the system to the sender of the order. The message received will be stored in the system in a new storage structure for each transaction number. The whole message can be viewed in the incoming message browser. The message will be stored as per each transaction.
The transaction number will be selected on the basis of the order reference number sent in the status message and also present in the Order Confirmation status Report message. The transactions order reference number present in the status message can be one or more than one. When the order messages are processed by the system, the system stores the order reference number of those uploaded transactions in the system. So when the order confirmation status report message is received, the system can match the order Reference number present in the status message with the order reference number of the upload transaction to get the FCIS transaction number.The complete cycle of a transaction is as follows
The error codes which will be provided in the confirmation status message will only be stored in the system. The statuses which will be stored in the system are as follows:
The error codes and description of those are as follows:
Code |
Name |
Definition |
COAC |
ConfirmationAccepted |
Order confirmation or order confirmation amendment is accepted |
CPNP |
CommunicationProblemNextParty |
Communication problems with the next party. |
CREC |
ConfirmationReceived |
Order confirmation or order confirmation amendment is received, i.e., technical validation of the message is OK, and the message is now at the receiving side. |
STNP |
SentToNextParty |
Order confirmation or order confirmation cancellation instruction or order confirmation amendment has been sent to the next party, for instance, the next intermediary. |
The system support multiple switch orders in a single SWIFT order message. Moreover, corresponding acknowledgement and confirmation messages will be delivered like multiple orders’ information, especially error handling (same handling as subscription and redemption orders).
This message will be automatically generated when the system rejects a message for non business reasons. The message will not be sent out in case of a business rule validation.
This message will be generated automatically if any message is rejected for non business reasons by the system, if incoming SWIFT message is not supported or if Reference is invalid or unrecognized. This message contains the following reason code that explains why the message is rejected:
The rejection code ‘NALO’ will be sent in case the message type received in the instruction is not recognized. For instance, if the message type of the incoming message is sent as setr.047.001.01 (SubscriptionOrderConfirmationCancellationInstructionV01) which is not supported by the system then system will validate and reject the message. And the SecuritiesMessageRejectionV02 message will contain the rejection code as ‘NALO’.
In case of transaction cancellation or transaction confirmation if the reference number passed in the instruction does not match with the original transaction order reference number then system will display an error message which will be stored. Once this error happens, the system will generate the SecuritiesMessageRejectionV02 which can be viewed in the outgoing message browser.
The SecuritiesMessageRejection message is used for the following reasons”
MessageElement/BuildingBlock<XML |
Tag> |
Functionality |
Legend |
Type |
Impact |
FCIS Meaning |
Comments |
MessageIdentification |
<MsgId> |
Reference that uniquely identifies a message from a business application standpoint. |
[1.1] |
± (Master Element) |
N/A |
Main tag for <ID> |
New Tag |
Identification |
<Id> |
Identification of the message. |
[1.1] |
Text (Child Element of Message ID) |
Max35Text |
Message Identification Number |
New Tag |
CreationDateTime |
<CreDtTm> |
Date of creation of the message. |
[1.1] |
DateTime (Child Element of Message ID) |
ISODateTime |
Module Time in case of outgoing messagestored in swifttxnhdrlogtbl |
New Tag |
RelatedReference |
<RltdRef> |
Reference to a linked message that was previously received. |
[1.1] |
± (Master Element) |
N/A |
Main Node for <Ref> and <MsgNm>. <Ref> contains the master Ref number from the message. <MsgNm> contains the message code. |
New Tag |
Reference |
<Ref> |
Business reference of a message assigned by the party issuing the message |
[1.1] |
Text (Child Element of Related Reference) |
Max35Text |
Reference Number |
New Tag |
Reason |
<Rsn> |
Reason to reject the message. |
[1.1] |
N/A |
REFE, NALO (InvalidOrUnrecognisedReference, NotAllowedRequest) |
Code REFE will be extracted or Invalid reference number and Code NALO will be extracted for where status request is not allowed to the party. |
New Tag |
Incoming Securities Message Rejection
The message can also be an incoming message. In case of incoming message the referenced message status will be updated. The incoming message can be viewed in incoming message browser. The referenced messages are stored in the system.
The RedemptionOrder message is used to instruct single redemption orders, that is, a message containing one order for one financial instrument and related to one investment account. The RedemptionOrder message will also be used for multiple orders, that is, a message containing several orders related to the same investment account for different financial instruments.
For a single redemption order, the system will use RedemptionOrder message and not RedemptionBulkOrder message. If there are redemption orders for the same financial instrument but for different accounts, then the system will use RedemptionBulkOrder message.
If MultipleOrderDetails/ TotalSettlementAmount is present, then the currency in IndividualOrderDetails/SettlementAmount, if present, should be the same in all occurrences of IndividualOrderDetails.
The system will validate if total settlement amount for multiple order details and settlement amount for Individual order details is present then the currency should be same in all occurrences of Individual order details.
MessageElement/BuildingBlock<XML |
Tag> |
Functionality |
Legend |
Type |
Impact |
FCIS Meaning |
Comments |
SettlementAmount |
<SttlmAmt> |
Date on which Total amount of money paid /to be paid or received in exchange for the financial instrument in the individual order. |
[0..1] |
Amount |
N/A |
Settlement amount in the redemption order |
None |
TotalSettlementAmount |
<TtlSttlmAmt> |
Total amount of money paid /to be paid or received in exchange for the financial instrument in the multiple order. |
[0..1] |
Amount |
N/A |
Total Settlement amount in the redemption order (multiple orders) |
None |
The SubscriptionOrder message is used to instruct single subscription orders, that is, a message containing one order for one financial instrument and related to one investment account. The SubscriptionOrder message can also be used for multiple orders, that is, a message containing several orders related to the same investment account for different financial instruments. For a single subscription order, the system will use SubscriptionOrder message and not SubscriptionBulkOrder message. If there are subscription orders for the same financial instrument but for different accounts, then the system will use SubscriptionBulkOrder message.
If MultipleOrderDetails/ TotalSettlementAmount is present, then the currency in IndividualOrderDetails/SettlementAmount, if present, should be the same in all occurrences of IndividualOrderDetails.
The system will validate if total settlement amount for multiple order details and settlement amount for Individual order details is present then the currency should be same in all occurrences of Individual order details.
MessageElement/BuildingBlock<XML |
Tag> |
Functionality |
Legend |
Type |
Impact |
FCIS Meaning |
Comments |
SettlementAmount |
<SttlmAmt> |
Date on which Total amount of money paid /to be paid or received in exchange for the financial instrument in the individual order. |
[0..1] |
Amount |
N/A |
Settlement amount in the redemption order |
None |
TotalSettlementAmount |
<TtlSttlmAmt> |
Total amount of money paid /to be paid or received in exchange for the financial instrument in the multiple order. |
[0..1] |
Amount |
N/A |
Total Settlement amount in the redemption order (multiple orders) |
None |
Intermediary Override
The system will consider < RltdPtyDtls > tag present in the main tag < IndvOrdrDtls>. The tag < RltdPtyDtls > will contain the Intermediary Override details along with <Role> tag with value ‘INTR’. If tag <Role> with value ‘INTR’ is present, the system will consider Intermediary Agent from the incoming SWIFT message, and default intermediary hierarchy (Agency Branch, IFA, Account Officer) for the transaction. However, the system will check if mapping of Agent-Agency Branch-Account Officer and IFA mapping is in place for transaction. The Role tag highlighted in Related Party details are as follows:
Message |
<Role> tag value in < RltdPtyDtls> tag |
Remark |
SubscriptionOrderV03 (setr.010.001.03)/ |
INTR |
The Intermediary Details will be picked as provided in the incoming message(in < RltdPtyDtls> tag) |
SubscriptionBulkOrderV03 (setr.007.001.03) |
||
SubscriptionOrderV03 (setr.010.001.03)/ |
Not Provided or provided but not equal to ‘INTR’ |
The Intermediary will not be picked as provided in the incoming message. The UH Default Intermediary will be defaulted. |
SubscriptionBulkOrderV03 (setr.007.001.03) |
||
SubscriptionOrderConfirmationV03(setr.012.001.03)/SubscriptionBulkOrderConfirmationV03(setr.009.001.03) |
INTR |
Transaction Intermediary will be extracted. |
SubscriptionOrderConfirmationV03(setr.012.001.03)/SubscriptionBulkOrderConfirmationV03(setr.009.001.03) |
Not Provided or provided but not equal to ‘INTR’ |
AMC BIC Code will be extracted. |
RedemptionOrderV03 (setr.004.001.03)/ |
INTR |
The Intermediary Details will be picked as provided in the incoming message (in < RltdPtyDtls> tag) |
RedemptionBulkOrderV03 (setr.001.001.03) |
||
RedemptionOrderV03 (setr.004.001.03)/ |
Not Provided or provided but not equal to ‘INTR’ |
The Intermediary will not be picked as provided in the incoming message. The UH Default Intermediary will be selected. |
RedemptionBulkOrderV03 (setr.001.001.03) |
||
RedemptionBulkOrderConfirmationV03(setr.003.001.03)/RedemptionOrderConfirmationV03(setr.006.001.03) |
INTR |
Transaction Intermediary will be extracted. |
RedemptionBulkOrderConfirmationV03(setr.003.001.03)/RedemptionOrderConfirmationV03(setr.006.001.03) |
Not Provided or provided but not equal to ‘INTR’ |
AMC BIC Code will be extracted. |
SwitchOrderV03 (setr.013.001.03) |
INTR |
The Intermediary Details will be picked as provided in the incoming message (in < RltdPtyDtls> tag) |
SwitchOrderV03 (setr.013.001.03) |
Not Provided or provided but not equal to ‘INTR’ |
The Intermediary will not be picked as provided in the incoming message. The UH Default Intermediary will be selected. |
SwitchOrderConfirmationV03(setr.015.001.03) |
INTR |
Transaction Intermediary will be extracted. |
SwitchOrderConfirmationV03(setr.015.001.03) |
Not Provided or provided but not equal to ‘INTR’ |
AMC BIC Code will be extracted. |
When Role<INTR> is available in incoming Order Message, then whatever intermediary entity ID is provided in incoming order message, the same will be populated in confirmation message.
On receipt of Incoming Transaction Order, the system will override the Transaction’s Agent based on EntityID or BIC Code present in < RltdPtyDtls> tag.
The system will extract Agent’s Entity ID or BIC Code from < RltdPtyDtls> tag.
It will then determine the number of Intermediary Levels based on the setup maintained in AMC Agent SLA Maintenance. In this maintenance AMC ID will be identified using Fund ISIN while Agent ID will be identified from < RltdPtyDtls> provided in SWIFT Incoming Order message.
The system will determine the linkage between Agent and corresponding intermediary levels including Agency Branch, Account Officer and IFA. For instance, Agent 1 <–> Agency Branch 1 <–> Account Officer 1 <–> IFA 1.
If all the levels in Intermediary hierarchy for selected Agent have one relationship, the system will override the values of all levels of intermediary hierarchy for that transaction. That is, if there is only one corresponding Agency Branch / AO / IFA mapping found for the Agent Code, then system will use that Agency Branch / AO / IFA and create the transaction.
Error Handling
The system will look if ‘AgentCode’ value given under <PrtryId> tag is valid. If Agent ID is valid, then it will proceed with Intermediary derivation. In case, AgentID value given under <PrtryId> tag is incorrect, then the system will reject the transaction displaying an error message as ‘Invalid AgentID in message’. If the tag < PrtryId > is not present in the message, then the system will look for < BICOrBEI > tag.
If <BICOrBEI> tag is present in the message and given with an incorrect value or the given value is not maintained in FCIS, then transaction creation will be rejected directly by displaying an error messagte as ‘Invalid Agent BICCode in the message’.
If value given for tag <BICOrBEI> is matched with the multiple Agent Entities BIC Code setup then transaction will be created with first Agent (sorted ascending order of Agent Entities).
In case both < BICOrBEI> and <PrtryId> tags are not present in the message, system will default UH Intermediary at transaction.
If Agent code value is correct and if there is no SLA setup maintained under AMC Agent SLA setup then the intermediary level will be considered as ‘One’ i.e. only Agent level and transaction will be created only with Agent ID.
When Agent code value is correct and if AMC Agent SLA set up level is more than ‘One’ level then the system will subsequently check for the Agency Branch, AO and IFA mappings using ‘Agency Branch AO’ and ‘Account Officer IFA’ mappings maintenances.
If there is no mapping found or multiple mappings (one to many relationship) found for the same agent and if SLA level is maintained as 4 then the system will create the transaction Intermediary based on the given Agent ID and with default values for Agency Branch will be the first available Agency Branch (sorted in ascending order) mapped to the given Agent in the message and then ‘DIRECT’ for AO and IFA.
If a single mapping for the agency branch, IFA, Account Officer is found, then the system will not raise any warning message during swift upload.
If role is INTR and given intermediary details are not present, then the system will take the agent code. However, if agent code is not present then error INTE is raised saying ‘Intermediary is not matched’ or select from ‘swifttxnrejectedstatustbl’ table.
Agency Branch Override
The system will first check if tag <RltdPtyDtls> exists in the Message. If it exists, then system will check if tag <Role> exists and check if Role is UCL1.
If Role is not UCL1 or if <RltdPtyDtls> does not exist in the Message, transaction will be processed normally, and trade will be placed with Default Intermediaries. If SWIFT Message has <ROLE>, system will override the agency branch details.
The system will check if Agency Branch provided in the SWIFT Message is valid. If Agency Branch is invalid, the system will reject the Message with ‘Invalid Agency Branch in message’.
Relevant SWIFT Rejection Code will be “INTE – Intermediary is not recognised or is invalid”
If Agency Branch is valid, the system will pick up relevant Agent mapped to the Agency Branch. If SLA is 3 or 4, then system will pick up Account Officer and IFA mapped to the Unitholder.
If agent is provided in the message, then the system will look default agency branch available. If default agency branch details are not available then system will reject the order and error will be logged in the table. You cannot add multiple default agency branch details.
Message |
<Role> tag value in < RltdPtyDtls> tag |
Remark |
SubscriptionOrderV03 (setr.010.001.03)/ |
UCL1 |
System will pick up the relevant agent mapped to the Agency branch |
SubscriptionBulkOrderV03 (setr.007.001.03) |
||
SubscriptionOrderV03 (setr.010.001.03)/ |
Not Provided or provided but not equal to UCL1 |
The UH Default Intermediary will be defaulted. |
SubscriptionBulkOrderV03 (setr.007.001.03) |
||
SubscriptionOrderConfirmationV03(setr.012.001.03)/SubscriptionBulkOrderConfirmationV03(setr.009.001.03) |
UCL1 |
Agency branch details will be extracted |
SubscriptionOrderConfirmationV03(setr.012.001.03)/SubscriptionBulkOrderConfirmationV03(setr.009.001.03) |
Not Provided or provided but not equal to UCL1 |
AMC BIC Code will be extracted. |
RedemptionOrderV03 (setr.004.001.03)/ |
UCL1 |
System will pick up the relevant agent mapped to the Agency branch |
RedemptionBulkOrderV03 (setr.001.001.03) |
||
RedemptionOrderV03 (setr.004.001.03)/ |
Not Provided or provided but not equal to UCL1 |
The UH Default Intermediary will be defaulted. |
RedemptionBulkOrderV03 (setr.001.001.03) |
||
RedemptionBulkOrderConfirmationV03(setr.003.001.03)/RedemptionOrderConfirmationV03(setr.006.001.03) |
UCL1 |
Agency branch details will be extracted |
RedemptionBulkOrderConfirmationV03(setr.003.001.03)/RedemptionOrderConfirmationV03(setr.006.001.03) |
Not Provided or provided but not equal to UCL1 |
AMC BIC Code will be extracted. |
SwitchOrderV03 (setr.013.001.03) |
UCL1 |
System will pick up the relevant agent mapped to the Agency branch |
SwitchOrderV03 (setr.013.001.03) |
Not Provided or provided but not equal to UCL1 |
The UH Default Intermediary will be defaulted. |
SwitchOrderConfirmationV03(setr.015.001.03) |
UCL1 |
Agency branch details will be extracted |
SwitchOrderConfirmationV03(setr.015.001.03) |
Not Provided or provided but not equal to UCL1 |
AMC BIC Code will be extracted. |
If a client country parameter ‘ExtractDtTM’ is ON then dealing date will be extracted as TradDtTm. If the parameter “ExtractDtTM” is OFF then transaction date will be extracted as TradDtTm.
The following SWIFT messages will be impacted:
For the Switch Order Confirmation message, the <FXDtls> block will be maintained even when the Transaction Currency is identical to the Fund Base Currency or Price Currency.
The <ToAmt> and <FrAmt> tags are added in <FXDtls> block for below confirmation messages only when the transaction currency is different from FBC or Price currency:
The amount tags will be populated in all the cases even if both the amount is same.
In case of subscription and Redemption confirmation messages, the < FXDtls> block will be populated only if Txn CCY <> Price Ccy(COE) and Txn Ccy <> Fund Base currency (Non COE)
In case of Switch confirmation message, the < FXDtls> block will be populated always, and the amount mentioned in these tags can either be the same (when no exchange rate is applied) or different, when a rate is applied.
In case of subscription and Redemption messages; the < ToAmt> , < FrAmt> tags will be passed as follows (only when an exchange rate is applied).
Subscription/Bulk Order Confirmation:
< FrAmt> Settlement Amount in Transaction Ccy
< ToAmt> Settlement Amount in price Ccy
Redemption/Bulk Order Confirmation:
< FrAmt> Settlement Amount in Price ccy
< ToAmt> Settlement Amount in Transaction Ccy
Subscription/Bulk Order Confirmation:
< FrAmt> Settlement Amount in Transaction Ccy
< ToAmt> Settlement Amount in Fund Base Ccy
Redemption/Bulk Order Confirmation:
< FrAmt> Settlement Amount in fund base ccy
< ToAmt> Settlement Amount in Transaction Ccy
In case of Switch confirmation message; the <FxDtls> block will have FX rate details that are part of Switch In leg only. There will be no changes in <Unitccy> and <QtdCcy> tags values derivation since they are already supported, hence only <FrAmt> and <ToAmt> tags wil be populated with respective amount values of <Unitccy> and <QtdCcy> from Switch IN leg.
This section contains the following topics:
The ‘Swift Message Setup Summary’ screen helps you locate and retrieve the message codes you want to edit, view, delete, authorize or amend, from the database. You can invoke this screen by typing ‘UTSSWMSG’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can retrieve a previously entered record in the Swift Message Setup Summary screen, as follows:
Invoke the Swift Message Setup Summary screen and specify any or all of the following details in the corresponding fields:
After you have specified the required details, click ‘Search’ button. All transactions with the specified details are retrieved and displayed in the lower portion of the screen.
Note
You can also retrieve the individual record detail from the detail screen by doing query in the following manner:-
You can perform Edit, Delete, Amend, Authorize, Reverse, Confirm operations by selecting from the Action list.
You can also search the record by using combination of % and alphanumeric value.
For example
You can search the record for Message Reference Code by using the combination of % and alphanumeric value as follows:-
You can modify the details of a record that you have already entered into the system, provided it has not been subsequently authorized. You can perform this operation as follows:
To view a record that you have previously entered, you must retrieve the same in the Swift Message Setup Summary screen, as follows:
You can delete only unauthorized transactions in the system.
To delete a record that you have previously entered, you must retrieve the same in the Swift Message Setup Summary screen, as follows:
An unauthorized record must be authorized in the system for it to be processed.
To authorize a transaction, you must first retrieve the same in the Record Summary screen.
When the checker authorizes a record, details of validations, if any, that were overridden by the maker of the record during the Save operation, are displayed. If any of these overrides results in an error, the checker must reject the record.
After a record is authorized, it can be modified using the Unlock operation from Action list. To make changes to a record after authorization, you must invoke the Unlock operation which is termed as Amend Operation.
An amended record must be authorized for the amendment to be made effective in the system. Authorization of amended transactions can only be done from Fund Manager Module and Agency branch Module.
If you want to create a new record having the same attributes of an existing record, you can copy the attributes of the existing record to the new record.
To copy the attributes of an existing record to a new record:
This section contains the following topics:
User elements are pre-shipped. However, you do have the option of changing a few. The ‘Swift Element UDF Summary’ screen allows you to do the same. You can invoke this screen by typing ‘UTSSWUDF’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can retrieve a previously entered transaction in the Swift Element UDF screen, as follows:
Note
You can also retrieve the individual record detail from the Swift Element UDF detail screen by doing query in the following manner:-
You can perform Edit, Delete, Amend, Authorize, Reverse, Confirm operations by selecting from the Action list.
You can also search the record by using combination of % and alphanumeric value.
For example
You can search the record for Message Code by using the combination of % and alphanumeric value as follows:-
You can modify the details of a record that you have already entered into the system, provided it has not been subsequently authorized. You can perform this operation as follows:
To view a record that you have previously entered, you must retrieve the same in the Swift Element UDF Summary screen, as follows:
You can delete only unauthorized records in the system.
To delete a record that you have previously entered, you must retrieve the same in the Swift Element UDF Summary screen, as follows:
An unauthorized record must be authorized in the system for it to be processed.
To authorize a record, you must first retrieve the same in the Swift Element UDF Summary screen.
When the checker authorizes a record, details of validations, if any, that were overridden by the maker of the record during the Save operation, are displayed. If any of these overrides results in an error, the checker must reject the record.
After a record is authorized, it can be modified using the Unlock operation from Action list. To make changes to a record after authorization, you must invoke the Unlock operation which is termed as Amend Operation.
Select ‘New’ from the Actions menu in the Application tool bar or click new icon to enter the details of the Swift Element UDF screen.
Specify the following details:
Message Code
Alphanumeric; 3 Characters; Optional
Specify the message code. You can also select message code from the option list.
Message Name
Display
The system displays the message name for the selected message code.
Medium
Optional
Select the medium from the drop-down list. The list displays the following values:
The following fields will be displayed:
Element Description
Display
The elements of the message code will be displayed here.
Group Description
Display
The group description for the element will be displayed here.
Field Choices
Mandatory if you have selected ‘Yes’ in ‘Client Support’ field
If you have selected ‘Yes’ in ‘Client Support’ field for an element, select the field choices that you want to map to the message element.
User Map Allowed
Display
If its mentioned as ‘Yes’, it means a user will be allowed to specify the UDF mapping for the elements of a message. If ‘No’, the user will not be allowed to specify a UDF mapping.
An amended record must be authorized for the amendment to be made effective in the system. Authorization of amended records can only be done from Fund Manager Module and Agency branch Module.
If you want to create a new record having the same attributes of an existing record, you can copy the attributes of the existing record to the new record.
To copy the attributes of an existing record to a new record:
This section contains the following topics:
The Manual Message Generation screen helps you locate and retrieve the messages you want to manually generate, from the database. Specify any or all of the details corresponding to the message you want to retrieve; the system uses your specifications to as search criteria to query the database and retrieve the record that you are looking for.
You can generate an outgoing message manually, through the ‘Manual Message Detail’ screen. You can invoke this screen by typing ‘UTDSWIFT’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Select ‘New’ from the Actions menu in the Application tool bar or click new icon to enter the details of the Manual Message screen.
Message Code
Alphanumeric; 3 Characters; Mandatory
Select the message code from the drop-down list.
Message Reference Code
Alphanumeric; 3 Characters; Optional
Enter a unique reference number for the message.
Effective Date
Date Format; Optional
Enter the Effective Date for the message.
To Entity Type
Alphanumeric; 1 Character; Optional
Select the Entity Type for which the message will be generated.
To Entity ID
Alphanumeric; 1 Characters; Optional
Select the entity for which the message is applicable.
From Date
Date Format; Optional
Enter the ‘From date’ that marks the beginning of the period for which the Manual Message generates.
To Date
Date Format; Optional
Enter the ‘To date’ that marks the end of the period for which the Manual Message generates.
It is mandatory that you specify the Message Code as a search criterion. Once you specify the same, you have the option of entering the Message Reference Code of the message you want to manually generate.
Once you specify the search criteria, click ‘Ok’ button. The records matching your search criteria will be displayed.
Check the option ‘Select’ along a message record to indicate the message should be manually generated.
The following swift message code details will be displayed:
AMC ID
Alphanumeric; 12 Characters; Optional
Specify the AMC ID.
Applicable Fund Button
Clicking ‘Applicable Fund’ button, the system will display ‘Applicable Fund Details’ screen. You can specify the necessary details here.
Applicable UH Button
Clicking ‘Applicable UH’ button, the system will display ‘Applicable UH Details’ screen. You can specify the necessary details here.
Check the option ‘Check’ along a message record to indicate the message should be manually generated.
The following swift report details will be displayed:
Click ‘Check’ button to check the report log.
Click ‘Process’ button to process the record.
In ‘Manual ‘Message Generation’ screen, you can select one or multiple funds using ‘Applicable Fund’ button. Those funds that are selected in SWIFT Message setup will be considered for Manual generation by default, if you have not selected different set of funds. Fund IDs that are shown in available list will be from the selected AMCID. The outgoing messages which will be altered to facilitate this requirement are as follows:
AMC Restriction
As the DN address of an Agent/Agency Branch/IFA/Account Officer must be maintained for Agent/Agency Branch/IFA/Account Officer and AMC/Legal Entity combination so at the time of SWIFT message set up, the AMC ID must be provided if the ‘To Entity Type’ is Agent/Agency Branch/IFA/Account Officer. The provided AMC ID will act as the criteria to select the details to be passed to the message. If the ‘To Entity ID’ is selected as AMC or Legal Entity then that AMCID or Legal Entity ID will be used as the search criteria to pass the details.
Unit Holder Restriction
In ‘Manual ‘Message Generation’ screen, you can select one or multiple unitholder IDs or names using ‘Applicable UH’ button for which the outgoing message must be generated. Those unit holders that are selected in SWIFT Message Setup will be considered for Manual Generation by default if you have not selected different set of unit holders.
If the Entity is an AMC, the available UHs will be limited to the UHs for that AMC. If the Entity is an Agent, the available UHs will be limited to the UHs for that Agent in the UH /Agent hierarchy. If the Entity is an Agency Branch, the available UHs will be limited to the UHs for that Agency Branch in the UH /Agent hierarchy. If the Entity is an Account Officer, the available UHs will be limited to the UHs for that Account Officer in the UH /Agent hierarchy. If the Entity is an IFA, the available UHs will be limited to the UHs for that IFA in the UH /Agent hierarchy.
The ‘Applicable UH’ button is enabled for the outgoing messages related to unitholders, for instance, confirmation messages, account statement of holding, custody statement of holding. The fields AMC ID and Fund Selection will be available for selection for all the messages. For confirmation messages the message will be generated for all AMCs. But you can pass specific Fund and unitholder. You can also generate the confirmation message for specific AMC. The unitholder selected list will be used only for the messages where the unitholder related data will be extracted to the XML message. This requirement will be applicable to the following messages:
If you select different set of fund(s) or unit holder(s) while generating Manual Message, the system will consider overridden filters only for that particular message generation, however the filters that have setup in SWIFT Message setup will not change.
The transaction will be processed as per the information contained in the requested settlement currency tag of the Swift incoming order message <ReqdSttlmCcy>. While processing the order message the system will extract the value of the tag ReqdSttlmCcy from the incoming order messages. The messages which will be enhanced to support the <ReqdSttlmCcy> tag are as follows:
The tag value of the ReqdSttlmCcy must contain the valid settlement currency code, for instance, HKD, USD etc. If the tag value contains the value other than the maintained currencies in the system, then the transaction will be rejected with the rejection code as NCRR- Unrecognised or invalid Settlement Amount Currency.
Upon receipt of the settlement currency code value, the system will check if bank account is maintained at UH level for the currency maintained in the tag. If bank account is not maintained, i.e., default corresponding account is maintained for the Unit holder then the system will reject the order instruction with the rejection code as NCRR- Unrecognised or invalid Settlement Amount Currency. The order Instruction Status message (OrderInstructionStatusReportV03 setr.016.001.03) will be generated with the rejection Code as ‘NCRR’.
If the tag value for < ReqdSttlmCcy> is present in the message and bank account is maintained for the UH for the settlement currency present in ReqdSttlmCcy tag, then the settlement currency code mentioned in the tag ReqdSttlmCcy will be considered as the transaction currency for the transaction. The system will apply the Exchange rate if requested settlement currency is different from the pricing currency.
In case of switch transaction, the above rules will be applied to the redemption leg and the value will override the transaction currency of redemption leg.
The system will consider the default exchange rate source ID maintained at general operating rules level of the fund. If no default exchange rate is maintained at Fund general operating rules, then system will consider the segment level default exchange rate source maintained in ‘Module Defaults Setup’ screen. For instance, if the user wants any specific FX rate required for AMG Funds then user needs to maintain the default source ID for AMG funds, then that source ID will be used to get the exchange rate.This is applicable for both amount based and unit based transactions.
The <ReqdSttlmCcy> tag will be provided for the <RedLegDtls> section of the switch confirmation message which contains the Transaction currency.
The system will override the loads attached to the fund at the time of transaction capture through SWIFT. The system will also override all the loads, if multiple loads are found for ‘From’ and ‘To’ Entity Type Combinations. If any transaction is generated with warning messages, then the transaction will be generated unauthorized.
Note
For those schemas where the Transaction Exception Management Queue is not enabled, transaction will be created as Authorised/ Unauthorised depending on maintenance in system and during the view of the transaction in ‘Transaction Summary’ screen, the warning messages attached to the transaction can be viewed through ‘Override Warning’ button available in the summary screen. This is applicable to all the schemas.
The Price basis loads cannot be overridden as the price basis load gets calculated as per the fund formula setup. If such loads are maintained, then the system will not reject the transaction; also, the values in the tags will not override the Price basis Loads mapped to the fund.The derived loads cannot be overridden, for instance, ‘AMC to Agent’ load derived from ‘Unitholder to AMC’ load cannot be overridden. If such loads are maintained, then, the system will not reject the transaction; also, the values in the tags will not override the Derived loads mapped to the fund.
SWIFT Upload
The tags <ChrgDtls> and <ComssnDtls> will be extracted from the incoming order messages and will be used to override the loads attached to the Fund. The segment level parameter which is currently used for generation of these tags in outgoing order confirmation messages will be re-used here for overriding. If the parameter is turned on, then the values of these tags will be used to override the loads attached to the fund and as well as the tags get generated in outgoing order confirmation messages. If the parameter is turned off, then both, the tags will not be used to override the loads attached to the fund and as well as the tags will not be generated in outgoing order confirmation messages. The incoming messages which will be enhanced are
For the incoming messages listed above, the tags <ChrgDtls> and <ComssnDtls> will be received by the system and will extract the values present in the sub tags <Tp>, <Amt> or < Rate>.
In switch order SwitchOrderV03 (setr.013.001.03) the tags <ChrgDtls> and <ComssnDtls> will be present both in the Redemption (Switch Out) and subscription (Switch In) leg of the transaction.
The <Amt> or <Rate> tag value provided in the main tag < ChrgDtls> will be used to override the AMC commission from Unitholder. (Unitholder to AMC). That is, the system will override the discount to UH, if <Tp> present in the main tag < ChrgDtls> contain the value as DISC. And if the <Tp> contains the value as BEND/FEND then Unitholder to AMC commission will be overridden.
The <Amt> or <Rate> tag value provided in the main tag < ComssnDtls > will be used to override the Agent commission from Unitholder. (Unitholder to Agent). If the incoming message does not contain the tags < ChrgDtls> and < ComssnDtls > at all, then the loads will be not be overridden.
If the incoming message contain the tags < ChrgDtls> and < ComssnDtls > but with blank values in the sub tag <Rate> or <Amt>, then the loads will not be overridden. However, if they contain the value as 0 then the load values will be overridden as 0.
The commission for Unitholder to Agency Branch, Unitholder to Account Officer, Unitholder to IFA and Unitholder to Fund cannot be overridden with the help of the <ChrgDtls> and <ComssnDtls> tags, since they are out of scope of the requirement. The Loads or Derived Loads maintained in these combinations will be ignored.
If more than one Unitholder to AMC commissions load are mapped to the Fund as part of Fund Load Maintenance, then all the mapped Unitholder to AMC loads will be overridden with the value present in the tag <ChrgDtls>. Since the system cannot determine which load to override, the system will override all the loads applicable to the transaction having ‘From Entity’ as Unitholder and ‘To Entity’ as AMC.
At the time of transaction capture, the system does not perform the criteria evaluation; hence it not possible to override the specific load mapped to the entity which satisfies the load criteria. However, the system will override all the loads mapped to the Fund. At the time of allocation, only the loads satisfying the criteria will get calculated.
Similar to <ChrgDtls>, if more than one Unitholder to Agent commissions load are mapped to the Fund as part of Fund Load Maintenance, then the all the mapped Unitholder to Agent loads will be overridden with the value present in the tag < ComssnDtls>.
The tags <ChrgDtls> and <ComssnDtls> must contain either <Amt> or <Rate> Sub tag. Both <Amt> and <Rate> cannot be present together. If both <Amt> and <Rate> tags are present in <ChrgDtls> or <ComssnDtls> tags, then system will reject the transaction. The Order Instruction Status message OrderInstructionStatusReportV03 (setr.016.001.03) will be generated with the error code as FEEE.
If the tags <ChrgDtls> and <ComssnDtls> contain <Amt> and the load to be overridden is a percentage based load, then the transaction will be rejected. The Order Instruction Status message OrderInstructionStatusReportV03 (setr.016.001.03) will be generated with the error code as FEEE.
The <Tp> tag can contain the values of BEND, FEND or DISC. The transaction will be rejected if any other value is provided.
The <Tp> tag can contain the values of BEND alone in the redemption orders and Switch out leg of the Switch order. If system receives values other than BEND, in the redemption order or Redemption leg of the Switch message, then the transaction will be rejected with the rejection code as FEEE.
The <Tp> tag can contain the values of FEND alone in the redemption orders and Switch out leg of the Switch order. If system receives values other than FEND, in the Subscription order or Subscription leg of the Switch message, then the transaction will be rejected with the rejection code as FEEE.
The <Tp> tag can contain the values as DISC in all the order messages.
If the <Tp> tag present in the main tag <ChrgDtls> contains the value as “DISC” then the Discount load from AMC to Unitholder will be overridden. However if <Tp> tag <ComssnDtls> contains the value as “DISC”, then no Action is performed.
It is possible that both the <ChrgDtls> and <ComssnDtls> tag or any one of them can be present in the order messages.
The system can select the incoming Switch transactions to be handled as Normal Switch or Pseudo Switch. using ‘PSEUDOSWITCHENABLED’ parameter. If the parameter is turned ON then system will process all the incoming Switch transactions as Pseudo Switch and if the parameter is turned OFF, then it will be processed as Pseudo Switch otherwise as Normal Switch.
As per ISO20022 standards, Swift allows only 100,000 characters per message. If message contains more than 100,000 characters it is creating a performance issue. To overcome this issue as part of Swift message maintenance, 3 fields, namely, ‘Split required’, ‘Repeated Tag’ and ‘Maximum Length Allowed’ will be parameterized. The default value for ‘Split required’ field will be ‘No’.
The repeated tag for “Custody Statement of Holdings V02” is < BalForSubAcct>.
The repeated tag for “Accounting Statement of Holdings V02” (unit holder based) is <BalForAcct>.
The repeated tag for “Statement of Investment Fund Transaction V02” is <TxOnSubAcct>
The repeated tag for “Price Reprot V04” is <PriceValtnDtls>
The value of parameters will be maintained in the ‘SWIFTMAINTENANCETBL’ as follows:
SWIFT Report |
Message Code |
Split Required? |
Repeated Tag in XML |
Maximum Length allowed |
AccountingStatementOfHoldingsV02 (Unitholder Based) |
semt.003.001.02 |
Yes |
< BalForAcct> |
100000 |
CustodyStatementOfHoldingsV02 |
semt.002.001.02 |
Yes |
< BalForSubAcct> |
100000 |
StatementOfInvestmentFundTransactionV02 |
semt.006.001.02 |
Yes |
< TxOnSubAcct> |
100000 |
PriceReportV04 |
reda.001.001.04 |
Yes |
<PricValtnDtls> |
100000 |
Initially, the system will check the length of the entire message which includes the count of characters in Header Section, Footer Section and Message body. If the length is less than 100,000 characters then system will skip the entire process and proceed for message generation.
In case if the length of the message exceeds the 100,000 characters, then based on each tag (< BalForAcct> in case of Accounting Statement of Holdings V02), it will accommodate up to 100,000 characters and rest will be stored in different message. The system will repeat the above process until report is generated.
The system will generate a unique message ID number <MsgId> for each split message. The tag <PgNb>Page No</PgNb> of the first message will be 1 and it will be incremented by 1 for other messages.
The value of the tag <LastPgInd>value</LastPgInd> of the last message will be ‘True’ and all other messages will be ‘False’.
The complete block of the tag will be present in the message and will not get split over to the next message. In case, if report pertaining to one fund is not sufficient to store in the first message itself, then message will not get generated.
For instance, in case of Accounting Statement of Holdings V02 if the message is exceeding the 100,000 characters and based on CIF, if the message can be accommodated in the 1st Message is up to 99,850 characters, then the system will start placing the message information in the 2nd message with Header, Footer and Body of Message. Similarly if in the 2nd message also exceeds 100,000 characters then it will start placing the remaining message information in 3rd message and so on.
The system will check the Header, Footer and Message body section for each and every split before generating the message.
An account servicer, for instance, a transfer agent sends the AccountStatementOfHoldings message to the account owner, for example, a fund manager or an account owner's designated agent to provide detailed holdings of the portfolio at a specified moment in time.
A Swift message will be maintained in the system named as AccountingStatementOfHoldingsV02 (semt.003.001.02).
The new outgoing message can be viewed in the outgoing message browser.
An account servicer, for instance, a registrar, transfer agent or custodian bank, sends the Securities-MessageRejection message to the account owner, for instance, an investor or its authorized agent, to reject a previously received message on which action cannot be taken.
The message is generated when there is a problem in the incoming Message and it gets rejected. SMR will get generated automatically. This message is generated when the Sender’s DN address doesnot match with the DN address set up. Or the LOB Schema could not be decided with the responder DN Address.
Swift message will be maintained in the system named as SecuritiesMessageRejectionV02 (semt.001.001.02).
This message will be automatically generated when the system rejects a message for non business reasons
The message will not be sent out in case of a business rule validation.
This message will be generated automatically if any message is rejected for non business reasons by the system. (If incoming SWIFT message is not supported or if Reference is invalid or unrecognized)
This message will contain a following reason code that explains why the message is rejected:
The rejection code ‘NALO’ will be sent in case the message type received in the instruction is not recognized. For instance, if the message type of the incoming message is sent as setr.047.001.01 (SubscriptionOrderConfirmationCancellationInstructionV01) which is not supported by the system then the system will validate and reject the message. And the SecuritiesMessageRejectionV02 message will contain the rejection code as ‘NALO’.
In case of transaction cancellation or transaction confirmation if the reference number passed in the instruction does not match with the original transaction order reference number then the system will display an error which will be stored. Once this error happens system will generate the SecuritiesMessageRejectionV02 which can be viewed in the outgoing message browser.
Incoming Securities Message Rejection
The message can also be an incoming message. In case of incoming message the referenced message status will be updated. The incoming message can be viewed in incoming message browser. The referenced messages are stored in the system.
A report provider, for instance, a transfer agent, fund accountant or market data provider, sends the PriceReportCancellation message to the report recipient, for instance, a fund management company, transfer agent, market data provider, regulator or any other interested party to cancel previously sent prices.
An executing party, for example, a transfer agent, send the RequestForOrderConfirmationStatusReport message to the instructing party, for instance, an investment manager or its authorized representative, to request the status of one or several order confirmations.
A report provider, for instance, a transfer agent, fund accountant or market data provider, sends the PriceReport message to the report recipient, for instance, a fund management company, transfer agent, market data provider, regulator or any other interested party to provide the net asset value and price information for financial instruments on specific trade dates and, optionally, to quote price variation information.
PriceReportIdentification <PricRptId> - Unique and unambiguous identifier for the price report, as assigned by the reporting party, support upto 35 char.
Following functions are supported in price report:
Code Name |
Name |
Definition |
REPL |
CompleteReplacementPriceReport |
The price report conveys the correction of the complete set of prices previously sent for the same price report identification. |
NEWP |
NewPriceReport |
The price report is 'new', that is the report is not being used as a correction of is not being used as a correction of previously sent prices. |
PART |
PartialCorrectionPriceReport |
The price report conveys the correction of some of the prices previously sent for the same price report identification. |
Price Report Generation as per the new codes are as follows:
Since, the PriceReportV04 is already generated at 2:00 pm IST, the system will check the history table whether all prices have been changed as per the previous report. In this case, only Fund 4 and Fund 5 have gone change in the prices, the system will consider it as a partial change in the price report and regenerate the PriceReportV04 with code value PART and will include the funds with changes in prices.
Similarly, if prices for all the funds are changed, then the system will check the latest prices in history table and will regenerate the PriceReportV04 with code value REPL which will replace the previous report. All the latest fund prices will be included in new report.
This section contains the following topics:
The XML format of SWIFT Messages can be validated. To maintain validation parameters for the XML format, use the ‘Parameter Setup Detail’ screen.
You can invoke this screen by typing ‘UTDPARAM’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
When you open the screen, choose the language for which you want to view the maintained codes, in the Language field.
Then select the Parameter Code ‘SWIFTFORMAT’ and click add icon to add the parameters. The following screen will be displayed:
You can specify the following details:
Param Code
Alphanumeric; 25 Characters; Mandatory
Specify the param code. Alternatively, you can select Param code from the option list.
Param Description
Display
The system displays the description for the selected param code.
Maintainable
Optional
Select if the record is maintainable or not from the drop-down list. The list displays the following values:
After specifying the necessary details, click ‘Execute Query’. The system displays the following values:
This section contains the following topics:
You can use the incoming message browser to perform the following functions with respect to an incoming SWIFT message:
In order to perform any of these functions, you must first retrieve the ‘In’ message and display it in the ‘Incoming Msg Browser Summary’ screen. You can invoke this screen by typing ‘UTSMSGIN’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
To display the message, you can specify any or all of the following details:
Authorized
Optional
Select the authorization status of the messages that you wish to view from the drop-down list. The list displays the following values:
Message Type
Alphanumeric; 100 Characters; Optional
Specify the Swift Message type to display the message.
For instance, Subscription Bulk Order, Redemption Bulk Order etc.
Message Id
Alphanumeric; 35 Characters; Optional
Specify the message ID. Alternatively, you can select message ID from the option list. The list displays all valid message ID maintained in the system.
Message Status
Alphanumeric; 1 Character; Optional
Specify the status of the message that has to be displayed. The status could be unprocessed, processed, repair, suppressed or all.
Sender
Alphanumeric; 12 Characters; Optional
Indicate the sender of the message.
Swift Code
Alphanumeric; 30 Characters; Optional
Specify the Swift code. Alternatively, you can select swift code from the option list. The list displays all valid swift code maintained in the system.
Message Date
Date Format; Optional
Specify the date range for which the system has to retrieve the messages.
Message Time
Time Format; Optional
Specify the time to retrieve the message.
Note
If time zone is available in incoming messages, it will be truncated and not stored/ used for processing.
Order Reference Number
Alphanumeric; 35 Characters; Optional
Specify the order reference number. Alternatively, you can select order reference number from the option list. The list displays all valid order reference number maintained in the system.
Counterpart Type
Alphanumeric; 1 Character; Optional
Specify the counterpart type. Alternatively, you can select counterpart type from the option list. The list displays all valid counterpart types maintained in the system.
Counterparty
Alphanumeric; 12 Characters; Optional
Specify the counterpart ID. Alternatively, you can select counterpart from the option list. The list displays all valid counterpart ID maintained in the system.
Transaction Status
Optional
Select the transaction status from the drop-down list. The list displays the following values:
Unit Holder ID
Alphanumeric; 12 Characters; Optional
Specify the unit holder ID. Alternatively, you can select unit holder ID from the option list. The list displays all valid unit holder ID maintained in the system.
AMC ID
Alphanumeric; 12 Characters; Optional
Specify the AMC ID. Alternatively, you can select AMC ID from the option list. The list displays all valid AMC ID maintained in the system.
ISIN Code
Alphanumeric; 12 Characters; Optional
Specify the ISIN code. Alternatively, you can select ISIN coder from the option list. The list displays all valid ISIN code maintained in the system.
Fund ID
Alphanumeric; 6 Characters; Optional
Specify the fund ID. Alternatively, you can select fund ID from the option list. The list displays all valid fund ID maintained in the system.
All messages matching your criteria are displayed in the grid portion of the screen. Click on the message that you wish to operate on, in the DCN field. The Incoming Message Browser screen, with the details of the message displayed.
All messages matching your criteria are displayed in the grid portion of the screen. Click ‘Message Details’ button that you wish to operate on, in the DCN field.
A horizontal array of icons is available for you to perform operations on the message.
You can view the following details:
Click the following buttons to view the details as follows:
Operation |
Description |
View |
Click this button to view the contents of a message. The contents of the message will be displayed in the Message section of the screen. |
Linked Message |
Click this button to view linked messages, if any. |
Transaction Details |
Click 'Transaction Details' button to view the transaction details. |
Authorize |
Click this button to authorize an unauthorized unprocessed message that has been edited; an unauthorized processed message that has been repaired, or an unauthorized suppressed message. If the upload status is ‘U’ (unauthorized) then the message will be received to MSTB_DLY_MSG_IN table as unauthorized. You can authorize the same from message browsers screens and once authorized, only the record will be considered for processing. |
This section contains the following topics:
You can use the outgoing message browser to perform the following functions with respect to an outgoing SWIFT message:
In order to perform any of these functions, you must first retrieve the message in and display it in the ‘Outgoing Message Browser Summary’ screen. You can invoke this screen by typing ‘UTSMSGOT’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
To display the message, you can specify any or all of the following details:
Authorized
Optional
Select the authorization status of the messages that you wish to view from the drop-down list. The list displays the following values:
DCN
Alphanumeric; 16 Characters; Optional
Specify the DCN.
Message Type
Alphanumeric; 100 Characters; Optional
Specify the Swift Message type to display the message.
For instance, Subscription Bulk Order, Redemption Bulk Order etc.
Following are the message types that are maintained:
Message Id
Alphanumeric; 35 Characters; Optional
Specify the message ID. Alternatively, you can select message ID from the option list. The list displays all valid message ID maintained in the system.
Message Status
Alphanumeric; 1 Character; Optional
Specify the status of the message that has to be displayed. The status could be unprocessed, processed, repair, suppressed or all.
Receiver
Alphanumeric; 300 Characters; Optional
Specify the receiver details. Alternatively, you can select receiver details from the option list. The list displays all valid receiver details code maintained in the system.
Transaction Number
Alphanumeric; 16 Characters; Optional
Specify the transaction number. Alternatively, you can select transaction number from the option list. The list displays all valid transaction number maintained in the system.
Link Reference Number
Alphanumeric; 35 Characters; Optional
Specify the link reference number. Alternatively, you can select link reference number from the option list. The list displays all valid link reference number maintained in the system.
Message Date
Date Format; Optional
Select the date range for which the system has to retrieve the messages from the adjoining calendar.
Message Time
Time Format; Optional
Specify the time to retrieve the message.
Note
If time zone is available in incoming messages, it will be truncated and not stored/ used for processing.
Individual Order Reference
Alphanumeric; 35 Characters; Optional
Specify the individual order reference number. Alternatively, you can select individual order reference number from the option list. The list displays all valid individual order reference number maintained in the system.
Counterpart Type
Alphanumeric; 1 Character; Optional
Specify the counterpart type. Alternatively, you can select counterpart type from the option list. The list displays all valid counterpart types maintained in the system.
Counterparty
Alphanumeric; 12 Characters; Optional
Specify the counterpart ID. Alternatively, you can select counterpart from the option list. The list displays all valid counterpart ID maintained in the system.
Unit Holder ID
Alphanumeric; 12 Characters; Optional
Specify the unit holder ID. Alternatively, you can select unit holder ID from the option list. The list displays all valid unit holder ID maintained in the system.
Source Entity ID
Alphanumeric; 12 Characters; Optional
Specify the source entity ID. Alternatively, you can select source entity ID from the option list. The list displays all valid source entity ID maintained in the system.
ISIN Code
Alphanumeric; 12 Characters; Optional
Specify the ISIN code. Alternatively, you can select ISIN coder from the option list. The list displays all valid ISIN code maintained in the system.
Fund ID
Alphanumeric; 6 Characters; Optional
Specify the fund ID. Alternatively, you can select fund ID from the option list. The list displays all valid fund ID maintained in the system.
Message Reference Code
Alphanumeric; 35 Characters; Optional
Specify the message reference code. Alternatively, you can select message reference coder from the option list. The list displays all valid message reference code maintained in the system.
All messages matching your criteria are displayed in the grid portion of the screen. Double-click on any of the records that you wish to operate on, in the DCN field. The Outgoing Message Browser screen, with the details of the message displayed.
A horizontal array of icons is available for you to perform operations on the message.
Outgoing Message Info
All messages matching your criteria are displayed in this portion of the screen. In the outgoing message info grid, you can view the following details:
Operations |
Description |
View |
Click this button to view the contents of a message. The contents of the message will be displayed in the Message section of the screen. |
Authorize |
Click this button to authorize an unauthorized ungenerated message that has been edited or an unauthorized generated message that has been repaired. For out messages, if ‘Confirm Outgoing Messages’ in the Swift Message Set up is set as true then the message will be generated and populated to MSTB_DLY_MSG_OUT table as authorized else it will be populated as unauthorized. |
This section contains the following topic:
To upload incoming messages, you can use the ‘Process Incoming Swift Messages’ screen. You can invoke this screen by typing ‘UTDPSWIN’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Operation
Optional
Select the Operation as 'Start' to trigger the upload process from the drop-down list. The list displays the following values:
Triggering the upload process in this screen will move all unprocessed messages collected by the message system from the SWIFT terminal delivery channel, to the ‘processed’ status.
This section contains the following topic:
To generate outgoing messages, use the ‘Process Outgoing Swift Messages’ screen. You can invoke this screen by typing ‘UTDPSWOU’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Operation
Optional
Select the Operation as 'Start' to trigger the generation process from the drop-down list. The list displays the following values:
Triggering the generation process in this screen will move all ungenerated messages, to the ‘generated’ status; and the outgoing messages are generated and moved to the outgoing queue of the appropriate SWIFT terminal delivery channel.
This section contains the following topics:
You can maintain the DN address for SWIFT Entities, such as, Segment, AMC, Legal Entity, Agent, Agency Branch, IFA and Account Officer using ‘Swift Entity Maintenance’ screen.
The DN address setup for different SWIFT Entities will be maintained as follows:
For SWIFT Entity - ‘Segment’
If the entity type is selected as Segment, the entity ID will be defaulted as Installed Entity and mapped entity details will be disabled. Only one DN address will be allowed to be maintained for ‘Segment’ SWIFT Entity. The DN address maintained for ‘Segment’ Entity type is used as Responder DN for all incoming messages from different swift entity types for the respective segment and also used as Requester DN for all outgoing messages generated from respective segment. If there is more than one schema with same segment level DN address, then the system cannot pass the message received to the intended segment by checking the responder DN address present in the message.
Once the message is received, the system will check whether Related Reference or Previous Reference is available in the message. If it is available then system will find the schema from mstm_msg_trrack table. If Related Reference or Previous reference is not available or cannot find schema from mstm_msg_track table, then the system will find the schema from DN address maintenance (based on requestor).
The system will also check whether Responder DN mentioned in the message is maintained in identified segment. If maintained, the message will consider for processing in that segment.
For SWIFT Entity Type ‘AMC’ or ‘Legal Entity’
If the entity type is selected as AMC then you must select AMC ID, if the entity type is selected as ‘Legal Entity’ then you must select Legal Entity ID. For AMC or Legal entity, entity ID will be defaulted as Installed Entity and mapped entity details will be disabled. If Entity Type is ‘M’ (AMC) then the entity ID option list will list only AMC’s
For SWIFT Entity Type ‘Agent’ or ‘Agency Branch/Account Officer/IFA’
If the Entity type is ‘Agent’ or ‘Agency Branch/Account Officer/IFA’ then you can only select the Entity ID along with the AMC or Legal Entity ID. AMC ID/Legal Entity ID is mandatory when Entity type is ‘Agent’ or ‘Agency Branch/Account Officer/IFA’. Only one of the DN address maintained for Agent and AMC ID combination can set as Default DN address. You can enable DBN address. you can also specify whether the DN address is maintained for only outgoing message and no incoming message from that address will be processed in the system using ‘Outbound Only’ check box. If this checkbox is checked then no incoming message from that Requestor DN address will be processed.
For Segment, AMC, Legal Entity counterparts; there will be only one DN address allowed to be maintained. For Agent, Agency Branch, Account Officer and IFA counterparts; multiple DN addresses for each AMC ID for different communication modes must be able to be maintained.
For message with multiple orders where for one Unitholder more than one transaction will be done for different funds, the system will check the above rules for E-dealing allowed for the legal entities mapped to those funds. If for one of the legal entities, the E-dealing is not allowed, then system will reject only the transactions done to those funds where the mapped legal entity is not checked in ‘Electronic Deal’ field in ‘Entity Maintenance’ screen.
In the case of a Swift Switch message between two different Legal Entities, the message will be accepted only if both ‘legal entities’ allow electronic dealing and the ‘AMC allows electronic dealing.
The validations which will to be applied DN address maintained in Entity SWIFT Setup are as follows.
Incoming message coming into the system will have the tags <Requestor> and <Responder> The <Responder> tag will be the DN address of the specific segment in which the message will be processed. The DN address mentioned in the <Requestor> tag will be searched in the DN addresses maintained in the system for all SWIFT Entity Types except where DN address is flagged as Outbound only. If it does not find the corresponding DN Address then the system will generate an outgoing Securities Message Rejection and sent out with rejection code as ‘NALO’. If the system finds the corresponding DN address then the incoming message will be further validated.
Once the DN address is matched with maintained list, the system will identify the actual entity which is sending the message.
If the identified sender entity is ‘Agent, Agency branch, IFA, Account Officer’, the corresponding AMC ID or Legal Entity will be identified based on Fund ISIN mentioned in the message. The system then checks that the DN address received as requester is maintained for that Agent and AMC/Legal Entity combination. If so, the system will further check whether the identified AMC allows the incoming message type based on the list of allowed messages maintained as part of Entity Maintenance. If the incoming message is not allowed or DN address received in the message does not match with the Agent and AMC/Legal Entity combination setup then system will reject the message and generate an outgoing Securities Message Rejection message with reject code ‘NALO’.
If the identified sender entity is ‘AMC’ or ‘Legal Entity’ then the system will further check whether the identified AMC allows the incoming message type based on the list of allowed messages maintained as part of Entity Maintenance. If the incoming message is not allowed then the system will reject the message and generate an outgoing Securities Message Rejection message with reject code ‘NALO’
Once the message is processed (i.e. The transaction may or may not been created when the message is processed in FCIS) in the system then the Order Instruction Status message will be generated and will be sent to the same DN address which was present in the incoming message as requester. The same process will apply for the confirmation messages when the transaction is priced. The confirmation message will be generated after the created transaction is allocated in the system. This will also be sent to the same DN address which was present in the incoming message as requestor.
For outgoing messages for which there is no outbound message such as PriceReportV03 (reda.001.001.03), AccountingStatementOfHoldingsV02 (semt.003.001.02) for instance, the requester DN will be the DN address of the Segment. The Responder DN will be the DN address of the ‘To Entity ID’ maintained as part of the SWIFT Message Setup for the specific outgoing message. If ‘To Entity Type’ is Agent/Agency Branch/IFA/Account Officer then the system will use the AMC ID maintained as part of SWIFT Message setup to derive the respective default DN address for Agent and AMC combination.
You can invoke the ‘Swift Entity Maintenance’ screen by typing ‘UTDENTSW’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can specify the following details:
Reference Number
Display
The system displays the reference number.
Entity Type
Alphanumeric; 1 Characters; Mandatory
Specify the entity type. Alternatively, you can select the entity type from the option list. The list displays all valid entity type maintained in the system.
Entity ID
Alphanumeric; 12 Characters; Mandatory
Specify the entity ID. Alternatively, you can select the entity ID from the option list. The list displays all valid entity ID maintained in the system.
Entity Name
Display
The system displays the entity name for the selected entity ID.
Mapped Entity Type
Alphanumeric; 1 Character; Optional
Specify the mapped entity type. Alternatively, you can select the mapped entity type from the option list. The list displays all valid mapped entity type maintained in the system.
Mapped Entity ID
Alphanumeric; 12 Characters; Optional
Specify the mapped entity ID. Alternatively, you can select the mapped entity ID from the option list. The list displays all valid mapped entity ID maintained in the system.
Mapped Entity Name
Display
The system displays the mapped entity name for the selected mapped entity ID.
Communication Mode
Optional
Select the mode of communication from the drop-down list. The list displays the following values:
DN Address
Alphanumeric; 100 Characters; Mandatory
Specify the DN address.
Out Bound Only
Optional
Check this box to indicate that the Requestor DN address corresponding to this checked record will be used only for outgoing messages and will not be used for incoming messages.
If any incoming message is received from the Requestor DN address for which ‘Outbound Only’ field is checked, the message will be rejected since that DN address is defined to be used only for outgoing messages.
Note
The ‘Outbound Only’ check box must be flagged against only one DN. This field is not applicable for ‘Segment’ entity type. It will be defaulted as checked.
Is Default
Optional
Check this box to indicate that DN address is defaulted.
The ‘Default’ check box must be flagged against only one DN. The ‘Default’ check box will also be defaulted as ‘checked’ for the DN address record where ‘Outbound Only’ check box is checked.
Disable?
Optional
Check this box to disable the DN address(s) for a specific Entity.
While processing the incoming message only enabled DN addresses present in the system will be matched against the incoming requestor DN address to find out the SWIFT correspondent. If the matched DN address is marked as disabled then the message will not be processed and security rejection message with reason Code as ‘NALO’ will be generated and sent out.
This section contains the following topics:
You can invoke ‘Swift Entity Maintenance’ screen by typing ‘UTSENTSW’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can retrieve a previously entered record in the Swift Entity Maintenance Summary screen, as follows:
Invoke the Swift Entity Maintenance Summary screen and specify any or all of the following details in the corresponding fields:
After you have specified the required details, click ‘Search’ button. All transactions with the specified details are retrieved and displayed in the lower portion of the screen.
Note
You can also retrieve the individual record detail from the detail screen by doing query in the following manner:
You can perform Edit, Delete, Amend, Authorize, Reverse, Confirm operations by selecting from the Action list.
You can also search the record by using combination of % and alphanumeric value.
For example
You can search the record for Message Code by using the combination of % and alphanumeric value as follows:-
You can modify the details of a record that you have already entered into the system, provided it has not been subsequently authorized. You can perform this operation as follows:
To view a record that you have previously entered, you must retrieve the same in the Swift Entity Maintenance Summary screen, as follows:
You can delete only unauthorized transactions in the system.
To delete a record that you have previously entered, you must retrieve the same in the Swift Entity Maintenance Summary screen, as follows:
An unauthorized record must be authorized in the system for it to be processed.
To authorize a transaction, you must first retrieve the same in the Record Summary screen.
When the checker authorizes a record, details of validations, if any, that were overridden by the maker of the record during the Save operation, are displayed. If any of these overrides results in an error, the checker must reject the record.
After a record is authorized, it can be modified using the Unlock operation from Action list. To make changes to a record after authorization, you must invoke the Unlock operation which is termed as Amend Operation.
An amended record must be authorized for the amendment to be made effective in the system. Authorization of amended transactions can only be done from Fund Manager Module and Agency branch Module.
This section contains the following topics:
This message is sent by an intermediary to an executing party or to another intermediary party. This message is used to instruct the executing party to subscribe to a specified amount/quantity of a specified financial instrument.
The Subscription Bulk Order message is used to bulk several individual orders into one bulk order. The individual orders come from different instructing parties, but are related to the same financial instrument. The Subscription Bulk Order message can result in one single bulk cash settlement or several individual cash settlements.
This message cannot be used for a single order (a message containing one order for one instrument and for one investment account). The Subscription Multiple Order message, not the Subscription Bulk Order message, must be used for a single order.
Optional
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
FinancialInstrumentDetails
Mandatory
This tag provides details to identify a fund.
Identification
Mandatory
The fund can be identified based on the ISIN, Alternate Identification, RIC, Ticker Symbol, Bloomberg, CTA or Common.
IndividualOrderDetails
(Mandatory / Repetitive)
OrderReference
Mandatory
This is a unique identifier for an order, as assigned by the instructing party.
Cash Settlement Date
Optional
Incoming/Outgoing – Both, the Incoming and Outgoing indicators, will be the Transaction Settlement Date.
InvestmentAccountDetails
Account Identification à Proprietary à Identification
Mandatory
This tag is to identify an investor’s account. However, incase of a service provider installation, priority would be given to BeneficiaryDetails tag to get the identification type and identification number.
BeneficiaryDetails
Optional
Other Identification à Identification
Mandatory
Incoming – This would map to the Identification Number of the Unit holder.
Other Identification à Identification Type/ExtendedIdentificationType àStructured
Mandatory
This is a choice between Identification Type and Extended Identification Type.
Incoming – FCIS uses data mapping to find the Unit holder account type. Only PASS (passport) and NRIN (the National Registration Number, which is NRIC for Singapore) are supported as Identification Types.
Other Identification à Identification Type à Additional Information
Optional
If structured type is OTHR, the description of identification would be provided. For example, ‘Birth Certificate’.
Choice for Units / NetAmount
Mandatory
GrossAmount
Optional
ForeignExchangeDetails
Optional
This is information related to currency exchange or conversion.
The following sub tags are mandatory:
PhysicalDeliveryIndicator
Mandatory
This tag indicates whether or not the financial instrument is to be physically delivered.
CashSettlementDetails
Optional
Payment Instrument
Optional
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”.
PaymentCardDetails
(Mandatory / Choice)
Type
Mandatory
This indicates the type of card.
Payment Mode |
Sub Payment Mode |
Type |
R |
R |
CRDT |
R |
DR |
DBIT |
Number
Mandatory
Incoming/Outgoing – This will be the 16-digit Card Number.
Card Issuer Identification
Optional
This is the party that issues the card. FCIS supports identification based on the following tags:
Incoming: If BIC Or BEI is provided, the system will get the relevant bank information, if available. If Proprietary Identification is provided, the UDF mapping for the field would be used to determine the bank. This will be a set of other information fields applicable for entity type ‘Bank’.
Outgoing: As FCIS is capable of supporting both, the BIC Or BEI and Proprietary Identification, SWIFT UDF mapping will be used to determine the element that client would want to send.
ChequeDetails
(Mandatory / Choice)
Number
Mandatory
Incoming/Outgoing – This will be the Transaction Cheque Number.
Drawee Identification
Optional
This is to identify the bank details.
FCIS supports BIC and Proprietary Identification.
Incoming: If BIC is provided, system the will get the relevant bank information, if available. If Proprietary Identification is provided, the UDF mapping for the field would be used to determine the bank. This would be a set of other information fields applicable for entity type ‘Bank’.
Outgoing: As FCIS is capable of supporting both, the BIC and Proprietary Identification, SWIFT UDF mapping will be used to determine the element that client would want to send.
Credit Transfer Details
(Mandatory / Choice)
Reference
Optional
Incoming/Outgoing: This will be the Transaction Reference Number.
Debtor Details à Identification
Mandatory
FCIS supports Domestic Account based identification.
Incoming: The details available for Domestic Account will be used in conjunction with the element details of the tag First Agent 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.
Debtor Account à Name
Optional
This is the name of the account. It provides additional means of identification.
Outgoing - This will be the Transfer Account Holder Name of the transaction.
Debtor Agent
Mandatory
This is the financial institution that receives the payment transaction from the account owner.
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.
DirectDebitDetails
(Mandatory / Choice)
These are the details of the bank where the client has given a mandate to debit the account.
DebtorAccount
Mandatory
This tag will be used to identity the bank account of the investor. FCIS supports DomesticAccount based identification.
Incoming: The details available for DomesticAccount will be used in conjunction with the element details of the tag Debtor Agent 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.
Debtor Identification
Mandatory
This tag will be used to identity the bank account of the investor. FCIS supports DomesticAccount based identification.
Debtor Agent
Mandatory
This is used to identify the bank of the investor.
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.
Cash AccountDetails
(Mandatory / Choice)
AccountIdentification à Proprietary à Identification (Mandatory)
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.
Type à Structured
Mandatory
The following are the SWIFT supported codes for structured types along with the FCIS mapping:
Structured codes |
FCIS Map |
CASH |
No mapping |
CPFO |
CPFOA |
CPFS |
CPFSA |
OTHR |
ASPFOA / ASPFSA |
SRSA |
SRS |
This section contains the following topics:
This message is sent by an executing party to an intermediary party. This message is used to confirm the details of the execution of a Subscription Bulk Order message.
The Subscription Bulk Order Confirmation message is sent, after the price has been determined, to confirm the execution of all individual orders.
There is usually one bulk confirmation message for one bulk order message.
For all incoming messages, FCIS will set the status of transactions based on individual ‘Order Reference’ number.
For outgoing message, FCIS will generate the confirmation message only after allocation.
FCIS will allow generation of this message in an automated way (based on certain events triggered in the system, which have to be set for the message), or manually.
Mandatory
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.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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
This is the Reference Number to a linked message that was previously received.
Reference
Mandatory
Incoming: This reference number should be the Message Identification of the original message sent. This would be the link between confirmation message and original bulk order message.
Confirmation messages will be generated against each MessageIdentification/message.
Outgoing : FCIS will send the original ‘Message Identification’ number for the external system to establish the relation between original bulk order message and confirmation message.
Mandatory
This is general information related to the execution of investment orders.
Financial Instrument Details
Mandatory
This tag provides details to identify a fund.
Identification
Mandatory
Outgoing - FCIS sends out the fund ISIN.
Individual Execution Details
(Mandatory / Repetitive)
This is the individual execution of a subscription order.
OrderReference
Mandatory
Incoming: As this would be the Transaction Number handed off in the original message, FCIS will set the Order Status to ‘Confirmed’ depending on the Order Reference number communicated.
Outgoing: This will be mapped to the incoming ‘OrderReference’ corresponding to the transaction number that was allotted successfully by FCIS.
DealReference
Mandatory
This is a unique number assigned by the confirming party.
Incoming: This number is used for storage.
Outgoing: This would map to the Transaction Number generated by the system corresponding to the Order Reference number.
Settlement Amount
Optional
Oracle FLEXCUBE would pass settlement amount of the transaction in this tag.
Investment Account Details
Mandatory
AccountIdentification à Proprietary à Identification
Outgoing - The system uses the relevant UDF mapping for this tag.
Beneficiary Details
Optional
OtherIdentification à Identification
Mandatory
Outgoing: This would map to the Identification Number of the Unit holder.
OtherIdentification à IdentificationType
Mandatory
Outgoing: FCIS supports the Passport Number and NRIC as Identification Types. If the Unit Holder is identified differently, the value ‘OTHR’ would be passed, with the description in the tag AdditionalInformation.
OtherIdentification à ExtendedIdentificationType
Optional
If structured type is OTHR, the description of identification would be provided. For example, ‘Birth Certificate’. Identification other than NRIC and Passport would be passed in extended type with code as Identification Type description
Units Number
Mandatory
Unit
Mandatory
Outgoing: The allocated units for the transaction.
Net Amount
Mandatory
This is the net amount invested in a specific financial instrument by an investor, expressed in the currency requested by the investor.
Outgoing: The system will compute the net amount in transaction currency for transaction getting confirmed.
Gross Amount
Optional
Outgoing: This will be the settlement amount in the transaction currency available in the transaction data store.
Transaction Date Time
Mandatory
This is a choice between Date and DateTime.
Outgoing : Depending on the UDF mapping, the Transaction Date / Transaction Time will be passed.
DealingPriceDetails
Mandatory
This is the price at which order was executed.
ExtendedType
Mandatory
Outgoing : FCIS will support the code ‘OTHR’ only.
Value à Amount
Mandatory
Outgoing:This will be the allocation price for the transaction.
Partially Executed Indicator
Mandatory
This indicates whether the order has been partially executed.
Outgoing: This will be defaulted to ‘NO’.
Cum Dividend Indicator
Mandatory
This indicates whether the dividend (cum dividend) is included in the executed price. When the dividend is not included, the price will be ex-dividend.
Outgoing: This will be defaulted to ‘NO’.
Physical Delivery Indicator
Mandatory
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 script based.
This section contains the following topics:
This message is sent by an intermediary party to an executing party or to another intermediary party. The Subscription Bulk Order Cancellation Instruction message is used to cancel a previously sent Subscription Bulk Order message or a set of individual orders that it contains. There is no amendment, but a cancellation and re-instruct policy.
For all incoming bulk order cancellations, FCIS will process the reversals based on either the Previous Reference or individual Order Reference. For outgoing cancellation messages, FCIS will communicate the details of original transaction and not the newly reversed transaction, provided the original transaction was handed off to SWIFT. If a transaction is reversed before, neither transaction will be included in the SWIFT message.
For outgoing messages, FCIS will always provide the reference of the original message and group cancellations, if multiple transactions of the same batch have been reversed.
FCIS will allow the generation of this message in an automated way (based on a certain event that is triggered in the system, which can be set for the message), or manually.
Mandatory
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Creation Date Time
Optional
Applicable for incoming and outgoing message. This is the message generation date time.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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.
Optional
This is the reference to a linked message previously sent.
Reference
Mandatory
Incoming: If FCIS is receives this message, this reference number should be the Message Identification of the original message sent. This will be the link between cancellation message and the bulk order message.
If the tag ‘Order To Be Cancelled is not provided in the message, the system will identify the transactions to be reversed based on this link, as FCIS would have logged the bulk orders against the Message Identification.
Outgoing: FCIS will hand off only those reversals for which SWIFT bulk order was sent earlier.
This is common information related to all the orders to be cancelled.
Bulk Order Details
Mandatory
Financial Instrument Details
Mandatory
This tag provides details to identify a fund.
Outgoing : FCIS sends out the fund ISIN.
Individual Order Details
(Mandatory / Repetitive)
OrderReference
Mandatory
Incoming: The system will internally trigger a transaction reversal based on the transaction number logged earlier, corresponding to this order reference.
Outgoing: This will be the Transaction Number of original transaction, corresponding to the newly reversed transaction.
Investment Account Details
Mandatory
AccountIdentification à Proprietary à Identification
Outgoing: The system uses the relevant UDF mapping for this tag.
Beneficiary Details
Optional
Other Identification à Identification
Mandatory
Outgoing: This would map to the Identification Number of the Unit holder.
Other Identification à Identification Type
Mandatory
Outgoing: FCIS supports the Passport Number and NRIC as Identification Types. If the Unit Holder is identified differently, the value ‘OTHR’ would be passed, with the description in the tag Additional Information.
Other Identification à Extended Identification Type
Optional
If structured type is OTHR, the description of identification would be provided. For example, ‘Birth Certificate’.
Choice for Units / NetAmount
Mandatory
Outgoing: Irrespective of the ‘GrossOrNet’ indicator, amount transactions in FCIS, will be reported in the field ‘NetAmt’. However, if the transaction is ‘Gross’, the same will be additionally reported under the tag ‘GrossAmount’.
Unit based transactions will be passed under the tag Units.
Gross Amount
Optional
This is the gross amount invested in the fund.
Outgoing: This will map to transaction gross amount in the fund base currency, if available.
Foreign Exchange Details
Optional
This is information related to currency exchange or conversion.
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:
Physical Delivery Indicator
Mandatory
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.
Cash Settlement Date
Optional
Incoming/Outgoing: Both, the Incoming and Outgoing indicators, will be the Transaction Settlement Date.
This section contains the following topics:
This message is sent by an instructing party to an executing party. There may be one or more intermediary parties between the instructing party and the executing party. The Subscription Multiple Order message is used to subscribe to different financial instruments for the same investment account. It can result in one single bulk cash settlement or several individual cash settlements.
This message can also be used for single orders, i.e., a message containing one order for one financial instrument and related to one investment account.
The Subscription Multiple Order message, and not the Subscription Bulk Order message, must be used for a single order.
FCIS will allow generation of this message in an automated way (based on an event triggered) or manually. The grouping of multiple orders is driven by investment account and not the fund, as in the Subscription Bulk Order message.
Mandatory
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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
This is the account impacted by an investment fund order.
Identification à Proprietary à Identification
Mandatory
This tag is to identify an investor’s account. However, incase of a service provider installation, priority would be given to Owner Details 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.
Owner Identification
Optional
Incoming: If BICOrBEI is provided, the system will get the relevant bank information, if available. If Proprietary Identification is provided, the UDF mapping for the field would be used to determine the bank. This will be a set of other information fields applicable for entity type ‘Bank’.
Outgoing: As FCIS is capable of supporting both, the BICOrBEI and Proprietary Identification, SWIFT UDF mapping will be used to determine the element that client would want to send.
OrderReference
Mandatory
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.
This tag provides details to identify a fund.
Identification
Mandatory
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.
Choice for Units Number / Amount
Mandatory
Incoming: The system determines the Transaction Mode and Value depending on the element available. If the field ‘Amt’ 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 ‘GrossAmountIndicator’ 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 ‘Amt’. The transaction currency will be passed as tag attribute. However, if the transaction is ‘Gross’, the same will be reported under the optional tag ‘GrossAmountIndicator’ as well as the tag ‘Amt’, as this is mandatory.
Gross Amount Indicator
Optional
Incoming: If the value in this field is true, 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.
Commission Details
Optional
This indicates the load corresponding to the commission that is being overridden. The Load in the system can be identified using the Load Id or the Recipient information.
Type à Extended Type
Mandatory
Incoming: This will map to the Load Id. If BIC code, the system will find whether the entity is an agent, AMC, broker or distributor. System will select a load with the corresponding ‘To Entity Type’.
Choice for Amount/Rate
Mandatory
Incoming: If the ‘Amt’ is provided and the Load concerned is amount load, then this indicates the overridden value. However, if the field is ‘Rate’ is provided and the load concerned is percent load then this indicates the overridden value.
Waiving Details
Optional
This tag represents the override percentage that the system will apply. The value provided in this field will be ignored if ‘Amount’ or ‘Rate’ tags are provided since the values provided for those tags represent the final value.
Instruction Basis
Mandatory
This tag can have the value WICA. However the system will not use this value for any processing and hence will be ignored.
Waived Rate
Optional
This field provides the discount percentage. This is applicable only for percentage based loads. The override is by discount.
Physical Delivery Indicator
Mandatory
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.
Cash Settlement Date
Optional
Incoming/Outgoing: Both, the Incoming and Outgoing indicators, will be the Transaction Settlement Date.
Payment Instrument Choice
Optional
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”.
This is information related to an intermediary.
Identification
Mandatory
FCIS supports identification based on the following tags:
If BIC is provided, the system will get either the Broker BIC or the Entity BIC based on the client country parameter ‘TXNBROKERS’. If ProprietaryIdentification is provided, the value provided in this field should be a valid Entity Id or Broker Id in the system based on the client country parameter ‘TXNBROKERS’.
Extended Role
Optional
In case of entity, the values provided in this field can be ‘AGENT’, AGENCY BRANCH’, ‘IFA’ or ‘AO’. If none of the above values are specified, system will throw exception saying ‘Invalid ExtendedRole’.
This section contains the following topics:
This message is sent by an executing party to an instructing party. There may be one or more intermediary parties between the executing party and the instructing party. The Subscription Multiple Order Confirmation message is sent, after the price has been determined, to confirm the execution of the individual orders.
A Subscription Multiple Order can generate more than one Subscription Multiple Order Confirmation message, as the valuation cycle of the financial instruments of each individual order may be different. When the executing party sends several confirmations, there is no specific indication in the message that it is an incomplete confirmation. Reconciliation must be based on the references.
A Subscription Multiple Order must in be answered by the Subscription Multiple Order Confirmation message(s) and in no circumstances by the Subscription Bulk Order Confirmation message(s).
For all incoming messages, FCIS will be able to set the status of transactions based on the individual ‘Order Reference’ number. For outgoing messages, the system will be able to generate the confirmation message only after allocation. Transactions will be grouped based on the original Multiple Order Message.
FCIS will allow generation of this message in an automated way (based on a certain event that is triggered in the system) or manually.
Optional
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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
This is the Reference Number to a linked message that was previously received.
Reference
Mandatory
Incoming: This reference number should be the Message Identification of the original message sent. This would be the link between confirmation message and original bulk order message.
The confirmation messages will be generated against each MessageIdentification/ message.
Outgoing: FCIS will send the original ‘Message Identification’ number for the external system to establish the relation between original bulk order message and confirmation message.
Mandatory
OrderDateTime
Optional
Outgoing: This will be mapped to the transaction save time.
Identification à Proprietary à Identification
Outgoing: The system uses the relevant UDF mapping for this tag.
Settlement Amount
Optional
ORACLE FLEXCUBE would pass settlement amount of the transaction in this tag.
This is the individual execution of a subscription order.
OrderReference
Mandatory
Incoming: As this would be the Transaction Number handed off in the original message, FCIS will set the Order Status to ‘Confirmed’ depending on the Order Reference number communicated.
Outgoing: This will be mapped to the incoming ‘OrderReference’ corresponding to the transaction number that was allotted successfully by FCIS.
Deal Reference
Mandatory
This is a unique number assigned by the confirming party.
Incoming: This number is used for storage.
Outgoing: This would map to the Transaction Number generated by the system corresponding to the Order Reference number.
This tag provides details to identify a fund.
Identification
Mandatory
Outgoing: FCIS sends out the fund ISIN.
Units Number
Mandatory
UnitsNumber
Mandatory
Outgoing: The allocated units for the transaction.
Amount
Mandatory
This is the net amount invested in a specific financial instrument by an investor, expressed in the currency requested by the investor.
Outgoing: The system will compute the net amount in transaction currency for transaction getting confirmed.
Gross Amount Indicator
Optional
Outgoing: This will be the settlement amount in the transaction currency available in the transaction data store.
Transaction Date Time
Mandatory
This tag provides the transaction date
Outgoing: Depending on the UDF mapping, the Transaction Date will be passed.
Price Details
Mandatory
This is the price at which order was executed.
Value à Amount
Mandatory
Outgoing: This will be the allocation price for the transaction.
Partially Executed Indicator
Mandatory
This indicates whether the order has been partially executed.
Outgoing: This will be defaulted to ‘NO’.
Cum Dividend Indicator
Mandatory
This indicates whether the dividend (cum dividend) is included in the executed price. When the dividend is not included, the price will be ex-dividend.
Outgoing: This will be defaulted to ‘NO’.
Optional
This is information related to currency exchange or conversion.
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:
Commission General Details
Optional
This indicates the load corresponding to the ‘From Entity Type’ ‘U’ and ‘To Entity Type’ ‘F’.
TotalAmountofCommissions
Optional
Outgoing – FCIS sends out the value of the load where the ‘From Entity Type’ is ‘U’and ‘To Entity Type’ is ‘F’.
CommissionDetails
Type à Extended Type
Mandatory
Outgoing: This would map to the Identification Number of the Load. If BIC is provided, this would map to the corresponding entity’s BIC.
Amount
Mandatory
Outgoing: This tag corresponds to the individual Loads under the main U-F load viz. F-M and F-A loads.
Rate
Optional
This tag corresponds to the rates of individual Loads under the main U-F load viz. F-M and F-A loads.
ChargeGeneralDetails
Optional
This tag corresponds to the sum of all the loads other than the load mentioned in the ‘CommissionGeneralDetails’ tag.
TotalAmountofCharges
Optional
Outgoing: FCIS sends out the sum f all the loads other than the load mentioned in the ‘CommissionGeneralDetails’ tag.
ChargeDetails
Type à Unstructured or RecipientIdentification à BICOrBEI
Mandatory
Outgoing: This would map to the Identification Number of the Load. If BIC is provided, this would map to the corresponding entity’s BIC.
Amount
Mandatory
Outgoing: The load amount in terms of the fund base currency.
PhysicalDeliveryIndicator
Mandatory
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.
RelatedPartyDetails
Optional
This is information related to an intermediary.
Identification à Proprietary à Identification
Mandatory
Outgoing - Identification of the agent, agency branch, AO or IFA as maintained in FCIS.
ExtendedRole
Optional
In case of entity, the values provided in this field can be ‘AGENT’, AGENCY BRANCH’, ‘IFA’, ‘BROKER’ or ‘AO’.
This section contains the following topics:
This message is sent by an instructing party to an executing party. There may be one or more intermediary parties between the instructing party and the executing party. The Subscription Multiple Order Cancellation Instruction message is used to cancel the entire previously sent order message and all the individual orders that it contained. There is no amendment, but a cancellation and re-instruct policy.
A cancellation instruction must always be of the same family of message, i.e., switch, redemption or subscription and bulk or multiple, as the original order to be cancelled.
For all incoming multiple order cancellations, FCIS will be able to process the reversals based on either the Previous Reference or individual Order Reference.
For outgoing cancellation messages, FCIS will communicate the details of original transaction, and not the newly reversed transaction, provided the original transaction was handed off to SWIFT. If a transaction has been reversed, neither of the transactions will be included in the SWIFT message.
For outgoing messages, FCIS will always provide the reference of the original message and group cancellations, if multiple transactions of the same batch have been reversed. FCIS will allow the generation of this message in an automated way (based on a certain event that is triggered in the system), or manually.
Mandatory
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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.
Optional
This is the reference to a linked message previously sent.
Reference
Mandatory
Incoming: If FCIS is receives this message, this reference number should be the Message Identification of the original message sent. This will be the link between cancellation message and the bulk order message.
If the tag ‘Order To Be Cancelled is not provided in the message, the system will identify the transactions to be reversed based on this link, as FCIS would have logged the bulk orders against the Message Identification.
Outgoing: FCIS will hand off only those reversals for which SWIFT bulk order was sent earlier.
This is common information related to all the orders to be cancelled.
MultipleOrderDetails
Mandatory
InvestmentAccountDetails
Mandatory
AccountIdentification à Proprietary à Identification
Outgoing - The system uses the relevant UDF mapping for this tag.
BeneficiaryDetails
Optional
OtherIdentification à Identification
Mandatory
Outgoing - This would map to the Identification Number of the Unit holder.
OtherIdentification à IdentificationType
Mandatory
Outgoing - FCIS supports the Passport Number and NRIC as Identification Types. If the Unit Holder is identified differently, the value ‘OTHR’ would be passed, with the description in the tag AdditionalInformation.
OtherIdentification à ExtendedIdentificationType
Optional
If structured type is OTHR, the description of identification would be provided. For example, ‘Birth Certificate’. Identification other than NRIC and Passport would be passed in extended type with code as Identification Type description.
IndividualOrderDetails
(Mandatory / Repetitive)
OrderReference
Mandatory
Incoming – The system will internally trigger a transaction reversal based on the transaction number logged earlier, corresponding to this order reference.
Outgoing - This will be the Transaction Number of original transaction, corresponding to the newly reversed transaction.
FinancialInstrumentDetails
Mandatory
Identification
Mandatory
This tag provides details to identify a fund.
Outgoing - FCIS sends out the fund ISIN.
Choice for Units / NetAmount
Mandatory
Outgoing : Irrespective of the ‘GrossOrNet’ indicator, amount transactions in FCIS, will be reported in the field ‘NetAmt’. However, if the transaction is ‘Gross’, the same will be additionally reported under the tag ‘GrossAmount’.
Unit based transactions will be passed under the tag Units.
GrossAmount
Optional
Outgoing: This will map to transaction gross amount in the fund base currency, if available.
ForeignExchangeDetails
Optional
This is information related to currency exchange or conversion.
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:
PhysicalDeliveryIndicator
Mandatory
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.
CashSettlementDate
Optional
Outgoing: This will be the Transaction Settlement Date.
This section contains the following topics:
This message is sent by an intermediary party to an executing party or to another intermediary party.
The Redemption Bulk Order message is used to bulk several individual orders into one bulk order. The individual orders come from different instructing parties, i.e., account owners, but are related to the same financial instrument. The Redemption Bulk Order can result in one single bulk cash settlement or several individual cash settlements.
This message will typically be used by a party collecting order, to bulk those individual orders into one bulk order before sending it to another party.
This message cannot be used for a single order, i.e., a message containing one order for one financial instrument and for one investment account. The Redemption Multiple Order message, and not the Redemption Bulk Order message, must be used for a single order.
FCIS will allow the generation of this message in an automated way (based on certain event that is triggered in the system) or manually.
Optional
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Creation Date Time
Optional
This is applicable for incoming and outgoing message. This is the message generation date time.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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
FinancialInstrumentDetails
Mandatory
This tag provides details to identify a fund.
Identification
Mandatory
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.
IndividualOrderDetails
(Mandatory / Repetitive)
OrderReference
Mandatory
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.
InvestmentAccountDetails
Mandatory
AccountIdentification à Proprietary à Identification
Mandatory
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.
BeneficiaryDetails
Optional
OtherIdentification à Identification
Mandatory
Incoming: This would map to the Identification Number of the Unit holder.
OtherIdentification à IdentificationType
Mandatory
Incoming : FCIS uses data mapping to find the Unit holder account type.
Choice for Units / NetAmount/Holdings Redemption Rate
Mandatory
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.
GrossAmount
Optional
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.
ForeignExchangeDetails
Optional
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:
PhysicalDeliveryIndicator
Mandatory
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.
CashSettlementDate
Optional
Incoming/Outgoing: Both, the Incoming and Outgoing indicators, will be the Transaction Settlement Date.
PaymentInstrument
Optional
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”.
CreditTransferDetails
(Mandatory / Choice)
Reference
Optional
Incoming/Outgoing: This will be the TransactionReferenceNumber.
CreditorDetails à AccountIdentification à Identification
Mandatory
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.
CreditorDetails à AccountIdentification à Name
Optional
This is the name of the account. It provides additional means of identification.
Outgoing: This will be the TransferAccountHolderName of the transaction.
CreditorDetails à FinalAgent
Mandatory
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.
ChequeDetails
(Mandatory / Choice)
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.
AccountDetails
(Mandatory / Choice)
AccountIdentification à Proprietary à Identification (Mandatory)
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.
Type à Structured
Mandatory
The following are the SWIFT supported codes for structured types along with the FCIS mapping:
Structured codes |
FCIS Map |
CASH |
No mapping |
CPFO |
CPFOA |
CPFS |
CPFSA |
OTHR |
ASPFOA / ASPFSA |
SRSA |
SRS |
This section contains the following topics:
This message is sent by an executing party to a intermediary party or to another intermediary party. The Redemption Bulk Order Confirmation message is sent, after the price has been determined, to confirm the execution of all individual orders. There is usually one bulk confirmation message for one bulk order message.
For all incoming messages, FCIS will be able to set the status of transactions based on the individual ‘Order Reference’ number. For outgoing messages, the system will be able to generate the confirmation message only after allocation.
FCIS will allow the generation of this message in an automated way (based on certain event that is triggered in the system), or manually.
Mandatory
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.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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.
Creation Date Time
Optional
Applicable for incoming and outgoing message. This is the message generation date time.
Mandatory
This is the Reference Number to a linked message that was previously received.
Reference
Mandatory
Incoming: This reference number should be the Message Identification of the original message sent. This would be the link between confirmation message and original bulk order message.
The confirmation messages will be generated against each MessageIdentification/ message.
Outgoing : FCIS will send the original ‘Message Identification’ number for the external system to establish the relation between original bulk order message and confirmation message.
Mandatory
This is general information related to the execution of investment orders.
FinancialInstrumentDetails
Mandatory
This tag provides details to identify a fund.
Identification
Mandatory
Outgoing - FCIS sends out the fund ISIN.
IndividualExecutionDetails
(Mandatory / Repetitive)
This is the individual execution of a subscription order.
OrderReference
Mandatory
Incoming - As this would be the Transaction Number handed off in the original message, FCIS will set the Order Status to ‘Confirmed’ depending on the Order Reference number communicated.
Outgoing - This will be mapped to the incoming ‘OrderReference’ corresponding to the transaction number that was allotted successfully by FCIS.
DealReference
Mandatory
This is a unique number assigned by the confirming party.
Incoming - This number is used for storage.
Outgoing – This would map to the Transaction Number generated by the system corresponding to the Order Reference number.
InvestmentAccountDetails
Mandatory
AccountIdentification à Proprietary à Identification
Outgoing: The system uses the relevant UDF mapping for this tag.
BeneficiaryDetails
Optional
UnitsNumber
Mandatory
Unit
Mandatory
Outgoing – The allocated units for the transaction.
NetAmount
Mandatory
This is the net amount invested in a specific financial instrument by an investor, expressed in the currency requested by the investor.
Outgoing: This would be settlement amount of redemption transaction available in transaction currency.
GrossAmount
Optional
Outgoing: This will be the settlement amount in the transaction currency available in the transaction data store.
TransactionDateTime
Mandatory
This is a choice between Date and DateTime.
Outgoing: Depending on the UDF mapping, the Transaction Date / Transaction Time will be passed.
DealingPriceDetails
Mandatory
This is the price at which order was executed.
ExtendedType
Mandatory
Outgoing: FCIS will support the code ‘OTHR’ only.
Value à Amount
Mandatory
Outgoing: This will be the allocation price for the transaction.
PartiallyExecutedIndicator
Mandatory
This indicates whether the order has been partially executed.
Outgoing: This will be defaulted to ‘NO’.
CumDividendIndicator
Mandatory
This indicates whether the dividend (cum dividend) is included in the executed price. When the dividend is not included, the price will be ex-dividend.
Outgoing: This will be defaulted to ‘NO’.
PhysicalDeliveryIndicator
Mandatory
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.
This section contains the following topics:
This message is sent by an intermediary party to an executing party or to another intermediary party. The Redemption Bulk Order Cancellation Instruction message is used to cancel the entire previously sent order message and all of the individual orders that it contained. There is no amendment, but a cancellation and re-instruct policy.
A cancellation instruction must always be of the same family of message, i.e., switch, redemption or subscription and bulk or multiple, as the original order to be cancelled.
For all incoming bulk order cancellations, FCIS will be able to process the reversals based on either the Previous Reference or the individual Order Reference. For outgoing cancellation messages, FCIS will communicate the details of original transaction and not the newly reversed transaction, provided the original transaction has been handed off to SWIFT. If a transaction is reversed before neither of the transactions will be included in the SWIFT message.
For outgoing messages, FCIS will always provide the reference of the original message and group cancellations, if multiple transactions of the same batch have been reversed. FCIS will allow the generation of this message in an automated way (based on certain event that is triggered in the system) or manually.
Mandatory
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Creation Date Time
Optional
Applicable for incoming and outgoing message. This is the message generation date time.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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.
Optional
This is the reference to a linked message previously sent.
Reference
Mandatory
Incoming: If FCIS is receives this message, this reference number should be the Message Identification of the original message sent. This will be the link between cancellation message and the bulk order message.
If the tag ‘Order To Be Cancelled is not provided in the message, the system will identify the transactions to be reversed based on this link, as FCIS would have logged the bulk orders against the Message Identification.
Outgoing: FCIS will hand off only those reversals for which SWIFT bulk order was sent earlier.
This is common information related to all the orders to be cancelled.
FinancialInstrumentDetails
Mandatory
This tag provides details to identify a fund.
Identification
Mandatory
Outgoing - FCIS sends out the fund ISIN.
IndividualOrderDetails
(Mandatory / Repetitive)
OrderReference
Mandatory
Incoming: The system will internally trigger a transaction reversal based on the transaction number logged earlier, corresponding to this order reference.
Outgoing : This will be the Transaction Number of original transaction, corresponding to the newly reversed transaction.
InvestmentAccountDetails
Mandatory
AccountIdentification à Proprietary à Identification
Outgoing - The system uses the relevant UDF mapping for this tag.
BeneficiaryDetails
Optional
OtherIdentification à Identification
Mandatory
Outgoing: This would map to the Identification Number of the Unit holder.
OtherIdentification à IdentificationType
Mandatory
Outgoing - FCIS supports the Passport Number and NRIC as Identification Types. If the Unit Holder is identified differently, the value ‘OTHR’ would be passed, with the description in the tag AdditionalInformation.
OtherIdentification à ExtendedIdentificationType
Optional
If structured type is OTHR, the description of identification would be provided. For example, ‘Birth Certificate’. Identification other than NRIC and Passport would be passed in extended type with code as Identification Type description.
Choice for Units / NetAmount/HoldingsRedemptionRate
Mandatory
Outgoing – Irrespective of the ‘GrossOrNet’ indicator, amount transactions in FCIS, will be reported in the field ‘NetAmt’. However, if the transaction is ‘Gross’, the same will be additionally reported under the tag ‘GrossAmount’.
Unit based transactions will be passed under the tag Units.
Percentage based transactions will be passed under the tag HoldingsRedemptionRate.
GrossAmount
Optional
This is the gross amount invested in the fund.
Outgoing: This will map to transaction gross amount in the fund base currency, if available.
ForeignExchangeDetails
Optional
This is information related to currency exchange or conversion.
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:
PhysicalDeliveryIndicator
Mandatory
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.
CashSettlementDate
Optional
Incoming/Outgoing: Both, the Incoming and Outgoing indicators, will be the Transaction Settlement Date.
This section contains the following topics:
This message is sent by an instructing party to an executing party. There may be one or more intermediary parties between the instructing party and the executing party. The Redemption Multiple Order message is used to redeem different financial instruments from the same investment account. It can result in one single bulk cash settlement or several individual cash settlements.
This message can also be used for single orders, i.e., a message containing one order for one financial instrument and related to one investment account. The Redemption Multiple Order message, and not the Redemption Bulk Order message, must be used for a single order.
FCIS would allow generation of this message in an automated way (based on an event) or manually. The grouping of multiple orders is driven by the investment account and not the fund as in a bulk order message.
Mandatory
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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
InvestmentAccountDetails
Mandatory
This is the account impacted by an investment fund order.
Identification à Proprietary à Identification
Mandatory
This tag is to identify an investor’s account. However, incase of a service provider installation, priority would be given to OwnerIdentification 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.
IndividualOrderDetails
(Mandatory / Repetitive)
OrderReference
Mandatory
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.
FinancialInstrumentDetails
Mandatory
This tag provides details to identify a fund.
Identification
Mandatory
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.
Choice for UnitsNumber / Amount/HoldingsRedemptionRate
Mandatory
Incoming: The system determines the Transaction Mode and Value depending on the element available. If the field ‘Amt’ 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 ‘GrossAmountIndicator’ 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 ‘Amt’. The transaction currency will be passed as tag attribute. However, if the transaction is ‘Gross’, the same will be reported under the optional tag ‘GrossAmountIndicator’ as well as the tag ‘Amt’, as this is mandatory.
GrossAmountIndicator
Optional
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.
CommissionDetails
Optional
This indicates the load corresponding to the commission that is being overridden. The Load in the system can be identified using the Load Id or the Recipient information.
Type à Extended
Mandatory
Incoming – This will map to the Load Id.
Choice for Amount/Rate
Mandatory
Incoming - If the ‘Amt’ is provided and the Load concerned is amount load, then this indicates the overridden value. However, if the field is ‘Rate’ is provided and the load concerned is percent load then this indicates the overridden value.
RecipientIdentification
Optional
If a value is provided in this field, FCIS supports identification based on the following tags:
If BIC code, the system will find whether the entity is an agent, AMC, broker or distributor. System will select a load with the corresponding ‘To Entity Type’.
Waiving Details
Optional
This tag represents the override percentage that the system will apply. Waive details have higher precedence over ‘Rate’ hence ‘Rate’ will be ignored if ‘Waiving details’ are provided.
InstructionBasis
Mandatory
This tag can have the value WICA. However the system will not use this value for any processing and hence will be ignored.
WaivedRate
Optional
This field provides the discount percentage. This is applicable only for percentage based loads. The override is by discount.
ForeignExchangeRate
Optional
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:
PhysicalDeliveryIndicator
Mandatory
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.
PaymentInstrumentChoice
Optional
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”.
CashSettlementDate
Optional
Incoming/Outgoing – Both, the Incoming and Outgoing indicators, will be the Transaction Settlement Date.
RelatedPartyDetails
Optional
This is information related to an intermediary.
Identification
Mandatory
FCIS supports identification based on the following tags:
If BIC is provided, the system will get either the Broker BIC or the Entity BIC based on the client country parameter ‘TXNBROKERS’. If ProprietaryIdentification is provided, the value provided in this field should be a valid Entity Id or Broker Id in the system based on the client country parameter ‘TXNBROKERS’.
ExtendedRole
Optional
In case of entity, the values provided in this field can be ‘AGENT’, AGENCY BRANCH’, ‘IFA’ or ‘AO’. If ExtendedRole is not one of the mentioned ones, system will throw error.
This section contains the following topics:
This message is sent by an executing party to an instructing party. There may be one or more intermediary parties between the executing party and the instructing party. The Redemption Multiple Order Confirmation message is sent, after the price has been determined, to confirm the execution of all individual orders.
Redemption Multiple Order can be generated by more than one Redemption Multiple Order Confirmation, as the valuation cycle of the financial instruments of each individual order may be different.
When the executing party sends several confirmations, there is no specific indication in the message that it is an incomplete confirmation. Reconciliation must be based on the references.
A Redemption Multiple Order response should be the Redemption Multiple Order Confirmation message(s) and in no circumstances by the Redemption Bulk Order Confirmation message(s).
For all incoming messages, FCIS will be able to set the status of transactions based on the individual ‘Order Reference’ number. For outgoing messages, the system will be able to generate the confirmation message only after allocation. Transactions will be grouped based on the original Multiple Order Message.
FCIS will allow generation of this message in an automated way (based on certain event that is triggered in the system) or manually.
Optional
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Creation Date Time
Optional
This is applicable for incoming and outgoing message. This is the message generation date time.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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
This is the Reference Number to a linked message that was previously received.
Reference
Mandatory
Incoming: This reference number should be the Message Identification of the original message sent. This would be the link between confirmation message and original bulk order message.
The confirmation messages will be generated against each Masterreference/ message.
Outgoing: FCIS will send the original ‘Message Identification’ number for the external system to establish the relation between original bulk order message and confirmation message.
Mandatory
OrderDateTime
Optional
Outgoing – This will be mapped to the transaction save time.
InvestmentAccountDetails
Mandatory
AccountIdentification à Proprietary à Identification
Outgoing - The system uses the relevant UDF mapping for this tag.
IndividualExecutionDetails
(Mandatory / Repetitive)
This is the individual execution of a subscription order.
OrderReference
Mandatory
Incoming - As this would be the Transaction Number handed off in the original message, FCIS will set the Order Status to ‘Confirmed’ depending on the Order Reference number communicated.
Outgoing - This will be mapped to the incoming ‘OrderReference’ corresponding to the transaction number that was allotted successfully by FCIS.
DealReference
Mandatory
This is a unique number assigned by the confirming party.
Incoming: This number is used for storage.
Outgoing: This would map to the Transaction Number generated by the system corresponding to the Order Reference number.
SettlementAmount
Optional
ORACLE FLEXCUBE would pass settlement amount of the transaction in this tag.
FinancialInstrumentDetails
Mandatory
This tag provides details to identify a fund.
Identification
Mandatory
Outgoing - FCIS sends out the fund ISIN.
UnitsNumber
Mandatory
UnitsNumber
Mandatory
Outgoing: The allocated units for the transaction.
Amount
Mandatory
This is the net amount invested in a specific financial instrument by an investor, expressed in the currency requested by the investor.
Outgoing: This is be settlement amount of the redemption transaction available in the transaction currency.
GrossAmountIndicator
Optional
Outgoing: This will be ‘true’ is the amount is ‘Net’ else ‘false’.
TransactionDateTime
Mandatory
This tag provides the transaction date
Outgoing: Depending on the UDF mapping, the Transaction Date will be passed.
Value à Amount
Mandatory
Outgoing: This will be the allocation price for the transaction.
PartiallyExecutedIndicator
Mandatory
This indicates whether the order has been partially executed.
Outgoing: This will be defaulted to ‘NO’.
CumDividendIndicator
Mandatory
This indicates whether the dividend (cum dividend) is included in the executed price. When the dividend is not included, the price will be ex-dividend.
Outgoing: This will be defaulted to ‘NO’.
ForeignExchangeDetails
Optional
This is information related to currency exchange or conversion.
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:
CommissionGeneralDetails
Optional
This indicates the load corresponding to the ‘From Entity Type’ ‘U’ and ‘To Entity Type’ ‘F’.
TotalAmountofCommissions
Optional
Outgoing – FCIS sends out the value of the load where the ‘From Entity Type’ is ‘U’and ‘To Entity Type’ is ‘F’.
CommissionDetails
Amount
Mandatory
Outgoing – This tag corresponds to the individual Loads under the main U-F load viz. F-M and F-A loads.
Rate
Optional
This tag corresponds to the rates of individual Loads under the main U-F load viz. F-M and F-A loads.
ChargeGeneralDetails
Optional
This tag corresponds to the sum of all the loads other than the load mentioned in the ‘CommissionGeneralDetails’ tag.
TotalAmountofCharges
Optional
Outgoing: FCIS sends out the sum f all the loads other than the load mentioned in the ‘CommissionGeneralDetails’ tag.
ChargeDetails
Type à Unstructured or RecipientIdentification à BICOrBEI
Mandatory
Outgoing: This would map to the Identification Number of the Load. If BIC is provided, this would map to the corresponding entity’s BIC.
Amount
Mandatory
Outgoing: The load amount in terms of the fund base currency.
PhysicalDeliveryIndicator
Mandatory
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.
RelatedPartyDetails
Optional
This is information related to an intermediary.
Identification à Proprietary à Identification
Mandatory
Outgoing: Identification of the agent, agency branch, AO or IFA as maintained in FCIS.
ExtendedRole
Optional
In case of entity, the values provided in this field can be ‘AGENT’, AGENCY BRANCH’, ‘IFA’ ‘BROKER’ or ‘AO’. If none of these values are specified, then system will look for the specified entity. An error will be thrown if more than one entity type has the same name.
This section contains the following topics:
This message is sent by an instructing party to an executing party. There may be one or more intermediary parties between the instructing party and the executing party.
The Redemption Multiple Order Cancellation Instruction message is used to cancel the entire previously sent order message and all of the individual orders that it contained. There is no amendment, but a cancellation and re-instruct policy.
A cancellation instruction must always be of the same family of message, i.e., switch, redemption or subscription and bulk or multiple, as the original order to be cancelled.
For all incoming multiple order cancellations, FCIS will be able to process the reversals based on either the Previous Reference or the individual Order Reference. For outgoing cancellation messages, FCIS will communicate the details of original transaction and not the newly reversed transaction provided the original transaction was handed off to SWIFT. If a transaction has been reversed before, neither of the transactions will be included in the SWIFT message.
For outgoing messages, FCIS will always provide the reference of the original message and group cancellations, if multiple transactions of the same batch have been reversed. FCIS will allow generation of this message in an automated way (based on certain event that is triggered in the system) or manually.
Mandatory
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Creation Date Time
Optional
This is applicable for incoming and outgoing message. This is the message generation date time.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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.
Optional
This is the reference to a linked message previously sent.
Reference
Mandatory
Incoming: If FCIS is receives this message, this reference number should be the Message Identification of the original message sent. This will be the link between cancellation message and the bulk order message.
If the tag ‘Order To Be Cancelled is not provided in the message, the system will identify the transactions to be reversed based on this link, as FCIS would have logged the bulk orders against the Message Identification.
Outgoing: FCIS will hand off only those reversals for which SWIFT bulk order was sent earlier.
This is common information related to all the orders to be cancelled.
MultipleOrderDetails
Mandatory
InvestmentAccountDetails
Mandatory
AccountIdentification à Proprietary à Identification
Outgoing: The system uses the relevant UDF mapping for this tag.
BeneficiaryDetails
Optional
OtherIdentification à Identification
Mandatory
Outgoing: This would map to the Identification Number of the Unit holder.
OtherIdentification à IdentificationType
Mandatory
Outgoing: FCIS supports the Passport Number and NRIC as Identification Types. If the Unit Holder is identified differently, the value ‘OTHR’ would be passed, with the description in the tag AdditionalInformation.
OtherIdentification à ExtendedIdentificationType
Optional
If structured type is OTHR, the description of identification would be provided. E Example, ‘Birth Certificate’. Identification other than NRIC and Passport would be passed in extended type with code as Identification Type description.
IndividualOrderDetails
(Mandatory / Repetitive)
OrderReference
Mandatory
Incoming: The system will internally trigger a transaction reversal based on the transaction number logged earlier, corresponding to this order reference.
Outgoing: This will be the Transaction Number of original transaction, corresponding to the newly reversed transaction.
FinancialInstrumentDetails
Mandatory
Identification
Mandatory
This tag provides details to identify a fund.
Outgoing: FCIS sends out the fund ISIN.
Choice for Units / NetAmount/HoldingsRedemptionRate
Mandatory
Outgoing: Irrespective of the ‘GrossOrNet’ indicator, amount transactions in FCIS, will be reported in the field ‘NetAmt’. However, if the transaction is ‘Gross’, the same will be additionally reported under the tag ‘GrossAmount’.
Unit based transactions will be passed under the tag Units.
Percentage based transactions will be passed under the HoldingsRedemptionRate tag.
GrossAmount
Optional
Outgoing:This will map to transaction gross amount in the fund base currency, if available.
ForeignExchangeDetails
Optional
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:
PhysicalDeliveryIndicator
Mandatory
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.
CashSettlementDate
Optional
Incoming/Outgoing: This will be the Transaction Settlement Date.
This section contains the following topics:
The Request For Order Status Report is sent by an instructing party to the executing party. There may be one or more intermediary parties between the instructing party and the executing party.
The Request For Status Report message is used to request the status of
If the Request For Order Status Report message is used to request the status of several messages, then the instructing party will receive several reply messages from the executing party, i.e., several Order Instruction Status Report messages and/or Order Cancellation Status Report messages. The number of reply messages will match the number of references stated in the Request For Order Status Report message.
The Request For Status Report message may not be used to request the status of an investment account, a transfer or the status of a financial instrument.
FCIS allows a manual trigger for the Request For Order Status Report. The user has the flexibility to select the references to the previously sent messages of various types, i.e., subscription, redemption, switch and cancellations and individual transactions within the same, if required.
FCIS will generate the Request For Order Status Report message for every reference number selected by the user.
A request for the status for the following is possible:
If FCIS is the receiving party of this message, the ‘Order Instruction Status Report’ or ‘Order Cancellation Status Report’, or both, will be generated, depending upon the individual ‘Previous Reference à Reference’.
Mandatory/Repetitive
This is to identify the order(s) for which the status is requested.
Choice (OtherReference/PreviousReference)
Mandatory
Incoming/Outgoing - FCIS will support the tag ‘PreviousReference’ for incoming and outgoing messages.
PreviousReference à Reference
Mandatory
Incoming: If the tag ‘IndividualOrderReference’ is not provided, the system will use this reference to identify the transactions for which status message is requested. This will be the MessageIdentification number of the original bulk / multiple / cancellation order request.
Outgoing: This will be the individual MessageIdentification number selected by the user from the online option.
IndividualOrderReference
Optional/Repetitive
Incoming: If the individual order references are provided, the system will generate the reply message corresponding to the transaction number for this order reference.
Outgoing: This will be the OrderReference numbers corresponding to the transactions selected by the user for status request.
This section contains the following topics:
The Order Instruction Status Report is sent by an executing party to an instructing party. There may be one or more intermediary parties between the executing party and the instructing party.
The Order Instruction Status Report message is sent by an executing party to the instructing party to report on the status of a subscription, redemption or a switch order. The message can be used to report one of the following:
Further information about the repair, unmatched, rejected or pending settlement statuses must be specified using either codes or unstructured information.
For subscription and redemption orders, this message covers both bulk and multiple categories of orders, and this message may provide the status either at the bulk or at the individual level. For a switch order, however, the message provides the status of the whole order. It is not possible to accept one leg and to reject the other leg. The entire switch order has to be rejected. In order to identify which leg within the switch is causing a problem, the switch order leg identification is used.
FCIS will receive the ‘Order Instruction Status Report’ in response to ‘Request For Order Status’ message generated. This information will be used to set the status of individual orders. FCIS will generate the ‘Order Instruction Status Report’ in response to the ‘Request For Order Status’ message received, provided the Message Identification number communicated to FCIS in the tag Previous Reference relates to bulk / multiple or switch order, as cancellation is reported through a different message.
For Switch order responses, FCIS will reply with the status under the Order Details Report section as it is not possible to accept one leg of the switch and reject another leg. For other orders, FCIS will reply with the status under Individual Order Details Report section. However, if the original message has been suppressed or has not been processed, FCIS will report the failure under the section Order Details Report à Suspended.
The following is the structure of the message:
Mandatory
Reference
Mandatory
Incoming: FCIS will support the tag ‘PreviousReference à Reference’ communicated in the message ‘Request For Order Status’. This number will be used to set the status of underlying transactions if the individual order details are not reported.
Outgoing : FCIS will support the tag ‘PreviousReference à Reference’ communicated in the message ‘Request For Order Status’. This will be the ‘MessageIdentification’ number of the original order.
Optional
Reference
Mandatory
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.
Creation Date Time
Optional
Applicable for incoming and outgoing message. This is the message generation date time.
If the OrderDetailsReport section is provided in the message, FCIS will use the status reported in this section in conjunction with the RelatedReference to set the status of underlying transactions. On the other hand, if the section IndividualOrderDetailsReport is provided, FCIS will use the OrderReference to track the order status.
Incoming: Only status tracking will happen. FCIS will not track the reason for rejection, if any.
Outgoing: FCIS supports the reporting of the following statuses under IndividualOrderDetailsReport:
OrderReference
Mandatory
Incoming: FCIS will track the status for the transaction number generated corresponding to this order reference.
Outgoing: This is the Order Reference number corresponding to the transaction number for which status is getting reported.
This section contains the following topics:
The Order Cancellation Status Report is sent by an executing party to the instructing party. There may be one or more intermediary parties between the executing party and the instructing party.
The Order Cancellation Status Report message is used to report the status of an order cancellation instruction message that was previously sent by the instructing party. The message can be used to report that the cancellation has either been acted upon or has been rejected.
Incoming: FCIS will receive the ‘Order Cancellation Status Report’ in response to the ‘Request For Order Status’ if the Previous Reference tag has reference to the order cancellation message. This information would be used to set the status of individual orders.
Outgoing: FCIS will generate the ‘Order Cancellation Status Report’ in response to the ‘Request For Order Status’ message received, provided the Message Identification number communicated to FCIS in the Previous Reference tag relates to bulk / multiple or switch order cancellation.
Note
FCIS will generate one cancellation status message for every transaction that has been cancelled as a result of the cancellation instruction.
The following is the structure of the message:
FCIS supports both, repetitive tags to pass the related reference, and the order reference.
Reference - Iteration 1
Mandatory
Incoming - FCIS will support the tag ‘Previous Reference à Reference’ communicated in the message ‘Request For Order Status’. This number will be used to set the status of underlying transactions if the individual order details are not reported.
Outgoing - FCIS will support the tag ‘Previous Reference à Reference’ communicated in the message ‘Request For Order Status’. This will be the ‘Message Identification’ number of the original cancellation order.
Reference - Iteration 2
Mandatory
Incoming – The status of individual order references is communicated to FCIS in the second iteration. The status will be tracked for the transaction generated by the system corresponding to this reference number.
Outgoing – This is the Order Reference number corresponding to the transaction number, for which the status is getting reported.
Mandatory
Incoming: Only status tracking will happen. FCIS will not track reasons for rejections, if any.
Outgoing: Following are the cases possible for reversal a transaction:
This section contains the following topics:
The Switch Order message is sent by an instructing party to an executing party. There may be one or more intermediary parties between the instructing party and the executing party.
The Switch Order message is used when the instructing party, i.e., an investor, wants to change its investments within the same fund family according to the terms of the prospectus.
FCIS supports one to one switch transactions for incoming requests. The ‘To Fund’ information will be taken from Subscription Leg Details.
For outgoing messages, switch transactions will be communicated in separate legs for redemption and subscription. FCIS will allow the generation of this message in an automated way (based on a certain event that is triggered in the system) or manually.
If the AMC of the ‘From Fund’ and ‘To Fund’ are different; system will generate a pseudo switch transaction. In other cases system will generate a normal switch transaction.
Optional
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Creation Date Time
Optional
Applicable for incoming and outgoing message. This is the message generation date time.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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
This is information related to the switch order.
OrderReference
Mandatory
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.
InvestmentAccountDetails
Mandatory
Identification à Proprietary à Identification
Mandatory
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.
Redemption Leg Details
Mandatory
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the ‘Switch From’ fund.
Identification
Mandatory
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.
FinancialInstrumentQuantityChoice
Mandatory
This is to identify the quantity represented in amount / units to switch from a fund.
FCIS would support the following elements:
PhysicalDeliveryIndicator
Mandatory
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.
Subscription Leg Details
Mandatory
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the ‘Switch To’ fund.
Identification
Mandatory
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.
FinancialInstrumentQuantityChoice
Mandatory
This is to identify the quantity represented in amount / units to switch into a fund.
Outgoing: FCIS will pass the value ‘0’ under the relevant redemption leg tag.
CommissionDetails
Choice for Amount/Rate
Mandatory
Incoming - If the ‘Amt’ is provided and the Load concerned is amount load, then this indicates the overridden value. However, if the field is ‘Rate’ is provided and the load concerned is percent load then this indicates the overridden value.
Waiving Details
Optional
This tag represents the override percentage that the system will apply. The value provided in this field will be ignored if ‘Amount’ or ‘Rate’ tags are provided since the values provided for those tags represent the final value.
InstructionBasis
Mandatory
This tag can have the value WICA. However the system will not use this value for any processing and hence will be ignored.
WaivedRate
Optional
This field provides the discount percentage. This is applicable only for percentage based loads. The override is by discount.
PhysicalDeliveryIndicator
Mandatory
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.
ForeignExchangeDetails
Optional
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:
RelatedPartyDetails
Optional
This is information related to an intermediary.
Identification
Mandatory
FCIS supports identification based on the following tags:
If BIC is provided, the system will get either the Broker BIC or the Entity BIC based on the client country parameter ‘TXNBROKERS’. If ProprietaryIdentification is provided, the value provided in this field should be a valid Entity Id or Broker Id in the system based on the client country parameter ‘TXNBROKERS’.
ExtendedRole
Optional
In case of entity, the values provided in this field can be ‘AGENT’, AGENCY BRANCH’, ‘IFA’ ‘BROKER’ or ‘AO’. If none of these values are specified, then system will look for the specified entity. An error will be thrown if more than one entity type has the same name.
This section contains the following topics:
The Switch Order Confirmation message is sent by an executing party to an instructing party. There may be one or more intermediary parties between the executing party and the instructing party. The Switch Order Confirmation message is sent only once to confirm that all the legs of the switch have been executed.
For all incoming messages, FCIS will be able to set the status of transactions based on the individual ‘Order Reference’ number. For an outgoing message, the system will be able to generate the confirmation message only after allocation.
FCIS will allow generation of this message in an automated way (based on a certain event that is triggered in the system) or manually.
If the AMC of the ‘From Fund’ and ‘To Fund’ are different; system will generate a pseudo switch transaction. In other cases system will generate a normal switch transaction.
Optional
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Creation Date Time
Applicable for incoming and outgoing message. This is the message generation date time.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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
This is the Reference Number to a linked message that was previously received.
Reference
Mandatory
Incoming: This reference number should be the Message Identification of the original message sent. This would be the link between confirmation message and original bulk order message.
Outgoing: FCIS will send the original ‘Message Identification’ number for the external system to establish the relation between original bulk order message and confirmation message.
Mandatory
This is general information related to the execution of a switch transaction.
DealReference
Mandatory
This is a unique number assigned by the confirming party.
Incoming: This number is used for storage.
Outgoing: This would map to the Transaction Number generated by the system corresponding to the Order Reference number.
OrderReference
Mandatory
Incoming: As this would be the Transaction Number handed off in the original message, FCIS will set the Order Status to ‘Confirmed’ depending on the Order Reference number communicated.
Outgoing: This will be mapped to the incoming ‘OrderReference’ corresponding to the transaction number that was allotted successfully by FCIS.
InvestmentAccountDetails
Mandatory
Identification à Proprietary à Identification
Outgoing: The system uses the relevant UDF mapping for this tag.
ResultingCashOut
The value will be 0 since the system does not support difference in sub amount and red amount in switch.
Redemption Leg Details
Mandatory
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the ‘Switch From’ fund.
Identification
Mandatory
Outgoing - FCIS sends out the ‘Switch From’ fund ISIN.
UnitsNumber à Unit
Mandatory
Outgoing – The allocated units for the switch out leg of the transaction.
Amount
Mandatory
This is the net amount of the switch out transaction in the currency requested by the investor.
Outgoing : The system will compute the net amount in transaction currency for transaction getting confirmed.
TradeDateTime
Mandatory
This is a choice between Date and DateTime.
Outgoing: Depending on the UDF mapping, the Transaction Date / Transaction Time will be passed.
PriceDetails
Mandatory
This is the price at which order was executed.
Value à Amount
Mandatory
Outgoing – This will be the allocation price of the ‘Switch From’ fund.
CumDividendIndicator
Mandatory
This indicates whether the dividend (cum dividend) is included in the executed price. When the dividend is not included, the price will be ex-dividend.
Outgoing: This will be defaulted to ‘NO’.
PhysicalDeliveryIndicator
Mandatory
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.
Subscription Leg Details
Mandatory
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the ‘Switch To’ fund.
Identification
Mandatory
Outgoing - FCIS sends out the fund ISIN for the ‘Switch To’ fund.
UnitsNumber à Unit
Mandatory
Outgoing – The allocated units for the switch out leg of the transaction.
Amount
Mandatory
This is the net amount of the switch out transaction in the currency requested by the investor.
Outgoing: The system will compute the net amount in transaction currency for transaction getting confirmed.
TradeDateTime
Mandatory
This is a choice between Date and DateTime.
Outgoing: Depending on the UDF mapping, the Transaction Date / Transaction Time will be passed.
DealingPriceDetails
Mandatory
This is the price at which order was executed.
PriceDetails à ExtendedType
Mandatory
Outgoing – FCIS will support the code ‘OTHR’ only.
Value à Amount
Mandatory
Outgoing – This will be the allocation price of the ‘Switch From’ fund.
CumDividendIndicator
Mandatory
This indicates whether the dividend (cum dividend) is included in the executed price. When the dividend is not included, the price will be ex-dividend.
Outgoing: This will be defaulted to ‘NO’.
CommissionDetails
Choice for Amount/Rate
Mandatory
Incoming - If the ‘Amt’ is provided and the Load concerned is amount load, then this indicates the overridden value. However, if the field is ‘Rate’ is provided and the load concerned is percent load then this indicates the overridden value.
Waiving Details
Optional
This tag represents the override percentage that the system will apply. The value provided in this field will be ignored if ‘Amount’ or ‘Rate’ tags are provided since the values provided for those tags represent the final value.
InstructionBasis
Mandatory
This tag can have the value WICA. However the system will not use this value for any processing and hence will be ignored.
WaivedRate
Optional
This field provides the discount percentage. This is applicable only for percentage based loads. The override is by discount.
PhysicalDeliveryIndicator
Mandatory
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.
RelatedPartyDetails
Optional
This is information related to an intermediary.
Identification
Mandatory
FCIS supports identification based on the following tags:
If BIC is provided, the system will get either the Broker BIC or the Entity BIC based on the client country parameter ‘TXNBROKERS’. If ProprietaryIdentification is provided, the value provided in this field should be a valid Entity Id or Broker Id in the system based on the client country parameter ‘TXNBROKERS’.
ExtendedRole
Optional
In case of entity, the values provided in this field can be ‘AGENT’, AGENCY BRANCH’, ‘IFA’ ‘BROKER’or ‘AO’. If none of these values are specified, then system will look for the specified entity. An error will be thrown if more than one entity type has the same name.
This section contains the following topics:
The Switch Order Cancellation Instruction message is sent by an instructing party to an executing party. There may be one or more intermediary parties between the instructing party and the executing party.
The Switch Order Cancellation Instruction message is used to cancel the entire previously sent order message and all the individual legs that it contained. There is no amendment, but a cancellation and re-instruct policy.
For incoming Switch order cancellations, FCIS will process the reversals based on the tags Previous Reference or Cancellation ByOrder Details à Switch Order Details à Order Reference.
For outgoing cancellation messages, FCIS will communicate the details of original transaction and not the newly reversed transaction provided the original transaction was handed off to SWIFT. If a transaction has been reversed before, neither of the transactions will be included in the SWIFT message.
FCIS will allow generation of this message in an automated way (based on a certain event that is triggered in the system) or manually.
Optional
This is a Reference to a set of orders. Even though this block is optional, FCIS will need this to relate to subsequent messages.
Reference
Mandatory
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.
Creation Date Time
Optional
Applicable for incoming and utgoing message. This is the message generation date time.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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
This is the Reference Number to a linked message that was previously received.
Reference
Mandatory
Incoming - This reference number should be the Message Identification of the original message sent. This would be the link between confirmation message and original bulk order message.
FCIS will always communicate cancellations through CancellationByOrderDetails à SwitchOrderDetails à OrderReference.
This is common information related to all the orders to be cancelled.
SwitchOrderDetails
Mandatory
OrderReference
Mandatory
Incoming: The system will internally trigger a transaction reversal based on the transaction number logged earlier, corresponding to this order reference.
Outgoing: This will be the Transaction Number of original transaction, corresponding to the newly reversed transaction.
InvestmentAccountDetails
Mandatory
AccountIdentification à Proprietary à Identification
Outgoing - The system uses the relevant UDF mapping for this tag.
Redemption Leg Details
Mandatory
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the fund.
Identification
Mandatory
Outgoing: FCIS sends out the ‘Switch From’ fund ISIN.
PhysicalDeliveryIndicator
Mandatory
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.
Subscription Leg Details
Mandatory
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the ‘Switch To’ fund.
Identification
Mandatory
Outgoing: FCIS sends out the fund ISIN for the ‘Switch To’ fund.
PhysicalDeliveryIndicator
Mandatory
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.
This section contains the following topics:
The Price Report message is sent by a report provider to a report user.
This message can be used for different purposes:
If a fund is based on price components, the individual component details will be provided in PriceValuationDetails à PriceDetails (repetitive tag). FCIS will also provide the prices for each transaction type under PriceValuationDetails à PriceDetails (repetitive tag).
This report could be taken out of the system in automated way based on a particular event or manually.
User would have the option to key in the Effective Date for which the Price Report should be generated. If the price is not provided, the latest price would be picked up. FCIS will provide the latest NAV details, if auto generated, for the funds, through this report.
Optional
This is a collective reference to identify set of messages.
Reference
Mandatory
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/Repetitive
This is information related to the price valuation of a financial instrument.
Identification
Mandatory
Outgoing: Unique number generated by FCIS for every instance of Fund Price getting reported.
ValuationDateTime
Optional
This is the date and time of the price valuation for the investment fund / fund class.
Outgoing: This will be the effective date of the fund price and will be passed under the tag ValuationDateTime à Date.
TradeDateTime
Optional
This is the date and time at which price is applied, according to the terms stated in the prospects.
Outgoing: This will be the effective date of the fund price and will be passed under the tag TradeDateTime à Date.
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the fund.
Identification
Mandatory
Outgoing: FCIS sends out the fund ISIN.
TotalNAV
Optional/Repetitive
This is the value of all the holdings, minus the fund’s liabilities.
Outgoing: This will be Funds Holdings * Declared NAV for the Effective Date, (TradeDateTime).
TotalUnitsNumber
Optional
This is the total number of investment fund class units that have been issued.
Unit
Mandatory
Outgoing - This would map to the tag ‘Outstanding Units’ in fund data store for the fund.
PreviousValuationDateTime
Optional
This is the date and time of the previous valuation for the investment fund / fund class.
Outgoing - This will be the effective date of the fund price prior to the date provided under the tag TradeDateTime. This information will be provided under the tag PreviousValuationDateTime à Date.
ValuationCycle
Mandatory
This specifies how the price valuation timing is done based on the timeline defined in the prospectus.
FCIS will always communicate the value USUA (Usual) as the code to indicate that price valuation is done within the timeframe specified in the prospectus.
SuspendedIndicator
Mandatory
Indicates whether the valuation of the investment fund class is suspended.
FCIS will always the pass the value ‘NO’.
PriceDetails
Mandatory
FCIS will use this tag to provide the Fund Price components, if applicable, for the fund, and Fund Price details at a transaction type level.
Type
Mandatory
ValueInInvestmentCurrency
(Mandatory / Repetitive)
This tag will be used to pass the Declared NAV, Component Value for Component ID and Transaction Base Price for Transaction Type.
ForExecutionIndicator
Mandatory
This indicates whether the price information can be used for the execution of a transaction. This indicator would be ‘Yes’ for fund price details and ‘No’ for component details.
CumDividendIndicator
Mandatory
The value will always be ‘NO’.
This section contains the following topics:
The Price Report Cancellation message is sent by a report provider to a report user.
This message is used to cancel an entire Price Report message that was previously sent by the fund accountant. If only a part of the information has to be cancelled and replaced, the Price Report Correction message must be used.
This report has to be generated manually. FCIS communicates the original Pool Reference of the price report.
Optional
This is a collective reference to identify set of messages.
Outgoing: This will be a unique reference number generated by FCIS.
Mandatory
This is the Reference Number to a linked message that was previously received.
Reference
Mandatory
Outgoing: This will be the PoolReference of the original price report that was communicated.
This section contains the following topics:
The Fund Estimated Cash Forecast Report message is sent by a report provider to a report user.
This message is used to provide an estimate of the cash incomings and outgoings per investment fund. This message can be used to report on several investment funds. The cash incomings and outgoings result from, for example, redemption, subscription, switch transactions or dividends.
The recipient of this message is an AMC. FCIS will generate an estimated inflow and outflow report of the funds belonging to the AMC selected for the message for a particular date which is user input, if manual or the Application Date if the report is generated automatically.
The following are the contents of this report:
All unalloted transactions that are newly captured or reversed and where the maker date of the original transaction is not the same as maker date of the reversed transaction and original transaction is allocated, will be picked up.
IPO / Subscription
Redemptions
Switch In
Switch Out
IPO / Subscription – Reversal
Redemption – Reversal
Switch In – Reversal
Switch Out – Reversal
Dividend payout
Criteria for dividend record consideration:
Dividend Amount = Sum of Freeze Holdings Units * EPU
Dividend Amendments (Outflow)
Criterion for dividend record consideration:
Dividend Amount = Sum of Freeze Holdings Units * New EPU
Dividend Amendments (Inflow)
Criterion for dividend record consideration:
Dividend Amount = Sum of Freeze Holdings Units * Old EPU
Estimated Cash In = A + C + F+ H + K
Estimated Cash Out = B + D + E + G + I + J
This report will be generated for all funds in an AMC as maintained in the message maintenance. The trigger could be based on an event or manual.
Optional
This is a collective reference to identify set of messages.
Outgoing: This will be a unique reference number generated by FCIS.
Mandatory/Optional
TradeDateTime
Optional
Outgoing - This will be the date for which the report is being generated.
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the fund.
Identification
Mandatory
Outgoing: FCIS sends out the fund ISIN.
ExceptionalNetCashFlowIndicator
Mandatory
FCIS will always the pass the value ‘NO’.
EstimatedCashInForecastDetails
Original/Repetitive
SettlementDate
Mandatory
This is the date for which report is generated.
SubTotalAmount
Optional
This will be the ‘Estimated Cash In’.
EstimatedCashOutForecastDetails
Original/Repetitive
SettlementDate
Mandatory
This is the date for which report is generated.
SubTotalAmount
Optional
This will be the ‘Estimated Cash Out’.
This section contains the following topics:
The Fund Confirmed Cash Forecast Report message is sent by a report provider to a report user.
This message is used to provide a confirmed report of the cash incomings and outgoings per investment fund. This message can be used to report on several investment funds. The cash incomings and outgoings result from, for example, redemption, subscription, switch transactions or dividends.
The following are the contents of this report:
IPO / Subscription
Redemptions
Switch In
Switch Out
IPO / Subscription – Reversal
Redemption – Reversal
Switch In – Reversal
Switch Out – Reversal
Dividend payout
Criteria for dividend record consideration:
Dividend: Sum Total Amount Paid to the investor for the fund and dividend payment date.
Dividend reversal
Criteria for dividend record consideration:
Dividend = Sum original Total Amount Paid to investor
Dividend Amendments (Outflow)
Criteria for dividend record consideration:
Dividend = Sum Total Amount Paid for the amended dividend
Dividend Amendments (Inflow)
Criteria for dividend record consideration:
Dividend = Sum Original Total Amount Paid
Confirmed Cash In = A + C + F+ H + J + L
Confirmed Cash Out = B + D + E + G + I + K
Optional
This is a collective reference to identify set of messages.
Outgoing – This will be a unique reference number generated by FCIS.
Mandatory/Optional
TradeDateTime
Optional
Outgoing - This will be the date for which the report is being generated.
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the fund.
Identification
Mandatory
Outgoing - FCIS sends out the fund ISIN.
ExceptionalNetCashFlowIndicator
Mandatory
FCIS will always the pass the value ‘NO’.
CashInForecastDetails
Mandatory
SettlementDate
Mandatory
This is the date for which report is generated.
SubTotalAmount
Optional
This will be the ‘Estimated Cash In’.
CashOutForecastDetails
Original/Repetitive
SettlementDate
Mandatory
This is the date for which report is generated.
SubTotalAmount
Optional
This will be the ‘Estimated Cash Out’.
This section contains the following topics:
The Fund Confirmed Cash Forecast Report Cancellation message is sent by a report provider to a report user.
This message is used to cancel a previously sent Fund Confirmed Cash Forecast Report message. The Fund Confirmed Cash Forecast Report Cancellation message must contain the reference of the message to be cancelled. This message may also contain details of the message to be cancelled, but this is not recommended.
Optional
This is a collective reference to identify set of messages.
Outgoing: This will be a unique reference number generated by FCIS.
Mandatory
This is the Reference Number to a linked message that was previously received.
Reference
Mandatory
Outgoing: This will be selected by the user.
This section contains the following topics:
The Fund Detailed Estimated Cash Forecast Report message is sent by a report provider to a report user.
This message is used to provide an estimate of the cash incoming and outgoing flows per investment fund, sorted by country, institution or the criteria defined by the user. The message can be used to report on several investment funds. These cash incoming and outgoing flows result from, for example, redemption, subscription switch transactions or dividends.
The details provided here are similar to the Fund Estimated Cash Forecast Report with the breakup based on one of the following:
FCIS supports SortingCriteriaType à Unstructured and ForecastBreakdownDetails à ReportParameterà UserDefined indicating break up of inflows and outflows for the following:
Optional
This is a collective reference to identify set of messages.
Outgoing: This will be a unique reference number generated by FCIS.
Mandatory/Repetitive
TradeDateTime
Optional
Outgoing: This will be the date for which the report is being generated.
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the fund.
Identification
Mandatory
Outgoing: FCIS sends out the fund ISIN.
ExceptionalNetCashFlowIndicator
Mandatory
FCIS will always the pass the value ‘NO’.
SortingCriteriaDetails
Mandatory/Repetitive
SortingCriterionType à Unstructured
Outgoing - FCIS will pass “TXNDIVIDENDBASED” as unstructured code.
ForecastBreakdownDetails
Mandatory/Repetitive
ReportParameter à UserDefined à Unstructured
Outgoing - FCIS will pass “TXNDIVIDENDBASED” as unstructured code.
EstimatedCashInForecastDetails
Original/Repetitive
SettlementDate
Mandatory
This is the date for which report is generated.
SubTotalAmount
Optional
This will be the ‘Estimated Cash In’ breakup details for the various components.
EstimatedCashOutForecastDetails
Original/Repetitive
SettlementDate
Mandatory
This is the date for which report is generated.
SubTotalAmount
Optional
This will be the ‘Estimated Cash Out’ breakup for various components.
This section contains the following topics:
The Fund Detailed Confirmed Cash Forecast Report message is sent by a report provider to a report user.
This message is used to provide a confirmed report of the cash incoming and outgoing flows per investment fund, sorted by country, institution or criteria defined by the user. The message can be used to report on several investment funds. The cash incoming and outgoing flows result from, for example, redemption, subscription, switch transactions or dividends.
The details provided here are similar to Fund Confirmed Cash Forecast Report with the breakup based on one of the following:
FCIS supports the tags SortingCriteriaType à Unstructured and ForecastBreakdownDetails à ReportParameterà UserDefined, indicating the break up of inflows and outflows for the following:
Optional
This is a collective reference to identify set of messages.
Outgoing: This will be a unique reference number generated by FCIS.
Mandatory/Repetitive
TradeDateTime
Optional
Outgoing - This will be the date for which the report is being generated.
FinancialInstrumentDetails
Mandatory
This tag provides details to identify the fund.
Identification
Mandatory
Outgoing: FCIS sends out the fund ISIN.
ExceptionalNetCashFlowIndicator
Mandatory
FCIS will always the pass the value ‘NO’.
SortingCriteriaDetails
Mandatory/Repetitive
SortingCriterionType à Unstructured
Outgoing - FCIS will pass “TXNDIVIDENDBASED” as unstructured code.
ForecastBreakdownDetails
Mandatory/Repetitive
ReportParameter à UserDefined à Unstructured
Outgoing - FCIS will pass “TXNDIVIDENDBASED” as unstructured code.
CashInForecastDetails
Mandatory
SettlementDate
Mandatory
This is the date for which report is generated.
SubTotalAmount
Optional
This will be the ‘Confirmed Cash In’ breakup for components.
CashOutForecastDetails
Original/Repetitive
SettlementDate
Mandatory
This is the date for which report is generated.
SubTotalAmount
Optional
This will be the ‘Confirmed Cash Out’ breakup for components.
This section contains the following topics:
The Fund Detailed Confirmed Cash Forecast Report Cancellation message is sent by a report provider to a report user. This report will be manually generated.
This message is to cancel a previously sent Fund Detailed Confirmed Cash Forecast Report message. The Fund Detailed Confirmed Cash Forecast Report Cancellation message must contain the reference of the message to be cancelled. This message may also contain details of the message to be cancelled, but this is not recommended.
Optional
This is a collective reference to identify set of messages.
Outgoing: This will be a unique reference number generated by FCIS.
Mandatory
This is the Reference Number to a linked message that was previously received.
Reference
Mandatory
Outgoing: This will be selected by the user.
This section contains the following topics:
The Custody Statement Of Holdings message is sent by an account servicer to an account owner or its designated agent. The account servicer may be a local agent acting on behalf of its global custodian customer, a custodian acting on behalf of an investment management institution or a broker/dealer, a fund administrator or fund intermediary, trustee or registrar, etc. This message reports, at a specified moment in time, the quantity and identification of financial instruments that the account servicer maintains for the account owner.
The Custody Statement Of Holdings message is sent at the beginning of a month for reporting the month end balance of investor. User requests a holding report by portfolio as of the last date of the previous month.
MessagePagination
This tag indicates the pagination of the message.
PageNumber
Mandatory
This indicates the page number.
LastPageIndicator
Mandatory
This tag indicates the last page of the report. This will be true for the last unit holder report and false for the others.
StatementGeneralDetails
Mandatory
This tag provides general information related to the custody statement of holdings.
Reference
Mandatory
This is the Reference Number generated by the system.
StatementDateTime
Mandatory
This indicator is the effective date as of which the report is generated.
ActivityIndicator
Mandatory
This indicator would be ‘Yes’ is there is any activity reported in the statement. Else, it will be ‘No’.
AccountDetails
Mandatory
Identification à SimpleIdentification à Proprietary à Identification
Mandatory
This tag is to identify the investor’s CIF ID in FCIS.
FungibleIndicator
Mandatory
This tag would be set to ‘Yes’.
IntermediaryInformation à Identification à Proprietary
Mandatory
This tag provides the intermediary details attached with the Unitholder account.
BalanceForAccount details
This contains the CIF level account balance details as on date requested.
SubAccountDetails
Optional
Identification à SimpleIdentification à Proprietary à Identification
Mandatory
This would map to the Identification Number of the Unit holder.
FungibleIndicator
Mandatory
This tag would be set to ‘Yes’.
ActivityIndicator
Mandatory
This indicator would be set to ‘Yes’.
BalanceForSubAccount
Optional
AggregateQuantity à Quantity
Mandatory
This tag indicates the balance in the fund.
FinancialInstrumentDetails
Mandatory
This tag provides details to identify a fund.
Identification
Mandatory
The fund can be identified based on the ISIN, Alternate Identification, RIC, Ticker Symbol, Bloomberg, CTA or Common.
Outgoing : FCIS supports identification based on the ISIN or Ticker Symbol. For other options, it will use the UDF mapping relevant for this tag.
PriceDetails
Mandatory
This is the price at which order was executed.
Value à Amount
Mandatory
Outgoing – This is the fund base currency code followed by the price as of the effective date of the report.
Type
Mandatory
This has the value ‘NAVL’.
QuotationDate à Date
Optional
This indicates the maximum price date for which price is available as of the effective date of the report.
This section contains the following topics:
The Statement Of Investment Fund Transactions is sent by an account servicer to an account owner or its designated agent. The account servicer may be a fund administrator or fund intermediary, trustee or registrar. This message provides the details of increases and decreases of holdings which occurred during a specified period. This message can also be used for information purposes, eg, tax information.
This report provides the statement of transactions for a customer and a customer’s accounts for a given period.
MessagePagination
This tag indicates the pagination of the message.
PageNumber
Mandatory
This indicates the page number.
LastPageIndicator
Mandatory
This tag indicates the last page of the report. This will be true for the last unit holder report and false for the others.
StatementGeneralDetails
Mandatory
This tag provides general information related to the investment reports.
Reference
Mandatory
This is the Reference Number generated by the system.
StatementPeriod à FromDate
Mandatory
This indicator is the ‘From date’ that marks the beginning of the period for which the statement is being generated.
StatementPeriod à ToDate
Mandatory
This indicator is the ‘To date’ that marks the end of the period for which the statement is being generated.
UpdateType
Mandatory
This tag will have the value ‘COMP’ to indicate that the report is complete.
ActivityIndicator
Mandatory
This indicator would be ‘Yes’ is there is any activity reported in the statement. Else, it will be ‘No’.
InvestmentAccountDetails
Mandatory
Identification à Proprietary à Identification
Mandatory
This tag is to identify the investor’s CIF ID in FCIS.
IntermediaryInformation à Identification à Proprietary
Mandatory
This tag provides the intermediary details attached with the Unitholder account.
SubAccountDetails
Optional
Identification à SimpleIdentification à Proprietary à Identification
Mandatory
This would map to the Identification Number of the Unit holder.
FungibleIndicator
Mandatory
This tag would be set to ‘Yes’.
ActivityIndicator
Mandatory
This indicator would be set to ‘Yes’.
TransactionOnSubAccount
Optional
Identification
This tag provides details to identify a fund.
Identification
Mandatory
The fund can be identified based on the ISIN, Alternate Identification, RIC, Ticker Symbol, Bloomberg, CTA or Common.
Outgoing: FCIS sends out the fund ISIN based on the UDF set up and not ISIN always.
TransactionDetails
Mandatory
TransactionType
Mandatory
This tag indicates the type of transaction.
DealReference
Optional
This is a unique number assigned to the transaction by FCIS.
SettledTransactionIndicator
Mandatory
This indicates whether the transaction is settled. This indicator would be ‘Yes’ if the transaction is settled. Else, it would be ‘No’.
RegisteredTransactionIndicator
Mandatory
This tag would be set to ‘No’.
UnitsQuantity à Unit
Mandatory
The allocated units for the transaction.
CreditDebit
Mandatory
This tag indicates the direction of the transaction. This would be ‘CRDT’ for inflow transactions and ‘DBIT’ for outflow transactions.
Reversal
Optional
This tag indicates reversal of transactions. This would be ‘CRDT’ for inflow transactions and ‘DBIT’ for outflow transactions.
GrossSettlementAmount
Optional
This will be the gross settlement amount in the settlement currency.
TradeDateTime
Date
Mandatory
This will be the Transaction Date.
DateTime
Mandatory
This will be the save time of the Transaction.
CumDividendIndicator
Mandatory
This indicates whether the dividend (cum dividend) is included in the executed price. When the dividend is not included, the price will be ex-dividend.
This will be defaulted to ‘NO’.
PartiallyExecutedIndicator
Mandatory
This indicates whether the order has been partially executed.
This will be defaulted to ‘NO’.
PriceDetails
Mandatory
This is the price at which order was executed.
Value à Amount
Mandatory
Outgoing – This is the fund base currency code followed by the price as of the effective date of the report.
Type
Mandatory