T3SCAT - Securities Administration & Trading - Front Office

T24 Securities Administration and
Trading
TEMENOS EDUCATION CENTRE

NOTICE
These training materials are the copyrighted work of Temenos Headquarters SA and other companies in the TEMENOS group of
companies (The Copyright Owner). The training materials contain protected logos, graphics and images. Use of the training materials
is restricted solely for use by licensed end users, partners and employees. Any un-licensed reproduction by any means, redistribution,
editing, transformation, publishing, distribution, or public demonstration of the training materials whether for commercial or personal
gain is expressly prohibited by law, and may result in severe civil and criminal penalties. Violators will be prosecuted to the maximum
extent possible. Such training materials shall not be represented, extracted into or included in part, or in whole, as part of any other
training documentation without the express permission of the Copyright Owner, which must given in writing by an authorised agent of
the Copyright Owner to be valid. Where such permission is given a clear and prominent notice must be displayed on any and all
documentation accrediting the Copyright Owner with having copyright over the materials. End-user licenses will in no event contain
permissions extending the use of these training materials to third parties for commercial training purposes.
Without limiting the foregoing, copying or reproduction of the training materials in part or in whole to any other sever or location for
further reproduction or redistribution is expressly prohibited, unless such reproduction is expressly licensed by the Copyright Owner.
Copyright © 2010 Temenos Headquarters SA
Securities Trading and Administration - Objectives
 Introducing the participants to the T24 SECURITIES ADMINISTRATION &

TRADING (SC) module
 Learning about linkages with core tables including tax, interest, charges and
commissions
 Learning to set up parameter and static tables connected with the trading activity
of the module
 Learning to input, execute and complete different types of securities order and
trade transactions/deals
 Learning about risk management, accounting and messaging, as appropriate to

this activity in the module and using reports and enquiries relevant to this
module
Slide 2
Securities Trading & Administration – Participants & Connectivity
Introducing the participants to T24 (SC) ADMINISTRATION & TRADING module
Players Customer, Own Book, Broker, Depositary set up
Core Tables Commission, Tax, Interest, Parameter & Static Tables
Securities Orders Shares & Bond Set-up on T24, Trading – Buy & Sell
Order, Execution & Trade Completion Stage,

Accounting Impact
Trade Date Accounting & Value Date Accounting
Swift Message Broker, Customer & Depositary Interaction via Swift
Limits How limits related to trading activity is set up in T24
Reports & Enquiries Extracting Reports from T24 for Reporting Purposes
Slide 3
Securities Administration & Trading - Product Overview
Order
Share Own Book

Buy
Securities
Sell
Bond Customer
Trade
Security
Position
Slide 4
Securities - Dependencies
 Securities makes use of

 Customer & Account
 Core dependencies
 Delivery Messages, Accounting & Limits
 Category codes are set up through SC.PARAMETER
 Specific transactions possible to set through SC.TRANS.TYPE

 Default range is 22000 to 22999 in T24
 Default code 22999 is set up in SC.PARAMETER in the Model Bank
 Different category codes can be indicated for reporting and information

purpose through ASSET.TYPE and SUB.ASSET.TYPE
 Asset type Ex:- Shares
 Sub Asset type Ex:- Equity and Preference Shares
Slide 5
Application Specific Parameters
Slide 6
Securities – Parameter Tables
 Parameter tables to be set-up for Securities Administration and Trading

are given below
 Top level parameter tables

 SC.PARAMETER
 ACCOUNT.PARAMETER
 SC.TRANS.NAME
 SC.TRANS.TYPE
 SC.STD.SEC.TRADE
 Portfolio related tables are to be set up during secondary build as it is

specific to Customers
 INVESTMENT.PROGRAM MANAGED.ACCOUNT
 CUSTOMER.SECURITY SEC.ACC.MASTER
 SC.ORDER.TYPE
Slide 7
SC.PARAMETER TABLE & DEPENDENCIES
Others
Valuation Currency
Related Related
SC.PARAMETER
TABLE & CORE
DEPENDENCIES
Corporate Action Settlement
Related Related
Segregated Closed
Income Account Portfolio
Slide 8
Core Dependencies - Currency Related
COUNTRY REGION
CURRENCY.PARAM
HOLIDAY
CURRENCY CURRENCY.MARKET
Holidays calendar will be checked for defaulting value date for Trade
Country or Region specific tax rates can be set up for calculation at
the time of the trade
Currency exchange rates used or trades involving two currencies and
valuation of portfolios. Default currency Market to be parameterized
Slide 9
Securities Dependencies - Charges Related
These types can be used while collecting Commission in Securities.

Also used for Brokerage payment and Stock Exchange fees.
Required to be indicated in the related Parameter tables
Slide 10
Securities Dependencies - Settlement Related
Accounts used as per Transaction

A/ C 4567 (GBP) currency.
A/C 7867 (GBP) First Account indicated is chosen
A/C 2345 (USD) For GBP Transaction, 4567.
A/C 6897 (USD) As no account is indicated for
EUR, A/C 4567 chosen, being the
SEC.ACC. very first account in SAM
MASTER
(For Trade
Customer) Buy –A/C 2345
Sell- A/C 4567 Accounts used for specified
Transactions, irrespective of
Corp. Actions
Transaction currency
Dividend – A/C 2345
Coupon – A/C 7867
If Account for Transaction
currency is not available in
CUSTOMER.
NOSTRO CUSTOMER.SECURITY,
SECURITY ACCOUNT Account in
(For Broker) NOSTRO.ACCOUNT used
Slide 11
SC.PARAMETER - Security Characteristics Related
 Security Id format
 Format of the ID used for the Security is specified SECURITY.FORMAT
Field
 Default format is ######-### which is Telekurs number format
 Alternate index
 ISIN/CEDEL.NO/EUROCLEAR.NO/SEDOL.NO/SWISS.NO/CUSIPNO can
be stored in the SECURITY.MASTER
 Done through ALT.USER.INDEX Field
 Used as an alternate to identify the security
 ISIN made mandatory to enable Swift messaging
 User defined index
Characteristics/format of Id created in ALT.SEC.PARAMETER and linked
Slide 12
SC.PARAMETER - Settlement Related
 Choice of Actual or Contractual settlement

 Set through ACTUAL.SETTLEMENT Field
 Yes/No flag, triggers the accounting on actual settlement basis
 Following fields to be used for actual settlement i.e. if above set to YES
 CUST.ACT.SUSP.CAT Field to define internal account category for
customer amount
 BROK.ACT.SUCP.CAT Field to define internal account category for broker
amount
 MISC.ACT.SUSP.CAT Field to define internal account category for other
charges/tax amount
 Posting of suspense entries till the settlement
 Internal accounts to be opened in the local currency
Slide 13
SC.PARAMETER - Settlement Related
 Maturity of settled transactions

 SETT.MAT.DAYS Field used to define the number of days for which the
settlement record remains in the Live file after settlement has taken place
 Suppression of customer entries pending settlement

 SUP.ACT.FWD.ENT Field set toYes
 Used to suppress the raising of “F” entries for the trades which are pending
settlement
 Start of day processing

 If SOD.ACCTG Field is set as ALL, processing of settlement and corporate
actions will be included in Start of day processing during COB
 If this field is left blank, then entries will be posted during Close of Business
Slide 14
SC.PARAMETER - Tax Related
 User defined Tax subroutine

 TAX.SUBROUTINE Field can define whether country specific tax needs to
be calculated or not
 Posting of stamp tax

 When Stamp tax/EBV fees are calculated, posting can be in local currency if
opted
 Opted through STAMPTAX.LOCAL.CCY Field
 Cantonal rounding
 Rounding factor for the deal amount for tax calculation purpose
For ex: If cantonal rounding is 1000, then deal amount of
CHF1045 would be rounded to CHF2000
 Rounded to higher unit
 Exemption of stock exchange fees

 If EXEMPT.EBV.FEES Field set to Yes, tax routine will not calculate stock
exchange fees
Slide 15
SC.PARAMETER - Valuation Related
 Performance History
 PERFORM.MONTHS Field to specify the number of months SAM holds
history
 Maximum up to 99 months, default value is 13
 Position holding
 Choice of separate valuations of holdings, depository wise or combined
 SEP.DEPOSITORY Field is set to YES or NO to allow whether different
depositories to be shown as such on portfolio valuations reports
 Method to use when calculating the margin value

 MARGIN.VALUE Field defines the choice
 ASSET means that assets are included
 BOTH or Null means that both assets & liabilities are included
 Trade date or value date basis for cost of position

 RECALC.COST Field can be set to calculate on Trade or Value date
 If null, then cost of position is maintained in trade date
Slide 16
SC.PARAMETER - Corporate Actions Related
 Coupon and Redemption events

 Automatic processing of interest/redemption of bonds
 Coupon event set up thorough COUPON.TYPE Field
 REDEMPTION.TYPE Field for redemption event
 Core routine for automatic processing

 Routines for processing the above events during COB set through
JOB.NAME Field
 Reports generated for the above events
 Dates for processing

 START.DATE and END.DATE Fields are the range of dates between which
the above processing takes place
 Dates recycled as part of COB
 Splitting of source and local tax

 If SOURCE.TAX.SPLIT Field set as YES, then accounting entries will be
posted separately into the customer account
Slide 17
SC.PARAMETER – Segregated Income Account
 It is possible to include Segregated Account for valuation.
 Field EXCL.INC.VALUATION needs to be set to YES, use an Account

which is linked to a different Portfolio as an Income account.
Slide 18
SC.PARAMETER - Closed Portfolio
 Closed portfolio updation rules
 CALC.CLOSED.PORT Field enables switching off calculations on closed

customer portfolios
 Portfolio would be considered closed only if the closure date is less than the
system date and safekeeping and advisory fees have been posted (i.e.)
there are no dues in respect of these
 If set to NO, then updating the performance related files and fields for the
closed portfolios will be stopped as under SC.VALUATION.EXTRACT from
the day after the closure Performance fields in SEC.ACC.MASTER from
the month after the closure
Slide 19
SC.STD.SEC.TRADE
 SC.STD.SEC.TRADE This table contains company level default values

which will be used when processing Spot Purchases and Sales
transactions.
 Defaulting transaction codes and category codes for different

charges like brokerage, Miscellaneous fees, client charges and
commissions, discounts and reallowances which are the various types
of charges collected/paid during a trading transaction of buy and sell.
 Parameter File for trade application
 Set-up of
 Categories and transaction codes charges and commissions for brokers
and customers
 Trade level processing rules
Slide 20
SC.STD.SEC.TRADE
 Price tolerance in trade

 PRICE.TOLRNC.PERC Field contains the variance percentage from last
price
 Price input in transaction compared with last price of security
 If greater or less than the percentage, system generates an override
 Calculation of charges
 Commission on amount inclusive of interest or only Principal set up through
COMM.PRIN.INT Field
 Defaulting of price in trade from SECURITY MASTER

 DEF.CUST.PRICE Field can be used
 Defaulting of trade time

 TRADE.TIME.FLAG Field if set to Yes, will default input time to
SEC.TRADE record
Slide 21
SC.STD.SEC.TRADE
 Transactions exempted from charges/commission

 NO.COM.TRN.CDS Field contains list of Transaction codes where no
commission is to be charged
 Order transmission
 TRANSMIT.ORDER Field used to create SC.EXE.SEC.ORDERS record on
authorising SEC.OPEN.ORDER or on transmitting
 Selling of blocked position

 OVERSELL.BLOCK Field control the trading of a security when a block is
defined
 “YES” creates an Override
 “NO” gives an Error message for selling blocked position
Slide 22
SC.STD.SEC.TRADE
 Partially filled orders
 CANCEL.REMAIN.ORD Field controls whether “remaining order sent to

history” displayed on executed trades or not
 Settlement Based on Currency Calendar
 CURRENCY.CALENDAR field need to be set to YES to enable system to

calculates the Settlement date based on both the Holiday tables of the
Currency’s country and the Stock Exchange Country.
Slide 23
ACCOUNT.PARAMETER
Checking of balance in account
CREDIT.CHECK Field validates for availability of funds from either of
 Working Balance
 Available Balance
 Working Balance plus today’s forward balance
 Available Balance and Working Balance
Slide 24
ACCOUNT.PARAMETER
 Choice of Trade date or value date accounting

 VAL.DATE.SYS.ID Field is used to determine whether SC should have
accounting treated as trade or value dated
 Value date accounting cannot be reset to trade dated accounting
 Updation of available balance in customer account

 AVAILABLE.BAL.UPD Field identifies whether unauthorized debits or
Unauthorized credits, or both or none of them
Slide 25
OTHER PARAMETER TABLES
 SC.TRANS.NAME
 Allows to set up codes for all transactions.
 ID for each of these transactions is a 1-3 alpha/numeric code
Ex: “BUY" for all security purchases & “DIN" for Dividend Received payments
 TRANSACTION
 Table that defines the accounting transaction codes.
 Whether they debit or credit an account, narrative to be used for account
statements etc
 SC.TRANS.TYPE
 Describes valid combinations of SC.TRANS.NAME with accounting
TRANSACTION
 SC.DEL.INSTR
 SC.DEL.INSTR table is used to indicate type of settlement to be carried
out on any individual transaction.. It indicates whether securities are to be
received or delivered and if that delivery is free or against payment.
Slide 26
SC.DEL.INSTR
SC.DEL.INSTR table defines characteristics of settlement instructions
 Identifies whether securities are to be received/delivered which is applied

when formatting delivery instructions
 TO.BE.RECD.OR.DEL Field specifies whether the transaction is of a type

where Stock is to be either Received or delivered in the normal course of
settlement
 WITH.PAYMENT.FLAG Field specifies whether delivery is to be against

payment or without payment
 If free of payment (FOP) the security and cash movement are not linked
MT103 message sent to Nostro to make payment to broker
 MT540 sent to depository expect to receive security free of payment
 COUNTERPARTY.LIMIT Field indicates whether counterparty to be

applied for deliveries
Slide 27
SECURITY MASTER
Slide 28
SECURITY.MASTER - OVERVIEW
 SECURITY.MASTER
 Defines Security on T24
 ID can be of numeric characters only
 Common file for all types of Securities
 Specific fields are only valid for particular types of security (bonds, shares)
 Many elements available to support world-wide securities requirements
 T24 transactions obtains information related to the security traded
 SECURITY.SUPP
 Optional record
 Additional information like YTM, Duration
 System creates and updates details during COB
 Can be amended by user
Slide 29
SECURITY.MASTER - Security Characteristics
 Security Id format
 Format of the ID used for the Security is specified in SECURITY.FORMAT
Field
 Default format is ######-### which is Telekurs number format
 Alternate index
 ISIN/CEDEL.NO/EUROCLEAR.NO/SEDOL.NO/SWISS.NO/CUSIPNO can
be stored in the SECURITY.MASTER
 Done through ALT.USER.INDEX Field
 Used as an alternate to identify the security
 ISIN made mandatory to enable Swift messaging
 User defined index
Characteristics/format of Id created in ALT.SEC.PARAMETER and linked
Slide 30
SECURITY.MASTER - LINKS
PRICE. TYPE
STOCK.EXCHANGE
PRICE. UPDATE ASSET.TYPE
CUSTOMER.
SECURITY.MASTER
SECURITY SUB.ASSET.TYPE
COUPON.TAX.
CODE EB.RATING SC.INDUSTRY
Slide 31
STOCK.EXCHANGE
 Id comprises of alphanumeric characters
 Settlement days
 SETTLEMENT.DAYS Field indicates the number of days forward the value
date to be
 Number of days to default the value date for a trade
 Settlement basis
 SETT.DAYS.BASIS Field Indicates whether the value date is to be
calculated on a business or calendar day basis
 Fixed day settlement set up separately
 Domicile of the exchange

 DOMICILE Field used for validating the holiday table to arrive at value date
 Used for calculation of stamp tax, if setup
Slide 32
STOCK.EXCHANGE
 Simple stock exchange fees setup
 For bond and share separately for broker and customer dealing at this
Stock Exchange
 BR.BOND.COMM Field defines the charges for a broker dealing in bonds
 BR.SHR.COMM Field defines the charges for a broker dealing in shares
 CU.BOND.COMM Field defines the charges for a customer dealing in
bonds
 CU.SHR.COMM Field defines the charges for a customer dealing in shares
 Generally set for the broker
 Linked to a valid record in FT.COMMISSION.TYPE
 Effective date for levy of commission for shares/bonds
 Can be setup for ALL or by a particular country

 Input by sub valuing the fields within the date
Slide 33
STOCK.EXCHANGE - Settlement Periods
Settlement date of a security transaction is based on the Stock exchange

where the transaction takes place.
 The settlement dates can be different for different currencies and different types
of transactions for the same Stock Exchange.
STOCK EXCHANGE-
 TRANSACTION.TYPE - BUY/SELL
 TRADE.CURRENCY
The above Fields are used to specify the settlement days in the exchange by
transaction type and by currency which will calculate the Settlement Date.
Slide 34
Settlement periods
 Settlement Period for the Trades in New York Stock Exchange
Example:
 SETTLEMENT.DAYS.1 - 2
 TRANSACTION.TYPE1.1 -
 TRADE CURRENCY 2.1 –
 SETTLEMENT.DAYS.2 – 3
 TRANSACTION.TYPE 1.2 – DEBIT
 TRADE CURRENCY 2.2 –
Settlement days will be ‘2’ for all purchase

transactions whereas it will be ‘3’ days for
all sale transactions in the exchange.
Slide 35
Workshop - 1
 Use Admin Menu > Private Administration > Securities > Static Data
and Parameters > Stock Exchanges > Stock Exchange Input
 Create a STOCK.EXCHANGE record with the following details

 Id from 300 onwards OR 3 any letter stock exchange id
 Settlement days as 1 business day
 Broker charges for all bonds with SCSKBOND and for all shares SCSKEQ
with effect from today
 Commit the record
 Get the record authorized
Slide 36
Workshop - 1 Solution
Slide 37
PRICE.TYPE
 Relates the nominal to market price quotes
 Description of the Price type

 Defined through DESCRIPTION Field
 Whether the price is a percentage price or unit price

 PERCENTAGE Field specifies whether the price quoted on a security is
expressed as a percentage or a multiple of the nominal value
 No for CALC.METHOD Field as PRICE
 Multiplying factor with the price

 MULTIPLY.FACTOR Field specifies the weighting attached to the price
quoted on a security
Slide 38
PRICE.TYPE
 PRICE.TYPE Field is a unique reference which identifies the method

of price calculation
 PRICE
 Percentage can be Y or N. Cannot be a discount instrument
 For following calculation method, discount and percentage must be Yes

 DISCOUNT
Rate of discount used instead of price of security
 DPRICE
Combination with price. Discount/premium calculated on the face value
 YIELD
Yield rate instead of price
Slide 39
PRICE.TYPE
 Discount Calculation
 For Example, security with a face (maturity) value of USD100,000 bought
with 100 days remaining until maturity - dealt at a discount rate of 5% using
a 365-day calculation basis
 Amount = Nominal *(1- Days remaining * Rate/year days)
 Consideration amount under discount calculation is USD 98630.14
 Yield Calculation
 Security with a face (maturity) value of USD 100,000 bought at a yield of
5% with 100 days remaining until final maturity using a 365 days calculation
basis
 Consideration amount = Nominal / 1+((Days remaining * Rate)/year days)
 Consideration amount under yield calculation is USD 98648.65
Slide 40
PRICE.TYPE
 Discounted Instruments
 If DISC.INSTRUMENT Field is specified as YES, then daily
amortisation/accrual of discount for Own Book will take place is similar set
up exists in Portfolio
 Cannot be used for PRICE
 Percentage has to be Y
 Price Basis to be used

 PRICE.BASIS Field indicates whether the price quoted for a Bond, includes
or excludes interest accrued
 I = INC.ACCR, E = EXC.ACCR
 Default is EXC.ACCR
Slide 41
Quiz 2
 A PRICE.TYPE record is shown
 The security definition is

 Price of 98, Interest rate of 10%
 Accrual starts from July 1, 2015
 Maturity date June 30, 2016
 Value date Aug 27, 2015
 What will be the gross amount calculated for a nominal of 10000?

Ans : 10000*98% = 9800
Slide 42
Quiz 3
 A PRICE.TYPE record is as below
 The security definition is

 Price of 98.
 Value date Aug 27, 2010
 What will be the gross amount calculated for a nominal of 10000?

Ans : Since percentage is NO, we have
10000*98 = 980000
Slide 43
PRICE.UPDATE
 Used to maintain static information to indicate to the system how and

from Security last price is to be updated
 Prices can be updated manually or automatically

 AUTO.UPDATE.REQD Field specifies whether Price updates will be
automatic or manual
 If set as Yes, then manual input not allowed
 External services like Telekurs, Reuters, Bloomberg… can be used on-

line
MANUAL
TELEKURS,REUTERS
FIXED PRICE
NO UPDATE
UPDATED WEEKLY
 Past prices updates

 PAST.UPDATE.PRICE Field controls input of historic prices
 Options are YES, NO or OVERRIDE, the default value is YES
Slide 44
ASSET.TYPE / SUB.ASSET.TYPE
 ASSET.TYPE
 GROUPS the securities product
Ex:- Shares
 SUB.ASSET.TYPE
 SUB.ASSET.TYPE record linked to ASSET.TYPE record
Ex:- Equity shares
 Used in Securities
 Control the definition of groups for accounting key formations
 Control charging and fee structure
 Set-up margin rates
Slide 45
Workshop - 2
Use Admin menu > Private Administration > Securities > Parameter files
> Other Parameters > Asset Type
 View existing record namely 30 for shares
Use Admin menu > Private Administration > Securities > Parameter files
> Other Parameters > Sub Asset Type
 Create a sub asset type record using Ids from 321 onwards
 Link it to asset type record 30
Slide 46
Slide 47
Other Tables - SC.INDUSTRY & EB.RATING
 SC.INDUSTRY
 Defines industry codes assigned to each Security Master
 Enables reports to be produced for local authorities
 Enables defining of asset allocation in portfolio modelling
 EB.RATING
 Determines the quality of the Company or of the issuer
 Maintains ratings of the security and linked to SECURITY.MASTER
 EB.RATING.AGENCY
 Holds information of the agency like Standard and Poors, Moody's
 SC.ISSUER
 Issuers are created using SC.ISSUER application for the Issuers who are
not opened as "Customers" in T24. An Issuer is then linked to instruments
using the OV.ISSUER field in SECURITY.MASTER
Slide 48
SECURITY.MASTER - Mandatory Input
 Top most classification of security

 BOND.OR.SHARE Field indicates the type of security - Bond or Share
 Asset type classification

 SUB.ASSET.TYPE Field defines the group Securities, which are reported
together
 Currency in which the security is issued and usually quoted

 SECURITY.CURRENCY Field is the currency in which the security was
issued
Slide 49
SECURITY.MASTER - Mandatory Input
 Country domicile of the security issued

 SECURITY.DOMICILE Field specifies the country domicile of the Security
being issued
 Default depository where the security is normally held

 DEFAULT.DEPOSITORY Field is used to define the depository in which this
particular stock is to be kept
 Default Stock Exchange for the security

 STOCK.EXCHANGE Field used to define Stock Exchange at which the
Security is normally traded
 Must exist in the STOCK.EXCHANGE table
 Link to tax for coupon/dividend

 COUPON.TAX.CODE Field indicates the tax calculation
Slide 50
SECURITY.MASTER
 Bond rating
 RATING Field defines the credit rating of the Security.
 Must exist on the EB.RATING table
 Industry to which security belongs

 INDUSTRY.CODE Field specifies the industry of the Security
 Must exist on the SC.INDUSTRY table
 Alternate index like ISIN, CEDEL.NO.. can be defined
 ISIN identifier
 Validation is setup in SC.PARAMETER
12 digit with first 2 alphabets and a final check digit
 Used in the swift messages generated for the order/trade
Slide 51
SECURITY.MASTER
 Minimum holding of the Security

 MINIMUM.HOLDING Field specifies the Minimum holding for the security
 Possible to include the transaction codes in SC.PARAMETER for which the
validation is done
 Override message is produced when total holding falls below the minimum
holding
 Trading units
 TRADING.UNITS Field specifies the smallest nominal traded
 "1" to indicate that only whole numbers are allowable
 "0" to indicate any amount of decimals up to and including 6
 A setting of "0.001" means that the underlying security may be traded, for
example, 123.1 or 123.12 or 123.123 but not 123.1234
 Par or face value of a security

 PAR.VALUE Field defines par value of the stock in the
"SECURITY.CURRENCY"
 Mandatory for a share/optional for a bond
Slide 52
SECURITY.MASTER - Other Features
SC.PRICE.CHANGE
 Stores information of all the Securities for which the Price/Yield is

updated Manually
 Historic price changes can also be done, which is used for back dated
recalculation if so opted for
 Information in TIME.CHANGE, NEW.PRICE, OLD.PRICE Fields are

updated during authorization of a modification to a SECURITY.MASTER
record
 SECURITY.NO Field is the Security for which the Price is changed
Slide 53
SECURITY.MASTER - Other Features
 Blocking of Security
 BLOCKING.DATE Field defines the date from which all activity in this
security is to be prohibited
 BLOCKING.NARR Field used to define a narrative to be displayed in the
override when a blocked security is used
 Country and Currency risk associated to the security

 RISK.CCY Field is the currency where the risk is deemed to reside for this
security which can be used for generation of currency risk information
If no value is entered, then it is defaulted with the value in
SECURITY.CURRENCY Field
 RISK.COUNTRY Field is the Country where the risk is deemed to reside
for this security which can be used for generation of country risk information
If no value is entered, then it is defaulted with the value in
SECURITY.DOMICILE Field
Slide 54
SECURITY MASTER
SHARES SET-UP
Slide 55
Workshop - 3
 Use User Menu > Private Operations > Securities > Back Office >
Security Master > Maintenance
 Input a SECURITY.MASTER for a share using the following values-
 Security currency as USD
 Trading units as 100
 Price type as UNIT
 Price update code as Manual
 Sub asset created in the previous workshop
 Last price USD 99
 Stock Exchange created in Workshop 1
 Par Value as 1
 Coupon Tax code as US
 Default depository - choose an existing depository
 Commit and get the record authorised
Slide 56
1 1
2
Slide 57
SECURITY.MASTER - Bond
 In addition to the details for a share, the bond characteristics

 Coupon details like rate, date, Maturity dates
 Interest rate and effective rate

 INTEREST.RATE Field specifies the fixed interest rate payable on a
particular bond type of security
 RATE.CH.DATE Field is the date the interest rate is changed or is due to
change
 No of coupon payments in a year

 NO.OF.PAYMENTS Field specifies the number of coupon payments in a
year
 1 for annual, 4 for quarterly, 12 for monthly, 52 for weekly...
 Day basis
 INTEREST.DAY.BASIS Field defines calculation method for accrued
interest
Slide 58
SECURITY.MASTER – Interest Day Basis
 Different Interest day basis for calculation of interest possible

depending on methods followed for calculating number of days in an
interest period and days in a year
 A3 360 / 360
Key Days/Denominator
period varies according to
A 360/360
start and value dates A3 360/360 US
B 366/360
 O = French OAT C 366/366
Calculation is ACT / ACT C1 366/366
Rounded to 3 decimal places C2 366/366
D 360/366
 U = USTRSRY used in US Treasury Bills E 366/365
Denominator = Numerator * No of days in F 360/365
interest period G 366/364
O OAT
 3 different methods in C explained next U USTRSRY
Slide 59
SECURITY.MASTER - Bond
 Date of issue of bond

 ISSUE.DATE Field defines the issue date of the Security
 Used for information purposes only
 Maturity date of bond

 MATURITY.DATE Field specifies the maturity date of the Security
 Date of next interest due date

 INT.PAYMENT.DATE Field specifies the date on which the 1st interest
payment or coupon falls due
 Based on number of payments, the dates get cycled after the first payment
 Accrual start date

 ACCRUAL.START.DATE Field holds the date from which accrued
interest, coupons and dividends are payable
 Used in accrual calculation as the “From” date
Slide 60
SECURITY.MASTER – Bonds – Other features
 T24 can process floating rate bonds where the coupon rate is typically
linked to a benchmark rate such as the LIBOR
 Specific rounding rules can be set-up for Bond interest
Slide 61
Security Master – Capturing Fund Attributes
 Fund attributes are captured in the Security Master based on the below
classification. However, the additional information on the performances,
expenses and holdings can be fetched from the SECURITY.SUPP file
Classification :
 Sub Asset Classification

 Open/Close ended fund
 Hedge/Non Hedge
 Currency Classes
 Registration status
 Indicator if fund is using Derivatives
 Indicator if fund is ETF
Slide 62
SECURITY.SUPP
 This Table holds additional information for each SECURITY.MASTER

record
 Information held are

 Current Yield
 Yield to maturity
 Duration
 History of Dividends or Coupons Paid
 Automatically created and updated by the system
Slide 63
Workshop - 4
Security Master > Bond Maintenance
 Input a SECURITY.MASTER for a bond with the following conditions:
 Domicile as US and Currency as USD
 Sub asset type as an existing 101 , Industry 10
 Price Type Bond, last Price USD 105
 Include the existing Stock Exchange NYSE
 Coupon Tax Code US
 Rate of interest of 5% with quarterly interest payments and maturing in 5
years time from today
 Interest basis as U
 Choose one default depository
 Commit accepting overrides and get it authorised
Slide 64
Slide 65
Quiz - 5
1) Name the different methods for identifying the Security Master record ?
Ans: Id of SECURITY.MASTER or MNEMONIC of the security or
ALTERNATE.INDEX or ALT.USER.INDEX
2) Is par value of a security a mandatory input, at the time of creation of

SECURITY.MASTER record?
Ans: It is mandatory for share only and not for bonds
3) How can floating interest rate for a bond be specified in

SECURITY.MASTER ?
Ans: Either input of rates with effective date or automatically when linked to
PERIODIC.INTEREST
4) Interest bearing debt instruments carry only fixed rate of interest ?
Ans: FALSE (Also carry Floating Rate of Interest)
Slide 66
SECURITY.MASTER - RECAP
External feed
Price input Security
Manual
Price Types Shares - Bond-

Normal/ T-bonds,
preference Govt bonds
…. …..
Unit /
Normal
Percentage
Fixed
rate
Discount Multiply Maturity
Factor Floating date
rate
Yield Interest
Factored payment
rate dates
Slide 67
Quiz - Parameter and Security Master
1) Price.Update field allows to enter price for security manually ?

Ans: True
2) Value Date Accounting once turned ON can be turned off if required ?

Ans: No
3) Which Category code types are used for reporting and information purpose?
Ans: Asset.Type & Sub.Asset.Type
4) All Charges, Commissions, Stock Exchange Fees set up through _________?

Ans: FT.Commission.Type
5) Securities are created and defined in _______________ table ?

Ans: Security.Master
6) Specific transaction can be set up in ________________ table ?

Ans: SC.TRANS.TYPE
7) Which FIELD in the Security.Master file defines a security as Share or Bond ?

Ans: Bond or Share field
Slide 68
Creating Portfolios
Slide 69
Role of Customer in Securities Transaction
Own Book
Customer
Portfolio Customer
CUSTOMER.SECURITY
Broker Counterparty Depository
Slide 70
CUSTOMER.SECURITY
 Enables SC Module to use CUSTOMER table

 Mandatory input
 Id is same as Customer Id
 Roles of customer defined

 CUSTOMER.TYPE Field used to define the different roles
 Identifies trading relationship within securities module
 System validates compatibility of role in transactions
 Can be multi valued to allow a customer to act in more than one capacity
Ex:- Broker & Depository, Customer, Client, Counterparty
Slide 71
CUSTOMER.SECURITY
 A “CUSTOMER” type can be setup with the following details
 Valuation statement frequency

 STATEMENT.FREQUENCY Field used for definition of valuation reports to
the customer
 Default depository for Customer

 DEFAULT.DEPOSITORY Field used to default when an order is placed on
behalf of the Customer for receipt or delivery of the security
 Agreement between Bank & Customer

 For settling transactions contractually indicated in AUTO.CUST.SETT Field
Slide 72
Workshop - 5
 Use Role Based Home Pages > Private Operations > PWM Front
Office > PWM Front Office Operations >Customer Maintenance> Client
Maintenance
 Choose Customer static tabs
 Input a new CUSTOMER record
 Use SECTOR code as 1001 and RESIDENCE as US
 Use TARGET as 2 and CUSTOMER.STATUS as 2
 Commit the record and get the record authorised
Office > PWM Front Office Operations >Customer Maintenance> Client
Maintenance
 Choose Securities Data tabs
 For the above customer open a CUSTOMER.SECURITY record as
“CUSTOMER” type and commit the record
Slide 73
Slide 74
Slide 75
CUSTOMER.SECURITY
 “BROKER” type can be setup with the following details
 Brokerage for shares and bonds

 SHARE.BR.COMM.TYPE Field for shares
 BOND.BR.COMM.TYPE Field for bonds
 Linked to a valid record in FT.COMMISSION.TYPE
 Separate commission records can be linked for the purpose of brokerage
 Default delivery instructions

 BR.DEL.INSTR Field is used to specify the default delivery instruction for
broker
 Valid record defined in SC.DEL.INSTR
 Broker Settlement details are defaulted automatically in a Trade
Transaction, once set at the Broker Level
Slide 76
CUSTOMER.SECURITY
 Default depository for broker

 BR.DEF.DEPO Field used for default depository
 Can be setup by SECURITY/ASSET.TYPE/SUB.ASSET.TYPE or ALL
through BR.SEC.TYPE Field
 Default settlement instructions

 Can be set up for each broker through BR.SET.ACC Field
 Agreement between Bank and Broker for settling contractually

 For settling transactions contractually indicated in AUTO.BROK.SETT Field
Slide 77
CUSTOMER.SECURITY
 Separate accounting for the broker’s unsettled trades in suspense

account separate from the parameter
 Appropriate internal account category should be mentioned
 BROK.SUSP.DR Field will determine the internal account category to
which the Broker side Suspense Debit entries will be posted
 BROK.SUSP.CR Field will determine the internal account to which the
Broker side Suspense Credit entries will be posted.
 Will be allowed to input only if ACTUAL.SETTLEMENT Field is set to "YES"
in SC.PARAMETER
 Authorised broker
 Can be specified whether the broker is authorised through
AUTHORISED.BROKER Field
 T24 raises an override when transacted through an unauthorised broker
 Report is generated during COB
Slide 78
Workshop - 6
 Use Admin Menu > Private Administration > Securities > Static Data
and Parameters > Counterparty Maintenance > Broker Maintenance >
Broker Input
 Choose Broker Static tabs
 Create a CUSTOMER record for a broker using values from drop down list
 Commit and get the record authorised
 Use Admin menu > Private Administration > Securities > Static Data
and Parameters > Counterparty Maintenance > Broker Maintenance >
Broker Input
 Choose Broker Securities Data tabs
 For the above customer open a CUSTOMER.SECURITY record with
“BROKER” type
 Use existing FT.COMMISSION.TYPE namely SCBROKCOM to define the
brokerage due to the broker for both shares and bonds
Slide 79
Slide 80
CUSTOMER.SECURITY
 “DEPOSITORY” type can be setup with the following details
 Reconciliation frequency for holdings statement

 RECON.FREQ Field to indicate frequency
 To produce required statement for all sub-accounts and securities
 Depository will return a statement of holdings which will be reconciled
 If this is not required then this field should be left blank and application
SR.STATEMENT.REQUEST can be used for ad-hoc
 Details of sub account

 SUB.ACCOUNT Field specifies sub accounts for this depository
 Associated with the SUB.ACC.EXT.ID Field
 Reconciliation frequency for sub accounts, if different

 SUB.ACCT.STMT Field used in conjunction with statement frequency field
for generation of statement of holdings by sub account
Slide 81
CUSTOMER.SECURITY
 Type of position used namely trade or value for reconciliation

 DATE.TYPE Field may either be TRADE or VALUE
 Defines Swift Delivery instruction formats

 Defined thorough DEPO.INSTR.TYPE Field
 Valid inputs are MT540-543
 Indicates whether holdings included for corporate actions

 CORPORATE.ACTIONS Field is used to indicate whether holdings held
with the depository is eligible for Corporate Actions
Slide 82
CUSTOMER.SECURITY
 For unsettled cash portion of a transaction, possible to specify the

tolerance currency & amount
 SETT.TOL.CCY Field to define tolerance currency
 SETT.TOL.AMT Field to define tolerance amount
 Posting of such balances are made to the category specified in
SC.PARAMETER table
 Mandatory to include the default code in CUSTOMER.CHARGE table

for the customer, before opening a record as depository in
CUSTOMER.SECURITY
Slide 83
Workshop - 7
and Parameters > Counterparty Maintenance > Depository
Maintenance
 Choose Depository Static tabs
 Input CUSTOMER record for depository, commit & get it authorized
Maintenance
 Choose Depository Charge Group tabs
 Input 999 in depository group, commit & get it authorised
Maintenance
 Choose Depository Securities Data tabs
 Input CUSTOMER.SECURITY with customer type as “DEPOSITORY”
Slide 84
Slide 85
Slide 86
Slide 87
Workshop - 8
Office > PWM Front Office Operations >Customer Maintenance >
Additional Settings > Update Address
 Update SWIFT address of Customer created earlier
 Update SWIFT address of Broker created earlier
 Update SWIFT address of Depository created earlier
Slide 88
Slide 89
Slide 90
Slide 91
SEC.ACC.MASTER - Portfolio Types
Portfolio
Customer Own book
Account defaulting Accounting rules
Fees Interest accruals
Modeling Discount accruals
Revaluation
Slide 92
SEC.ACC.MASTER
 Can be defined only for customers setup as CUSTOMER in the

CUSTOMER.SECURITY
 Id format is <customer. Id>-<NNN>

 Where NNN stands for numbers from 1 to 998 excluding 777
 A customer can have multiple portfolios
 Joint ownership of portfolio

 JOINT.HOLDER Field used to link joint owner defined in CUSTOMER
 RELATION.CODE Field defines the relation of the Joint Holder with
Portfolio
 Relationship validated with the RELATION table
 Maintained for information and no processing done
Slide 93
SEC.ACC.MASTER
 Investment policy followed for the portfolio

 INVESTMENT.PROGRAM Field identifies the investment policy followed
 Linked to the INVESTMENT.PROGRAM Table
Ex:- Balanced Model, Income Model
 Used for definition of standing instructions for corporate actions
 Can be linked to reports and valuations for analysis and comparison
 This field plays vital role in Asset Management
 How managed and maintained

 MANAGED.ACCOUNT Field defines the management regime to be applied
to this portfolio
 Linked to MANAGED.ACCOUNT Table
Ex:- Managed - Bank have Client's mandate to conduct business .
Non Managed, Advisory
 Used in fee calculation
Slide 94
SEC.ACC.MASTER
 Officer responsible for the portfolio

 Area of responsibility, defined through ACCOUNT.OFFICER Field
 If the value is null system will default from the CUSTOMER record
 Linked to the DEPT.ACCT.OFFICER Table
 Used for posting of fees manually
 Reference and Valuation currency

 REFERENCE.CURRENCY Field specifies the currency in which the
Portfolio is maintained. One reference currency for valuation purposes
 VALUATION.CURRENCY Field identifies the currency in which the
valuation reports are printed. If the value in this field is null then the
reference currency will be used to produce the reports.
 Portfolio Name
 ACCOUNT.NAME Field contains the Security Account title
Ex:- Mr. John Smith's Portfolio Account
Slide 95
SEC.ACC.MASTER - Account Numbers
 Memo Portfolios
 MEMO.ACCOUNT Field Can be flagged as Y for a MEMO account.
 No accounting for customer transactions
 Handled by the customer
 Account numbers
 ACCOUNT.NOS Field identifies account over which the account entries for
this portfolios transactions are to be passed
 At least one account number to be specified for a non MEMO account
 Same account cannot be used for different portfolios
Slide 96
SEC.ACC.MASTER – Segregated Account
 Capital and Income of a Portfolio can be segregated and booked in separate

Accounts specified in the Portfolio.
 Portfolios can keep the income and capital segregated. It is possible to attach an
Income account to a portfolio which does not belong to the Portfolio.
 It is also possible to attach a Capital account of a Portfolio as the Income

account of another portfolio.
 The interest accrued through a purchase or sale on bond positions and changes
are designated to a separate income account.
 For those portfolios that have elected to segregate income, the accrued interest
and charges are posted to a separate income account and only the gross
consideration is posted to the capital account.
Slide 97
SEC.ACC.MASTER - Default Depository
 Defaulting of depository
 DEFAULT.DEPO Field is populated with a depository to be defaulted
 Valid customer defined as depository in CUSTOMER.SECURITY
 Defaulting of the depository takes place on trade or order for the portfolio
 Defaulting criteria can also be defined through

 APP.FIELD - value restricted to fields available in SECURITY.MASTER
 APP.OPERAND
 APP.VALUE
 Multiple conditions can be defined which are connected by “AND”
Slide 98
SEC.ACC.MASTER - Safekeeping and Advisory Fees
 Safekeeping and advisory account

 SAFEKEEP.CHRG.ACC Field holds the account for collecting safe
custody/advisory fees
 Frequency for fees

 SAFECUSTODY.FREQ Field holds the date of the next calculation of Safe
custody Fees and frequency for subsequent calculation
 ADVISORY.FREQ Field holds the next calculation of Advisory Fees and
frequency for subsequent calculation
 Defaults from the parameter SAFECUSTODY.VALUES
 Either company wide or portfolio specific
 Charge condition for fees

 SAFE.CHG.SCALE Field records the Safe custody Fees scale that the
portfolio is linked
 Similarly ADV.CHG.SCALE Field records the Advisory Fees scale
Slide 99
SEC.ACC.MASTER - Safekeeping and Advisory Fees
 Calculation of fees
 PORTFOLIO.FEES Field indicates how portfolio fees are calculated
 Automatic /manual/not at all
 Based on Interco Parameter P&L and Tax will be booked in the portfolio's
own company.
 Last date for calculation
 For both fees the last run date is maintained by system if the choice is
automatic in ADV.LAST.RUN and SAFE.LAST.RUN Fields
 Grouping of portfolio for fees

 Asset Management module allows grouping of portfolios for the purpose of
fees
 Closing of portfolios
 CLOSURE.DATE Field is used to close a portfolio and cannot be changed
after authorization
 Used for fees calculation in case a closure date is given for a SAM record
Slide 100
SEC.ACC.MASTER - VALUATION
 Valuation of the portfolio and margin valuation of a portfolio

 VALUATION.AMT Field contains the current portfolio valuation in the
reference currency
 MARGIN.VALUE Field contains the calculated margin value of the
securities held
 Applicable when the customer is allowed a margin facility
 Valuation date
 DATE.OF.VALUATION Field specifies the last date when a valuation report
is run online or COB
 Generation of MT536 messages

 Frequency of the messages
 MT536.RECIPIENT Field will hold the valid DE.SWIFT.ADDRESS in Swift
Format of all other recipients who would receive the message
Slide 101
SEC.ACC.MASTER Margin Details
 Margin value (or Security Value) denotes the maximum amount that
can be borrowed against the Portfolio.
 Sec Margin Ratio can be calculated and used as a performance

monitoring tool for portfolios pledged as collateral for credit facility
provided to customers by the bank.
 The valuation details for the Individual/Master Portfolios (Market value,

Second Market value, Liabilities, margin value) will be updated in
Portfolio in separate fields.
 Global Limits can be linked at OV.PARAMETER, SEC.ACC.MASTER and

SC.VALUATION.GROUP.
 TOP.UP.MGN.RATE and SELL.OUT.MGN.RATE will hold top up and sell out

rate that can be set at portfolio level, if top up and sell out rate is not set then it
will take it from the ov.parameter
 GLOBAL.LIMIT to specify the global limit
Slide 102
SEC.ACC.MASTER – Income analysis
 T24 allows classification of capital and income
 Separate transaction entries generated
 Users to update account to which income and charges are to be posted
Slide 103
Workshop - 9
Office> PWM Front Office Operations >Customer Maintenance> Client
Maintenance
 Choose Cash Account tabs
 Create 3 current accounts in USD/GBP/EUR for Customer created earlier
Office> PWM Front Office Operations >Customer Maintenance> Client
Maintenance
 Choose Portfolio tabs
 Create SAM for the Customer attaching these accounts
 Define GBP as reference currency
 Attach existing investment program, account office and managed account
 Attach the USD account as Safekeeping Account
 Define the USD account as default for securities buy transaction (BUY)
 Note that on committing a message is displayed that safekeeping frequency
and advisory fee frequency is defaulted from the fees parameter
Slide 104
Slide 105
Slide 106
SEC.ACC.MASTER - Own Book Portfolio
 Bank’s own portfolio dealing book

 Identified by the value in the DEALER.BOOK Field
 Accounting of assets purchased and sold

 ASSET.CATEGORY Field specifies the account to which the entries to be
posted
 In most cases assets will be posted to LIVEDB as a spec entry
 Interest Categories/account for accruals/P&L

 Accruals posted to a category INT.PAID.CAT & INT.RECD.CAT Fields
 Or to an internal account category defined in INT.PAID.ACCOUNT and
INT.RECD.ACCOUNT Fields
Slide 107
SEC.ACC.MASTER - Own Book Portfolio
 Coupon payable/receivable & adjustment categories

 CPN.PAYABLE.CAT Field is used to specify the CATEGORY code to
which coupons payable will be posted
 Similarly CPN.RECEIVABLE.CAT Field is used to specify the CATEGORY
for Coupons Receivable
 CPN.ADJ.CR.CAT Field specifies the CATEGORY to which Adjustments in
accounted for coupons receivable
 Similarly CPN.ADJ.DR.CAT Field specifies the CATEGORY to which
Adjustments accounted in respect of coupons payable
 Profit & Loss categories for realised and unrealised profit/loss

 REAL.PL.CAT.PROFIT and REAL.PL.CAT.LOSS Fields specifies the
CATEGORY for such accounting
 UNREAL.PL.CAT.PRT and UNREAL.PL.CAT.LOSS Field specifies the
CATEGORY to which unrealized loss accounting entries posted
 Based on the setup in SAM in the POST.UNREAL.PL Field
 Setup required for revaluation
Slide 108
SEC.ACC.MASTER - Discount Processing
 Flag to include discount processing

 ACCRUE.DISCOUNT Field specify whether discount processing is
YES/NO
 Category for discount instruments

 Single category for debits/credits defined through DISCOUNT.CAT Field.
 Category to post the discount/premium accrual/amortised
 No distinction by type of security
 Discount accrual method

 Method controlled by LINEAR.COMP.ACCR Field
 Linear method
Simpler. Same amount until position changes or matures
 Compound method
Based on Yield to Maturity information held on SC.TRADING.POSITION
Table
Better measure of risk as risk decreases closer to maturity
Slide 109
SEC.ACC.MASTER - Discount Processing
 Posting of discount
 POST.DISC.UPFRONT Field specifies whether discount is posted upfront
 If Yes, Amortisation takes place, otherwise accruals posted
 Posting of discount on sale

 DISCSOLD.TO.REALPL Field to control posting of discount to realised PL
on sale of securities
 If set to “Y”, proportional amount is transferred from the discount P/L to the
trading P/L under the entry type “Discount Sold”
Slide 110
SEC.ACC.MASTER - Interest Accrual
Accruals made on bank’s interest bearing security positions
 Accruals are done daily
 Accruals take place only for Own Book portfolios
 Accruals happen during COB based on the SECURITY.MASTER settings
 Accrual is controlled by the accrual start date and interest payment date
fields
 Position calculated from transaction history on SC.TRANS.POS.HISTORY
 Accrual entries raised to the category setup in SAM record
Slide 111
SEC.ACC.MASTER - Portfolio Types
Portfolio type for Security Account.
 PORTFOLIO.TYPE Field defines the portfolio type for Security Account
 Choices are: TRADING, INVESTMENT, AVAIL.SALE
 For investment or commercial purposes
 Different tax rate is applicable if Securities are bought or sold for investment
or commercial purposes
 Unrealised profits due to revaluation of TRADING & INVESTMENT portfolio

could be raised to LIVEDB (Asset) or Internal account and credited to P&L
 But for a AVAIL.SALE portfolio it is debited to LIVEDB or Internal account

and credit to internal account and not to P&L category
Slide 112
SEC.ACC.MASTER - Revaluation
 Mark to Market frequencies and types

 REVALUATION Field triggers revaluation process
 Unrealised profit or loss will be calculated
 Posting of revaluation entries

 REVAL.POST.METHOD Field defines revaluation posting method
 If ADJ, then the revaluation entries are raised only for the adjustment value
 If set as I/O, then the previous entries are reversed and fresh entries raised
for the revised amount every day during COB
 Frequency required for revaluation

 REVAL.FREQ Field indicates the frequency
 POST.UNREAL.PL Field defines choice of revaluation posting

 BOTH/LOSS/RVAL/LOWER.COST/NONE
Slide 113
SEC.ACC.MASTER - Revaluation
 T24 uses Average Cost Price to hold cost of a Security Position.

Calculated by the addition of Purchases only
 Average cost determines the realized profit instead of the selling price,
so that the average cost of the remaining position remains unchanged
after the sale until additional purchase trade
 If portfolio is flagged for revaluation marked to market revaluation is

performed depending on revaluation frequency
 SC.TRADING.POSITION Table holds details relating to the Trading

position of each security including unrealised profit and loss
Slide 114
Workshop - 10
 Use User Menu> Treasury Operations > Securities (Own Book) > Back
Office > Create Portfolio > Create Portfolio
 Use copy function and create a portfolio with Id as 999999-NNN from a
existing portfolio, namely 999999-1
 Get the record authorised
Slide 115
Slide 116
Quiz - 9
1) How many portfolio records can be created for a customer ?

Ans: Maximum no is 997
2) What is the purpose of reference currency in a SAM record?

Ans: It is the currency in which assets of a portfolio is valued
3) What are the different methods of revaluation posting that is possible?

Ans: I/O method and ADJ method
4) How is a customer portfolio and Banks own portfolio identified by the

system?
Ans: Identified by the value in the DEALER.BOOK Field
5) Does discount processing take place for all portfolios?

Ans: Only happens for own book portfolios defined in SAM
Slide 117
SEC.ACC.MASTER - Recap
SEC.ACC.MASTER
Customer Own book
Reference currency
Portfolio valuation Type of portfolio
INVESTMENT.PROGRAM
Revaluation methods
Portfolio modelling
MANAGED.ACCOUNT Discount calculations

Advisory fees
Defaulting ACCOUNT Interest Accruals

numbers
Slide 118
Product Features
Slide 119
Order Processing
Slide 120
Securities Trading Overview
Product Specific Security Entities Securities Products

Parameters
Specific Parameter files
Trade
T24
Processing SECURITIES
Order Execution Security Trade Settlement
Slide 121
Application Processing
Order Order Placement

transmitted
to broker
Confirmation
from broker Execution of the
Confirmation from
order
depository
Direct
Input of
trade Message to
Completion of depository Settlement of
trade trade
Security Position
Slide 122
Order Processing
SEC.OPEN.ORDER
Order
transmitted Executed order Execution details
authorised
SC.EXE.SEC.ORDERS SC.EXE.SEC.ORDERS SC.EXE.SEC.ORDERS
$NAU LIVE $HIS
Balance Partly executed Completed

nominal order order
unfilled in
IHLD status
SEC.TRADE
Slide 123
SC.PARAMETER - Order Processing
 Open order accounting

 If OPEN.ORD.FWD.ACCT Field is set to Y, raises F entry for the open
order
 Charge calculation
 If CALC.CHG.ST.HLD Field is set as Y, then charges Charges/tax are
defaulted in the trade created in Hold, when the order is executed/traded
 Else the charges are computed while committing
 Cash availability for bulk order

 AC.ORDER.BAL Field controls which Account balance to use when carrying
out cash availability checks for portfolios for bulk orders
 Cash availability is checked with ONLINE or FORWARD balance
 Trading in broken units

 OVER.TRADE.UNIT Field has value YES or NO flag to allow whether the
customer side of the order can be in broken trading units
Slide 124
SC.ORDER.TYPE
 Different types of Orders
 Fields in SC.ORDER.TYPE record

 CASH.ORDER
Only cash amount furnished and system calculates the quantity of
security
 LIMIT.PRICE
Price order with min/max price for sell or buy order mandatory
 FULL.TRADE
When Yes, Override if partially executed
 LIMIT.PRICE.CHECK
If yes then override raised validating with LIMIT.PRICE in order
Slide 125
SEC.OPEN.ORDER
 Dealing department of the bank

 Direct instructions from client
 Instructions to Account Officer by the client transmitted to the Dealing Dept.
 Instructions for portfolio management
 Application holds the buy/sell instructions for a security at a certain

order type valid for a specified date in the required currency
 Id is OPODSCYYDDDSSSSS where OPODSC is the prefix for the

application, YY is the year of the transaction, DDD is the Julian date &
SSSSS is the sequence number. If Unique ID is set, then SSSSS
would be random alpha numeric
 Order Type
 ORDER.TYPE Field input details the type of Order
Ex:- BEST or at MARKET
Slide 126
SEC.OPEN.ORDER
 Date and time of order submission
 Value date of order

 Defaults from STOCK.EXCHANGE
 Also user input
 Validity of order
 LIMIT.TYPE Field specifies how long the order is valid
 GTD/GTW/GTM/GTY or
 Date can be specified in LIMIT.EXP.DATE Field
 Type of transaction
 Indicates whether buy/sale of the security
 TRANSACTION.CODE Field indicates the order is to buy or sell
Slide 127
SEC.OPEN.ORDER
 Order details
 Security number of instrument traded

 Only one can be ordered at a time
 Customer placing order

 Multiple customer including mix of Customer and Own Book
 Channel via which Order is placed

 Fees can vary based on channel mentioned in SEC.TYPE field in the
SCTR.GROUP.CONDITION
 Customer account/nominal
 CUST.ACC.NO Field identifies the customer's account
 CU.CASH.AMOUNT Field contains the cash amount that is to be traded
 Only for cash order otherwise nominal in NO.NOMINAL Field
 SECURITY.MASTER price defaulted for cash flow of customer account
Slide 128
SEC.OPEN.ORDER
 Current status of the order

 DEAL.STATUS Field controls the next action to be continued with the order
 TRANSMITTED
If SC.STD.SEC.TRADE has TRANSMIT.ORDER Field set to YES,
the SC.EXE.SEC.ORDERS records will only be created once the
authorized SEC.OPEN.ORDER record
Otherwise the SC.EXE.SEC.ORDERS record will be created at
authorization of the SEC.OPEN.ORDER
 TRADED
Directly creates a trade
 ACCEPTED
Pre transmission
 REJECTED
When the status is rejected by the broker in the execution file
 “ ” (Null)
When null, order can be modified
For grouping of orders
Slide 129
Workshop - 11
 Use User Menu > Private Operations > Securities > Front Office >
Direct Ordering > Single Orders > Order Entry > Buy Order
 Indicate Security created earlier and Order Type as Market
 Input a purchase of 100,000 quantity of a share for your customer and
Portfolio created earlier
 Use Broker created earlier
 Ensure Deal status is Transmitted.
 Commit the transaction and make a note of Transaction Id
Slide 130
Slide 131
Slide 132
SC.EXE.SEC.ORDERS
 When the order is transmitted record created in this file with the same
Id as SEC.OPEN.ORDER
 To be filled with broker details and execution price
 Can be partially executed
 Can be executed by multiple brokers
 Once details input & authorised creates a SEC.TRADE in IHLD
 The broker details with the execution gets updated into the order record
Slide 133
Workshop - 12
 Use User Menu > Private Operations > Securities > Middle Office
Client Order Execution> Order execution > Dealer Blotter
 From out of the list of orders to be executed, select your order and execute
at a price of USD 103
 Accept override
Slide 134
Workshop – 12 Solution
Slide 135
SEC.TRADE
 Primary application to hold information of the trade like

 Security, buy/sell details, customer/counterparty/broker, quantiity of trade
 Id prefixed with SCTRSC followed by YYDDDABCDE, where

 YY is the year of the transaction
 DDD is the Julian date
 ABCDE
Sequence number or alphanumeric sequence
Slide 136
SEC.TRADE - Input
 Minimum input comprises of the following:
 Security traded
 Customer - buying or selling
 Broker - buying or selling
 Quantity bought/sold by each
 Price of the deal
 Defaulting of other details provided suitable setup available
Slide 137
SEC.TRADE
 Direct input of trade
 Security details
 SECURITY.CODE Field identifies the security traded
 The stock to be traded
 Based on stock details from the SECURITY.MASTER default as follows
Currency traded
Default Depository
Stock Exchange
Price defaults if DEF.CUST.PRICE Field in SC.STD.SEC.TRADE is Yes
Interest particulars like dates, rate, if applicable
 Trade/Value Date
 TRADE.DATE Field defaults to system date
 VALUE.DATE Field records depends on execution date like T+1 or T+2
 Based on the Stock Exchange traded, the value date is calculated from
trade date
Slide 138
SEC.TRADE
 Customer details involved in the transaction

 CUSTOMER.NO Field identifies the Customer(s) with whom the trade is
made
 Multiple customers can be used
 Mix of Individual Customer and Own Book
 Defined in the CUSTOMER.SECURITY as Customer
 Type of transaction
 CUST.TRANS.CODE Field indicates whether the Customer is buying or
selling
 Buy or Sell – Valid type from SC.TRANS.TYPE
 Portfolio number
 CUST.SEC.ACC Field identifies the Security Account of the Customer
 Must be a Security Account of the Customer
 First SAM record and has to be input by user for other portfolios
Slide 139
SEC.TRADE
 Account number
 Customer Portfolios
 Defaulted from SAM but user amendable
 Possible to setup rules for defaulting the specific accounts based on type of
transaction as set in the SAM
 Can be an account with currency different from the trade or security
currency, but should be an account defined in the SAM
 Possible to use an account belonging to another customer but the same
raises an override
 Own Book portfolios

 XXX–CRF-00 defaults for Own Book where XXX represents Trade Currency
 CRF is term for general ledger defined in the SAM
 In most cases assets will be posted to LIVEDB
Slide 140
SEC.TRADE
 Nominal
 CUST.NO.NOM Field specifies the nominal of the Security
 Quantity of the security traded
 Validated with trading units in SECURITY.MASTER
 In multiples of the trading units if set
 Price
 CUST.PRICE Field records the Price at which the trade has been dealt
 Defaulted from SECURITY.MASTER if set
 Interest amount
 CUST.INTR.AMT Field is applicable for bonds
 Based on security details namely rate and interest days, interest amount is
calculated by T24
 Calculates interest up to the value date from the last accrual date
 Possible for user to amend the interest amount which has been defaulted
Slide 141
SEC.TRADE
 Broker details if involved in transaction
 Trade can be completed between 2 or more customers
 Customer set of fields multi valued for this purpose
 Combination of different number of buys/sells
 Total buy and Total sell quantity should be equal
Slide 142
SEC.TRADE
 Broker through whom executed

 BROKER.NO Field indicates the Broker details
 Multiple brokers can be defined
 Defined in the CUSTOMER.SECURITY
 Role of the broker with respect to the trade

 BROKER.TYPE Field indicates with what type of Counterpart
 Allowed Input are Broker/Counterparty/Client
 If single role defined in CUSTOMER.SECURITY, then default takes place
 Transaction type of the trade

 BR.TRANS.CODE Field to confirm whether the broker is buying or selling
 Valid type from SC.TRANS.TYPE Table
Slide 143
SEC.TRADE
 More Broker details

 BR.NO.NOM Field is used to enter quantity of the security traded
 Price arranged with broker is entered in BR.PRICE Field
 Multiple brokers at different price - multi value fields
Same broker with different price - sub value fields
 BR.ACC.NO Field Identifies the Account over which financial entries relating
to the Broker for the trade, are to be passed
Defaults from NOSTRO.ACCOUNT record for the trade
currency/settlement currency
Can be defaulted from CUSTOMER.SECURITY record of Broker
 Broker depository
BROKER.DEPO Field records which Depository the Broker is using
Mandatory if the settlement through a clearing system
Defaults from CUSTOMER.SECURITY record of Broker, if available
Slide 144
SEC.TRADE
 More broker details
 BR.DELIV.INSTR Field used when Broker amount not credited to his

current account but requests an external delivery of the funds to a Bank
 Valid record in SC.DEL.INSTR
 Security and cash movements are not interlinked if free of payment
 Both cash and securities movements if delivery against payment basis
 Will form part of the message formats when building SWIFT type messages
 BR.BEN.BANK.1 Field identifies the Beneficiary Bank, when the Broker has
requested external delivery of the proceeds of the transaction
Slide 145
SEC.TRADE - Currency Related
 Security currency is defaulted from SECURITY.MASTER
 Account currency defaulted from the SAM
 Broker account defaulted from the NOSTRO for the security currency
 User can amend any of the above to other accounts which could be
same or different currency
 If different, exchange rate for conversion defaults from currency record

but can be amended by user
Slide 146
SEC.TRADE - Others
 NET of commissions or with commissions

 NET.TRADE Field enables to specify this functionality
 NO means system calculates brokerage and fees separately and populates
relevant fields
 YES means such fees are included in trade price so no separate calculation
performed
 PRORATA
Broker charges can be pro-rated against multiple customers- allocations
are based on simple nominals of bonds and shares
 Price
 Can be different when multiple Customer/Broker is used
 Dealer book – price different between Broker/Customer NOT allowed
Slide 147
SEC.TRADE
 T24 updates/calculates the following into the trade
 Interest accrual
 Gross amount
 Charges – Customer/Broker
 EBV fees
 Stamp tax
 Arrives at NET AMOUNT
Slide 148
Settlement of Trade
 Contractual Settlement
 When trade is authorised, T24 raises accounting entries for the value / trade
date
Customer’s account debited / credited
 Positions are updated on committing the transaction
 Actual Settlement
 T24 does further processing after trade completion
 Suspense entries raised on trade authorisation
 On cash settlement confirmation, Suspense entries revered and
entries raised on customer account
 Positions are updated as unsettled till settlement of securities is confirmed
by depository
Slide 149
Workshop -13
 Use User Menu > Private Operations > Securities > Middle Office >
Client Order Execution > Direct Sec Trade Input
 Input a purchase trade of a bond for own book and customer
 Use any BOND Security
 Use own book portfolio and individual customer portfolio created earlier
 Use own book Customer as 999999 and Own Book Portfolio as 999999-1
 Quantity - 1000 for own book and 500 for customer
 In the section Actual settlement, do not opt to hold cash and stock and
complete the trade contractually
 Observe the defaulting of the value date and the depository
 Value date to be made as today’s date
 Commit and get the record Authorised
Slide 150
Slide 151
Slide 152
Slide 153
Slide 154
Workshop - 14
 Use User Menu > Private Operations > Securities > Back office >
Securities Authorisation > Securities transactions
 Pick up the SEC.TRADE created by system for the Order executed earlier
 Change the default value date to today's date
 In the Actual settlement section, do not opt to hold cash and stock to
complete the trade contractually
 Complete and get the record authorised
Accounting Entries > View Transaction Entries
 View the accounting entries by giving the trade Id of your transaction
Slide 155
Workshop -14 Solution
Slide 156
Workshop -14 Solution
Slide 157
Workshop - 15
 Use User menu > Private Operations > Securities > Front Office >
Client Maintenance > Private Customer > Private Customer > Choose
Customer Securities Data
 Open the CUSTOMER.SECURITY record of your customer and include
your depository as default depository
Direct Ordering > Single Orders > 2 Step Order Entry > Buy Order
 Input a purchase order with multiple customers, for the above customer and
another existing customer.
 Order type as PRICE and Limit price as per details below
 Orders of 10,000 for each
 Use share created earlier
 Limit price of USD 97 and type GTD
Slide 158
Slide 159
Slide 160
Workshop - 16
 Use User Menu > Private Operations > Securities > Middle Office>
Client Order Execution > Order execution > Order to transmit
 Input the broker created earlier, broker nominal and transmit the order
Slide 161
Slide 162
Workshop - 17
Client Order Execution > Order execution > Dealer Blotter
 Execute the order partially at a price of USD 99, which is more than the
limit price
 Input broker nominal of 16,000
 Observe the customer nominal gets prorated on validation
 Observe the override and accept it
 Note that 2 trades are created in IHLD for the order
Securities Authorisation > Securities Transactions
 Complete the trade using depository as 100114
 Ensure that the actual settlement is set as NO
 Value date is today’s date
 Commit and get the both the trades Authorised
Slide 163
3
2
Slide 164
Slide 165
Slide 166
Workshop - 18
 Execute the remaining order at a price of USD 96
 Input balance nominal
 Complete the trade
 Value date is today’s date
 Commit and get the both the trades Authorised
Slide 167
Slide 168
Slide 169
Cash Order
 SEC.OPEN.ORDER can handle cash orders

 Enter a “cash” value and system will calculate the number of nominal
 Cash amount
 CU.CASH.AMOUNT Field for input of cash amount considered for security
trade when order type CASH
 Price of the security

 CURR.PRICE Field used to enter for the security
 Otherwise the system will obtain from SECURITY.MASTER record
 Calculation of charges
 CALC.CHRGS Field determines whether the system will automatically
calculate the charges
 If Yes charges are calculated and they will be passed through into the
SC.EXE.SEC.ORDERS application
Slide 170
Cash Order
 Basis of calculation of charges

 Nominal for the cash amount trade including all applicable charges that are
to be applied
 When Rounding is UNDER/OVER & commission adjust N/A

 CASH.ROUNDING Field options are EXACT or UNDER/OVER.
 If set to 'EXACT' then ADJUST.COMM Field becomes active to determine
whether to reduce the commission to make the trade match the cash
amount exactly
 For purchase order nominal will be calculated so that the total nominal
value plus applicable charges will be either exact or under the cash amount
by a trading unit
 For sale order nominal will be calculated so that the total nominal value plus
applicable charges will be either exact or over the cash amount by a trading
unit
Slide 171
Cash Order
 When rounding is EXACT & adjust commission is NO
 For purchase nominal will be calculated so that the total nominal value plus
any applicable charges will match the cash amount exactly. If an exact
match cannot be found then the transaction cannot proceed
 For sale nominal will be calculated so that the total nominal value minus any
applicable charges will match the cash amount exactly. If an exact match
cannot be found then the transaction cannot proceed
Slide 172
Cash Order
 When rounding is EXACT & Adjust Commission is YES, then the

nominal will be calculated for purchase and sale
 For purchase total nominal value plus any applicable charges will match the
cash amount exactly
 If this cannot be achieved the system will calculate to the nearest trading
unit over the total cash amount (cash amount plus charges) and the
difference between this and the total trade will be taken off the Commission
 For sale nominal will be calculated so that the total nominal value minus any
applicable charges will match the cash amount exactly
 If this cannot the achieved the system will calculate to the nearest trading
unit under the total cash amount (cash amount minus charges) and the
difference between this and the total trade will be taken off the Commission.
If there is not enough commission to achieve this then the transaction
cannot proceed
Slide 173
Execution of Cash Order
 When cash orders are executed the suggested price in the order and
the execution price may be same or different
 For example if a cash order for USD10,000 for a security order price
of USD 98 the suggested order will be for 102 nominal
 If the execution price is also USD 98 the order will be executed in full
 If the execution price decrease to USD 90 the order will be executed for
102 *90 USD 9180
 The remaining cash amount of 820 is waiting to be still executed.
 As this is cash order this is a partial execution and open order is remaining
 If the execution price increases to USD 100 the cash amount will be
exhausted and order will be executed for lesser nominal
Slide 174
Workshop - 19
 Input a cash order GROSS for purchase of cash amount USD 100,000 of
a share for another customer portfolio
 Choose security as 100025-000
 Choose another broker
 Nominal field becomes NO INPUT when the order type is mentioned as
CASH
 Calculate charges on the Gross amount
 Observe the defaulting of the price from the security master on

validating
 Accept any override and Commit the record
Slide 175
Slide 176
Workshop - 20
Security Position Enquiries > Positions by Security
 Indicate your Security
 View position of your portfolio
 Check the positions for the portfolios and drill down to the trade
 Observe the calculation of the gross amount
Slide 177
Slide 178
Slide 179
Order Grouping - Converting To Parent
Child Orders
Slide 180
Parent Child Orders
 Security Orders can be created as Parent Child Orders where Parent Order
holds the Broker(Market) side and the Child Orders holds each Customer’s side.
 The Parent Child Orders are linked by a common Reference. The Parent child
separation continues into Execution and Trade creation.
 The separation of an Order into Broker side and Customer sides can also be
done at the time of execution.
 In this case, the system creates separate trades – a Parent trade for the Broker
side and child trades for each of the Customers side
 This functionality makes it possible for the users to amend/cancel one or more
Client legs of an Order/ Trade without impacting the Market side and vice-versa.
Slide 181
SC.STD.SEC.TRADE
The SC.STD.SEC.TRADE needs to be

SC.STD.SEC.TRADE
parameterised for this functionality to work
 SYNTHETIC.PORT - Synthetic portfolio

that is to be used for parent child
processing. This Portfolio will be updated
in the customer side of parent
transaction.
 SYNTHETIC.CPTY - Synthetic
counterparty to be used for parent child
processing. The counterparty specified
here will be updated into broker side of
child transaction.
 ORDER.ALLOC.SUBR
Holds the local API which is going to allocate the nominals to
the customer based on the priority
Eg - Allocate first to the client with highest order quantity
Nominal allocated can be updated in customer nominal field
SC.EXE.SEC.ORDERS record
Slide 182
SC.STD.SEC.TRADE
 SYNTHETIC.SUSP.CAT - Synthetic suspense category to be used for

parent child processing.
 The internal account category specified here will be used for entry
processing in parent and child trades.
 For parent trade, Customer side account will be the internal account
formed using this category.
 For child trade, Broker side account will be the internal account formed
using this category.
Slide 183
SC.STD.SEC.TRADE
SC.STD.SEC.TRADE
 AUTHORISE.CHILD - Accepts a value

YES to denote that child trades are to be
authorised on authorisation of parent.
 Child trades will also be automatically

authorised if AUTHORISE.TRADE field in
SC.EXE.SEC.ORDERS of parent is set
as YES.
 PARENT.CHILD.DEPO - Where there

are different Depositories involved, this
setting will create Separate Parent Trade
for each Depository.
Slide 184
SC.BULK.TRANS.MATCHING
SC.BULK.TRANS.MATCHING
 This parameter is used to tell the system as to
which fields in Parent and Child transactions need
to be the same.
 The first field FIELD.NAME refers to fields in
SEC.TRADE. The ORD.FIELD.NAME refers to
fields in SEC.OPEN.ORDER.
 The field ORDER.EXCEP.CHECK determines if

exception checks needs to happen for
SEC.OPEN.ORDERs.
 If this is not set, then Exception check will happen

only for SEC.TRADEs.
Slide 185
Grouping of Orders
 SC.PARAMETER
• GROUP.ORDER Field controls the grouping method to be used
• MANUAL / AUTOMATIC / BOTH
 SC.STD.SEC.TRADE
• In SC.STD.SEC.TRADE the field TRANSMIT.ORDER has to be set to ‘YES’.
OFS.SOURCE and OFS.VERSION records have to be set up.
Slide 186
Group Parameter
 SC.GROUP.PARAM
 Includes system defined fields for grouping
 User defined fields can be included
 User defined routines can be created
SC.GROUP.PARAM has to be set-up. The record id of SC.GROUP.PARAM can be set as follows:
SECURITY.MASTER -A valid SECURITY.MASTER id can be defined as Id.

(100040-000)
SUB.ASSET.TYPE -A valid SUB.ASSET.TYPE can be defined as Id. (S-
102)
ASSET.TYPE A valid ASSET.TYPE can be defines as Id. (A-10)
SYSTEM A Generic Parameter record; this will be used when

no specific parameter is defined
Slide 187
Group Parameter
SC.GROUP.PARAM has a set of system fields, which are the mandatory parameters for
grouping.
SYS.FIELDS automatically populated by the system. While orders are grouped these
fields in SEC.OPEN.ORDER will be checked for a similar value.
Slide 188
Automatic Grouping of Orders
SC.AUTO.GROUP.ORDERS
SC.AUTO.GROUP.ORDERS will be used for automatic grouping of orders. The id of a

SC.AUTO.GROUP.ORDERS can be set as follows:
A valid SECURITY.NO (######-###, E.g. 100056-000)

S- followed by a valid SUB.ASSET.TYPE
A- followed by a valid ASSET.TYPE
ALL
Slide 189
Automatic Grouping Converting To Parent Child Orders
 Two levels of grouping can be achieved by setting GROUP.ORDER field in

SC.PARAMETER as BOTH. By doing so both Manual and Automatic grouping
can be used at the same time.
 The only distinction is “ALL” record in SC.AUTO.GROUP.ORDERS will not be

considered for automatic grouping.
 When Automatic Grouping records are set up in SC.AUTO.GROUP.ORDERS

then automatic grouping will be done; the other orders without grouping are to
be grouped manually.
 Enabling the field Parent.Child as YES allows to create parent child orders
based on the criteria's set
Slide 190
Automatic Grouping – Parent Child Orders
 Security Orders can be created as Parent Child Orders where Parent Order
holds the Broker (Market) side and Child Orders holds each Customer’s side
 Parent Child field enabled to Yes creates parent child orders
 The Parent Child Orders are linked by a Common Reference. The Parent Child
separation continues into Execution and Trade creation
Slide 191
• At the cut-off time, once SEC.OPEN.ORDERS is created, upon committing the record
the orders are grouped reflecting deal status as GROUPED and the grouped parent
child order is automatically TRANSMITTED
Slide 192
 After the cut-off time, provided relevant services are executed the
SEC.OPEN.ORDERS with multiple Customers, can be split into Parent Child Orders at
the time of execution. The TRADE.CREATION field defaults from the
SC.STD.SEC.TRADE record and must be set to PARENT.CHILD
Then, on authorizing the SC.EXE.SEC.ORDERS record, the system splits and creates the
following:
 Parent Trade with the Synthetic Portfolio on Customer’s side and the Actual Broker and
 As many Child Trades as required with the Actual Customers on the Customer side and
the Synthetic Counterparty on the Broker Side.
The Trades are created in 'IHLD' status and on completing and authorizing the PARENT
trade the child trades are auto executed and authorised.
Slide 193
Workshop - 23
 Create Parent Child orders using Automatic Order Grouping

functionality
 Use any valid Security record from SECURITY.MASTER table
 Set up SC.AUTO.GROUP.ORDERS for the selected security
 Run relevant services
Slide 194
Workshop – 23 - SOLUTION
 Pick up any security and set up SC.AUTO.GROUP.ORDERS for the

security to be grouped and parent child orders to be created.
 Record Id will be any valid Asset Type (A-###), Sub-Asset type (S-###)
or Security number (######-###) valid format
 Cut Off Time field – Valid system time for the orders to be grouped
 Cut Off Frequency field – Daily, Weekly, Monthly
 Parent Child Field – Enable the Field by checking Tick Mark box
Slide 195
Start the below services in Model Bank in Auto mode
 TSA.SERVICE, TSM
 TSA.SERVICE, BNK/SC.GRP.ORD.SERVICE
 TSA.SERVICE, BNK/SC.PARENT.EXECUTION
 TSA.SERVICE, BNK/SC.PARENT.CHILD.PROCESSING
 TSA.SERVICE, BNK/OFS.MESSAGE.SERVICE
Open TAFJ Shell screen and key in the below command
 tRun START.TSM – DEBUG

The above command will give the list of T24 services running
 Based on the service number open multiple TAFJ screens and using
the below command execute the remaining services
 tRun tSA # (# - stands for service number)
Slide 196
 Open TAFJ Shell screen and key in the below command would show the list of
running services
 tRun START.TSM – DEBUG
 Based on the screenshot

execute the remaining
services on multiple TAFJ
screens
 tRun tSA 2
 tRun tSA 3
 tRun tSA 4
 tRun tSA 5
Slide 197
 Create a SEC.OPEN.ORDER
 Indicate Security used to set up the automatic grouping in
SC.AUTO.GROUP.ORDERS
 Order Type as Market
 Input a purchase of 500 quantity of the same security for your customer
created earlier
 Ensure Deal status is left BLANK
 Commit the transaction and make a note of Transaction Id
 After committing / authorizing the transaction the orders will be grouped
and deal status will automatically change to TRANSMITTED
Slide 198
1 2
Slide 199
 The Child order will contain the PARENT order reference number
 There are 2 orders that get generated. One being the parent order and another
as child order
 Pick up the Parent order reference number and further execute the trade from
middle office (or using command SC.EXE.SEC.ORDERS,) by keying in the
Broker details and price
 Use User Menu > Private Operations > Securities > Middle Office > Client Order
Execution > Order Execution > Order Entry > Order Execution Shares
Slide 200
Pick up the Parent order reference number and further execute the trade
from middle office (or using command SC.EXE.SEC.ORDERS,) by keying
in the Broker details and price
Client Order Execution> Order execution > Dealer Blotter
 From out of the list of orders to be executed, select your order and execute
at a price of USD 100
 Accept override
Slide 201
 Commit and Authorize the Parent trade upon which SEC.TRADE is created in
IHLD status
 The Child orders will get executed as well and SEC.TRADE will be created in
IHLD status
Slide 202
Parent Order of SEC.TRADE Child Order of SEC.TRADE
Slide 203
Pick up the Parent order SEC.TRADE reference number and further

execute the trade from IHLD status (or using command SEC.TRADE,)
Client Order Execution> Direct Sec Trade Input
 Click on the Up arrow icon, key in the SEC TRADE# and press enter
 Accept overrides
Slide 204
 Parent Order of SEC.TRADE

 Accept override messages
 Upon authorizing the parent SEC.TRADE the child orders are automatically authorized
provided AUTHORISE.TRADE field is enabled in SC.STD.SEC.TRADE
Slide 205
Child Order of SEC.TRADE
Slide 206
Limits
Slide 207
Limits
 For Own Book portfolio trading there can be 2 types of limit
 Issuer
 Based on the issuer, limit the holdings for the dealer book
 Counterparty
 Trading Limits set for each Counterparty/Broker
Slide 208
Issuer Limit
 Setup
 LIMIT.REFERENCE
 LIMIT.PARAMETER
 LIMIT for the issuer who should be a security customer
 SECURITY.MASTER for a bond – with value in the issuer and the limit
reference
 SAM record with check limits set as YES
 SC.PARAMETER with the setup to update limits with nominal or value
 Input of a dealer book trade hits the issuer limit
Slide 209
Limits - Issuer
LIMIT.PARAMETER - SYSTEM
SC.PARAMETER
When a trade is input for the security to

the own book, then the limit of the issuer
is updated with the nominal
210
Limits - Counterparty
 COUNTERPARTY LIMIT
 In SC.DEL.INSTR type (for e.g.) FRE, setup for

COUNTERPARTY.LIMIT as YES
 Set LIMIT.PARAMETER for the LIMIT.REFERENCE
 LIMIT setup for the counterparty
 Limits checked for transactions with the Counterparty/Broker using the

SC.DEL.INSTR defined above
 Counterparty limits updated with the value of the trade
Slide 211
Limits - Counterparty
LIMIT.PARAMETER - SYSTEM
SC.DEL.INSTR
212
Delivery Messages
 The following swift messages are generated by securities module
 Delivery address maintained based on specific customer numbers

account number and portfolio
 103 - Customer transfer of cash

 This message is generated from SEC.TRADE and SECURITY.TRANSFER
applications. Message is sent to the Nostro bank
 202 -Third party transfer of cash

applications. Message is sent to the Nostro bank. When the delivery
instruction is free of payment and if settlement is made by a Nostro account
to a Bank (Broker is a Bank) then a MT 202 is generated
Slide 213
Delivery Messages
 515 - Securities Client Confirmation

applications. Message is sent to a customer
 518 - Counterparty confirmation

applications. Message is sent to other brokers This message will be sent if
BROKER.MSG.TYPE field in SC.PARAMETER is set to “518” and confirms
the trade details
Slide 214
Delivery Messages
Slide no. 276 Delivery Messages
Broker SSI
 The system defaults Broker Standard
Settlement Instructions (SSI) in Security
Transfers and Trades based on
STOCK.EXCHANGE, PL.SETT,
ASSET.TYPE/SUB.ASSET.TYPE, ISIN
COUNTRY.
 The user can also define the Priority to be

used to default Broker SSI instructions in
Security Trade and Transfers through a new
parameter.
 The Settlement instructions are mapped in

Depository Messages SWIFT MT540 to
MT543.
Slide 215
Delivery Messages
 MT540-543 messages to the depository are raised based on the

transaction type (BUY/SELL) and the delivery instructions (FOP/DVP)
 MT540 – Receive Free
 MT541 – Receive against payment
 MT542 – Deliver free
 MT543 – Deliver against payment
Slide 216
Delivery Messages
 MT 540 Receive free

 MT540 Receive Free will be generated if the customer is buying and the
broker is selling stock with broker delivery instructions set to FREE
 MT 541 Receive against payment

 MT541 Receive Against Payment will be generated if the customer is
buying and broker is selling stock with broker delivery instructions is DAP
 MT 542 Deliver free

 MT542 Deliver Free will be generated if the customer is selling and the
broker is buying stock with broker delivery instructions set to FRE
 MT 543 Delivery against payment

 An MT543 Deliver Against Payment will be generated if the customer is
selling and the broker is buying stock
Slide 217
Delivery Messages Inward
 MT 544 Receive free confirmation

 Received from the depository to whom an MT540 Receive Free is sent
 Confirm the receipt of stock from the respective Broker
 MT 545 Receive against payment confirmation

 Received from the depository against an MT541 Receive against payment
 Confirm the receipt of stock from or to from the respective Broker
 MT 546 Deliver free confirmation

 Received from the depository to whom an MT542 Deliver Free is sent
 Confirm the receipt of stock in full or in part from the respective Broker
 MT 547 Delivery against payment confirmation

 Received from the depository against an MT543 Deliver against payment
 Confirm the delivery of stock in full or in part and Payment received in full or
in part from or to the respective Broker
Slide 218
MT544-547 MESSAGES
T24 supports
MT540 –
Account Owner MT543 Account Servicer
Global Custodian Local Custodian
MT544 – MT547
MT544 –
MT547
Incoming
T24 Private Bank
Outgoing
Slide 219
MT544 - 547 MESSAGES
 Transaction settlement could be done either manually or by an

incoming SWIFT message
 The following messages are supported for processing incoming

settlement:
 MT 544 – Deliver free confirmation
 MT 545 – Deliver against payment confirmation
 MT 546 – Receive free confirmation
 MT 547 – Receive against payment confirmation
 System can also generate outward MT 544-547 messages on

settlement
 T24 covers both the roles of account owner for processing of incoming
messages and account servicer for generation of outbound
confirmation messages
Slide 220
MT 548 MESSAGE
 MT548 is a settlement status message sent by the custodian
 Processing of inbound MT548 controlled by field PROCESS.MT548.IN

in SC PARAMETER
 If MT 548 processing is turned on, SC MT548 MATCH QUEUE is

automatically updated for actual settlement Trades and transfers
 Incoming pre-matching Message (MT 548) updates the SC MT548

MATCH QUEUE with the Match code
 In case of incorrect Match code/transaction references, repair queue is

updated
Slide 221
ISIN for SWIFT Messages
 ISIN is the SWIFT accepted identifier for securities. In case the Security is
traded without ISIN then the SWIFT messages will not be sent at the time of
Trade instead the SWIFT messages would be sent post ISIN is received
 List of trades needs to be mentioned in the SC.GENERATE.INST

application post the ISIN is received for which Customer, Broker and/or
Depository advice needs to be sent
 On committing the record the system would re-generate and send out the
advices after the ISIN is received
Slide 222
Workshop – 21
Create a SEC.TRADE, wherein SECURITY.MASTER has no ISIN code.

 Input NO in the fields customer, broker and depo advice and authorise this
trade in SC.GENERATE.INST
Slide 223
SM record without ISIN
Slide 224
List of SEC.TRADE needs to be

mentioned and the system would re-
generate and send out the advices post
running the service
Run the Service

Amending the SM record with ISIN SC.GENERATE.INST.SERVICE
Slide 225
Slide 226
Enquiry - ISIN for SWIFT Messages
 To list all Securities without ISIN
 To list all the Securities where the ISIN has been recently updated
but the SWIFT has not been sent.
Slide 227
Workshop -22
 Use Role Based Home Pages > Private Operations > Private Banking
Front Office Home Page> Position Enquiries > Security Positions >
Positions by Portfolio
 View position of the portfolio of your customer
 Drill down to transaction
 Through more actions view the following

 Broker Delivery Message
 Customer Delivery Message
 Depo Delivery Message
Slide 228
Slide 229
Slide 230
Slide 231
Slide 232
Slide 233
Workshop - 23
Security Position Enquiries > Positions by Portfolio
 Indicate the security created earlier
 View position of customer portfolio
 Choose security movements from drop down option
 Use drop down option to sell position
 Sell off part of the position created earlier
 Complete the order as under

 Sell a nominal of 8,000
 Choose another Broker
 Set the Deal Status as Transmitted
Slide 234
Slide 235
Slide 236
Workshop - 24
 Execute the order at a price of USD 101
Slide 237
Slide 238
Workshop - 25
 Input depository details and get the record authorised
 Value date to be TODAY
 Get the record authorised
 After completion of trade view the following through context enquiries

 Broker Delivery Message
 Customer Delivery Message
 Depo Delivery Message
Slide 239
Slide 240
Slide 241
Slide 242
Slide 243
Slide 244
Enquiries
Following enquiries available to view details of security positions
 Position Summary
List of all positions held within T24
 Positions by Portfolio
Position for a particular portfolio
 Positions by Security
Security wise portfolios
 Positions by Depository
 Position as on Trade/value date
 Position between two dates
 Own Book positions
Own book positions with details of accruals and revaluation
Slide 245
COB Reports
 Following Close of Business reports for Orders available
 Orders to be purged
Expired orders
 Executed Orders
 Pending Orders
Slide 246
Other Features
Slide 247
Non Stop Processing
Slide 248
Non Stop Processing
 During the COB, the following functionality can be continued online
 Creation of CUSTOMER.SECURITY & SEC.ACC.MASTER,

SC.SETTLEMENT, DIARY and ENTITLEMENTS
 Input of new transactions with current or forward dates using the following
applications
SEC.OPEN.ORDER
SC.EXE.SEC.ORDERS
SEC.TRADE
SECURITY.TRANSFER
 Price update in SECURITY.MASTER
 Valuations enquiries in respect of existing and new positions
Slide 249
Non Stop Processing
 In the case of actual settlement being switched on, trade can be

completed up to creation of the settlement record
 New back dated transactions or amendment to authorised transactions

are not allowed
 Log of transactions input during COB can be maintained in

SC.TXNS.WHILE.COB when SC.PARAMETER is set
 T24 maintains position and valuation files - SECURITY.POSITION &

SC.POS.ASSET separately for transactions input during COB
Slide 250
Blocking of Positions
Slide 251
SC.BLOCK.SEC.POS
 Provides the ability for Position Blocking ie., block/unblock transactions

for future dates
 Blocked amount of security will be validated against the current holding

of the security
 Excess blocking raises an error message
 Unblocking will be permitted only if there exists a block on the security
 Id is prefixed with BBLKSC…
Slide 252
SC.BLOCK.SEC.POS
 Effective dates can be given for blocking/unblocking a position
 EFF.FROM.DATE Field
Date the new block/unblock transaction will commence
Can be today or future date
 EFF.TO.DATE Field
Date the new block/unblock transaction will terminate
If blank then permanent block
 NEW.BLOCK.AMT is a multi-valued field, which is associated with

BLOCK.EFF.FROM Field
 Contains the blocking amount that will become current on the actual
BLOCK.EFF.FROM Field
Slide 253
Blocking of Security Position
 Automatic creation of a record takes place in the following instance
 When the security is defined as the underlying instrument for a

derivative contract (covered call option) – setup made in Derivatives
module
 In SC it is possible to create an automatic block record

 Setting has to be done in the DIARY.TYPE
 With a setting in the DIARY, blocking is created when the ENTITLEMENT is
created in unauthorised stage
 With a setting in the ENTITLEMENT, blocking happens when the
ENTITLEMENT records are authorised
 When OVERSELL.BLOCK Field is specified in SC.STD.SEC.TRADE

as YES or “’(null) , then override else an error message
Slide 254
Blocking of Security Position
 SECURITY.POSITION
 BLOCK.EFF.FROM Field
contains the dates when the next change in block amount will occur
 NEW.BLOCK.AMT Field
contains the amount by which the total blocking amount will be effected
 Also holds the product namely SC/DX as blocking can be defined in
Derivatives module when the security is the underlying instrument
 SC.PARAMETER
 BLOCK.HISTORY Field, which specifies how many working days to keep a
block/unblock transaction in the SC.BLOCK.SEC.POS live file before
moving it to the History file
 Only records that have a date in the EFF.TO.DATE Field will be considered
for updating by the End of Day process
Slide 255
Workshop - 26
Front Office Home Page > Blocks and Restrictions > Blocks and
Restrictions > Block Sec Position
 To existing position a blocking created
 Input a block of 5,000 from today for 10 days and another block starting
after 10 days of the value date for a period for a week
Front Office Home Page> Position Enquiries > Security Positions >
Positions by Security
 View position of the portfolio of your customer
 Find out the positions blocked
Slide 256
Slide 257
Slide 258
Bulk Order Processing
Slide 259
ORDER.BY.CUST
 Powerful front-end securities order generation process
 ORDER.BY.CUST will select the required portfolios, using user defined

selection criteria
 Apportion the nominal bonds/shares or raise an amount of cash based

upon the current value of the portfolios that match the given criteria
 Handles purchase, sale, cash, blocking and switch orders using

multiple switches in a record
Slide 260
ORDER.BY.CUST
 Type of order
 ORDER.TYPE Field specifies the type of order
 Mandatory input
 Options are
CASH
PURCHASE
SELL
TARGET
PURCHASE.INCR
SELL.PERC
SWITCH
Slide 261
ORDER.BY.CUST
 Powerful front-end securities order generation process
 ORDER.BY.CUST will select the required portfolios, using user defined

selection criteria
 Apportion the nominal bonds/shares or raise an amount of cash based

upon the current value of the portfolios that match the given criteria
 Handles purchase, sale, cash, blocking and switch orders using

multiple switches in a record
Slide 262
Bulk Trade
 The Parent Child Bulk order functionality has been enhanced to handle
the following:
 Create Parent Child Orders from ORDER.BY.CUST and

AM.COMPARE
 Allow amendment to Parent Order/Trade and ensure that the

amendment is automatically updated in all Child Orders
 Allow Bulk authorisation of Child Orders/Trades when Parent

order/trade is authorised
 Allow bulk deletion/replacement of Parent Child transactions
Slide 263
Bulk Trade
 Validate some common fields like Nominals, Trade date, Value date,
Security No etc. match between Parent and Child transactions and
Update a Log file when there is a mis-match
 Ensure that child orders created/executed are for a set minimum order
lot
 Create Parent trades separately per Depository if parameterised and

also suppress parent depository instruction (Swift 54* messages)
based on a flag
 Bulk Orders with Multiple Customers can be separated into Customer

Side and Market side such that any amendment or cancellation of one
side does not impact the other.
Slide 264
ORDER.BY.CUST –TARGET
 When TARGET is entered the TRANS.TYPE.DB & TRANS.TYPE.CR

Fields must be populated
 Not possible to use TARGET with the ORDER.NOMINAL,
GROSS.AMOUNT or CASH.AMOUNT Field
 Credit security to be given

 SECURITY.NO.CR Field identifies the security for the purchase
 Value of the target percentage compared to the value of the current

security holding
 Difference in these two values will be used to calculate how many of the
security needs to be purchased or sold
 If percentage specified as zero then the entire holding will be sold
Slide 265
ORDER.BY.CUST- PURCHSE.INCR
 PURCHSE.INCR option valid when the PERCENTAGE Field is used

 Not possible to use with the ORDER.NOMINAL, GROSS.AMOUNT or
CASH.AMOUNT Fields
 PURCHASE.INCR option is to create Buy Orders for a Security based

on its valuation.
 For eg., if there are 2 positions as under
Stock Nominal Price Value
A 1000 10 10000
B 2000 20 40000
 If you want to increase the Position of A by say 10% the system will
arrive at 10% of the value of purchase based on Stock A valuation i.e.
10%*10000=1000 & arrive at the nominal i.e. 1000/10 = 100. So a Buy
Order for 100 nominals will be created
Slide 266
ORDER.BY.CUST - SELL.PERC
 SELL.PERC option is valid when the PERCENTAGE Field is used
 Not possible to use with the ORDER.NOMINAL, GROSS.AMOUNT or

CASH.AMOUNT Fields
 Value of the current holding is calculated and this value will be decreased
by the specified percentage
 Difference in these two values will be used to calculate how many of the
security need to be sold to achieve the new value
 For eg., if there are 2 positions as under
Stock Nominal Price Value
A 1000 10 10000
B 2000 20 40000
 If you want to decrease the position of A by say 10% the system will arrive
at 10% of the value of order based on Stock A valuation i.e.
10%*10000=1000 & arrive at the nominal i.e. 1000/10 = 100.
 Customer will not sell short
Slide 267
ORDER.BY.CUST - SWITCH
 SWITCH option generate orders to sell one or more security and

reinvest up to the amount generated in other securities
 Processes n-to-m switch orders which results in an n-to-m relationship

regarding the number of securities involved respectively in the sell and
the buy side of the order
 Proceeds from the sale side of the transaction are the upper limit to be
reinvested
 Each security can be assigned up to 100%
 On the buy side the sum of the allocations for all buy-side securities
should be 100% or less
Slide 268
ORDER.BY.CUST - SWITCH
 Multiple securities can be selected for the “sale” and the “buy” side of
the operation
 No duplicate security can be involved in the order
 Securities intended to be sold specified in the SECURITY.NO.DB

Field
 Similarly, the target securities for which the resultant buy order needs
to be generated should be input in SECURITY.NO.CR Field
 To specify any number of SECURITY.MASTER records
 Enables the user to sell and buy multiple securities in a single order
Slide 269
ORDER.BY.CUST
 Criteria for selection of portfolios

 DEPT.ACCT.OFF Field can be used as Selection Criteria
 And or one or more chosen criteria from any valid field name or number
from SEC.ACC.MASTER Table
 FIELD.SELECT Field enables to define selection Criteria
 FIELD.OPERATOR Field could be chosen as Equals, Not Equal to,
Greater, Less Than, Like, Unlike
 FIELD.OPERAND Field used used to provide Criteria values
INVESTMENT.PROGRAM EQ 47 and DEPT.ACCT.OFF EQ 320 will be
read as SEC.ACC.MASTER accounts with INVESTMENT.PROGRAM EQ
47 and with DEPT.ACCT.OFF EQ 320 to be selected
Slide 270
ORDER.BY.CUST
 SEC.OPEN.ORDER order type to be chosen

 SOO.ORDER.TYPE Field details the type of Order
 A valid record in SC.ORDER.TYPE
 CASH order not allowed
 Security details for sell, purchase and switch types
 Market price for SWITCH or SELL type
 Limit price for PRICE type
Slide 271
ORDER.BY.CUST
 Expiry dates of the order

 EXPIRY.DATE.DR and EXPIRY.DATE.CR Fields specify the validity of
the Limit, i.e. how long is it to remain in force
 Trading units of security

 TRADING.UNITS.CR and TRADING.UNITS.DR Fields specify the smallest
nominal amount that may be traded
 Stock exchange to which security traded or preferred exchange

 STOCK.EXCHANGE.CR and STOCK.EXCHANGE.DR Fields refer to the
Stock Exchange at which the Security belonging to is normally traded
 Display of orders
 ORDER.PRESENT Field determines the order of display for the suggested
orders
 Choice SECURITY or PORTFOLIO
Slide 272
ORDER.BY.CUST
 Order nominal to be purchased or sold

 ORDER.NOMINAL Field is used to indicate the total Nominal to be
Purchased or Sold
 Gross Amount of the required order

 GROSS.AMOUNT Field is the total Value of the required order. It is an
optional Input field. It must be entered, if ORDER.NOMINAL or
PERCENTAGE Field is not entered
 Percentage of the portfolio value

 GROSS.AMOUNT Field is the total Value of the required order
 Cash Amount
 CASH.AMOUNT Field is used to enter cash amount to be applied to each
portfolio selected
 Used to determine the amount of nominal to trade
Slide 273
ORDER.BY.CUST
 Cash rounding
 Used to specify the rounding method
 EXACT and UNDER/OVER options
 Adjust commission to determine, whether to reduce the commission
 Nominal rounding
 Options NATURAL/UNDER /OVER
 Commissions and charges are not considered in the calculations
Slide 274
ORDER.BY.CUST
 Rounding factor
 ROUNDING.FACTOR Field is the Minimum Lot Size of the suggested
Nominal for each portfolio
 Cash availability for the orders

 CASH.AVAIL.REQD Field is used for Purchase Orders, the Customer
Account Balance on any account in this currency will be looked at for
calculation
 Cash percentage to remain with the portfolio

 CASH.PCENT.LIMIT Field for Purchase Orders, the user can specify how
much of the portfolio balance is to remain as cash
 Minimum lot and Maximum lot for purchase orders

 MINIMUM.LOT For Purchase Orders, allows the user to specify the
Minimum nominal that will be allotted to a single portfolio
Slide 275
ORDER.BY.CUST
 Open order processing
 INC.OPEN.ORDERS Field is used to either include or exclude the current

open orders in the calculations
 Value of the open orders is stored in the SC.POS.ASSET for open order
nominal, value of the nominal and One for the accrued interest in the three
NET.OPEN.ORDER.NOM, NET.OPEN.ORDER.EST and
NET.OPEN.ORDER.AI Fields
 Total valuation amount including open orders is also stored in the

SEC.ACC.MASTER record in the NET.OPEN.ORDER.VAL Field
Slide 276
ORDER.BY.CUST
 Settlement currency can be defined
 If transaction is done in a currency for which the customer portfolio has an

account, that account will take priority
 Option to choose SETTLEMENT.CCY at the ORDER.BY.CUST level
 Enable the choice of customer account to be defaulted for the settlement of

the Trade
 SETTLEMENT.CCY on the Sell and Buy sides will have to be the same
Slide 277
ORDER.BY.CUST
 SECURITY.CCY.DB and SECURITY.CCY.CR are automatically

populated from the respective SECURITY.MASTER records
 Currency exchange rate to be used in case the settlement currency is

different from the security currencies can be defined by the user
 If not specified, the last recorded FX rate with a customer spread

applied between the two currencies will be used
 Broker details of sell side execution is provided in BROKER.NO.DB

Field. For buy side execution BROKER.NO.CR Field used
Slide 278
ORDER.BY.CUST
 Particular of trader
 Order passed on to a particular trader is specified in TRADER.CODE Field
which should be a valid DEPT.ACCOUNT.OFFICER record
 Input of instructions or comments, to be passed on to the dealers in
TRADER.DESC
 Input of Y in AUTO.SELECT Field, will generate/re-generate portfolios

with suggested nominal to complete the total Order - order
completion, trade and settlement wherever necessary
 SERVICE option will generate the order via a service
Slide 279
Workshop - 27
Direct Ordering > Bulk Orders > Bulk Orders
 Input PURCHASE.INCR for share created earlier, for the customer created
 Auto select is set to Y
Direct Ordering > Bulk Orders > Complete orders on hold
 Input broker details and only for 3000 nominal
 Value date is equal to today
 Complete both trades
 Value date is equal to today
 Actual settlement is set as NO
Slide 280
Slide 281
Slide 282
Slide 283
Slide 284
Slide 285
Slide 286
Slide 287
Workshop – 27
Direct Ordering > Bulk Orders > Bulk Orders
 Input a Switch order for 20 percent of Bond
 Switch the same for 100 percent of shares
 Auto select is set to Y
Direct Ordering > Bulk Orders > Complete orders on hold
 Input broker details and price for both orders
Slide 288
Slide 289
Slide 290
Slide 291
Slide 292
Slide 293
Thank You
TEMENOS EDUCATION CENTRE

NOTICE
These training materials are the copyrighted work of Temenos Headquarters SA and other companies in the TEMENOS group of
companies (The Copyright Owner). The training materials contain protected logos, graphics and images. Use of the training materials
is restricted solely for use by licensed end users, partners and employees. Any un-licensed reproduction by any means, redistribution,
editing, transformation, publishing, distribution, or public demonstration of the training materials whether for commercial or personal
gain is expressly prohibited by law, and may result in severe civil and criminal penalties. Violators will be prosecuted to the maximum
extent possible. Such training materials shall not be represented, extracted into or included in part, or in whole, as part of any other
training documentation without the express permission of the Copyright Owner, which must given in writing by an authorised agent of
the Copyright Owner to be valid. Where such permission is given a clear and prominent notice must be displayed on any and all
documentation accrediting the Copyright Owner with having copyright over the materials. End-user licenses will in no event contain
permissions extending the use of these training materials to third parties for commercial training purposes.
Without limiting the foregoing, copying or reproduction of the training materials in part or in whole to any other sever or location for
further reproduction or redistribution is expressly prohibited, unless such reproduction is expressly licensed by the Copyright Owner.
Copyright © 2010 Temenos Headquarters SA

T3SCAT - Securities Administration &amp; Trading - Front Office

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

T3SCAT - Securities Administration &amp; Trading - Front Office

Transféré par

Droits d'auteur :

Formats disponibles

T24 Securities Administration and

TEMENOS EDUCATION CENTRE

 Introducing the participants to the T24 SECURITIES ADMINISTRATION &

 Learning about risk management, accounting and messaging, as appropriate to

Introducing the participants to T24 (SC) ADMINISTRATION & TRADING module

Players Customer, Own Book, Broker, Depositary set up

Core Tables Commission, Tax, Interest, Parameter & Static Tables

Order, Execution & Trade Completion Stage,

Swift Message Broker, Customer & Depositary Interaction via Swift

Limits How limits related to trading activity is set up in T24

Share Own Book

 Securities makes use of

 Category codes are set up through SC.PARAMETER

 Specific transactions possible to set through SC.TRANS.TYPE

 Different category codes can be indicated for reporting and information

 Parameter tables to be set-up for Securities Administration and Trading

 Top level parameter tables

 Portfolio related tables are to be set up during secondary build as it is

These types can be used while collecting Commission in Securities.

Accounts used as per Transaction

 Choice of Actual or Contractual settlement

 Maturity of settled transactions

 Suppression of customer entries pending settlement

 Start of day processing

 User defined Tax subroutine

 Posting of stamp tax

 Exemption of stock exchange fees

 Method to use when calculating the margin value

 Trade date or value date basis for cost of position

 Coupon and Redemption events

 Core routine for automatic processing

 Dates for processing

 Splitting of source and local tax

 It is possible to include Segregated Account for valuation.

 Field EXCL.INC.VALUATION needs to be set to YES, use an Account

 Closed portfolio updation rules

 CALC.CLOSED.PORT Field enables switching off calculations on closed

 SC.STD.SEC.TRADE This table contains company level default values

 Defaulting transaction codes and category codes for different

 Parameter File for trade application

 Trade level processing rules

 Price tolerance in trade

 Defaulting of price in trade from SECURITY MASTER

 Defaulting of trade time

 Transactions exempted from charges/commission

 Selling of blocked position

 Partially filled orders

 CANCEL.REMAIN.ORD Field controls whether “remaining order sent to

 Settlement Based on Currency Calendar

 CURRENCY.CALENDAR field need to be set to YES to enable system to

Checking of balance in account

CREDIT.CHECK Field validates for availability of funds from either of

 Working Balance plus today’s forward balance

 Available Balance and Working Balance

 Choice of Trade date or value date accounting

 Updation of available balance in customer account

SC.DEL.INSTR table defines characteristics of settlement instructions

 Identifies whether securities are to be received/delivered which is applied

 TO.BE.RECD.OR.DEL Field specifies whether the transaction is of a type

 WITH.PAYMENT.FLAG Field specifies whether delivery is to be against

 MT540 sent to depository expect to receive security free of payment

 COUNTERPARTY.LIMIT Field indicates whether counterparty to be

 Id comprises of alphanumeric characters

 Domicile of the exchange

T3SCAT - Securities Administration & Trading - Front Office

T3SCAT - Securities Administration & Trading - Front Office