Introduction

The record in SC.PARAMETER is the mandatory parameter record. This application contains the default values at company level that must be set up for the SC module to function properly. These default values apply irrespective of the application, transaction type or user. A record in SC.PARAMETER needs to be present for each company in the SC module. The user must be aware of the functionality of all the fields in this record to ensure its proper usage.

Some fields require the specification of a category or record from another application. For example, if the user wants to perform price integrity validation on certain asset types, the Price Asset field requires completion, specifying the valid asset type record.

The system can be parameterised to automatically create diary records such as COUPON and REDEMPTION in the DIARY.TYPE application. The user must enter the appropriate record from DIARY.TYPE in the Coupon Type field in SC.PARAMETER to enable automatic processing of bond coupons and in the Redemption Type field in SC.PARAMETER to enable the automatic maturity of bond type securities.

If this field is updated, then the diary records are automatically created by EOD.DIV.AUT.REQ and EOD.DIV.AUT.REQ. The user can set the start and end dates and the system creates diary records where the bond’s coupon or maturity date falls within the range. The date range is automatically recycled by the system once the COB is completed on the end date.

The system additionally allows to create diary records during COB for specific sub-asset type for coupon or redemption event provided the Auto Cpn Sat and Auto Redem Sat fields are set. If the number of days is specified in the Dup Check Days field, the system checks if a duplicate diary record exists based on the ex-date plus or minus the number of calendar days as defined in this field. This happens when the diary record is created for the redemption and coupon events during COB and when an incoming MT564 is received. The Create Per Depository field allows the user to specify whether a single diary record should be created for the security or separate diary records should be created based on depository for the above-mentioned events.

The SC.STD.SEC.TRADE application helps to process a basic SEC.TRADE transaction. This record does not require modification, if configured properly. The initial fields contain many CATEGORY and TRANSACTION codes relating to debit and credit transaction entries posted during the trade capture. The fields shown in the screenshot below deal with processing rules, which also help during trade entry. The user can have the SEC.TRADE transaction to default the security price from the record in SECURITY.MASTER in all cases or make it a manual process.

The Def Cust Price field must be set to Y for the trade price to be defaulted from the record in SECURITY.MASTER if input is not given by the user. This facility is feasible only when the user can be certain that the security records are up-to-date with the latest pricing information. If the user has modified the price or is not sure of the pricing or in cases where the organisation gets the pricing details from an automated third-party system, the trade price can be updated when processing bulk records in SEC.TRADE (a bulk trade is when a large number of customer transactions with the same price are to be entered). In such cases, the Def Cust Price field can be set to No.

The user must change the price in the relevant record in SECURITY.MASTER to which the price is to be defaulted. This can be reverted to the current price once the record in SEC.TRADE is updated. If the user utilises this facility to default a required non-current price, it is mandatory that no other trades be entered in the same security.

The user can set the Consolidate Fx field to Y or N to indicate whether or not to total the currency requirements of each customer into a single amount. The consolidated rate is obtained from the forex dealers and it is updated in the Consol Rate field in the SEC.TRADE application. If this field is set to Y, the user cannot enter specific rates for each customer in the Cu Ex Rate Acc field in the SEC.TRADE application. Read the Trade Creation feature in the Securities user guide for more information on the SEC.TRADE application. If the Trade Time field is set to Y, the current system time (in HH.MM.SS format) is defaulted into any time fields within the order processing programs of the ORDER.BY.CUST, SEC.OPEN.ORDER, SC.EXE.SEC.ORDERS and SEC.TRADE applications.

The Trade Creation field controls the SEC.TRADE creation from SC.EXE.SEC.ORDERS. For example, if the Trade Creation field is selected as By Portfolio, then records are created in SEC.TRADE for each port.

If the user selects the Currency Calendar check box, the system calculates the settlement date (value date) for security transactions based on both the holiday tables of the currency’s country and stock exchange country. A date, which is a working date for both the countries, is considered. If the user clears this check box, the settlement date for a transaction is calculated based on the values in the Calc Country field in STOCK.EXCHANGE. If there is no input, it is calculated based on the local holiday calendar. The following fields are used when parent child trades take place.

The SC.STD.POS.TRANSF application contains the company-level default values, which are used to process the POSITION.TRANSFER, SECURITY.TRANSFER and SC.BULK.TRANSFER transactions. It allows the user to specify the default charge category for the bulk charges and specify the status for the record in SECURITY.TRANSFER  generated from the bulk transfer. The initial fields contain many CATEGORY and TRANSACTION codes relating to debit and credit transaction entries posted during the transfer out and in as shown in the screenshot below:

For a POSITION.TRANSFER transaction, the system defaults to a delivery instruction type as mentioned in the Del Instrn field.

If the Short Transfer field is set to Yes, the system allows transfer of short position.The Ofs Source and Default Version fields are used to create and authorise the applications used in the SC.BULK.TRANSFER application. The Stamp Tax Categ field is used for defaulting category for stamp tax posting from security transfer, where the Stamp Tax Dr Tr field defines the debit transaction code for the stamp tax posted and the Stamp Tax Cr Tr defines the credit transaction code for the stamp tax posted.

The value in the Default Counterparty field should be a valid record in the CUSTOMER.SECURITY application with any one of the following customer types such as BROKER, COUNTERPARY or CLIENT. This is the default counterparty at the company level for transfers.

The SC.TAX.PARAMETER application is used to define stamp tax. Different tax rates can be applied based on the application, security, stock exchange, sub-asset type and so on.

The Tax Code field defines the tax code used to calculate the tax amount. This field accepts the tax code defined in either the TAX application or the TAX.TYPE.CONDITION application. The ID of the record in TAX.TYPE.CONDITON should be prefixed with *. If this field has a defined TAX.TYPE.CONDITION value, the system calculates the tax based on the tax codes defined for the respective customer group defined in the record in TAX.TYPE.CONDITION. If this field has a defined tax code, the system performs tax calculation based on the tax code record defined in the TAX application.

Rules of the clearing systems are set in this application. The Sec Depo Ac field must be a valid record in CUSTOMER.SECURITY.

This table contains company-level default values, which are used when processing bond lending transactions.

Before Temenos Transact begins to control the contents of the vault, it is mandatory to complete the configuration of the VAULT.PARAMETER application, which enables the system to identity the vault(s), depositories or areas within the vault. The VAULT.PARAMETER application is required for each company to use the vault application facilities provided by Temenos Transact. The vaults must also be set up on the records in CUSTOMER and CUSTOMER.SECURITY before they are defined in the VAULT.PARAMETER application. This application controls whether vault (safecustody functionality in Temenos Transact) is turned on or off, and which depositories are turned on or off. If the vault is active, then records in the VAULT.EXPECT application can be produced from the VAULT.CONTROL application.

The SC.PARAMETER application is the main parameter record for the SC application that defines the company level default values which must be setup for the SC module to run correctly. These default values apply irrespective of the application, transaction type or user. Each record is created against each company running the SC module. The following are the key features of this application:

• Each attribute of this parameter are specific to the company.
• Local stock exchange and default stock exchange can be setup at company level.
• The Alternative Index field enables the user to specify an alternative means of accessing individual security records for examination or entry into any of the various transactions and enquiries.
• Some fields require the specification of a category or a record from another application.
• If the user wishes to perform price integrity validation on certain asset types, then the Price Asset field is specified with the valid ASSET.TYPE record. If the user wants to use the Corporate Actions (CA) system to process their bond redemptions, this field contains the DIARY.TYPE ID that is used to process the redemptions.
• The Cg Base Update field in the SC.PARAMETER application allows the user to control the update of the capital gains transaction base. If this field is set to Yes, the system maintains a transaction base that can be used to display the capital gains positions on portfolio trading in a security.
• The Source Tax Split and Local Tax Split fields can be used in conjunction when processing the CA events. If these fields are set to Yes, separate source or local tax accounting entries are posted. The customer is posted with the gross amount for the cash entitlement and a separate source or local tax amount.
• The Hub Company field specifies the centralised HUB, where all SC and DX trades take place. This is particularly relevant in the customer setup, where trades are always done in a central location.
• The Actual Settlement field defines whether the trades or corporate is settled manually or automatically (contractual settlement).
• The Default Ccy Market field defines the currency market used for all FX Intraday transactions and valuations.
• The COB Ccy Market field defines the currency market used for all portfolio or position valuations done during COB.
• If the user wishes to perform manual grouping of orders, then the Group Order field should be specified as ‘Manual’.

The SC.STD.SEC.TRADE application advises the system on how to process a SEC.TRADE transaction. This includes the buy or sell and other trade related transactions, and mainly the processing rules. The following are the key features of this application:

• The initial core fields contains the CATEGORY and TRANSACTION codes which relate to debit and credit transaction entries that are posted during trade capture.
• The Synthetic Port field is used for parent child processing. This portfolio updated in the customer side of parent transaction and the Synthetic Cpty field is used for parent child processing. The counterparty specified here is updated into broker side of child portfolio.
• The Authorise Child field accepts a value Yes, to denote that child trades are to be authorised on authorisation of parent. Child trades are also automatically authorised, if the Authorise Trade field in the SC.EXE.SEC.ORDERS application of parent is set to Yes.
• The Consolidate Fx field indicates whether the user wants the system to total the currency requirements of each customer into a single amount for which a consolidated rate can be obtained from the Forex dealers and entered into the Consol Rate field of the SEC.TRADE transaction.
• The Currency Calendar field is defined so that the system calculates the settlement date (value date) for security transactions based on both the holiday tables of the currency’s country and the stock exchange country.
• The Transmit Order field is set as ‘Yes’ to transmit the grouped orders.
• The Broker Only Cty field holds the synthetic counterparty for Broker only transaction. This is used for the Broker Only Trade (Customer Vs Intermediate Broker).
• The Broker Only Port field holds the Bank’s synthetic portfolio for Broker only transaction. This is updated in the Customer portfolio for the underlying trade (Intermediate Customer Vs External Broker) in Broker only processing.
• The Broker Only Cat field holds the suspense category, which is used for Broker only processing.

The SC.STD.POS.TRANSF application contains the company level default values which are used to process the POSITION.TRANSFER and SECURITY.TRANSFER transactions. It allows the user to specify the default charge category for the bulk charges and specify the status for SECURITY.TRANSFER or FUNDS.TRANSFER record generated from the bulk transfer. The following are the key features of this application:

• For a POSITION.TRANSFER transaction, the system defaults to a delivery instruction type as contained within the SC.DEL.INSTR application. If delivery instructions are not contained within the POSITION.TRANSFER application, the Delivery Instr field must contain the exact user requirement.
• The Ofs Source and Ofs Version fields are used to create and authorise the applications used in SC.BULK.TRANSFER.
• Each business transaction within Temenos Transact is allocated a category code which enables the construction of reports that give an accurate view of the bank's operations.
• The Stamp Tax Categ field is used for defaulting category for stamp tax posting from security transfer, where the Stamp Tax Dr Tr field defines the debit transaction code for the stamp tax posted and the Stamp Tax Cr Tr defines the credit transaction code for the stamp tax posted.
• The value in the Default Counterparty field should be a valid CUSTOMER.SECURITY record with any one of the following customer types BROKER, COUNTERPARY or CLIENT. This will be default counterparty at the company level for transfers.

The SM.PARAMETER application is used to store the SECURITY.MASTER related parameters that are shared across companies. Only one record is allowed with the ID as SYSTEM. The following are the key features of this application:

• The Price Qual Format field indicates if the cum and ex markers are to be in SWIFT format or not.
• The Isin Validation field determines whether the ISIN code entered through the SECURITY.MASTER application is validated. If this field is set to Yes, the check digit must be as calculated by system.
• The Alpha Key field enables the input of alphanumeric characters in the SECURITY.MASTER ID. If this is set to Yes, the system does not perform the formatting of SECURITY.MASTER reference, based on the format specified in the Security Format field in the SC.PARAMETER application.
• The Alt Index Check field is used to default the SECURITY.MASTER ID, when the user enters an alternate identifier like ISIN in the SEC.OPEN.ORDER or SEC.TRADE records. Read the Alternate Security Index section in Instrument Master feature under Securities User Guide for more information.
• The Sec Domicile Ssi field determines whether the security domicile must be considered for SSI search, when the Pl Sett field is not given in the SECURITY.MASTER record. Read the Settlement feature under Securities user guide for more information.

The SC.LOCAL.TAX.PARAM application is the main parameter application which holds the local tax that is applicable for SC. This can be defined for specific TXN.TAX.CODE and COMPANY or SYSTEM. The following are the key features of this application:

• This application defines the tax basis for calculating the withholding tax.
• The Tax Basis field indicates the type of transaction basis for the allocation and unallocation of nominal (for example, FIFO, LIFO and so on).

The SC.ORDER.ROUTING application is the main parameter to define the routing of orders at company level. The routing conditions can be set-up based on any field in SECURITY.MASTER or SEC.ACC.MASTER applications. Record ID of this application can be SYSTEM or a Company ID.

The following are the key features of this application:

• The Default Company and Default Portfolio fields will be set as the default routing conditions if all other conditions fail to match.
• If the Exe Orig Comp field is set to Yes, then the routed order will be executed in the originating (Bank) company and the execution will be mirrored in the route-to (Broker-dealer) company.

The SC.PERSONAL.ASSET.PARAM application is the main parameter application that holds the details applicable for personal assets set up in the core banking system.

The user can define the following list of fields based on the company and are required to create the personal assets:

• Transaction Codes (Buy, Sell, Write-In, Write-out, Maturity, Liability In, and Liability Out)
• Suspense Category
• Price Source
• Industry type
• Wash Depository
• Coupon Tax Code
• Stock Exchange

The SC.PERSONAL.ASSET.TYPE application enables the user to record the attributes relevant to each Personal Asset Type. The ID of this application is a SUB.ASSET.TYPE record.

Application allows the user to enter if SC.PERSONAL.ASSET.PARAM record exists for the company.

The SC.GROUP.PARAM application is the main parameter file for both AUTOMATIC and MANUAL grouping of orders, which can be defined at company level. while grouping, If a value is defined in the Sys Fields.1 field in SC.GROUP.PARAM is entered in the parameter table, then the system checks for the same value in the field of the orders to be grouped.

The record ID of this parameter can be set as follows:

The following are the key features of this application:

• Whenever a grouping is performed, a parameter record with SECURITY.MASTER , SUB.ASSET.TYPE, ASSET.TYPE and SYSTEM is checked. The same sequence is followed, if a record with SECURITY.MASTER is found in the first instance then the grouping is based on the parameter record.
• If no match is found then the SYSTEM record is used as a parameter for grouping.

Trailer fee is a commission paid by an issuer of security to the bank for providing the bank’s customer with services, such as, holding, investment advices and other handling services of those financial instruments. The SC.TR.FEE.PARAMETER is the parameter record which must be set up at company level for the banks to process the trailer fees received from the issuer.