AM Back Value Management-3
AM Back Value Management-3
Application Design
This document presents the principle back-value functionalities and orientations and then describes
the back-value operations mentioned above, followed by the recalculation process that is triggered
by those operations. Finally the last chapter describes the back-value system parameterisation.
Main functionalities
Below are the main rules that have been followed when designing and developing this system.
Back-value period
The back-value parameterisation system requires to define a first date which limits the back-value
recalculation process and a second date which, determines the date from which the recalculation
updating should start. Moreover, using the On-Line recalculation process (see in section below)
provides the user with the ability to apply the Back-Value recalculation for a selected date only.
Recalculation process
Back-Value portfolio recalculation process is split into five different sub-processes: price, exchange
rate, cash, security and corporate action. Each of these sub-processes can be launched either On-
Line, though a specific application, or at End Of Day. Note that Back-Value operations are
available for On-line process the day next to the day they have been recorded. Composite back-
value recalculation is an online process.
Back-value transactions are available within the existing transactional structure: only back valued
transactions, based on the value date of a transaction being less than the current working date, are
treated, no chained or combined transactions which may be indirectly linked to the back value
transaction are modified by this development.
The user records a back-value transaction on a security: share purchase for example on the 1st
February for a particular portfolio. If a corporate action has been recorded on this same share on the
15th March: the system will not automatically modify the original corporate action on this portfolio.
The user will have to record a new corporate action for the updated position.
Current Treatment
A back-value transaction is applied using the current parameters applied to the portfolio: historical
data such as parameters or links are not stored. Commission and tax calculation rates used for back-
value are the current ones. A back-value transaction will not be possible if the impacted entity has
changed status or link, e.g., it is not possible to create a back-value transaction on closed portfolios.
Accounts: Account has been removed from its portfolio since the back-value date.
Portfolio valuation recalculation results are maintained using a monthly file system.
Each file of this set of files is named SC.VEH.YYYYMM where YYYY MM represents
respectively the year and month of the portfolio valuation data available in the file.
The structure of this file is described in last chapter: ‘SC.VEH.YYYYMM file structure’.
This structure is unique for securities information and cash information: field definitions depend on
the type of position.
A model enquiry is provided, including a routine that addresses the SC.VEH.YYYYMM file
matching the date selected in the enquiry selection window.
This enquiry is: SC.VAL.HIST.YYYYMM
Re-printing
No re-printing functionality has been developed for this back-value system: the bank will use, adapt
or develop the tools necessary to re-print after back-value operations.
General principle
In the majority of operations included in this back-value system we can find three kinds of dates:
TRADE.DATE and VALUE.DATE are input by the user. T24 WORKING.DATE is generated by the
system.
For a standard operation we have generally the following relations between these dates:
Important:
The back-value system will consider an operation to be back-valued only if its TRADE.DATE is less
than T24 WORKING.DATE.
For the transactions without TRADE.DATE, the VALUE.DATE information is used instead. Details are
listed in chapter below.
Principle declination
The preceding generic principle declines itself according to existing application specific transaction
labels and structure. The table below lists the correspondences between TRADE.DATE references
mentioned above and the field used in each transaction for back-value identification.
Example: for FUNDS.TRANSFER as there is no concept of trade date for that transaction, the
VALUE.DATE information is used instead to determine a back-value operation.
The following activity diagram synthesises a dynamic view of the back-value system
Bv Corporate
Bv Security Bv Cash Bv Price Bv Forex Rate
Action
EOD Process
Collect BV
operations
Triggered either
Storage of Composite portfolios Portfolio Valuation
automatically for BV
impacted by BV operations Recalculation
EOD parameterisation,
or on user demand for
BV OnLine
parameterisation
On user demand
and on selected Composite Exclusion
Preparation
composite/period
Composite Performance
Recalculation