Euro

TEMENOS T24
Euro
User Guide
Information in this document is subject to change without notice.
No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.
Copyright 2005 TEMENOS Holdings NV. All rights reserved.

Euro
Table of Contents
TEMENOS T24........................................................................................................................................ 1
Euro ......................................................................................................................................................... 1
User Guide .............................................................................................................................................. 1
Overview.................................................................................................................................................. 4
Testing the Euro Module ...................................................................................................................... 4
Exchange Rates and Euro Set-up ........................................................................................................... 6
Exchange Rate calculations involving the Euro ................................................................................... 6
Defining the Euro Currency ................................................................................................................. 9
Displaying Euro equivalents .............................................................................................................. 18
Settlement of NCU Contracts ................................................................................................................ 25
Allowing settlement of NCU contracts in EUR ................................................................................... 25
Local Clearing .................................................................................................................................... 34
The Euro and Position Management ..................................................................................................... 36
Converting the system base currency to EUR ...................................................................................... 42
Configuring the system ready for the conversion .............................................................................. 42
Multi-threading of base currency conversion ..................................................................................... 46
Batch Process .................................................................................................................................... 48
Running the Local Currency Conversion ........................................................................................... 50
Re-denomination of Accounts ............................................................................................................... 52
Preparation of the Accounts .............................................................................................................. 56
Re-denomination of Accounts using the Bulk Conversion utility ....................................................... 58
Batch Process .................................................................................................................................... 59
Conversion process ........................................................................................................................... 61
Special Cases .................................................................................................................................... 62
Re-denomination of Contracts............................................................................................................... 64
Initial Configuration for Contract Conversion ..................................................................................... 64
Re-denomination of Money Market Contracts ................................................................................... 75
Re-denomination of Loans and Deposits........................................................................................... 87
Re-denomination of Mortgage Contracts ......................................................................................... 105
Re-denomination of Swap Contracts ............................................................................................... 108
Euro and Securities ............................................................................................................................. 113
Changing the Reference Currency of Portfolios – SC application ................................................... 113
Changing the Reference Currency of Portfolios – AM application .................................................. 117
Re-denomination of Securities – Both SC and AM applications ..................................................... 119
Euro and Derivatives ........................................................................................................................... 140
TEMENOS T24 User Guide Page 2 of 193

Euro
Asset Management Account Conversion......................................................................................... 145

Testing Onsite ..................................................................................................................................... 167
Realisation of In-Currency Forex Profit and Loss ............................................................................... 190
Recommended Testing for the Euro ................................................................................................... 193

Euro
Overview
On the 1st January 1999 the single European Currency, the EURO comes into existence, which by 31st
December 2002 will replace the existing national currencies of the eleven initial members. Later
phases will include other currencies. The introduction of the Euro will affect members of the banking
community by varying degrees.
This application is now upgraded to cater for further countries converting from national currency units
to euros.
The ‘Euro’ module is a set of additional functionality across all applications and utilities designed to
support the new requirements of the single currency, and to provide a smooth conversion from the
national currency.
Although this module was designed to deal with the introduction of the Single European Currency,
elements of the module may have additional uses. For example where there is a requirement to
perform a conversion of the system base currency. Any reference to Euro in this document could
equally apply to any currency irrevocably fixed to another. (If there is a requirement to change the
base currency to one which is not used as the base for usual exchange quotation rates then a slight
change to the conversion will be required.)
Testing the Euro Module

It is expected that most users will wish to test the Euro module before installation in their ‘live’
environment, and also test the operation of the module, as it will operate during the transition phase
and after.
The Euro conversion utilities provided as part of the module involve much of the system, and it is
important to prepare a test plan of exactly how these items are to be tested. For initial tests of some of
the conversion processes, it is recommended that the testing be performed in conjunction with
members of the TEMENOS Client Services department, who can provide expert assistance to
investigate any problems which may arise.
A recommended test plan covering the different areas of functionality of the Euro module is included in
this document.
Terminology
Article 235
The Council Regulation (EC), which governs Conversion and rounding rules
EMU
European Monetary Union

Euro
NCU
National Currency Unit – a general term for existing national currencies
In-Currency
A currency which is converting to EUR.
Out-Currency
A currency that is not a member of EMU
Triangulation
The process of converting one In-Currency amount to another via the euro
No Compulsion, No Prohibition
The principle whereby there is no compulsion or to use the Euro. Used for in-currency
transactions in the transition period. A principle was in the original set up of the euro but is not
expected to be followed in further conversions.
Re-denomination
Re-denomination is the process of converting an In-currency transaction to the euro
equivalent of something which is at the fixed conversion rate.
Transition Phase
The phase where both NCU and EUR can be used. ERI ‘Euro Related Information’ added to
SWIFT messages where the amount is converted from NCU to EUR.

Euro
Exchange Rates and Euro Set-up

Exchange Rate calculations involving the Euro
Although the euro can be viewed as simply another currency in certain circumstances, when ‘In-
currencies’ are involved additional rules apply regarding calculation of exchange rates. The euro
module allows the exchange rate regulations to be applied for all rate calculations in T24.
Fixed Exchange Rates / Triangulation

This means that, once fixed, each NCU should be viewed as a different expression of the Euro, rather
than as a separate currency. Since there is a fixed conversion rate between each NCU and the Euro,
it will therefore be possible to convert from any In-currency to another, or to the Euro, and always
receive the same result.
The rules for performing calculation and rounding, under Article 235 Regulation can be summarised as
follows.
• The conversion rates shall be adopted as one Euro expressed in terms of each of the national
currency units of the participating countries to six significant figures (note that the number of
decimal places will vary from one national currency to another).
• The conversion rates shall not be rounded or truncated when making conversions.
• When rounding monetary amounts to be paid or accounted for after a conversion, these must be
rounded up or down to the nearest sub-unit (or in the absence of a sub-unit to the nearest unit) or
according to national law or practice to a multiple or fraction of the sub-unit (or unit) of the national
currency unit. If the result is exactly halfway, the result shall be rounded up.
• The conversion rates shall be used for conversions in either direction between the Euro and its
national denominations.
• Inverse rates derived from the conversion rates shall not be used.
• Conversion between one national currency and another must be done via the Euro – referred to
as triangulation.
In T24 the fixed conversion rates are held in the CURRENCY file in the field FIXED.RATE, the
currency against which the rate is fixed (i.e. EUR) is held in the field FIXED.CCY, the date the fixed
rate applies from is held in the field FIXED.START.DATE. Any transaction involving an In-currency on
or after the fixed start date will follow the above rules. The details of the calculation methods are
described below.
T24 Conversion of In-Currency to In-Currency
As mentioned above conversions from one In-Currency to another must always be performed via the
Euro (once the FIXED.START.DATE has passed). This is frequently referred to as triangulation.

Euro
• An In-currency amount will be converted to the Euro amount by dividing the In-currency amount by
the FIXED.RATE to the Euro.
• The intermediary Euro value is held to six decimal places.
• The intermediary Euro amount is converted to the other In-Currency amount by multiplying by the
FIXED.RATE.
• The resulting amount is rounded and formatted to the number of decimals of the Currency.
T24 Conversion of In-Currency to euro
Conversions from an In-currency to the euro always use the fixed conversion rate (once the
FIXED.START.DATE has passed).
• An In-currency amount will be converted to the Euro amount by dividing the In-currency amount by
the FIXED.RATE to the euro.
• The resulting euro amount is rounded and formatted to the number of decimals of the Currency.
T24 Conversion of Euro to In-Currency
Conversions from the euro to an In-currency always use the fixed conversion rate (once the
FIXED.START.DATE has passed).
• A Euro amount will be converted to an In-Currency amount by multiplying by the FIXED.RATE.

• The resulting In-Currency amount is rounded and formatted to the number of decimals of the
Currency.
T24 Conversion of In-Currency to Out-Currency
Conversions of In-Currency amounts to Out-Currency amounts are performed via the Euro.
• The In-currency amount is converted to a Euro amount by dividing by the FIXED.RATE.

• The result is held to six decimal places.
• The Euro amount is converted to the Out Currency using the standard rate conversion.
• The resulting Out-Currency amount is rounded and formatted to the number of decimals of the
Currency.
T24 Conversion of Out-Currency to In-Currency
Conversions of Out-Currency amounts to In-Currency amounts are performed via the Euro.
• The Out-currency amount is converted to a Euro amount using the standard rate calculations.

Euro
• The result is held to six decimal places.

• The Euro amount is converted to the In-Currency by multiplying by the FIXED.RATE.
• The resulting In-Currency amount is rounded and formatted to the number of decimals of the
Currency.
Use of different rates between In-Currencies and Euro
Applications, which allow entry of exchange rates, will allow entry of rates that differ from the fixed rate
or the derived cross-rate (using the fixed rates). In this case an override will generated by the system,
if the rate entered differs from the fixed cross rate by more than 0.001 %.
Quotation of rates involving the Euro

It is important to understand the rules that apply when quoting exchange rates involving the Euro for
the In-currencies, and the likely market convention to be applied when quoting out-currencies against
the Euro.
T24 CURRENCY table
The T24 CURRENCY table will continue to express exchange rates against the system local currency.
If the local currency is ‘In’ there may no longer be a market rate quoted for the local currency against
out currencies after the Euro starts, a Euro rate will be quoted instead. In order to update the
CURRENCY table correctly in this situation the rates will need to be derived from the quoted Euro rate.
In-Currencies
All In-currencies will be quoted as the value of ‘1’ Euro to ‘n’ NCU. This might result in an exchange
rate of less than 1.
Out-Currencies
Although there is no definitive ruling, it is expected that market practice will also follow the 1 Euro to ‘n’
NCU quotation method. In the UK this is expected to be the practice, which will not follow the standard
UK quotation method (1GBP: n Fcy).
Quotation Code
When defining the EUR CURRENCY it is important that the quotation code is correctly defined in
order to follow the recommended practice.
Where EUR is not the local currency the quotation code should be ‘0’.
Where EUR is the local currency other currencies should be quoted with a code of null.

Euro
Base Currency Rank
The usual rule for defaulting the base currency of a deal is to use the currency that will yield a rate
greater than 1. From the rules for quoting Euro rates this may not be the case for certain currencies
against the Euro (e.g. GBP), where the current rule would result in an inverse rate being defaulted.
A further parameter has been introduced, BASE.CCY.RANK to resolve this potential problem. The
correct setting of this value can be used to force a CURRENCY to be the base currency instead of the
usual rule where the currency which will yield a rate greater than 1 will be used.
A value in the range 1 to 99 can be specified. Whenever the system attempts to default the base
currency, this value is tested. If a value is present that currency will be the default base currency.
Should both currencies have a value, the currency with the lowest value will be the default base.
Where the Euro is not the local currency it is important to set this value for the EUR CURRENCY to
ensure that Euro is taken as the default. It is recommended that a value greater than 1 (e.g. 5) is used
to allow for additional currencies, which should be the base when dealing with the Euro.
If EUR is the local currency, or the system has been converted to Euro, you may need to set the
BASE.CCY.RANK where there are existing exchange rates quoted less than 1 involving the local
currency (for example IEP / GBP). In these cases the rank should additionally be set for the old local
currency.
The most likely requirement is to enforce the sequence of EUR, GBP, USD. This could be done by
setting the values
Currency Base Rank
EUR 5
GBP 10
USD 15
Refer to the HELPTEXT in CURRENCY and CURRENCY.PARAM for further details and examples.
Defining the Euro Currency

The Euro is a new currency that must be defined just as any other in T24. Note that although the
exchange rate between the existing ECU (code XEU) and the Euro is defined as 1, the XEU must be
treated as a separate currency.
The following steps should be followed to define the Euro as a new CURRENCY (code EUR).

Euro
Country
Europe must be defined as a COUNTRY before the CURRENCY can be specified. There is probably
already a code XE, used for the XEU, however the Euro will need its own COUNTRY code, EU, to be
defined.
You may also wish to define a GEOGRAPHICAL.BLOCK to hold all In-countries.
Country record for EU
CURRENCY.PARAM
The common characteristics of the Euro should be defined in the CURRENCY.PARAM application.
The BASE.CCY.RANK should be set as described above.
A standard interest day basis has been agreed for the EURO, B 366/360.

Euro
CURRENCY.PARAM record for EUR
Currency
The CURRENCY record can now be defined for EUR. Ensure that the correct QUOTATION.CODE is
used. The FIXED.CCY, FIXED.DATE and FIXED.RATE fields should not be used for the EUR
currency.
Restricting use before the start date
[The Euro will be defined as a CURRENCY before it is due to come into existence, however financial
movements could be generated with Value date before this date (i.e. 01/01/99). The field
AVAILABLE.DATE should be set to the start date of the currency. The system will generate an
override message should any entry be posted across an account with a value date prior to the
AVAILABLE.DATE.]
The euro is an existing currency and does not need an AVAILABLE.DATE.
Note that the value of BASE.CCY.RANK is defaulted to the value in CURRENCY.PARAM and cannot
be amended directly. Should a change be required the underlying CURRENCY.PARAM record should
be amended. The next amendment to the CURRENCY record will update this field.

Euro
CURRENCY record for EUR
Holiday
The HOLIDAY table EU should be defined. Settlement is possible in Euro on all but two working days
– Christmas and New Year.

Euro
HOLIDAY table for EU
PERIODIC.INTEREST
It is recommended that the Periodic Interest table ‘01’ should be defined with the forward Euro interest
rates. The foreign exchange FORWARD.RATES can be built automatically if required by using the
field BUILD.FWD.RATE.
You should also check the system to see which other rate tables are used for other currencies, and
decide which require Euro interest rates.

Euro
PERIODIC.INTEREST for EUR
FORWARD.RATES
Local Currency is Out
Where foreign exchange processing is used and the local currency is not an In Currency,
FORWARD.RATES should be defined in the record EUR1. This table specifies the premium or
discount expected for the exchange rate of the Euro against the local currency.
If required these rates can be built automatically from the PERIODIC.INTEREST records by setting
BUILD.FWD.RATE to Y.
Local Currency is In
If the Local currency is an In-currency, there should be no premium or discount specified for the Euro
since after the start of the Euro the exchange rate is fixed irrevocably.

Euro
FORWARD.RATES for EUR
Basic Interest
Check your system for existing base rates for the local currency and each of the In-currencies: a Euro
rate will be required for each base rate used by existing contracts and accounts which may be re-
denominated in Euro.
Account Conditions
Account Conditions should be defined for each condition group that EUR accounts are expected to be
opened in. Account group conditions are defined in the applications GROUP.DEBIT.INT and
GROUP.CREDIT.INT.
Fixing In-Currencies to the Euro

The fixed rates and dates for IN currencies should be applied when known.
Use of Expected Fixed Rates

The expected rates will be published and these can be specified before the fixing date. If rates are
specified before the fixing date, the fixed rate calculations described in the section “Exchange Rate
Calculations” will not be used in transaction calculations until the fixing date is reached.
On the fixing date you must ensure that the rates of fixed IN currencies are set to be equal to the fixed
rate for the currency with zero spread.

Euro
Adding Rates to an In-Currency

The fixed rate should be added to the CURRENCY record for each In-Currency. Rates are fixed by
specifying the value of 1 Euro in the field FIXED.RATE. The FIXED.CCY should be defined as EUR;
the date at which the fixed rate applies should be defined in the FIXED START.DATE.
Setting the Expiry Date for a Currency

At the end of the transition phase the NCU will cease to exist. In order to prevent transactions being
raised after this date the field BLOCKED.DATE should be specified in the CURRENCY record. Any
transaction raised with a value date after this date will generate an override.
[Note that the XEU should be blocked from 01/01/99 as it is officially replaced by EUR on this date.]
'IN' currency
A summary of the currencies linked to a Fixed Currency can be obtained by viewing the
EU.FIXED.CURRENCY table.

Euro
Summary of 'IN' currencies
Forward Exchange Rates
Once the Euro begins, the conversion rate is fixed. There will therefore be no forward premium or
discount for any of the In-currencies against the Euro. If the local currency of the system is either an
In-Currency or the Euro, the FORWARD.RATES table should be modified to set the
FORWARD.PREMIUM to be zero from the Euro start date.
If FORWARD.RATES are built automatically from the PERIODIC.INTEREST table, this feature should
be disabled for each of the In-currencies in the above situation.
If the local currency is out, FORWARD.RATES will be required for EUR in the same way as any other
currency. For the In-currencies the rates will need to be derived from the Euro rates.
Interest Rates
When EMU starts the base interest rates will be the same for each In-currency, since each In-currency
is simply a different expression of the Euro. Currently interest rates will be different for each currency,
however these should converge towards a common rate towards the end of 1998. The interest rate
tables (PERIODIC.INTEREST, BASIC.INTEREST) are used to record the rates.

Euro
Interest rates used for accounts (GROUP.DEBIT.INT and GROUP.CREDIT.INT) will need to be
reviewed for each product.
Displaying Euro equivalents

T24 will allow the Euro equivalent to be displayed for In-Currency amounts throughout the system
including:
• Display of all amounts in all applications. An additional ENQUIRY CONVERSION option to display
the amount in Enquiries
• An additional CONVERSION option to display the amount in DE.FORMAT.PRINT and
DE.FORMAT.TEMPLATE applications.
Euro equivalents will be displayed whenever a FIXED.RATE is specified for a CURRENCY regardless
of whether the FIXED.START.DATE has been reached. This will allow the Euro equivalent to be
shown on customer output for information purposes prior to the start date.
Display of Euro equivalent in applications
Once the FIXED.RATE is specified on a CURRENCY record the system will automatically display the
Euro equivalent as an enrichment wherever possible.
The Euro equivalent will not be displayed if:
• There is already enrichment for the field.

• A version is used and the number of enrichment characters (ENRICHM.CHAR in the VERSION
record) for the field is not set.
If existing versions do not show the enrichment against an amount field, the version should be
amended accordingly.

Euro
Adding a EURO enrichment to a version
Foreign currency amount fields where the related currency is an In-currency will display the equivalent,
similarly local currency fields where the local currency is ‘In’.
Displayed Euro equivalent
Displaying Euro Equivalents in Enquiries

The T24 ENQUIRY application has been enhanced to provide three new conversion types to allow
Euro equivalents and related information to be displayed for any amount. These conversions are:
Fixed (Euro) Equivalent

Euro
Input Amount fields

Format UTIL FIXEQU, ccy name
Where Ccy name is the name of the enquiry field containing the value of the currency
Result If Ccy name is an In-currency the Euro Equivalent calculated at FIXED.RATE
If Ccy name is an out currency a null value is returned
In order to display the Euro equivalent of an amount in an enquiry, the currency of the amount must be
identified. In the enquiry a field should already hold the value of the currency, if not a field should be
added.
A new field should be added to display the possible Euro equivalent. The OPERATION should either a
contain amount field or a field containing the amount value. The above CONVERSION should be
specified with the field containing the currency value.
If you wish to apply the standard amount format, use the TYPE field with a value of CCY as usual, the
currency to format to should be field containing the fixed currency (see below).
Adding Euro equivalent to an enquiry
Fixed Currency
Input Not required
Format UTIL FIXCCY, ccy name
Result If Ccy name is an In-currency the fixed currency i.e. EUR
If Ccy name is an Out-currency a null value is returned

Euro
In order to extract the fixed currency, the value of the currency must be identified. In the enquiry a field
should already hold the value of the currency, if not a field should be added.
A new field will be required to hold the value of the fixed currency. The content of the related
OPERATION field is not important. The above CONVERSION should be specified with the field
containing the currency value.
Currency conversion on an enquiry
Fixed Conversion Rate

Input Not required
Format UTIL FIXRTE, ccy name
Result If Ccy name is an In-currency the fixed conversion to the currency
If Ccy name is an Out-currency a null value is returned
In order to extract the fixed conversion rate the value of the currency must be identified. In the enquiry
a field should already hold the value of the currency, if not a field should be added.
A new field will be required to hold the value of the fixed conversion rate. The content of the related
OPERATION field is not important. The above CONVERSION should be specified with the field

Euro
Displayed Euro equivalent on an enquiry
Displaying Euro in Printed Delivery Output

The T24 applications DE.FORMAT.PRINT and DE.FORMAT.TEMPLATE have been enhanced to
provide three new conversions to display Euro equivalents, and Euro related information. These can
be added to existing customer output as required.
The specification and use of the conversions is identical in both applications.
Fixed (Euro) Equivalent

Input Amount field
Format FIXEQU*ccy name
Where Ccy name is the name of the DE.MESSAGE field containing the value of the
currency
Result If Ccy name is an In-currency the Euro Equivalent calculated at FIXED.RATE
If Ccy name is an out-currency a null value is returned
In order to display the Euro equivalent of an amount in a formatted message, the currency of the
amount must be identified. In the DE.MESSAGE record a field should already hold the value of the
currency; if not a field should be added.

Euro
A new item should be added to display the possible Euro equivalent. The FIELD/”TEXT” should
contain an amount field (or possibly a total). The above CONVERSION should be specified with the field
Addition of currency conversion to printed delivery
Fixed Currency
Input Not required
Format FIXCCY*ccy name
currency
Result If Ccy name is an In-currency the fixed currency i.e. EUR
If Ccy name is an out-currency a null value is returned
In order to extract the fixed currency the value of the currency must be identified. In the DE.MESSAGE
record a field should already hold the value of the currency; if not a field should be added.
A new field will be required to hold the value of the fixed currency. The content of the related
FIELD/”TEXT” field is not important. The above CONVERSION should be specified with the field
Fixed Conversion Rate

Input Not required
Format FIXRTE*ccy name
currency

Euro
Result If Ccy name is an In-currency the fixed conversion to the currency.

If Ccy name is an out-currency a null value is returned.
In order to extract the fixed conversion rate the value of the currency must be identified. In the
DE.MESSAGE record a field should already hold the value of the currency; if not a field should be
added.
A new field will be required to hold the value of the fixed conversion rate. The content of the related
FIELD.NAME field is not important. The above CONVERSION should be specified with the field

Euro
Settlement of NCU Contracts

Allowing settlement of NCU contracts in EUR
During the transition period the principle of ‘No compulsion, No prohibition’ applies, which means that
a customer (or the bank) may wish to accept NCU payment in EUR or to remain in NCU. The bank
must be able to handle the conversion between NCU and EUR as required.
Most applications in T24 insist that settlement accounts are in the same currency as the contract. As
settlement of NCU amounts may now be made in EUR or NCU, this restriction would require a manual
process to settle via a suspense account on the underlying contract, and create a FUNDS.TRANSFER
(or similar) from the NCU suspense to the correct EUR account.
Whilst this practice may be acceptable for small numbers of Euro settlements, it would obviously be a
large operational overhead and also prone to operator error in any site with a reasonable volume of
transactions.
The Euro module allows automatic conversion of NCU amounts to EUR for any nominated ACCOUNT.
This can be processed in one of two ways:
• Auto Payment Account – An existing NCU account is linked to a EUR account. Many NCU
accounts can be linked to the same EUR account, all transactions across the linked NCU
accounts are converted to EUR and posted to the EUR account. Any related payments are
converted to EUR.
• General Suspense Account – A suspense account of specific category is used for settlement
from the contract. A customer who has only a EUR account nominates that any deal in a
specific NCU should be settled to the EUR account. The system will check any posting made
across the general suspense account to see if the customer has a nominated EUR account, if
so the entry will be converted and posted to the EUR account.
Using the Auto Pay Account

This section is concerned with the ability to settle NCU through EUR for individual accounts. The
section ‘Re-denomination of Accounts’ contains details of the automated process of converting an
account from NCU to EUR.
In Order to illustrate the use of the auto pay account the scenario of the bank deciding to settle NCU
through the Euro will be used an example.
Settlement in IEP is to be made through a EUR Nostro maintained with the same bank. The EUR
Nostro account has been opened in the usual manner:

Euro
EUR Nostro Account
The IEP ACCOUNT record needs to be linked to the Euro Nostro using the AUTO.PAY.ACCT:
Specifying the auto-pay account
Effect of the Auto Pay Account on Accounting Entries
Once the AUTO.PAY.ACCOUNT is defined as shown above:

Euro
• Accounting Entries Raised to the IEP Nostro (with the exception of certain entries through the
DATA.CAPTURE application – see later this section) will be converted to EUR and posted to
the EUR Nostro.
• Forward Accounting Entries to the IEP Nostro will be converted to EUR and posted to the EUR
Nostro. Any Forward entries, which exist prior to establishing the link with the auto pay account,
will be converted to EUR entries in the Close of Business processing. For this reason it is
recommended that the Nostro be linked at the end of the working day.
Converting Payment Messages using the Auto Pay Acct
Any payment message (e.g. MT100 / 202) for the IEP Nostro will also be converted to EUR, the
original IEP amount will appear in the message as ERI information if the payment is sent via SWIFT.
If there is a requirement that the payments must still be sent in the original currency and not converted,
the field ORIG.CCY.PAYMENT of the account should be set to YES. In this case the payment will
remain in NCU and no ERI information will be displayed.
Further Transactions in NCU
The NCU account should continue to be used for deals in NCU, if defined as a default Nostro the
account will continue to default where appropriate, any further postings and payments to the account
will be converted automatically as described above.
Adjusting the Balance of the NCU account
As mentioned once the link is established, all further postings are directed to the EUR
AUTO.PAY.ACCT. If an adjustment needs to be posted to the NCU account this must be posted
through the DATA.CAPTURE application, which can be used to force the entry to the NCU account.
When entry is forced to the NCU account an override is required.

Euro
Adjustments through DATA.CAPTURE
Configuration of DATA CAPTURE to allow NCU posting
By default the DATA.CAPTURE application will post entries to the specified account, so that when an
NCU account that is linked to an AUTO.PAY.ACCT is used, the posting is made to the NCU account
and is not converted.
The DATA.CAPTURE application has many uses and this rule may not always be appropriate, there
may be a requirement to post to the AUTO.PAY.ACCT in the same way as the other applications. For
example you may use the application to post transactions raised in another system and any postings
should be converted to a linked Euro account.
The automatic posting to the auto pay account can be controlled by setting the fields
DC.AUT.PAY.TXNS and SUBS.FOR.TXN.LIST in the EU.PARAMETER application, which is defined
at company level. Individual TRANSACTION codes, which should, or should not be posted to a linked
auto pay account should be specified in the DC.AUT.PAY.TXNS field. The field
SUBS.FOR.TXN.LIST denotes whether the TRANSACTION codes specified should or should not
convert.
Using the screenshot example below, any transactions raised using only codes 1 and 51 will be
posted to the AUTO.PAY.ACCT if defined.

Euro
EU.PARAMETER input screen
The following setting will result in all transactions except for 1 and 51 being posted to the
AUTO.PAY.ACCT if defined:
Setting up DATA.CAPTURE auto pay for all transactions except 1 & 51

Euro
Using the General Suspense Account

The Auto Payment Account is the best method to use for linking Nostros to EUR and for customers
with existing NCU accounts. However if a new Customer is opened and wishes to deal in NCU, but
settle through a EUR account, the General suspense account should be used.
This method does not require the customer to have an NCU account. Instead the EUR account record
defines which NCU currencies can post to the account. NCU contracts should use a general suspense
account for settlement.
Defining General Suspense Category
A new CATEGORY in the range 10-000 to 19-999 should be allocated for the general suspense
account.
Opening General Suspense Accounts
An internal account should be opened for each In-currency. The general suspense account will have
an ID in the format:
NCU nnnnn 0001 where nnnnn is the category defined in the previous step.
General Euro suspense account

Euro
Addition of General Suspense Category to Account Parameter
The general suspense category must be added to the ACCOUNT.PARAMETER application (ID of
SYSTEM) before it can be used.
Note that once the ACCOUNT.PARAMETER record is authorised, users must re-sign on to T24 in
order to use the updated setting.
Auto pay category
Linking the General Suspense Account to a Euro Account
The customer Euro account needs to be linked to the general suspense account to be used for
settlement of contracts. In order to do this, the NCU currencies that can be settled by the account,
should be specified in the field AUTO.REC.CCY.
AUTO.REC.CCY defined on an ACCOUNT

Euro
The application CUST.ACC.CCY.REC shows for a particular customer which accounts should receive
NCU payments.
Using the General Suspense Account
The general suspense account will default as the settlement account if the customer has specified that
Euro should be used to settle the particular currency of the deal. Entering the general suspense
account for that particular NCU can also specify the account.
Care should be taken if the suspense is specified for a customer who does not have a EUR account,
which can receive NCU. The movement will not be posted to the EUR account and will remain in
suspense in this situation.
Effect of the General Suspense Account on Accounting Entries
Once the AUTO.REC.CCY is defined as shown above:
• Accounting Entries Raised to the IEP and DEM suspense accounts for the customer will be
converted to EUR and posted to the EUR current account.
• Forward Accounting Entries to the IEP and DEM suspense accounts for the customer will be
converted to EUR and posted to the EUR current account. Any Forward entries, which exist
prior to establishing the link, will be converted to EUR entries in the Close of Business
processing.
Audit Information on Converted Entries

The system maintains a full audit trail for each entry, which is converted, to a EUR account using
either the AUTO.PAY.ACCT or general suspense account. The system records the original amount in
NCU, the original currency and the original account number and original exchange rate between the
local currency and NCU. This information is stored in the STMT.ENTRY record.

Euro
Euro information on a STMT.ENTRY
Euro Related Information in SWIFT messages

ERI is an optional information item, which can be included in narrative fields on SWIFT messages
when the currency and amount of the message is in EUR, but the underlying transaction was in NCU.
The NCU amount and currency is added to the narrative fields (for example field 72) in the format:
/xxxx/CCYnnnnnnn,nn
Where xxxx is a keyword, which can be OCMT (original amount) or CHGS (charge details):
CCY is the NCU

nnnn is the original amount in NCU
T24 will add ERI to the following messages in the following narrative fields whenever the underlying
transaction settles through an NCU account in EUR. All ERI values are added with the keyword OCMT.
Details of charges can be entered in the relevant narrative/Bank to Bank info fields in the underlying
transaction.
Messages containing ERI

ERI has only been added to the following SWIFT messages based on the SWIFT recommendations.

Euro
DE.FORMAT.SWIFT.ID Description ERI field

103.1.1 Customer Transfer 72
202.1.1 Financial Institution Transfer 72
400.1.1 Advice of Payment 72
521.1.1 Receive against Payment 72
523.1.1 Deliver against Payment 72
580.1.1 Instruction to Clearing System 72
752.1.1 Authorisation to pay/accept/negotiate 72
754.1.1 Advice of payment/acceptance/negotiation 72
756.1.1 Advice of reimbursement of payment 72
900.1.1 Debit advice 72
910.1.1 Credit Advice 72
940.1.1 Customer Statement 86
ERI fields on SWIFT messages
Local Clearing
Many In-country local clearing systems will allow payments to be made in Euro as well as in the local
currency. During the transition period payments may well be sent in both EUR and NCU.
Allowing Payment in EUR

Prior to the advent of the Euro, outgoing local clearing payments could only be made through the T24
FUNDS.TRANSFER system in the local currency. In order to allow transactions in EUR and NCU, the
FT.BC.PARAMETER parameter for the local clearing system should be modified.
In order to allow a non-local currency account to be debited when sending an outgoing payment, the
field ALLOW.FCY.DEBIT should be set to YES.
The field PAYMENT.CCY is used to control in which currencies payment can be sent the clearing
institution. If there is no value specified the system will assume that only the local currency is valid.
Payment will only be allowed in the currencies defined in this field if defined.

Euro
FT.BC.PARAMETER
Additional clearing accounts will be required for each additional currency specified in the
PAYMENT.CCY field. Each additional account should be added to the FT.LOCAL.CLEARING record
SYSTEM, in the fields BRNCH.NOSTRO.BI, BRNCH.NOSTRO.BC, BRNCH.NOSTRO.BD, before they
can be used in a local clearing FUNDS.TRANSFER transaction.
Layout of Local Clearing Files

If the local clearing system allows payment in EUR in addition to NCU, the record layout of the
clearing files to be sent and received is likely to be different. The changes required will depend on
each local system. Your local TEMENOS client services area will be able to give further information
regarding the required changes.

Euro
The Euro and Position Management

The Position Management application has additional functionality built in for use with the Euro.
Defining a Calendar for the Euro

The Euro has only two holidays (Christmas and New Year), so settlement will be possible even on
non-working days for the local country. You may wish to view some of the positions held in the
position management system based on the possible settlement dates, rather than based on the local
holiday definitions. The PM.CALENDAR application will allow dates to be calculated based upon
specific countries and/or regions.
The field BASE.COUNTRY allows the specific COUNTRY or REGION to be defined. Combinations may
be specified by expanding the multi-value, if a combination is used a common working day and will be
obtained when calculating the calendar dates. Existing PM.CALENDAR definitions may be modified,
or you may wish to create new calendars.
PM.CALENDAR
Grouping of In-Currencies in PM enquiries

When viewing positions using the Position Management enquiries, each currency is reported
separately. During the transition period the Euro position can be considered as the sum of the existing
EUR positions plus the In-Currency positions converted at the fixed rate. This requirement may vary
according to the type of enquiry being performed.

Euro
There is therefore an option to allow In-Currency positions to be grouped under the EUR position. The
option to group In-currencies is provided in the application PM.ENQ.PARAM, in the field
CONVERT.FIXED.CCY. When this field is set to Y, any in-currency amount is converted at the fixed
rate and displayed as the EUR equivalent when the EUR currency is selected.
This option can be used prior to the start date of the fixed rate, the FIXED.RATE entered in the
relevant CURRENCY record will be used for the conversion.
Note that when this option is used you will still be able to enquire on a specific In-Currency position by
specifying the currency in the selection.
The following enquiries support this option:
PM.GAP, PM.CAS, PM.NPV, PM.FXPOS, PM.WIPAL, PM.AVG.LIFE, PM.AVG.RATES, PM.DURATION,

PM.EDPAL.
PM.ENQ.PARAM

Euro
PM.GAP.1
DPC.TXNS.1
PM.GAP.2

Euro
DPC.TXNS.2
DPC.TXNS.3
Grouping of In-Currencies in Nostro Position Enquiry

This enquiry is used to view the total position for a currency. It may be required to view In-Currency
Nostros under the EUR position. In order to allow this, an option has been provided to allow In-
Currency Nostro Positions to be viewed under the Euro position instead of under the individual
currencies.

Euro
A new selection item, MERGE.NCU in the NOSTRO.POSITION enquiry should be set to Y to show In-
currency items as EUR converted at the fixed rate. If you specify this option you will not be able to
view the individual In-Currency positions. If not specified the enquiry will show each currency
separately.
This facility is available prior to the fixed start date, the projected FIXED.RATE held on the relevant
CURRENCY record will always be used.
When merged positions are displayed the original currency is shown in the second column.
Selecting merged positions for NOSTRO.POSITION

Euro
NOSTRO.POSITION

Euro
Converting the system base currency to EUR

Anybody using T24, who has a local currency that is one of the In-currencies, will need to convert the
base currency to EUR at some point during the transition phase.
The Euro module provides a utility that will allow this conversion to take place.
Timing of the conversion

The conversion can be run as soon as the fixed rates apply, and can actually be run in the Close of
Business process immediately preceding the start date.
The conversion process itself runs in the Close of Business after all the standard Close of Business
processing and reports have been processed, just before the date is cycled to the next working day.
The Close of Business process will halt just prior to the start of the actual conversion, which is at the
point the normal Close of Business processing is complete. At this point a backup should be taken, as
this will be the last point that the system will be in NCU. If the conversion is run at a financial period
end – which is likely to be the case, the backup taken at this point can be restored in another area to
allow additional reports and enquiries to take place on the old base currency.
Preparation of the Database

The local currency conversion will convert many files - poorly sized files can adversely affect the
performance of the conversion. In preparation for the conversion, the ACCOUNT.FILE.STATS process
should be run and the results analysed. Any poorly sized files should be resized. See the SYSTEM
ADMINISTRATION GUIDE for further information.
Configuring the system ready for the conversion

Conversion Difference Suspense Category
The conversion process is likely to result in rounding errors, which will be corrected by posting any
difference to a difference suspense account. In order to define the difference account, an internal
account CATEGORY in the range 10000 – 19999 should be created.
Contract Conversion Suspense Account
When contracts are converted, the early maturity of the NCU contract and drawdown of the EUR
contract are made through suspense accounts. A new CATEGORY should be created for this
suspense in the range 10000 – 19999.

Euro
Opening Difference and Contract Suspense Account
A different suspense account should be opened in EUR for the CATEGORY created in the above
steps. You must open an account in each company, which shares the CURRENCY file.
Difference adjustment transaction code
A TRANSACTION code should be created for any movement created to adjust conversion differences.
Transaction code for Euro conversion adjustments
Define EU.PARAMETER
The EU.PARAMETER file contains details for each company that is to be converted. You must convert
each COMPANY sharing a CURRENCY file at the same time; one record is required for each
company.
The file is keyed by the company code - you must be in the correct company to Input the record.
In order to run the conversion the following information should be provided:
CONVERTED.LCY

Euro
The currency to convert to, i.e. EUR
CONVERSION.DATE
The date the conversion is to be run on. This cannot be before the FIXED.START.DATE for
the CONVERTED.LCY. The date can be entered prior to the start date of the currency providing
it is the working day before the start date, so if you wish to convert on 1st January 1999, the
CONVERSION.DATE would be 01/01/99, the system date would be 31/12/98.
CONV.LCY.SUSP.CAT
The category created for the difference entry should be added in this field.
CONV.CONT.SUSP.CAT
The category opened for contract suspense accounts should be defined in this field.
CONV.LCY.TXN.CODE
The transaction code created in the previous steps should be defined in this field.
LCCY.CONV.REC
The record id to the EU.CONVERSION.PROCESS file should be specified here. The released
records EURO.LCCY.1 and EURO.LCCY.2 should be defined here. Do not add additional
records without prior consultation with TEMENOS.

Euro
Setting up the EU.PARAMETER for base currency conversion
The linked EU.CONVERSION.PROCESS records list the specific EU.CONVERSION.PARAM

items that will be run and the correct order of processing.

Euro
EU.CONVERSION.PROCESS record
Multi-threading of base currency conversion

It is possible to run base currency conversion with multi-threading functionality, which should make
greater use of processor availability and improve performance and conversion times during end-of-day.
Unlike most multi-threading, where there is no change necessary from the user to enable multi-
threading to take place, there are some minor changes that must be done to take advantage of the
functionality.
There is a routine called EU.BASE.RUN.CONVERT, which should be specified as the JOB.NAME in
the BATCH EU.RUN.BASE.CONVERT. This is the job that is run when the base currency is
converted from the in-currency to Euro.

Euro
EU.RUN.BASE.CONVERT
Setting parameters and processes for multi-threading
Once the batch base currency conversion record is set to run in Multi-thread, it is necessary to specify
which records are to be converted, and by which conversion thread. There are three stages to this:
firstly, the records which are to be converted need to be identified on the EU.CONVERSION.PARAM
table and where necessary these may need to be amended to suit local requirements. These are then
divided into sets on the EU.CONVERSION.PROCESS file, and these sets must then be applied to the
overall EU.PARAMETER record.
The records which need to be converted for the base currency conversion have been provided by
TEMENOS through released EU.CONVERSION.PARAM records. Each record specifies the field
names, which need to be converted for that application. In many cases it may be that no further
intervention by the user is required. However, it may be that some files have been changed to suit
local requirements. For example, if particularly large files have been split up into distributed files (for
example, perhaps the CATEG.ENTRY file) then in the VOC.FILE.NAME field of the
EU.CONVERSION.PARAM, the VOC name for that each file should be specified.
Once all EU.CONVERSION.PARAM files have been set up, they need to be put into
EU.CONVERSION.PROCESS groups. There are already two records that have been released,
EURO.LCCY.1 and EURO.LCCY.2, which contain all the records that need to be converted for the EU
base conversion process. However, to enable multithreading, new EU.CONVERSION.PROCESS

Euro
records should be set up, to split out the number of these records evenly across each process. These
records should then be included in EU.PARAMETER.
Note: it is important that there are at least as many EU.CONVERSION.PROCESS records listed in
EU.PARAMETER as there are batch sessions to be run during the Close of Business (as specified
in the BATCH.SESSIONS field on the SPF SYSTEM record). If there are fewer records in the
LCCY.CONV.REC field than the number of batch sessions then the system will automatically assume
that it must run in single-thread mode.
Batch Process
Run Dates
The run date should be set for the ad hoc jobs following BATCH records:
EU.BASE.VERIFY
EU.BATCH.INTERRUPT
EU.PRE.BASE.CONVERT
EU.RUN.BASE.CONVERT
EU.POST.BASE.CONVERT
EU.BASE.CONV.CRB.RECALC
EU.BASE.CONV.REPORTING
EU.BASE.CONV.REPORTS2
In a multi company environment these jobs run for each Currency level company - the dates should be
set only for those companies to be converted.
The EU.BASE.VERIFY job will set the run dates for the remaining EU batches.
Reports
The BATCH jobs EU.BASE.CONV.REPORTING and EU.BASE.CONV.REPORTS2 should be
configured to reproduce any reports required after the conversion of the system.
EU.BASE.CONV.REPORTING
Runs after the conversion process. Recommended reports to include are:
EB.PRINT
Reproduce the transaction journal in EUR

Euro
EOD.STAT.MISMATCH
Produce the mismatch report for the GL (a record should be defined in RE.STAT.MISMATCH
whose key is held in the DATA field).
RE.DEAL.DETAIL.REPORT
Detailed CRB report for the G/L – The report name should be specified in the DATA field.
EU.BASE.CONV.REPORTS2
Runs after the CRB reports have been recalculated. Recommended reports to be produced
are:
RE.DEAL.DETAIL.REPORT
Detailed CRB report for the G/L – The report name should be specified in the DATA field.
FX.POSITION.REPORT
Reproduce the currency positions with a EUR local currency.
Enquiries
There are two enquiries that should be checked after the conversion process has been run:
EU.CONV.SUM shows the before and after totals of the asset and liability CRB base in foreign and
local currency, to confirm that the system remains in balance after the local currency conversion.

Euro
Conversion summary
EU.ENTRY.REVAL shows the posted adjustment transactions raised for transactions that have taken
place in EUR on the day of Local Currency Conversion. Entries to this file are only raised if there is a
difference between the deal rate and the fixed rate.
Revaluation of FX deals
Running the Local Currency Conversion

Once the items in the previous steps have been configured, the batch can be started which will
convert the local currency. The Close of Business will run normally until the EU.BATCH.INTERRUPT
is reached.
Slight Revaluation differences

Euro
Where the quotation method of the rate for a (OUT) currency against euro differs from the quotation
method against the NCU then a small difference of revaluation can occur. This is because the
arithmetic mean of buy and sell rates is not exactly equivalent to the arithmetic mean of their inverses.
The difference in revaluation between the two mid rates depends on the percentage spread. It is of the
order of the square of the fractional spread.
Percentage spread Percentage difference in mid rate
5% 0.225%
.5% 0.0025%
0.05% 0.000025%
The difference is in the revalued local currency equivalents and thus is posted in Profit and Loss. This
changes when the rates change. It makes no difference to the P/L in the end.
If you want the revaluation rate to be exactly equivalent then you should set the REVAL.RATE in the
CURRENCY record(s) before the conversion EOD. Remember to clear it the following day.
Batch Halt
When the batch halts, a backup of the system should be taken.
Continue with the Batch
The batch can be restarted by taking the AUTO BATCH option. The batch will then continue as normal.

Euro
Re-denomination of Accounts
Anybody using T24, who has accounts in one of the In-currencies, will need to convert the account’s
currency to EUR at some point during the transition phase. The Euro module provides a utility that will
allow this conversion to take place.
Timing of the conversion

The conversion can be run as soon as the fixed rates apply. The conversion process itself can be run
either:
During the Batch where the BATCH.STAGE is “SXXX”” (system wide), after all the standard Close of
Business processing, just before the reports are to processed.
During the batch where the BATCH.STAGE is “DXXX”, Start of Day Processing.
BATCH.STAGE is system wide

When accounts need to be redenominated to another currency the actual processing
takes place in the System wide section of the COB.
Thus in the balance sheet the amounts are shown under the new currency.
The Conversion of the contracts takes place online, but requires the Accounts to have
been already converted.
Under this set up the accounts have to be converted on a different day to the contracts.
BATCH.STAGE is START.OF.DAY
This will allow for the contracts to be converted during the online that day and thus
both the accounts and contracts can be shown in the balance sheet under the new
currency.
The decision is entirely with the bank at which stage of the processing during the batch that they
require the accounts to be converted.
NB Once the conversion process has begun and an account has been converted, it will not be
possible to switch between the 2 options.
SETUP if system wide option is required
The field ACCT.CONV.TIME in the EU.PARAMETER can be either NULL or EOD.

Euro
EU.PARAMETER field ACCT.CON.TIME set to EOD

The BATCH record XXX/EU.ACCT.CONVERSION should be changed from Adhoc to Daily

Euro
BATCH XXX/EU.ACCT.CONVERSION
And ensure that the BATCH XXX/SOD.EU.ACCT.CONVERSION is set to Adhoc
SETUP if Start of Day is required
The field ACCT.CONV.TIME in the EU.PARAMETER should be SOD.

Euro
EU.PARAMETER field ACCT.CONV.TIME set to SOD

The BATCH record XXX/SOD.EU.ACCT.CONVERSION should be changed from Adhoc to Daily

Euro
BATCH XXX/SOD.EU.ACCT.CONVERSION
Ensure that the BATCH XXX/EU.ACCT.CONVERSION is set to Adhoc
Preparation of the Database

The account currency conversion will convert many files - the performance of the conversion can be
adversely affected by poorly sized files. In preparation for the conversion, the
ACCOUNT.FILE.STATS process should be run and the results analysed. Any poorly sized files
should be resized. See the SYSTEM ADMINISTRATION GUIDE for further information.
Preparation of the Accounts

A conversion request must be recorded in the application AC.CCY.CONVERSION in order to prepare
accounts to be converted at a specified date. This application will include details of:

Euro
• The account number to be used for the In-currency account when it is renumbered
(RENUMBER.AC.NO)
• Whether the renumbered account should be closed (AUTO.CLOSE.ACCT)
• If closure is required, the date of closure (default next interest payment) and posting restriction
code to be used (AUTO.CLOSURE.DATE and POSTING.RESTRICT)
• Whether the mnemonic for the account is to stay with the converted EUR account or with the
renumbered In-currency account (KEEP.MNEMONIC)
• The type of ‘AC’ Funds Transfer to be used to transfer the balance between the In-currency and
EUR account (BAL.TRANSFER.TYPE)
• Whether the standing orders are to be converted to the EUR ccy account or to be renumbered
to the new account number (CONVERT.STO)
Before the conversion request can be entered, a structure for allocating a new account number for the
national currency account must be decided upon. This account number does NOT have to meet
existing CHECKDIGIT requirements, so a simple structure could be adopted such as, replacing the
leading 0 of the number with a 9 or adding a ‘1’ to the number. A renumbering subroutine is available
with this module for adding ‘1’ to the existing number, EU.AC.NEXT.ID.
In the case of multi-company installations, the INTERCO.PARAMETER record will need adjustment to
include the new range of numbers as valid for each company if the above first structure is adopted.
For example if accounts beginning ‘001’ are valid for company A, this should now additionally allow
accounts beginning ‘901’
Setting an account for conversion

Euro
Individual records may be entered in this application for an account, or may be created automatically
via the bulk conversion EU.CCY.CONVERSION application. This application will allow a selection
criteria to be specified (i.e. all accounts in DEM for a particular customer), with a general set of
conversion conditions. When ‘verified’, this application will create individual AC.CCY.CONVERSION
records for accounts.
Conditions Verified Prior to Conversion

The following criteria, for all accounts, will be verified prior to conversion:-
• The account cannot have AUTO.PAY.ACCT set to pass accounting entries to another account.
• The CURRENCY of the account must be one of the ‘In-Currencies’. (This will be denoted by a
FIXED.RATE defined in the CURRENCY record for the existing currency of the account)
• Interest and charge conditions must be defined from the start of the current capitalisation period of
the EUR currency.
• The account cannot be a PASSBOOK account. PASSBOOK accounts must be opened under a new
key for EUR.
• The new Renumbered account number must be valid and consistent with the existing old account
number. Hence internal accounts must follow internal account number formats and for external
accounts, the INTERCO.PARAMETER must be crosschecked if it exists.
• The BAL.TRANSFER.TYPE must be of type beginning ‘AC’.
• POSTING.RESTRICT must be in the range 90-99 for account closure.
• No unauthorised AC.PENDING records may exist for the account.
• The account cannot be set for NOSTRO RECONCILATION.
• If the account is set for closure after the conversion then the following checks will be verified:
o The account is not an INTEREST LIQUIDATION ACCOUNT.
o The account is not an INTEREST COMPENSATION ACCOUNT.
o The account does not have any DIRECT DEBIT MANDATES.
o The account is not part of securities portfolio.
Re-denomination of Accounts using the Bulk Conversion utility

The application EU.CCY.CONVERSION is a utility used to perform multiple contract and account
conversions to EUR. The options specified will be used to create AC.CCY.CONVERSION records for
each account to be converted and similarly to create EU.CONTRACT.CONVERSION records for
contracts, as described in the ‘Re-denomination of Contracts’ section.
The utility provides the ability to convert accounts dependent upon user defined selection criteria. A
selection can be entered for the application ACCOUNT (e.g. CUSTOMER, CURRENCY, and CATEGORY),
plus the following information:
• Renumber routine, the routine to return the account number to be used for the national currency
account

Euro
• Keep mnemonic
• Convert standing orders
• Automatic closure required
• Conversion date
• Type of funds transfer required to perform balance transfer
In the screenshot below, once the record has been verified, the bulk utility will select all accounts
denominated in DEM and set them for re-denomination into EUR. This is achieved by creating a
record in AC.CCY.CONVERSION for each account selected, hence preparing the account for
conversion. In essence, the bulk utility enables the creation of AC.CCY.CONVERSION records
without the user having to enter each one individually.
Setting up bulk account conversion
Batch Process
Run Dates
The batch record EU.ACCT.CONVERSION is run on a daily basis. In a multi company environment
this job is run for each financial level company.
In order to enable multi-threading of account conversions, the BATCH EU.ACCT.CONVERSION
should run the routine EU.ACCT.CCY.CONVERT.

Euro
BATCH EU.ACCT.CONVERSION
Report
The BATCH job EU.ACCT.CONVERSION is configured to produce a report (ENQ

EU.AC.CCY.CONV.FAILED) after the conversion process. The report is a list of all failed account
conversions:

Euro
Failed account conversion enquiry
Conversion process
When an account is converted automatically, the account number will be maintained and the account
converted to EUR. The original account in the national currency will be re-numbered as stated in the
AC.CCY.CONVERSION record, thereby ensuring that the full history is maintained. The fields
ORIGINAL.ACCT and AUTO.PAY.ACCT in the account records will maintain a link between the two
accounts.
The conversion of the account balance to EUR from the existing currency will be performed by the
automatic creation of a Funds Transfer between the renumbered original account, and the existing
(now EUR) account number. A special account transfer transaction type can be created for the
account, which will allow creation of a specific advice, and charges to be taken if required using
standard functionality. This will be retrieved from the BAL.TRANSFER.TYPE field in the
AC.CCY.CONVERSION record.
However, if the company does not have the Funds Transfer module installed then accounting entries
will be created to transfer the funds from the renumbered original account to the existing (now EUR)
account. A special account transfer transaction type can be created and set in field AC.TXN.CODE in

Euro
the relevant company record, in application EU.PARAMETER, to be used for any accounting entries
that are raised during the transfer of balance.
Use of accounts on existing contracts

T24 does not generally allow accounts of a different currency to be used for settlement of contracts
denominated in another currency. Conversion of existing accounts to EUR may create situations
where this arises. Since the original account will have been renumbered and remains in contract
currency, when the account is converted, contracts using the account for settlement are also
converted, so that the settlement account is the renumbered account.
Account Conversion Fees and Advices

If required, a charge can be made for converting an account to EUR. This is controlled by the Funds
Transfer application, which is used to perform the transfer between the national currency account and
the EUR account created by the conversion process. An account conversion charge can be defined in
either FT.COMMISSION.TYPE or FT.CHARGE.TYPE and subsequently specified in
COMM.TYPE/CHARGE.TYPE fields of the FT.TXN.TYPE.CONDITION record used for the transfer.
New transaction codes can also be created for the Euro conversion, which should then be specified in
the FT.TXN.TYPE.CONDITION record.
Special Cases
Account Conversion and Cash Pooling
Cashpooling operates on a single currency basis; whether foreign or local, all the accounts in a group
must be of the same currency. When one of the accounts in the group is subject to an account
conversion to change the account to EUR currency (and at the same time renumbering the original
account) this can complicate the cashpooling operation.
In order to prevent any cross-currency complications of having mixed currencies in a group, which has
values, based on the group currency it is essential that the integrity of the group be maintained.
As part of the EU conversion any client who has cashpooling records in the currency being converted
to EUR will need to activate the BATCH record EU.ACCP.GROUP.PARAM and set the run date to
today.
EU conversion of cashpooling is closely tied to the account conversion process; once an account is
converted the cashpool COB procedures will check whether the account is part of a cashpool group. If
it is then the group may be flagged as inactive as a precaution. This is done by setting the field
EUCC.PROCESS to Yes, this will prevent any records in the group being modified and will exclude the
group from the cashpool processing until it is made active again.

Euro
Cash Pooling blocked for a partially converted group
Once all the accounts in the group are converted the cashpool records (AC.CASH.POOL) which
have been placed on hold, can be amended (for example to use more logical rounded Euro amounts,
rather than the unrounded exact equivalents) and authorised for the cashpool processing for the group
can resume.
Return Sweeps
Certain sweeps are configured to make sweep during the COB and return the funds the next morning,
an example would perhaps be where all surplus funds on a current account are swept up to a savings
account each night to attract interest but the balance is returned the next morning to provide a working
balance. In this scenario the return of the funds will be redirected to the new EUR account.
Conversion for Accounts with Sub Accounts

There is no automatic process for the conversion of Master accounts with Sub accounts. In order to
convert these accounts the following manual process must be adopted.
1. Remove the link between the master account and the sub account:
• In the account record of the sub account, the value in the field MASTER.ACCOUNT must
be removed.
• In the account record for the Master account, the value in the field MAX.SUB.ACCOUNT
must be removed.
2. Transfer the balance of the Sub account to the Master account, ensuring that the balance of
the Sub account is Zero, once the transaction is completed.
3. Set up an ACCOUNT.CLOSURE record for the Sub account, this can either be set to close
on line or in the COB.
4. Create an AC.CCY.CONVERSION record for the Master account and convert the account
following the normal account conversion process.
5. Once the Master account is converted to the new currency, edit the account record and
populate the MAX.SUB.ACCOUNT. This will allow the system to generate new sub accounts
under the new currency when required.

Euro
Re-denomination of Contracts
After the fixing of currency exchange rates it may be necessary to convert any contracts which have a
maturity beyond the end of the life of the NCU.
In T24 the following modules are supported for contract conversion subject to certain restrictions:
• LD Loans and Deposits
• MM Money Markets
• MG Mortgages
• SW Interest Rate Swaps
To achieve conversion we essentially early mature the NCU contract to suspense, and raise a new
contract in EUR through the following process:
• General set-up for contract conversion.

• Set the conversion conditions for the contract either individually or via the bulk utility.
• Input to the contract using the appropriate version. This will set the NCU contract to early
mature, and raise the new EUR contract in HLD status.
• Authorise the early maturity of the NCU contract.
• Input/Authorise the new EUR contract.
• Resolve any created Funds Transfer (under certain circumstances FTs are raised to handle
contract events)
Initial Configuration for Contract Conversion

Define EB.API
Ensure that the EB.API file contains details of the following records for contract conversion:
EU.LD.CREATE.UNAUTH.DEAL
EU.MG.CREATE.UNAUTH.DEAL
EU.MM.CREATE.UNAUTH.DEAL
EU.SW.CREATE.UNAUTH.DEAL
For example:

Euro
EB.API record for contract conversion
Suspense Accounts
Although it can be changed at the group or individual contract level, it is necessary to set-up a default
suspense category and accounts for the balance transfer.
A new CATEGORY for the suspense accounts used in the contract conversion process should be
created. This should be a standard internal account category in the range 10000 to 19999.
Contract Conversion Suspense Category
This default category should be entered on the EU.PARAMETER record:

Euro
Specifying the contract conversion suspense account on EU.PARAMETER
A Euro suspense account should be opened for the category created earlier. The last four digits
should be ‘0001’.

Euro
Contract Conversion Suspense Account
Similar accounts should be opened for each of the In-Currencies where conversions will take place.
There are two accounting options for these accounts:
Auto Pay
If the AUTO.PAY.ACCT for each In-Currency accounts is defined as the EUR suspense account above,
all entries raised from the conversion process wash through the same account; the net result being a
zero balance.
Manual
If the auto-pay is not set then the total value of the early matured contracts of the NCU will be held in
each of the NCU suspense accounts, and the total value of the new EUR contracts will be held in the
EUR suspense accounts. This option may be required if a check on these totals is deemed necessary.
The amounts could then be transferred manually to net off the balances as required.

Euro
In-currency Contract Conversion Account using Auto-Pay
If different suspense categories and accounts are required for different contract types, or for the
suspension of interest where conversion takes place on a non-interest date, these should be set-up in
a similar manner, however they do not require specification on the EU.PARAMETER record.
Category for suspension of accrued interest

Euro
EUR account for LD Interest Suspense
In-currency account for LD interest suspense

Euro
Creation of ‘Dummy’ Limit Reference

As a result of the process of early maturing the NCU contract and opening a new EUR contract, there
will for a time be both contracts affecting the limits system. To avoid the double exposure on the
LIMIT, the maturing NCU contract is moved from the customer limit to a dummy limit under a
separate LIMIT.REFERENCE. The new EUR contract will use the original limit and
LIMIT.REFERENCE.
N.B. This process if different for LD Commitments and their drawdowns, please refer to the relevant
user guide section for more information.
A minimum of one LIMIT.REFERENCE should be created. This should be a non-reducing type and
not require overrides, specified by defining the DEFAULT.CHECK field as NO.
Dummy LIMIT.REFERENCE for contract conversion
The Limit Reference should be added to the LIMIT.PARAMETER application as an additional

PRODUCT.NO for each application (i.e. LD.LOANS.AND.DEPOSITS, SWAP, MM.MONEY.MARKET
and MG.MORTGAGE) where conversion will take place, and for each set of decision fields relating to
contract conditions for contracts due to be converted.

Euro
Adding the dummy LIMIT.REFERENCE to the LIMIT.PARAMETER
When the contracts are converted the necessary dummy LIMIT records will be automatically created.
Bulk Conversion Utility – EU.CCY.CONVERSION
The settings for conversion of contracts is held in the EU.CONTRACT.CONVERSION file, each
record being keyed by the individual contract ID. However, to assist in the creation of these records
where sizeable volumes of contracts are being converted under the same conditions, there is a bulk
conversion utility, namely EU.CCY.CONVERSION.
The utility allows the user make selections from the contract files, based on any criteria on those files,
and set the conversion conditions. When the record is Verified, the related
EU.CONTRACT.CONVERSION records are created. If there are no errors or overrides, the
records are created fully authorised, otherwise they are created in HLD status to allow the user to
correct the settings prior to conversion. N.B. Neither this utility, nor EU.CONTRACT.CONVERSION
actually execute the contract conversion, they just set the parameters.
This utility is also used for bulk selection of accounts for conversion, but the fields in terms of contract
conversion are as follows:

Euro
ID The file has a free format key.

APPLICATION Set to the appropriate application for the desired conversion:
ACCOUNT
LD.LOANS.AND.DEPOSITS
MG.MORTGAGE
MM.MONEY.MARKET
SWAP
SELECT.FIELD These fields specify the conditions of the contracts (or accounts) which are to
OPERAND be converted using the parameters of this record. The SELECT.FIELD must be
VALUE from the above APPLICATION
NEW.CCY The currency for the new contract. i.e. EUR
RENUMBER.ROUTINE Only used for account conversion.
CONVERSION.DATE This field is optional for contracts.
If input this date will be passed to the CONVERSION.DATE field on the created
EU.CONTRACT.CONVERSION records.
If not input CONVERSION.DATE will be defaulted to the next interest schedule
date, unless the NON.INT.CONV flag is set, in which case the field will be
defaulted to today.
AUTO.CLOSE.AC Only used for account conversion.
AC.POST.RESTRICT
KEEP.MNEMONIC
BAL.TRANSFER.TYPE
CONVERT.STO
NCU.LIMIT.REF The dummy LIMIT.REFERENCE to be used on the maturing NCU contracts
to avoid double exposure on the customer limit.
Loans under commitment use different functionality in this regard, explained in
the relevant section of this user guide.
NCU.SUSP.CAT The suspense category to be used for the early maturity of the NCU contract
and the creation of the new EUR contract. This can be different from the
setting in EU.PARAMETER if required.
AC.TRANSFER.TYPE The internal and external FT.TXN.TYPE.CONDITION to be used for any
OT.TRANSFER.TYPE Funds Transfers that are created to account for principal schedules taking
place on the conversion date.
AUTH.RECORDS These system fields hold the results produced when this record is Verified.
HOLD.RECORDS They note the number of records that have been fully created, placed on hold
IGNORED.RECORDS due to override or error conditions, and have been ignored (if a
ERROR.DETAILS EU.CONTRACT.CONVERSION record already exists for the contract), and
any associated error messages.
NON.INT.CONV If this flag is set to Yes, then contracts converted under this selection can be
converted on a non-interest settlement date.
Currently, this flag can only be set for LDs and MMs.
INT.TRANSFER.TYPE The FT.TXN.TYPE.CONDITION for the future dated FT created to post the

Euro
suspended interest, if the CONVERSION.DATE is not an interest settlement

date.
INT.SUSP.CAT The CATEGORY of the suspense account to be used for the suspension of
interest, if the CONVERSION.DATE is not an interest settlement date.
LOCAL.REF Standard system local reference field.
Bulk Conversion of all CHF loans with category 21051
Contract Conversion Settings – EU.CONTRACT.CONVERSION
The EU.CONTRACT.CONVERSION record holds all the settings for the conversion of an individual
contract, and also records the results of the conversion for any post-conversion reconciliation and
checking. N.B. It does not execute the conversion itself.
It can be input directly for an individual contract or created via the EU.CCY.CONVERSION utility.
The fields are as follows:
ID The transaction reference number of the contract to be converted.
APPLICATION System field holding the application of the contract to be converted.
CONVERSION.DATE The value date at which the NCU contract will be matured, and the new
EUR contract starts.
The CONVERSION.DATE will default to the next interest settlement date,

Euro
unless the NON.INT.CONV flag has been set to Yes either from the
EU.CCY.CONVERSION record or through use of a version to pre-
populate it, in which case the CONVERSION.DATE will default to today.
If the NON.INT.CONV flag on this record is set to Yes via direct user
input, the CONVERSION.DATE will not be automatically updated from its
initial default value, but it can be updated manually.
OLD.CCY No input field recording the NCU currency.
NEW.CCY Automatically populated with the fixed currency (i.e. EUR)
OLD.LIMIT.REF System field recording the original LIMIT.REFERENCE from the NCU
contract. This will then be used on the new EUR contract.
NEW.LIMIT.REF The maturing NCU contract will be updated to use this
LIMIT.REFERENCE, and so this should contain the dummy
LIMIT.REFERENCE.
Loans under commitment use different functionality in this regard,
explained in the relevant section of this user guide.
BAL.SUSP.CAT The suspense category to be used for the early maturity of the NCU
contract and the creation of the new EUR contract. This will default from
the NCU.SUSP.CAT field, if this record is created from
EU.CCY.CONVERSION, or else the CONT.CONV.SUSP.CAT on
EU.PARAMETER, but it can be updated to an alternative valid category
if required.
NEW.CONTRACT After conversion has been run, this system field is updated with the
transaction id of the new EUR contract.
ACTUAL.CONV.DATE This system field records when the conversion was executed. Where
conversion is taking place on an interest date, this can be before the
CONVERSION.DATE (value date).
ORIGINAL.AMOUNT System field recording the principal of the NCU contract prior to
conversion.
CONVERTED.AMT System field recording the principal of the new EUR contract. If there has
been a principal payment on the conversion date, then this will not be the
EUR equivalent of the ORIGINAL.AMOUNT.
AC.TRANSFER.TYPE The internal and external FT.TXN.TYPE.CONDITION to be used for
OT.TRANSFER.TYPE any Funds Transfers that are created to account for principal schedules
taking place on the conversion date.
REPAYMENT.FT The ID and amount of any Funds Transfer raised to account for a principal
REPAYMENT.AMOUNT schedule taking pace on conversion date.
ERROR.MSG This field holds any error message encountered during the creation of this
record from EU.CCY.CONVERSION, or during the execution of the
conversion.
LOCAL.REF Standard system local reference field.
COMMIT.NO When a LD drawdown under commitment is being converted, this field is
updated with the original commitment number.
DRAWDOWN.AMT When a LD drawdown under commitment is being converted, this field
holds the principal of the drawdown in the currency of the commitment.

Euro
NON.INT.CONV If this flag is set to yes, then CONVERSION.DATE can be set to any
working day, not just the next interest settlement date.
Currently, this flag can only be set for LDs and MMs.
INT.TRANSFER.TYPE The FT.TXN.TYPE.CONDITION for the future dated FT created to post
the suspended interest, if the CONVERSION.DATE is not an interest
settlement date.
INT.SUSP.CAT The CATEGORY of the suspense account to be used for the suspension
of interest, if the CONVERSION.DATE is not an interest settlement date.
INTEREST.FT System fields updated with the ID, amount and value date of the Funds
INTEREST.AMT Transfer created to post the suspended interest, if the CONVERSION.DATE
INT.VALUE.DATE is not an interest settlement date.
Timing of the Conversion

In terms of T24, contract conversion can take place at any time after the rate fixing date, and is
independent of both the local currency conversion and account conversion processes, although it may
be preferable to convert contracts after customer accounts, so that the customer EUR accounts will
default onto the new EUR contracts.
The preparation of the EU.CONTRACT.CONVERSION records can take place in advance of the
conversion date. This is recommended for any sites where all the Euro conversions are due to take
place over a short space of time.
For contracts which are converting on an interest settlement date, it is possible to run the conversion
itself prior to the CONVERSION.DATE (value date for maturity of NCU contract and start of EUR
contract), however it is advisable to keep the gap between the run date and the conversion date as
short as possible, as any subsequently entered information or events against the NCU contract will not
be automatically reflected in the EUR contract. Where the contract is being converted on a non-
interest settlement date, the conversion must be run on the CONVERSION.DATE.
Re-denomination of Money Market Contracts

Once EU.CONTRACT.CONVERSION has been populated with details of the individual contracts to
be converted, conversion may be performed using the VERSION record provided. In the case of
Money Market contracts, this will be MM.MONEY.MARKET,EUCC allowing the conversion to run on-
line. Listed below is a more detailed explanation of each of the conversion processes.
Note that the Version calls an Input Routine EU.MM.CREATE.UNAUTH.DEAL which should be set up
as an EB.API record.
Converting on a non-interest date

It is possible to convert term and call notice loans and deposit type transactions on a non-interest
settlement date. If the NON.INT.CONV flag is set to Yes, then the CONVERSION.DATE specified on
the EU.CONTRACT.CONVERSION record can be any working day. If this flag is set through
EU.CCY.CONVERSION or via a version used to input the EU.CONTRACT.CONVERSION, then
the CONVERSION.DATE will default to today. However, if the flag is set by direct user input to the
EU.CONTRACT.CONVERSION record, then the CONVERSION.DATE will have already defaulted

Euro
to the next interest settlement date, so will need to be updated manually to the required conversion
date.
Because of the processing for the interest accrual, conversions set to take on a non-interest date,
must be executed on the CONVERSION.DATE itself.
Early maturing the existing contract

Early maturity of a Money Market contract takes place as soon as the contract is ‘INPUT’ via the
relevant VERSION and involves the following:
• Set the maturity date to be the next interest payment date to flag the contract for conversion.
This will, in effect, be the conversion date.
• The principal liquidation account will be set a suspense account (this may be an internal
account with a category of BAL.SUSP.CAT).
• Set the limit reference to be NEW.LIMIT.REF (as defined on

EU.CONTRACT.CONVERSION). In the case of a ‘loan’ contract, the limit reference should
Be amended to a ‘dummy’ reference of non-reducing type. This avoids the old and new
contracts both appearing under the same Limit Reference and the apparent double exposure,
and also ensures that if the loan was taken under a reducing Limit, the Limit is not reduced
again when the new EUR contract starts.
• Care must be taken to ensure that any principal repayment on the conversion date still takes
place.
When conversion is taking place on a non-interest date, the conversion will also:
• Set the INT.LIQ.ACCT on the NCU contract to the suspense account in the NCU currency
based on the category defined in INT.SUSP.CAT on the
EU.CONTRACT.CONVERSION record.

Euro
Setting an MM for conversion
Creation of the new EUR Contract

Upon Validation of the Early Maturity VERSION, an additional routine will create the new EUR
denominated Money Market contract based on the original contract and set it to ‘hold’ (i.e. with a
status of IHLD). The following is an outline of this creation process:
• The original contract will be used as the basis for the creation of the new EUR denominated
contract.
• The outstanding balance at the conversion date will be converted to EUR to become the
principal on new EUR contract.
• The value date of the new contract will be the conversion date.
• The drawdown account will be set to the suspense account (i.e. the internal account created
from BAL.SUSP.CAT in EU.CONTRACT.CONVERSION).
• The limit reference will be set to the Limit reference of the original contract (i.e. the limit
reference held in OLD.LIMIT.REF in EU.CONTRACT.CONVERSION).
• The reference number of the new contract will be held in the LINK.REFERENCE field of the
original contract and vice versa.
• No history records from the original contract will be converted.

Euro
Creation of a Funds Transfer for repayments

Any principal increase or decrease scheduled to take place on the conversion date will not take place
because the contract fully matures on this date through a suspense account. A manual repayment is
therefore required in these cases, which will automatically be created by the conversion utility at the
same time as the EUR denominated contract, and will be set to ‘hold’ (i.e. status of FHLD). The Funds
Transfer will debit the original principal liquidation account (for a loan) and credit the suspense
account used for early maturity. Entries will be vice versa for deposits.
FT for repayment
Once the new contract and Funds Transfer transactions have been created, the associated
EU.CONTRACT.CONVERSION record is updated with NEW.CONTRACT, ACTUAL.CONV.DATE,
ORIGINAL.AMOUNT, CONVERTED.AMT, REPAYMENT.FT and REPAYMENT.AMOUNT as demonstrated
below:

Euro
Updated EU.CONTRACT.CONVERSION record
Creation of Funds Transfer for Suspended Interest

When conversion is taking place on a non-interest date, the early maturity of the NCU contract will
post the interest accrual to a suspense account (as specified in the INT.SUSP.CAT field of the
EU.CONTRACT.CONVERSION record). In order to post this interest, as per the original contract,
the conversion will also raise an FT in HLD status crediting the NCU suspense account, and debiting
the original INT.LIQ.ACCT for a loan (vice-versa for a deposit).
The amount of the FT will be outstanding interest accrual, as captured on the
LMM.ACCOUNT.BALANCES record, and the value date will be the next scheduled interest settlement
date. The transaction codes and other settings on the FT, will be based on the
FT.TXN.TYPE.CONDITION specified in the INT.TRANSFER.TYPE field on the
The FT transaction id, amount and date will be recorded on the EU.CONTRACT.CONVERSION
record in the INTEREST.FT, INTEREST.AMT and INT.VALUE.DATE fields respectively.
Essentially, this process allows the NCU contract to fully mature, posting its interest to the suspense
account, where it is held until the next interest date and the FT posts it to the customer account. The
new EUR loan will start accruing interest normally from the conversion date. Any subsequent changes
to the interest conditions of the loan will take effect on the EUR contract as normal, but will not
automatically make any adjustment to the raised FT for the interest on the NCU contract.
On the interest settlement date, the interest posted to the customer will be in 2 entries: via FT for the
NCU contract, and via normal MM processing for the EUR contract.

Euro
Validation and authorisation of EUR contracts

Once the contract has been validated, the original contract will need to be authorised and the new
contract, which has a status of IHLD, will need to be validated and authorised.
Validation and authorisation of Funds Transfer transactions

If a Funds Transfer transaction was generated to satisfy a scheduled principal repayment and/or
suspended interest, this new Funds Transfer transaction, which also has a status of IHLD will need to
be validated and authorised.
In the case of an FT for suspended interest, this could be value dated further forward than normally
permitted by the settings on the relevant EB.DATES record. If this is the case, the EB.DATES settings
should be temporarily changed to allow these transactions to be input and authorised, before returning
it to its normal settings.
Worked example for conversion of a Money Market on a non-interest date

The example detailed below is for a PLN (assumed to be an in-currency fixed at 1 EUR = 3.84 PLN in
this case) call deposit, running from 12th April 2004.Its next interest payment is scheduled for 26th
April 2004, however the contract is being converted on 21st April 2004.
Deposit with Committed Interest of 388.89.

Euro
LMM.ACCOUNT.BALANCES record.
The committed interest for the period up to the next interest payment (scheduled for 26th April 2004) is
388.89, with the accrual on set at 250.00.

Euro
Contract set to convert on non-interest date.

Euro
NCU Contract after conversion
After conversion the NCU contract is matured on 21st April, with the interest to date as 250.00 being
posted to the PLN interest suspense account

Euro
New EUR Contract
The new EUR contract is raised starting from 21st April with a call maturity date. The committed
interest of 36.17 EUR is for the 5 days period until the interest settlement date.
Original Committed Interest up to 26th April 388.89 PLN

Suspended Interest for period up to 21st April 250.00 PLN
st th
Interest for new contract 21 Aug to 26 April 138.89 PLN = 26.17 EUR

Euro
New LMM.ACCOUNT.BALANCES record.

Euro
FT to credit interest to customer account.
The funds transfer raised to credit the customer account the suspended 250.00 PLN for the period up
to 21st April, posted for value 26th April.
Functional Limitations for MM Conversion on a non-interest date
Rollover and Principal Increase Information
As it is not possible to input rollover information on initial input of a contract, this information will not be
carried over to the EUR deal. This information will be lost in the conversion.
CAPITALISATION (for fixed maturity contracts)
ROLLOVER.MARKER
ROLLOVER.DATE
NEW.INTEREST.RATE
NEXT.INT.AMOUNT
NEXT.PRIN.AMOUNT
PRIN.INCREASE

Euro
INCR.EFF.DATE
If the contract has the AUTO.ROLLOVER and associated fields set then these will be maintained
correctly, and will populate the above fields as normal during COB processing.
Deferred Interest
We are assuming that the LIQ.DEFER.INTEREST field is not set to D. If interest should be deferred,
then this will require manual adjustment of the FT.
Capitalisation
For fixed maturity contracts capitalisation is only applicable on a rollover, so as mentioned above the
setting with be lost along with the other rollover information. The interest accrual will be processed on
the assumption of settling the interest to the customer account on the next interest date.
For Call / Notice contracts, we will maintain the setting in capitalisation for future interest events,
however the processing of the interest accrual will not be strictly correct. The interest accrual FT will
be raised with the posting to the customer account, rather than capitalising the interest onto the
contract. We will recommend that clients follow the procedure of removing these FTs and manually
inputting the EUR equivalent onto the contract as a principal increase, scheduled for the next interest
date.
Re-denomination of Loans and Deposits

Once the EU.CONTRACT.CONVERSION records have been set up, the standard workflow to
execute the LD conversion is as follows:
• Input the early maturity of the NCU contract (this will create the EUR contract in HLD status).
• Authorise the early maturity of the NCU contract.
• Input and authorise the new EUR contract.
• Input and authorise any resulting FTs relating to principal schedules and suspended interest.
N.B. The workflow for LD commitments and their drawdowns is a little more complex. Please refer to
the relevant section of this user guide.
Early maturing the NCU contract

To early mature the NCU contract, input to the main contract through the
LD.LOANS.AND.DEPOSITS,EUCC version.
Upon entry into the record through this version, the associated routines will:
• Check that the settings in the EU.CONTRACT.CONVERSION are valid

Euro
• Set the maturity date on the NCU contract to the CONVERSION.DATE

• Change the principal liquidation account on the NCU contract to a NCU suspense account
based on the category specified in the BAL.SUSP.CAT field on the
EU.CONTRACT.CONVERSION record
• If conversion is taking place on a non-interest settlement date, set the interest liquidation
account on the NCU contract to the NCU suspense account based on the category specified
in the INT.SUSP.CAT on the EU.CONTRACT.CONVERSION record.
• Sets the LIMIT.REFERENCE on the NCU contract to the dummy reference NEW.LIMIT.REF
from the EU.CONTRACT.CONVERSION record.
Creation of the new EUR contract

Upon committing the contract record through the version, the associated routines will create a new
EUR contract in HLD status, based on the terms and schedules of the NCU contract, and also:
• Set the principal on the EUR contract to be the fixed equivalent of the outstanding balance on
the NCU contract less any principal payments due to be made on the conversion date itself.
• Set the value date on the EUR contract to the conversion date.
• Set the drawdown account on the EUR contract to be the EUR suspense account, based on
the category specified in the EU.CONTRACT.CONVERSION record.
• Set the LIMIT.REFERENCE to that of the original NCU contract, i.e. the OLD.LIMIT.REF
from the EU.CONTRACT.CONVERSION record.
• Set the reference number of the new EUR contract in the LINK.REFERENCE field of the
original contract and vice versa
• Create FTs as appropriate for principal schedules and suspended interest. More detail below.
• Update the EU.CONTRACT.CONVERSION record with details of the conversion
No history records from the NCU contract are converted.
Warning: Any changes made to the NCU contract made after this time will not affect the new EUR
contract, so should be made with careful consideration. In particular changes should not be made
again through the LD.LOANS.AND.DEPOSITS,EUCC version, as this could have intended results.
Completing the conversion
Authorising the early maturity
The NCU contract set to early mature should now be authorised. For standard contracts this can be
done through any version (or none), however for commitments and loans under commitment the
LD.LOANS.AND.DEPOSITS,EUCC version must be used.

Euro
Completion of the EUR contract
The new EUR contracts have been created in HLD status, they will need to be input and authorised to
make them live. With the exception of drawdowns under commitment (see below), no particular
version is required for this.
Completion of created FT records
If the conversion created any Funds Transfer records for principal repayments, or suspended interest,
these will also require input and authorisation. No particular versions are required.
Principal Repayments
If a principal repayment is scheduled to take place on the conversion date, it is not possible to transfer
this schedule to the new contract. Therefore, upon committing the conversion through
LD.LOANS.AND.DEPOSITS,EUCC the system raises a Funds Transfer for the principal. The
Funds Transfer will debit the original principal liquidation account (for a loan) and credit the suspense
account used for early maturity (i.e. based on the category in the BAL.SUSP.CAT on the
EU.CONTRACT.CONVERSION record). Entries will be vice versa for deposits.
The transaction codes and other settings for the FT are taken from the FT.TXN.TYPE.CONDITION
specified in the AC.TRANSFER.TYPE field for internal transfers, or the OT.TRANSFER.TYPE field for
external transfers.
The FT is created in HLD status, so will require input and authorisation to complete the transaction.
Converting on a non-interest date
It is possible to convert loans and deposits on a non-interest settlement date. If the NON.INT.CONV
flag is set to Yes, then the CONVERSION.DATE specified on the EU.CONTRACT.CONVERSION
record can be any working day. If this flag is set through EU.CCY.CONVERSION or via a version
used to input the EU.CONTRACT.CONVERSION, then the CONVERSION.DATE will default to
today. However, if the flag is set by direct user input to the EU.CONTRACT.CONVERSION record,
then the CONVERSION.DATE will have already defaulted to the next interest settlement date, so will
need to be updated manually to the required conversion date.
Because of the processing for the interest accrual, conversions set to take on a non-interest date,
must be executed on the CONVERSION.DATE itself.
When the conversion is committed through LD.LOANS.AND.DEPOSITS,EUCC when conversion is

taking place on a non-interest date, the routines associated with the version will:
• Set the INT.LIQ.ACCT on the NCU contract to the suspense account in the NCU currency
based on the category defined in INT.SUSP.CAT on the EU.CONTRACT.CONVERSION
record.
• Raise an FT in HLD status crediting the NCU suspense account, and debiting the original
INT.LIQ.ACCT for a loan (vice-versa for a deposit).
• Set the amount of the FT to the outstanding interest accrual as held in the
LMM.ACCOUNT.BALANCES record for the NCU contract.

Euro
• Set the value date on the FT to the next scheduled interest settlement date, as held in the
LMM.ACCOUNT.BALANCES record for the NCU contract.
• Set the transaction codes
and other settings on the FT, based on the
FT.TXN.TYPE.CONDITION specified in the INT.TRANSFER.TYPE field on the
• Update the EU.CONTRACT.CONVERSION record with the transaction id, amount and
date of the FT in the INTEREST.FT, INTEREST.AMT and INT.VALUE.DATE fields
respectively.
Essentially, this process allows the NCU contract to fully mature, posting its interest to the suspense
account, where it is held until the next interest date and the FT posts it to the customer account. The
new EUR loan will start accruing interest normally from the conversion date. Any subsequent changes
to the interest conditions of the loan will take effect on the EUR contract as normal, but will not
automatically make any adjustment to the raised FT for the interest on the NCU contract.
On the interest settlement date, the interest posted to the customer will be in 2 entries: via FT for the
NCU contract, and via normal LD processing for the EUR contract.
The FT for suspended interest could be value dated further forward than normally permitted by the
settings on the relevant EB.DATES record. If this is the case, the EB.DATES settings should be
temporarily changed to allow these transactions to be input and authorised, before returning it to its
normal settings.
If the contract is a call/notice contract without an INT.DUE.DATE set, then it is not possible to fully
complete the FT at conversion. The FT will be raised for the suspended interest amount, but should be
left in HLD status until the next interest payment date is known and the dates (and possibly accounts)
on the FT should be manually adjusted at that time.
Please note restrictions mentioned later in this document regarding deposits with interest capitalisation
set.
Worked Example
The example detailed below is for a CHF (assumed to be an in-currency fixed at 1 EUR = 1.75 CHF in
this case) deposit, running from 01st June 2001 until the 30th September 2001. Its next interest
payment is scheduled for 22nd August, however the contract is being converted on 21st August.

Euro
Deposit with Committed Interest

Euro
Schedules shows Interest due on 22 AUG 2001
LMM.ACCOUNT.BALANCES showing accrued interest
The committed interest for the period up to the next interest payment (scheduled for 22nd Aug) is
6974.10, with the accrual on 21st August at 6889.05.

Euro
Contract set to convert on non-interest date

Euro
NCU Contract after conversion
After conversion the NCU contract is matured on 21st August, with the interest to date as 6889.05
being posted to the CHF LD interest suspense account

Euro
New EUR Contract
The new EUR contract is raised starting from 21st August and maturing on the original maturity date of
30th September. The committed interest of 48.60 EUR is for the 1 day period until the interest
settlement date.
Original Committed Interest up to 22nd Aug 6974.10 CHF

st
Suspended Interest for period up to 21 Aug 6889.05 CHF
st nd
Interest for new contract . 21 Aug to 22 Aug 85.05 CHF = 48.60 EUR

Euro
Schedules for EUR Contract. Interest due 22nd Aug
FT to credit interest to customer account
The funds transfer raised to credit the customer account the suspended 6889.05 CHF for the period
up to 21st Aug, posted for value 22nd Aug.

Euro
LD Commitments and Drawdowns

Although using the same general process as standalone loans, the conversion of Commitments and
Drawdowns requires a few changes. Most notably the different update to limits and the specific
workflow to allow the contracts to link up correctly after conversion whilst maintaining the same
commitment available amount.
This workflow must be adhered to exactly, particularly with regard to the use of different versions for
the different stages. It is recommended that suitable menus and/or SMS set-up is used to protect
against user error.
Basic Workflow Summary
Note that the following workflow is for the conversion of commitment and drawdown contracts which
are held in the same currency. For mixed currency contract structures refer to the later section.
• Create EU.CONTRACT.CONVERSION records
• Execute the conversion for all drawdown contracts.
• Execute the conversion for all commitment contracts.
• Input and authorise the new EUR commitment contracts
• Input and authorise the new EUR drawdown contracts
Conversion Parameters
The set-up for EU.CCY.CONVERSION and EU.CONTRACT.CONVERSION for commitments and

drawdowns is the same as for normal LD contracts, with one exception:
Because it is necessary to have commitments and drawdowns with the same LIMIT.REFERENCE, we
can not use the dummy limit process for the drawdown conversion. Instead it is necessary to input the
same reference on the OLD.LIMIT.REF and NEW.LIMIT.REF fields on the
EU.CONTRACT.CONVERSION record for the drawdown.
Conversion of Drawdown Contracts
Using the version LD.LOANS.AND.DEPOSITS,EUCC input the conversion for the drawdown contracts.
This will early mature the NCU contracts, and raise the EUR drawdown contracts in HLD status.
Using the version LD.LOANS.AND.DEPOSITS,EUCC authorise the conversion for the drawdown
contracts. This will store the associated commitment number and the NCU contract amount on the
EU.CONTRACT.CONVERSION record. It will also execute a limit increase for the NCU contract
amount for non-revolving deals, to address the double exposure created by the necessity of keeping
the same limit reference rather than using a dummy limit for the maturing NCU contract.
At this point leave the created EUR drawdown contracts in the HLD status. Convert all related
drawdown contracts before converting the associated commitment contract.
Conversion of Commitment Contracts
Using the version LD.LOANS.AND.DEPOSITS,EUCC input the conversion for the commitment
contracts. This will early mature the NCU contracts, and raise the EUR commitment contracts in HLD
status. For a non-revolving commitment, the new principal will be the EUR equivalent of the old

Euro
principal plus the active drawdown amounts as stored on the EU.CONTRACT.CONVERSION record
of the drawdown. (This is so that when the EUR drawdowns are attached onto the EUR commitment
the available amount is returned to the correct EUR equivalent for the pre-conversion NCU available
amount.)
Using the version LD.LOANS.AND.DEPOSITS,EUCC authorise the conversion for the commitment
contracts.
Input and authorise the new EUR commitment contracts from HLD status. No particular version is
required.
Completion of EUR Drawdown Contracts
Using version LD.LOANS.AND.DEPOSITS,EUDD (N.B. different version used) input the HLD EUR
drawdown contracts. This will update the commitment number on the contract from the NCU
commitment number to the new EUR commitment number, and execute the drawdown from the
commitment (thus for non-revolving commitments returning the available amount to the correct level).
Authorise the new EUR drawdown contracts. No particular version is required.
Worked Example for single currency structures
In this example a 10M SIT Non-revolving Commitment, has 2 live drawdowns and one fully matured
drawdown. The assumed fixed rate is 1 EUR = 264 SIT.
Initial structure
The drawdowns are converted i.e. the SIT contracts are early matured, and new EUR contracts raised
in HLD status, whilst recording the drawdown amount in SIT on the

Euro
Conversion of Drawdowns
When the commitment is converted, initially it has no drawdowns associated with it. The principal and
available amount are both 26515.15 EUR, being the equivalent of 7M SIT.

Euro
Conversion of Commitment
When the drawdown contracts are linked to the EUR commitment contract the available amount is
reduced to 18939.39 EUR, i.e. the equivalent of the original available amount of 5M SIT.

Euro
Re-linked drawdowns
Cross currency commitments and drawdowns
Where there are NCU drawdowns from an existing EUR commitment, an amended procedure is
required, as there will obviously be no conversion of the commitment itself.
• Set up the EU.CONTRACT.CONVERSION records for the drawdown contracts as above.

• Convert all the drawdown contracts as above.
• Prior to the input and authorisation of the EUR drawdown contracts in HLD, it is necessary to
reinstate the available amount for non-revolving commitments. This is done by using version
LD.LOANS.AND.DEPOSITS,EUPRINC to input to the commitment contracts. This will sum
the active drawdown amounts of the converted NCU contracts and execute a principal
increase on the commitment.
• Authorise the principal increase, no particular version is required.
• Input and authorise the HLD EUR drawdown contracts. This will execute the drawdown from
the commitment and return the available amount to the correct level. No particular version is
required for this, though use of LD.LOANS.AND.DEPOSITS,EUDD is valid should it be
deemed expedient to perform this process at the same time as for drawdowns where the
commitment has also been converted.

Euro
Worked Example for cross currency structures
In this example a non-revolving EUR commitment has a live EUR drawdown, a live SIT drawdown and
a fully matured drawdown.
Initial Structure
When the SIT drawdown

is converted the amount in EUR is stored on the
Conversion of Drawdown
In order to take account of the new EUR drawdown without ultimately affecting the available amount, a
principal increase for the amount stored on EU.CONTRACT.CONVERSION. This is facilitated by
using the LD.LOANS.AND.DEPOSITS,EUPRINC version supplied.

Euro
Principal increase of Commitment
When the new EUR drawdown is re-linked to the commitment the available amount returns to its initial
value.
Re-linking of drawdown

Euro
Automation of LD conversions
As well as using the EU.CCY.CONVERSION utility to aid in the set-up of the required
EU.CONTRACT.CONVERSION records, it is also possible to semi-automate the execution of the
conversions. Because of the structure of the conversions it is necessary for each contract to go
through the process of being opened through the version and committed. The use of the
EBS.AUTO.FUNCTION tool is therefore recommended to assist with volume conversions, as this
will emulate the required keystrokes with minimal user interface. The same workflow must, however
be adhered to so this does need to be used with care, particularly with commitments and drawdowns.
Functional Limitations for LD conversion
Ineligible Contracts
Contracts linked to the Bills module.

Contracts with a future value date.
Contracts with linked Past Due items.
Contracts using ISSUE.PRICE and REIMBURSE.PRICE not set to 100%
Contracts with a commission rate defined or using amortised fees and charges.
Discounted Loans can not be converted on a non-interest date.
Annuity Contracts can not be converted on a non-interest date.
Converting contracts with interest capitalisation
When converting contracts on a non-interest date, the FT raised to debit the suspense account and
credit the customer account (for a deposit, vice versa for loan) with the accrued interest is
inappropriate. For these contracts, the user should manually remove the FT, and input a principal
increase schedule to the EUR loan for the equivalent amount on the future interest capitalisation date.
Insufficient funds for interest FT
The processing of the Funds Transfer for suspended interest from the NCU loan, will take place during
the start-of-day phase of the COB on the interest settlement date. The payment will be processed
regardless of whether there is sufficient funds on the account. If this occurs the override is recorded on
the FT record and the exception will be highlighted in standard reports, and the issue dealt with
manually, raising a PD through PD.CAPTURE record if necessary.
The interest from the new EUR contract will be processed as per normal LD functionality at the end of
day, and will automatically raise a PD if settings require it.
The two events are independent, and will be processed separately.
Past Due
It is not possible to convert loans with past due items associated with them. It is necessary to manually
pay off the PD item linked to the loan to a suspense account and raise a fresh PD.CAPTURE item for
the payment.

Euro
Collateral
There is no automatic update of Collateral during the conversion of LDs. Any updates would need to
be handled manually.
Re-denomination of Mortgage Contracts

Once EU.CONTRACT.CONVERSION has been populated with details of the individual contracts to be
converted, conversion may be performed using the VERSION record provided. In the case of
Mortgage, this will be MG.MORTGAGE, EUCC allowing the conversion to run on-line. Listed below is
a more detailed explanation of each of the conversion processes.

Early maturity of a mortgage contract takes place as soon as the contract is ‘INPUT’ via the relevant
VERSION and involves the following:
• Mortgage contract are early matured by the creation of an MG.PAYMENT record for the
outstanding principal
• Set the value date and the transaction date to the required next interest payment date to flag
the contract for conversion. This will be, in effect, the conversion date.
• The transaction type will be set to ‘CLOSURE’.
• The Payment account will be set a suspense account (this may be an internal account with a
category of BAL.SUSP.CAT).
• Set the limit reference to be NEW.LIMIT.REF (as defined on EU.CONTRACT.CONVERSION).

The limit reference should be amended to a ‘dummy’ reference of non-reducing type. This
avoids the old and new contracts both appearing under the same limit reference and the
apparent double exposure, and also ensures that if the loan was taken under a reducing limit,
the limit is not reduced again when the new EUR contract starts.
Care must be taken to ensure that any principal repayment on the conversion date still takes place.

Euro
Setting an MG for Conversion

Upon validation of the early maturity VERSION, an additional routine will create the new EUR
denominated mortgage contract based on the original contract and set it to ‘hold’ (i.e. with a status of
IHLD). The following is an outline of this creation process:
contract
• The outstanding balance at the conversion date will be converted to EUR to become the
principal on new EUR contract
• The VALUE DATE of the new contract will be the conversion date
• The DRAWDOWN ACCOUNT will be set to the suspense account (i.e. the internal account created
from BAL.SUSP.CAT in EU.CONTRACT.CONVERSION)
• The limit reference will be set to the limit reference of the original contract (i.e. the limit
reference held in OLD.LIMIT.REF in EU.CONTRACT.CONVERSION)
• The reference number of the new contract will be held in the LINK.REFERENCE field of the
original contract and vice versa
No history records from the original contract will be converted.

Euro

Any scheduled repayment due to take place on the conversion date will not take place because the
contract fully matures on this date through a suspense account. A manual repayment is therefore
required in these cases, which will automatically be created by the conversion utility, at the same time
as the EUR denominated contract, and will be set to ‘hold’ (i.e. status of IHLD). The Funds Transfer
will debit the original MORTGAGE ACCOUNT and credit the suspense account used for early maturity.
FT for repayment
below.

Euro
Validation and Authorisation of MG.PAYMENT records

Following the conversion process, the MG.PAYMENT record created to early mature the mortgage
contract will need to be validated and authorised.
Validation and Authorisation of EUR contracts

Validation and Authorisation of Funds Transfer transactions

Where a scheduled principal repayment has taken place and a new Funds Transfer transaction
created, which also has a status of IHLD, this will need to be validated and authorised.
Re-denomination of Swap Contracts

Once EU.CONTRACT.CONVERSION has been populated with details of the individual contracts to be
converted, conversion may be performed using the VERSION record provided. In the case of Swap
contracts, this will be SWAP, EUCC allowing the conversion to run on-line.
Note that the Version calls Input Routine EU.SW.CREATE.UNAUTH.DEAL which should be defined
as an EB.API record.

Euro
Currency IRS contracts will not be converted automatically. However all other types of contract will be
converted. Listed below is a more detailed explanation of each of the conversion processes.

Early maturity of a Swap contract takes place as soon as the contract is ‘INPUT’ via the relevant
VERSION and involves the following:
• Set the maturity date, asset frequency and liability frequency for maturity date schedules to the
required conversion date.
• The account number for a principal repayment will be set a suspense account (this may be an
internal account with a category of BAL.SUSP.CAT).
• Set the limit reference to be NEW.LIMIT.REF (as defined on EU.CONTRACT.CONVERSION).

In the case of a ‘loan’ contract, the limit reference should be amended to a ‘dummy’ reference of
non-reducing type. This avoids the old and new contracts both appearing under the same limit
reference and the apparent double exposure, and also ensures that if the loan was taken under
a reducing limit, the limit is not reduced again when the new EUR contract starts.
• Care must be taken to ensure that any principal repayment on the conversion date still takes
place.
Setting a SWAP for conversion

Euro

Upon validation of the early maturity VERSION, an additional routine will create the new EUR
denominated Swap contract based on the original contract and set it to ‘hold’ (i.e. with a status of
IHLD). The following is an outline of this creation process:
contract.
• The outstanding asset and liability principal amounts the conversion date will be converted to
EUR to become the respective principal amounts on new EUR contract.
• The value date of the new contract will be set to the early closure date and the Maturity date will
be set to the original maturity date.
• The drawdown account will be set to the suspense account (i.e. the internal account created
from BAL.SUSP.CAT in EU.CONTRACT.CONVERSION).
• The limit reference will be set to the limit reference of the original contract (i.e. the limit
reference held in OLD.LIMIT.REF in EU.CONTRACT.CONVERSION).
• The reference number of the new contract will be held in the LINK.REFERENCE.FIELD of the
original contract and vice versa.
No history records from the original contract will be converted.

Any principal increase or decrease scheduled to take place on the conversion date will not take place
because the contract fully matures on this date through a suspense account. A manual repayment is
therefore required in these cases, which will automatically be created by the conversion utility, at the
same time as the EUR denominated contract, and will be set to ‘hold’ (i.e. status of FHLD). The Funds
Transfer will debit the original principal liquidation account (for a loan) and credit the suspense
account used for early maturity. Entries will be vice versa for deposits. IRS Swap contracts have a
notional principal for which decreases will not be passed through accounts.

Euro
FT for repayment
below:

Euro
Validation and authorisation of EUR contracts

Validation and authorisation of Funds Transfer transactions

If a Funds Transfer transaction was generated to satisfy a scheduled principal repayment, this new
Funds Transfer transaction, which has a status of FHLD will need to be validated and authorised.

Euro
Euro and Securities

Changing the Reference Currency of Portfolios – SC application
T24 will allow the reference currency of a portfolio to be changed to a different currency where a fixed
rate exists between the two currencies. That is, the currency can only be changed to the currency
identified in the FIXED.CCY field of the currency record of the initial reference currency. The change
to the reference currency will be facilitated by the addition of a new field that allows the new reference
currency to be input. As the ‘no compulsion – no prohibition’ principle applies, individual portfolios will
be re-denominated at different times during the transition period. However towards the end of the
transition period it will be necessary to convert any remaining portfolios in one go. Therefore in
addition to manual input into the new reference currency field, a conversion record will be required to
select portfolios and add the new reference currency to a group of portfolios (selected by current
reference currency for example).
When the portfolio reference currency is changed, there will still be a requirement to reprint historical
valuation reports in the original portfolio reference currency. Therefore the original reference currency
will be stored. Also, as the historical values of the portfolio will be required, the historical valuation
totals, contributions, withdrawals and invested capital amounts will have to be recorded in the original
reference currency as well as the converted values in the new reference currency. New fields will be
added to store the values in the original reference currency with the existing fields for contributions,
withdrawals etc. containing amounts that have been converted at the fixed exchange rate to the new
reference currency (i.e. the Euro).
The details of individual items for historical portfolio reports are held internally on T24 on twelve files
called SC.CASH.FLOW01, SC.CASH.FLOW02, SC.CASH.FLOW12 (where the number at the end
signifies the month number). These files will not be converted to the new reference currency but
instead will be populated with new historical data over the year following the conversion of the
reference currency, thus facilitating the production of historical valuation reports.
As the value of a portfolio can be re-calculated online, the portfolio can be valued in the new reference
currency immediately when the conversion takes place. However in addition to the portfolio data, T24
uses the reference currency of the portfolio to calculate the cost of position. The cost of a security
position is held on the SECURITY.POSITION file. The individual security movements that gave rise to
that position are contained in the SECURITY.TRANS file. Both these files contain a cost amount in the
portfolio reference currency, the SECURITY.POSITION figure being calculated from the figure
contained in SECURITY.TRANS. Therefore as part of the process of converting the portfolio reference
currency, T24 will need to convert the cost amounts to the new reference currency on all the individual
SECURITY.TRANS records and then rebuild the SECURITY.POSITION figure from them using the
recalculation of cost of position functionality, which already exists in T24. If the SECURITY.TRANS
records are converted and then the SECURITY.POSITION record rebuilt, this will eliminate the
possibility of rounding errors between the SECURITY.POSITION record and the total of the
SECURITY.TRANS records.
The conversion of the reference currency will take place during the Close of Business. It will be done
by the EOD.SC.CONV.REF.CCY process that will normally run in the application Close of Business. It
is suggested that a portfolio be converted to Euro immediately after the production of a portfolio
valuation report that has been sent to the customer informing them of the change. This program will
use a list of those portfolios that have been flagged to change reference currency and process each
portfolio in turn. First it will copy across all the historical figures on the SEC.ACC.MASTER record,
then it will convert all the SECURITY.TRANS records for that portfolio and rebuild the cost of position

Euro
in the Reference Currency on each SECURITY.POSITION record of that portfolio. Once this has been
done the SC.FUND.FLOW file will be converted (which contains details of all contributions and
withdrawals for the portfolio) and the contributions and withdrawals figures on the SEC.ACC.MASTER
record will be recalculated. The other total figures on the SEC.ACC.MASTER file will be converted at
the fixed rate and finally the current value of the portfolio recalculated using the on-line portfolio
revaluation that already exists in T24.
The screenshot below shows a SEC.ACC.MASTER record for which a request is being made to
change the reference currency to EUR. Note that the field REFERENCE.CURRENCY is set to ITL in this
screen:
Portfolio before conversion

Euro
New reference currency set
Note that the NEW.REFERENCE.CCY field has been set to EUR on this screen with an effective date of
1st Jan1999 set in the NEW.RFCCY.EFF.DATE field.
The following screen shows the SEC.ACC.MASTER record after conversion of the reference currency:

Euro
Portfolio after conversion
Note that the REFERENCE.CURRENCY field for this portfolio has been changed to EUR and the
OLD.REFERENCE.CCY field has been set to ITL.
Group specification of reference currency change

A new utility program called SC.ACC.MASTER.CONV may be used to define a new reference
currency for a group of portfolio ids linked by a logical relationship. There are fields in the file that can
be used to specify the logical relationship. The application will work out a list of portfolios that have
been selected as a result of the relationship. These portfolios will be converted in the Close of
Business processing by the program EOD.SC.CONV.REF.CCY that runs in the batch suite
SC.BATCH.APP.
An example of this is shown in the screenshot that follows:

Euro
Setting multiple portfolios for conversion
Note that here we have requested that all portfolios with a REFERENCE.CURRENCY of DEM change
their REFERENCE.CURRENCY to EUR.
Changing the Reference Currency of Portfolios – AM application

It is assumed that the system has been prepared in advance to enable the completion of the above
processes. If not, then kindly refer to the chapter under “Configuring the System ready for the
Conversion” earlier in this document.
Changing the reference currency of individual portfolios (SEC.ACC.MASTER) records is done in
exactly the same way as in the SC application instructions in the previous section. This is performed
by updating both the NEW.RFCCY.EFF.DATE and NEW.REFERENCE.CCY fields with the effective
date of the change to the currency specified.
A BATCH job, EU.SC.CONVERT, will include an additional trigger to update the portfolio details for
thos SEC.ACC.MASTER records undergoing reference currency conversion into a T24 internal
concat file, AM.CONV.SAM.REF.CCY.
In addition, additional processing is required to trigger the conversion of reference currency amounts
that exist in various AM files that are used in enquiries and reporting.
These are –
• AM.VEH (Historic Portfolio Valuation)
• AM.INST.VEH (Instrument Valuation)
• AM.INST.PERF.DETAIL (Instrument Performance)

Euro
Before performing the COB, the AM.PARAMETER file should have the field, CONV.HIST.VAL, set to
“Y” to indicate that historical valuation data should undergo conversion to the new reference currency
where appropriate.
AM.PARAMETER – Setting CONV.HIST.VAL
In much the same way as the SC application, the running of a COB will now perform the necessary
updates.
After the COB, various enquiries can be checked to ensure the integrity of the newly reported EUR
reference currency.
The changing of the reference currency will affect certain enquiries and reports that detail the current
reference currency equivalents.
The following extracts show a number of example enquiries after the setting of the change of
reference currency.

Euro
Re-denomination of Securities – Both SC and AM applications

Re-denomination of debt instruments
Definition and Background
The term "re-denomination" means the change of the unit in which the amount of outstanding debt is
stated from a national currency unit to the Euro unit. It does not mean the altering of any other term of
the debt.
The narrowest definition of re-denomination is a simple conversion of a value expressed in one

currency unit to another using a conversion factor. For example a bond with a national currency unit
value of 2000 could be re-denominated as a bond with a Euro value of 312.600129 EUR
(2000/6.39795 [conversion factor] = 312.600129). How this figure is rounded would depend on what
method of re-denomination is being used.
In addition to re-denomination, it is open to issuers to consider re-nominalization mechanisms to

change the nominal value of their bonds to round Euro values. The trading and settlement
inconvenience that bonds with non-round nominal values would generate could then be avoided.
However, re-nominalization would materially change the economic value of a bond and therefore
would require the agreement of bondholders, and possibly some form of compensatory payment. It
might also be necessary to issue new bond certificates or amend existing ones.
T24 Approach
Re-denomination of debt instruments will be done using the corporate actions functionality. A selection
of DIARY.TYPE records are supplied in the data library item EURO.SEC.TOOL as example re-
denomination conversion records. These records cover the range of options for re-denomination of
debt instruments at both bond and holding levels with various rounding rules.
The rate of conversion of the bonds will be at the fixed exchange rate between the national currency
and the Euro. However for any currency where 1 of the national currency is worth less than 1 Euro
(which is the case for most ‘in’ currencies) there will be residual cash amounts to be dealt with. This
problem will be exacerbated where the trading unit of the security is more than one. T24 can deal with
this problem by using another corporate action for the cash compensatory amount. Where the RE-
DENOMINATION flag on the DIARY record is set to ‘YES’, T24 will perform some additional updates.
The first of this will be to take the information on the SECURITY.SUPP file record on the national
currency security and update the SECURITY.SUPP record of the new EURO security. Any yield and
dividend information will be converted at the fixed rate between the old and new security currencies.
At present it is not possible to re-denominate discount bonds within T24. All other forms of securities
are supported for re-denomination.
Short positions are not supported in re-denomination.
Running the corporate action will automatically update the OLD.SECURITY and NEW.SECURITY fields
on the old and new SECURITY.MASTER records.

Euro
Re-denomination Methods
Re-denomination can be achieved by two main methods, in combination with alternative rounding
rules.
1. Re-denomination on the basis of individual bonds.
Securities are converted at a bond level (minimum trading unit) using fixed conversion factors.
After conversion, Euro nominal amounts would need to be rounded to the new minimum
trading unit. This minimum trading unit would typically be 1 Euro cent or 1 Euro but could in
practice be any value. The issuer will also decide whether the new nominal amounts will be
rounded down, up or to the nearest minimum trading unit.
The sum of all individual bonds would then be calculated by the financial institutions and
matched against the total held at the central depository. Any difference between the totals
would then have to be accommodated by adjustments in the financial institutions trading
accounts, adjustments in individual holdings (possibly with cash settlement) or adjustment via
a correspondent bank. The adjustments would then ensure the sum of individual holdings
equals the converted total at the central depository.
Example - Bond Issue re-denominated at bond level with rounding to the nearest Euro cent:
An issue consisting of ten bonds each with a nominal value in national currency units ("ND") of ND
1,000 is split in three holdings:
▪ Holding "A" two bonds (ND 2,000)

▪ Holding "B" three bonds (ND 3,000 and
▪ Holding "C" five bonds (ND 5,000).
▪ Conversion factor of 1 EUR equals ND 6.39785.
Each bond is converted from 1000 ND to 156.3025079 EUR. This value is then rounded to the nearest
minimum trading unit (1 Euro cent) - 156.30 EUR.
The holdings would convert to:
▪ "A" 312.60 EUR (156.30 EUR * two),

▪ "B" 468.90 EUR (156.30 EUR * three),
▪ "C" 781.50 EUR (156.30 EUR * five).
In this example all holdings have lost 1 cent.

Euro
Clearly the larger the holding, the larger the loss (or gain) could be. The total amount of the issue after
conversion is 1563.00 EUR
How this can be achieved in T24
In order to achieve this in T24 the user will need to do the following:
• Set up a new DIARY.TYPE as shown in the screenshot below:

(Available in data library item EURO.SEC.TOOL)

Euro
DIARY.TYPE for Bonds using the Unit calculation method and legal rounding
• Set up a new SECURITY.MASTER record with the new details for the securities. Make sure that
the TRADING.UNITS on the new SECURITY.MASTER is set to 0.01. This will allow the minimum
nominal value of the security to be set to 1 Euro Cent.

Euro
New SECURITY.MASTER record
• Create a corporate action to convert the old security into the new security with a conversion ratio
specified as OLD.RATIO : NEW.RATIO, e.g. 177.6 : 1.

Euro
DIARY for re-denomination
• Any cash compensation will be distributed by the issuer as another corporate action.
1. Re-denomination on the basis of individual holdings
Securities are converted at a holding level using fixed conversion factors. After conversion,
Euro nominal amounts would need to be rounded to the new minimum trading unit. This
minimum trading unit would typically be 1 Euro cent or 1 Euro but could in practice be any
value. The issuer will also decide whether the new nominal amounts will be rounded down, up
or to the nearest minimum trading unit.
The sum of all individual holdings would then be calculated by the financial institutions and
matched against the total held at the central depository. Any difference between the totals
would then have to be accommodated by adjustments in the financial institutions trading
accounts, adjustments in individual holdings (possibly with cash settlement) or adjustment via
a correspondent bank. The adjustments would then ensure the sum of individual holdings
equals the converted total at the central depository.
Example: Bond re-denominated at holding level with rounding to the nearest Euro cent:
An issue consisting of ten bonds each with a nominal value in national currency units ("ND") of ND
1,000 is split in three holdings:

Euro
▪ Holding "A" two bonds (ND 2,000)

▪ Holding "B" three bonds (ND 3,000) and
▪ Holding "C" five bonds (ND 5,000).
Conversion factor of 1 EUR equals ND 6.39785.
Thus holdings convert after rounding:
▪ "A" 312.61 EUR

▪ "B" 468.91 EUR and
▪ "C" 781.51 EUR
The new total amount for the issue is therefore 1,563.03 EUR, equalling ND 10,000.03, and compared
with 1563.02510 EUR for a simple conversion of the original total amount. The rounding error is
clearly very small.
• Set up a new DIARY.TYPE as follows:

Euro
DIARY.TYPE for bonds using holding method and legal rounding
the TRADING.UNITS on the new SECURITY.MASTER is set to 0.01. This will allow the minimum
nominal value of the security to be set to 1 Euro Cent.

Euro
Creating the new SECURITY.MASTER

Euro
DIARY for the re-denomination
• Any cash compensation will be distributed by the issuer as another corporate action.
Example: Bond re-denominated at holding level rounded down to a minimum trading unit of 1 Euro.
Total debit issue = ND 1,000,000,000

Nominal value = 1,000
Conversion rate between ND and EUR = 1.36
Step 1
Convert the nominal value from ND to EUR 1,000/1.36 = 735.2941176.
Step 2
Round down to units of 1 Euro = 735.00
Step 3
Use the amount as new EUR nominal value therefore total issue size in EUR is =
(1,000,000,000/1,000)*735.00 = 735,000,000.00

Euro
Step 4
Calculate the EUR size from the ND issue size = 1,000,000,000/1.36 =- 735,294,117.65.
Step 5
Therefore the difference because of rounding = 735,294,117.65 – 735,000,000.00 = 294,117.65.
Step 6
294,117.65 EUR will be paid out as cash compensation.
Set up a new DIARY.TYPE as follows:

Euro
DIARY.TYPE for Bonds using the holding method and downward rounding
the TRADING.UNITS on the new SECURITY.MASTER is set to 1. This will allow the minimum
nominal value of the security to be set to 1 Euro.
• The cash compensation will be distributed by the issuer as another corporate action.

Euro
Re-denomination of equities
Definitions and Background
In the context of the equity markets, re-denomination is the conversion of the par value of the shares
into Euro. Such simple conversion may be combined with a change of the nominal value.
There are four main options available to a company that wishes to re-denominate its equity:
(a) Leave shares indefinitely with a par value of un-rounded Euro.

(b) Convert the share par value rounding to the nearest cent.
(c) Change the par value to a round number of Euro and have a common nominal value (Re-
nominalization).
(d) Move to non par value shares.
These methods should be applied to avoid mismatching between the converted nominal capital and
the total of converted par values.
T24 Approach
Re-denomination of equities will be done using the corporate actions functionality.
For equities, T24 is already capable of converting from one security position to another whilst retaining
the book cost of the security position. However where the RE-DENOMINATION flag on the DIARY
record is set to ‘YES’, T24 will perform some additional updates. The first of this will be to take the
dividend information on the SECURITY.SUPP file record on the national currency security and update
the SECURITY.SUPP record of the new EURO security. Any yield and dividend information will be
converted at the fixed rate between the old and new security currencies.
Running the corporate action will automatically update the OLD.SECURITY and NEW.SECURITY fields
on the old and new SECURITY.MASTER records.
Discussion and Examples
1. Leave shares with an un-rounded par value in Euro. This method is to convert the
share capital into Euro at the fixed conversion rate (rounding up or down to the nearest cent)
and then to divide by the number of issued shares keeping the share par value in Euro un-
rounded.
This method would avoid mismatching between the converted nominal capital and the total of
converted par values. No action would be needed on the part of the company apart from a
shareholders' resolution. The shares could be rounded up on some future occasion when the
company wishes to make a capitalisation issue. In order to avoid rounding errors it might be

Euro
necessary to have shares with par value specified to several decimal places. At first sight, that
does not seem to have any implication.
However, un-rounded par value might not be practicable, as the number of decimals will need
to be limited at least for reporting purposes (i.e. in the company's statutes). If a rounding takes
place, it would result in a change in the total share capital, which should require additional
action on the part of the company.
2. Convert the par value of each share into Euro, rounding to the nearest cent. This
method is to convert the share par value into Euro by applying the fixed conversion rates and
the rounding rules foreseen in the "235" EC Regulation, the nominal share capital being the
sum of the par value of the shares in the issue. If no specific action has been taken by a
company at the end of the transitional period, shares par value will be deemed to be
converted into Euro according to this method.
As a result of this method, the sum of the rounding adjustments on each individual share will
alter the nominal share capital of the company up or down. In order to correct this mismatch,
two options are available to a company:
i) Increase the capital by a capitalisation of reserves, or

ii) Decrease the capital by a transfer to reserves.
The amount of capital increase or decrease required will depend on the conversion rate and on
the nominal value of the shares and their number. The effect will be greater for low value
shares issued in large number.
3. Change the par value to a round number of Euro in order to have a common par
value (Re-nominalization). Following this method the share capital is converted into Euro
at the fixed conversion rates (rounding up or down to the nearest unit). The share capital is
divided into shares with a par value of 1 Euro each. In order to retain the original share of the
shareholder in the share capital, the Euro share capital and thus the number of shares will
have to be adjusted accordingly. This could be achieved either by a capital increase or a
capital decrease. The effect on capital will be even greater than for simple re-denomination by
rounding to the nearest cent.
Re-nominalization would change the number of shares issued by a company, thereby

changing apparent share prices.
Given that the price of a share bears no relation to its nominal value, there seems to be no
advantage in having a common par value across Europe. Moreover such harmonisation would
be very difficult to achieve given the differences in par values across Europe.
4. Move to Non Par Value shares. In an NPV system, shares are simply a fraction of the capital
stock. NPV shares make the conversion to Euro very easy. Once the company’s articles
have been modified to provide for NPV shares, indicating the share capital, the number of

Euro
shares issues and the minimum issuing amount, no further action is required to convert to the
Euro. With NPV shares there is no need for a physical exchange of share certificates, if any.
The share prices can be lowered by simply splitting and there is no need for a capital increase
or descrease.
Moving to NPV shares allows a company to avoid capital and cost intensive measures. NPV
shares are allowed by the second Community Company Law Directive, but in many countries
the relevant national legislation has not yet been put in place. In the short term, an amendment
to national legislation would be required to allow the NPV solution to be implemented.
EXAMPLES
The conversion of the share nominal value into Euro by applying the fixed conversion factor would
result in a nominal value expressed in Euro with several decimals. The examples below illustrate the
different effects according to the method used.
Company's share capital: 250,000,000 (expressed in national denomination "ND") divided into
50,000,000 shares with a par value of 5 ND assuming a conversion rate of 1.95591.
Option 1 "un-rounded par value"
▪ Share capital in Euro: 250,000,000/1.95591 = 127,817,742.13

▪ Share nominal value in Euro: 127,847,742.13/50,000,000 = 2.5563548426
Option 2 "Share nominal value rounded to nearest cent"
▪ Share nominal value in Euro: 5 / 1.95591 = 2.556354842503 (rounded to the nearest cent) = 2.56
▪ Share capital: 2.56 x 50,000,000 = 128,000,000 EUR
▪ Capital increase required = 182,257.87 EUR
Option 3 "Re-nominalization into shares with a nominal value of 1 Euro
Share capital: 250,000,000/1.95591= 127,817,742 (rounded to the nearest unit) divided into
127,817,742 shares of 1 Euro, previous share nominal value 5 ND = 2.56 EUR.
i) Capital Increase Option

The shareholder will receive 3 one-Euro shares for each 5 ND share held
▪ Total share capital = 150,000,000 EUR
▪ Capital increase required: 22,182,258 EUR (17.35 %)

Euro
ii) Capital Reduction Option

The shareholder will receive 2 one-Euro shares for each 5 ND share held:
▪ Total share capital 100,000,000
▪ Capital reduction required: 27,817,742 EUR (21.76%)
Option 4 "Non Par Value shares"
Share capital 250,000,000 ND represented by 50,000,000 shares each share represents 1/50,000,000
of the share capital after conversion:
▪ Share capital = 127,817,742.13 Euro
▪ Each share still represents 1/50,000,000 of the capital
How share capital re-denomination can be achieved in T24:
• Set up a new DIARY.TYPE as follows:

Euro
DIARY.TYPE for equities
• Set up a new SECURITY.MASTER record with the new details for the securities with a new par
value of the EUR equivalent of the old par value. In this example the old par value of 50 DEM has
been converted to 25.32 EUR.

Euro
specified as 1 : 1 and by setting up an appropriate par value set by the issuers.

Euro
DIARY for equities re-denomination
• If there is any cash compensation, capital increase or capital decrease then these will be new
corporate actions.
How Share capital re-nominalization can be achieved in T24:
• The creation of the DIARY.TYPE record will be the same as in the earlier example.
• Set up a new SECURITY.MASTER record with the new details for the securities.

Euro
specified as the ratio between the converted old par value and the new par value, in this example
1 : .769625.

Euro
DIARY.TYPE for re-nominalisation
Automated Creation of New Securities

It is already possible to create SECURITY.MASTER records from feeds at some T24 sites. However a
utility will be required to select SECURITY.MASTER records and copy them to new Euro denominated
securities.
The application SEC.MASTER.CONV will allow the user to select on the SECURITY.MASTER file
(using any field on the SECURITY.MASTER STANDARD.SELECTION record).
The usage of this application has been described in the next section ‘Re-denomination Process
Guidelines’.

Euro
Euro and Derivatives

The Euro conversion of derivatives should be regarded as two separate processes; firstly the closing
and cash settling of all open DX.TRADES(s) and secondly the conversion of all related reporting and
static data records.
The closing and cash settling of all open DX.TRADES(s) can be performed both online or as part of a
Close of Business, however the conversion of all related static data can only be performed within a
Close of Business.
Cash settlement for the purpose of this functionality has been defined as:
For futures contracts the effective realisation of any profit and loss due to involved parties
For options contracts the payment of any outstanding option premium.
Conversion will not occur to individual transactions where any of the following conditions exist:
• Unauthorised Deals
• Unauthorised Closeouts
• Diary Events Pending
• Open Orders
• Partially Filled Orders
• Unauthorised Orders
• Unauthorised records in any DX application
• Partial Closeout
DX Close of Business Conversion
The COB process EU.DX.CONVERT.CCY has been created in BATCH, which will run daily to convert
derivatives contracts and customers as per settings in the DX.EU.PARAMETER file.
The dates, on which particular exchanges are to convert, along with the conversion date for the
customer reporting currency are set up in the new DX.EU.PARAMETER file. The related fields
PSN.CNV.DATE, PSN.CNV.CCY and PSN.CNV.EXCH correspond to derivatives contract conversion,
and the related fields CUS.CNV.DATE and CUS.CNV.CCY correspond to the customer reporting
currency conversion. Note that for both sets of fields, more than one currency can be specified for
each run date.
However, it should be noted that by utilising this methodology ALL contracts registered against the
selected exchanges WILL be converted and any associated open DX.TRADE(s) cash settled unless
the user exempts the contract from conversion by setting SETTLEMENT.ALLOWED to “NO” in the
relevant DX.CONTRACT.MASTER record.
Should it be required that only particular trades that relate to the same contract be converted i.e. NOT
all trades, the user will need to “select” specific trades for conversion by utilising the on-line enquiries
provided (see later). Care is needed to ensure that trades that are NOT to be converted are not
subsequently captured by the close of business conversion.

Euro
DX.EU.PARAMETER showing input fields
Any derivatives contracts where either or both the CURRENCY and DELIVERY.CURRENCY are in the
converting currency will be made inactive by setting the LAST.VALID.DATE to the conversion date
subsequent to performing the conversion it will no longer be possible to enter into any new transaction
in the converted contracts.
DX.CONTRACT.MASTER record prior to conversion

Euro
DX.CONTRACT.MASTER after conversion showing LAST.VALID.DATE being set
However, where new contract definitions are required, which are based on existing terminated
contracts (e.g. where an exchange provides a newly denominated equivalent contract to aid the
conversion process), the user may copy the DX.CONTRACT.MASTER record of the originating
contract definition and substitute new field definitions where required e.g. CURRENCY. Any
DX.CUSTOMER records where the REPORTING.CURRENCY is in the converting currency will be
converted such that the REPORTING.CURRENCY becomes the new currency.
DX.CUSTOMER record prior to conversion
DX.CUSTOMER record after conversion

All deals held in, or delivering into the conversion currency should be cash settled prior to the Euro
conversion date.

Euro
Having run the converting close of business all transactions meeting the selection will have their status
marked as CLOSED, the corresponding DX.REP.POSITION records will be reversed, futures
profits/losses realised and/or outstanding option premiums paid and updates passed to all other
relevant DX records.
DX Online TRADE Conversion

Users may prefer to individually select transactions to settle, to enable this, new enquiries
EU.DX.POSITIONS.TO.CLOSE and EU.DX.TRADES.TO.CLOSE can be used to identify and perform the
cash settlement of individual transactions online where either the delivery currency or the trade
currency is the same as the local currency that is to be converted. It should be remembered that if
this method is utilised it is necessary to settle both sides of a transaction uniquely i.e. this is NOT a
back-to-back process.
ENQ EU.DX.POSITIONS.TO.CLOSE (first page)
ENQ EU.DX.POSITIONS.TO.CLOSE (second page)

Note from the screen shots above that both sides of the position can be seen separately and have to
be settled individually.

Euro
From the results of ENQUIRY EU.DX.POSITIONS.TO.CLOSE it is then possible to select “View

Transaction”, this will launch the ENQUIRY EU.DX.TRADES.TO.CLOSE which in turn displays the
individual DX.TRADE(s) that compose the position and from here the user can select “Mature” which
will allow the user to settle the transaction.
ENQ EU.DX.TRADES.TO.CLOSE
Setting a Futures Trade to settle after selecting "Mature" from

ENQ EU.DX.TRADES.TO.CLOSE
It is envisaged that this will not always be a preferred method to convert trades when there are a large
number of transactions involved.
However as already suggested, where it is required that only particular trades that relate to the same
contract are converted i.e. NOT all trades for a given contract, the user will need to use this method to
“select” specific trades for conversion. Care is needed to ensure that the trades that are NOT to be
converted are not subsequently captured by the close of business conversion.
Having matured both sides of the selected transactions their status marked as CLOSED, the
corresponding DX.REP.POSITION records will be reversed, futures profits/losses realised and/or
outstanding option premiums paid.
It should be remembered that the online process will NOT perform any changes to the static data held
on the DX.CONTRACT.MASTER or DX.CUSTOMER files. These conversions will only occur
when a subsequent related close of business is run where the DX.EU.PARAMETER record is
configured to do so.

Euro
Asset Management Account Conversion
Following the ECD (Euro Conversion Date), the account balances for the converted accounts are
maintained in EUR, and recorded as such in the AM Valuation and Performance files.
Historic valuation and performance data continue to have the old currency accounts. E.g. if a DEM
account is converted to EUR, the historic valuation and performance files AM.VEH.MM,
AM.INST.VEH.MM and AM.INST.PERF.DETAIL will continue to hold DEM account balances.
The procedure for converting accounts is described in the section ‘Re-denomination of Accounts’ in
this document.
The following example illustrates the affect of an account conversion on AM Valuations: -
The EU.CONVERSION.PARAM record AM.VALUATION.ACCOUNT should be recorded on

EU.CONVERSION.PROCESS.
EU.CONVERSION.PARAM
EU.CONVERSION.PROCESS
EU.CONVERSION.PROCESS cont’d

Euro
The valuation for Portfolio 1006-1 (Account no. 21733) prior to conversion is as follows: -
Enquiry AM.VAL.HIST
Account 21733 is set to be converted to EUR: -
AC.CCY.CONVERSION
After the account has been converted the valuation for 12/6/03 is recorded in DEM, under the
renumbered account number. The valuation after the account conversion is recorded in EUR under
the pre-existing account number: -
Enquiry AM.VAL.HIST

Euro
Re-denomination of AC.CASH.POOL (Cashpooling)
Introduction
Cashpooling operates on a single currency basis; whether foreign or local, all the accounts in a group
must be of the same currency. When one of the accounts in the group is subject to an account
conversion to change the account to EUR currency (and at the same time renumbering the original
account) this can complicate the cashpooling operation.
In order to prevent any cross-currency complications of having mixed currencies in a group, which has
values, based on the group currency it is essential that the integrity of the group be maintained.
As part of the EU conversion any client who has cashpooling records in the currency being converted
to EUR will need to activate the BATCH record EU.ACCP.GROUP.PARAM and set the run date to
today.
EU conversion of cashpooling is closely tied to the account conversion process; once an account is
converted the cashpool eod procedures will check whether the account is part of a cashpool group. If
it is then the group may be flagged as inactive as a precaution. This is done by setting the field
EUCC.PROCESS to Yes, this will prevent any records in the group being modified and will exclude the
group from the cashpool processing until it is made active again. Once all the accounts in the group
are converted the cashpool records (AC.CASH.POOL) that had been placed on hold can be
amended/authorised and the cashpool processing for the group can resume.
Workflow of conversion process
We can consider that there are two basic scenarios:

• Full account conversion
• Partial account conversion
Full Conversion
Full conversion would mean that either all the accounts are converted en masse or in respect to
cashpooling all the accounts in a cashpool group are done at the same time. Depending on volumes
of cashpool records in use a full selection of the cashpool accounts may be the best option, in larger
volumes it may be desirable to convert group by group.
Example
We selected a group called SRP2, note the currency was ‘old’ currency CHF and was a working
sweep.

Euro
Group SRP1

Euro
Checked the accounts used in the group including those such as the main.master, which may not be
on any sweep record.
Highlighted accounts used in group SRP1

Euro
After cob the group currency is now EUR
Note the AC.CP.GROUP.PARAM record has been changed to EUR but the field EUCC.PROCESS
is not marked as YES, meaning the group can be input to, modified and authorised.

Euro
Sweeps in the SRP2 group
Checking on the AC.CASH.POOL records that exist in the SRP2 group we have three on hold, as
expected we can amend these records adjusting the new sweep amounts to more sensible rounded
amounts.

Euro
Modifying a converted AC.CASH.POOL record
As can be seen on the above screen the sweep is now EUR based (even though the account titles
were not changed in the conversion these are EUR accounts). The amounts would usually be made
more sensible as a client is not expecting a balance limit of EUR 57.14 but would be more likely to
choose EUR 50.00 as a check.
All the groups AC.CASH.POOL records were then amended and authorized ready for the next cob.
Doing a whole group at once reduces the impact and can have the group up and running in less time.
Since the records are effectively new the work files will be checked after the next cob.

Euro
Updated EUR sweep record

Euro
As can be seen now on the updated sweep record updated EUR sweep record screen above the
LAST.MAINT.DATE is set to the conversion date so effectively no adjustments caused by back valued
entries will be catered for prior to that.
The account before conversion and after conversion is checked using ENQUIRY STMT.ENT.BOOK,
WHICH shows the entries and correct conversion.
Renumbered ‘old’ account
Here the evidence shows the account was performing sweeps until the conversion where the balance
was transferred to the new account.

Euro
Account is now in EUR
The account number for the EUR account is the existing number, the balance transferred is shown
and the change in the sweep limits has itself forced a sweep to reduce the balance as required.
Partial Conversion
Partial account conversion relates to the actions where one or more accounts are converted by in so
doing this creates a group, which has both old currency and EUR accounts. Since the group is
suspended when this condition occurs and no sweeps are made until the group is re-activated the
conversion of the remaining accounts would need to be prioritised.
Selected group called SRP1, noted the currency was set to ‘old’ currency of CHF and was working.
Took one of the accounts used in the group as a conversion candidate and entered the account
conversion details.

Euro
AC.CP.GROUP.PARAM for SRP1
This group has several accounts in and is in the old currency ‘CHF’. Checked on the accounts used in
the group and selected one for conversion.
AC.CASH.POOL records for group SRP1

Euro
Account 41807 is being used so selected for conversion
Entered details of account 41807 in AC.CCY.CONVERSION

Euro
After running the cob the AC.CP.GROUP.PARAM record is checked and noted that it has been
flagged as being converted by using the field EUCC.PROCESS set as YES. Also, note the audit fields
reflect the update by the conversion process.
Post cob AC.CP.GROUP.PARAM for SRP1
Note the field EUCC.PROCESS is flagged YES; this means the group is inactive until all accounts are
converted.

Euro
Sweep records in group SRP1 are IHLD
Trying to modify one of the records
Until all the accounts in the SRP1 group are converted any updates to the sweep records is blocked
as shown above.
The previous CHF record is now on the history file of AC.CASH.POOL with the alternate account
number 941807

Euro
Return Sweeps
Certain sweeps are configured to make sweep during the cob and return the funds the next morning,
an example would perhaps be where all surplus funds on a current account are swept up to a savings
account each night to attract interest but the balance is returned the next morning to provide a working
balance.
In the example below we selected a cashpool group where the funds are returned each morning after
the sweep.
AC.CP.GROUP.PARAM before conversion
Checked that there are active sweeps linked to the group.

Euro
AC.CASH.POOL records for group SRP1RTN
Checked the sweep type set on the records:
Sweep type used is RSURPLUS

Euro
Checked settings on AC.SWEEP.TYPE record RSURPLUS is set to return at start of day.
AC.SWEEP.TYPE is a return type

Euro
Checked the ENQUIRY STMT.ENT.BOOK on an account in the group, as it was before conversion to
show the sweeps were processed and returned.
Sweeps on Account before conversion
The above screenshot shows the ‘old’ renumbered account. We can see evidence of the correct
working as follows:
Typical process
27 Aug 01 CHF 25,000 credited to account to give working balance
27 Aug 01 CHF 24,900 surplus swept to a/c 41912
28 Aug 01 CHF 24,900 returned
During conversion cob

28 Aug 01 CHF 24,900 surplus swept to a/c 41912
28 Aug 01 CHF 100 balance converted to EUR and posted to new EUR account
This leaves the ‘old’ renumbered account balance at zero.
New account:

Euro
Enquiry STMT.ENT.BOOK on new EUR account
We can see from above that the following has correctly been processed:
Conversion & standard sweep entries

28 Aug 01 Balance from old account credited CHF 100 / EUR 57.14
29 Aug 01 CHF 24,900 equivalent (EUR 14,228.57) is returned
31 Aug 01 Standard sweep is now made EUR 14,225.71
03 Sep 01 Standard return of EUR 14,225.71 is made.
Note the old sweep amount was CHF 24,900 / EUR 14,228.57 based on a maximum balance check of
CHF 100.00/; the converted record changed the check to EUR 57.14 which has been manually
amended to EUR 60.00 for simplicity.

Euro
Post conversion records checking
AC.CP.GROUP.PARAM after conversion
We can see here that the group is now a EUR group and the audit details confirm the conversion.

Euro
One of the sweeps in the group
Confirmation that the sweeps are now in EUR, are continuing to cycle and the LAST.MAINT.DATE
reflecting the changes made, note the amounts have been changed to rounded EUR amounts instead
of the system calculated equivalents.

Euro
Original AC.CASH.POOL in history
The original AC.CASH.POOL record, saved using the renumbered account, is in history.
Testing Onsite
If testing onsite then be aware that the group field EUCC.PROCESS is set if one or most of the
accounts are converted. If all accounts are converted the cashpool records will be on hold and need
amending & authorising and the field will be empty.
The presence of the field makes the group inactive.

Euro
Re-denomination Process Guidelines
Before 31/12/1998
IT Preparation
The IT department will need to do the following in order to use the guidelines explained here.
1. Set up Local Reference fields on the LOCAL.TABLE file. Sample records for these have been
provided in the data library ‘EURO.SEC.TOOL’. The screenshots shown give instructions for
setting up these records (all instructions are for amending the GB.DESCRIPTION field):
LOCAL.TABLE for conversion method

Euro
LOCAL.TABLE for New Interest Basis
LOCAL.TABLE for Nominal Rounding

Euro
LOCAL.TABLE for Minimum Unit
LOCAL.TABLE for New ISIN number
LOCAL.TABLE for New Security Number

Euro
LOCAL.TABLE for Cash Rounding
LOCAL.TABLE for Par Value Rounding
2. Link the local reference fields into the SECURITY.MASTER file layout using the
LOCAL.REF.TABLE record. This has been illustrated in the screen shot shown below:

Euro
Linking the LOCAL.TABLE records to the SECURITY.MASTER file
3. Set up the addresses for the local reference fields added in step 2 above into the
EU.PARAMETER record. This has been illustrated with a screen shot shown below:
Defining the local reference locations on the EU.PARAMETER record
Back Office Preparation

Euro
The back office will need to do the following in order to use the guidelines explained here.
1. Use SEC.MASTER.CONV in ‘TEST’ stage. This has been illustrated with a screen shot shown
below.
TEST of SEC.MASTER.CONV

Euro
TEST results
(Note that the user may use the sample routine SC.MAS.CNV.ID for the purposes of generating the
new security master id. Refer to the helptext for ID.ROUTINE for further details; this program has been
provided in the Data library ‘EURO.SEC.TOOL’).
2. Use SEC.MASTER.CONV in ‘PREPARE’ stage. This phase allows the user to populate NCU
security record’s local reference fields with the values specified in the corresponding fields on the
SEC.MASTER.CONV record. This has been illustrated in the screenshot below:

Euro
PREPARE phase
On authorising the above record the T24 system will return the following:

Euro
Confirmation of SECURITY.MASTER update
If the above is replied with an ‘OK’ the result will be that all the selected security master id records will
be changed and put on a hold status as shown below:
Updated SECURITY.MASTER records
3. The above step 2 will result in the update of the selected security master records. An example of
this has been shown below:

Euro
Populated Local Reference fields on the SECURITY.MASTER
4. The final step in this stage of events is to input and authorise the NCU securities put on hold as
shown above. This step would therefore have captured the required rules for re-denomination of
the security on the security master record itself setting a stage for further automation.
Starting 1/1/99
IT Preparation

Euro
In order to continue with the process of re-denomination the user will need to set up the DIARY.TYPE
records that will be used by the process. (Note these records have been included in the data library
‘EURO.SEC.TOOL’).
DIARY.TYPE record

Euro
DIARY.TYPE record

Euro
DIARY.TYPE record

Euro
DIARY.TYPE record

Euro
DIARY.TYPE record

Euro
DIARY.TYPE record

Euro
DIARY.TYPE record

Euro
DIARY.TYPE record
Back Office Preparation
Starting the 1st of Jan 1999 the new security master records for the security denominated in the EUR
currency can be set up. This has been entailed as below.

Euro
1. Creation of EUR security master records. In order to achieve this the user needs to input and
authorise the SEC.MASTER.CONV record with the process stage set to ‘CREATE’ this time.
This has been illustrated in the screenshot below.
CREATE phase
2. On authorisation of the above record the application SEC.MASTER.CONV would result in the
following security master records in IHLD status as shown below.

Euro
List of updated SECURITY.MASTER records
3. The user now needs to input and authorise each of the records created in the step above. This
may be achieved with the help of an EBS.AUTO.FUNCTION.
4. Once the NCU and EUR securities are in place, the user would be ready to now perform the
actual process of re-denomination.
5. In order to perform the re-denomination the user will need to perform a corporate action on the
NCU security as shown in the screen shot below. Note that using this version DIARY, EURO
(provided in the data library item EURO.SEC.TOOL) in combination with the set-up described
above, only the security number and the date of the event need to be input by the user. The
version initially defaults the value of EU.DEFAULT into the EVENT field, but upon validation this
is replaced by the appropriate DIARY.TYPE name for this security's re-denomination. This is
driven from the local reference fields on the SECURITY.MASTER, when set-up as described
above.

Euro
Created DIARY record
DIARY record after defaults

Euro
6. On having authorised the DIARY record and selected the creation of the ENTITLEMENT
records on-line the user would need to authorise each of the ENTITLEMENT records.
Resultant ENTITLEMENT records
7. Finally the user will need to perform a rebuild of the valuation records.

Euro
Realisation of In-Currency Forex Profit and Loss

At the start of the transition period, the exchange rate between member currencies will be irrevocably
fixed. As a result, the profit or loss due on deals involving two in-currencies can be realised
immediately. According to national convention, it may be required to realise this figure in the year
balance sheet for the year-end immediately prior to the start of the transition period (i.e. the end of
1998).
In T24 the facility to realise the profit/loss due is available on an individual contract basis, depending
on the type and use of contract.
Realised Profit and Loss Categories

The REVALUATION.PARAMETER table allows Profit and Loss category codes to be defined for each
product, for use when P&L is to be realised immediately. Internal account category codes can also be
specified for posting exchange adjustment entries for realised Profit and Loss.
REVALUATION.PARAMETER

Euro
Fixed profit and loss categories should be specified for the APPLIC.ID of FX, FX.SP and FX.RB.
Selection of Contracts to be realised
The field REALISE.FIX.PL on the FOREX application is used to denote whether or not the profit or
loss should be reported as realised when the deal involves two in-currencies. The date of this
realisation is recorded in the new FIX.PL.REALISED field.
Each contract to be realised should be updated with a Y in this field. The selection of contracts to be
realised can be performed prior to the start of the transition period.
Realisation of FX contract
Realisation Process
The Close of Business revaluation process will perform the realisation of profit and loss for those
contracts flagged. Realisation will only take place when both currencies of the contract are fixed, and
the system is either the working day immediately prior to the FIXED.START.DATE or after this date.

Euro
If realisation is to take place, existing unrealised profit and loss is posted to the FIX P&L categories. If
the contract performs accruals (for REVALUATION.TYPE SL, IN, IH, SF), the accruals are completed
for the life of the contract.
No further accrual or revaluation takes place for these contracts until maturity is reached.
A daily report ‘EU.PL.REALISED.TODAY shows the P&L realised.

Euro
Recommended Testing for the Euro

As mentioned in the introduction it is recommended that certain elements of the Euro module be
tested with TEMENOS personnel in attendance. The following is list of items, which can be tested, and
those, which will need assistance:
Items which can be tested
► Definition of Euro, Fixing Currencies; use of exchange rates

► Display of Euro equivalent
► Use of Euro Equivalent in ENQUIRY, DE.FORMAT.PRINT, DE.FORMAT.TEMPLATE
► Auto Payment Account
► General Suspense Account
► ERI
► Conversion of Money Market contracts
► Conversion of Loans and Deposit contracts
► Conversion of MG Mortgage
► Conversion of Swap contracts
► Change of Portfolio reference currency
► Re-denomination of Securities
Check with TEMENOS before commencing testing
► Automatic Account Conversion

► Bulk contract and account conversion
► Conversion of accounts
Items where TEMENOS assistance is recommended
► Local currency conversion

Euro

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Euro

Uploaded by

Copyright:

Available Formats

TEMENOS T24

Information in this document is subject to change without notice.

Copyright 2005 TEMENOS Holdings NV. All rights reserved.

TEMENOS T24 User Guide Page 2 of 193

Asset Management Account Conversion......................................................................................... 145

TEMENOS T24 User Guide Page 3 of 193

Testing the Euro Module

TEMENOS T24 User Guide Page 4 of 193

TEMENOS T24 User Guide Page 5 of 193

Exchange Rates and Euro Set-up

Fixed Exchange Rates / Triangulation

T24 Conversion of In-Currency to In-Currency

TEMENOS T24 User Guide Page 6 of 193

T24 Conversion of In-Currency to euro

T24 Conversion of Euro to In-Currency

• A Euro amount will be converted to an In-Currency amount by multiplying by the FIXED.RATE.

T24 Conversion of In-Currency to Out-Currency

• The In-currency amount is converted to a Euro amount by dividing by the FIXED.RATE.

T24 Conversion of Out-Currency to In-Currency

TEMENOS T24 User Guide Page 7 of 193

• The result is held to six decimal places.

Use of different rates between In-Currencies and Euro

Quotation of rates involving the Euro

T24 CURRENCY table

TEMENOS T24 User Guide Page 8 of 193

Base Currency Rank

Defining the Euro Currency

TEMENOS T24 User Guide Page 9 of 193

You may also wish to define a GEOGRAPHICAL.BLOCK to hold all In-countries.

Country record for EU

The BASE.CCY.RANK should be set as described above.

TEMENOS T24 User Guide Page 10 of 193

CURRENCY.PARAM record for EUR

Restricting use before the start date

TEMENOS T24 User Guide Page 11 of 193

CURRENCY record for EUR

TEMENOS T24 User Guide Page 12 of 193

HOLIDAY table for EU

TEMENOS T24 User Guide Page 13 of 193

PERIODIC.INTEREST for EUR

Local Currency is Out

TEMENOS T24 User Guide Page 14 of 193

FORWARD.RATES for EUR

Fixing In-Currencies to the Euro

Use of Expected Fixed Rates

TEMENOS T24 User Guide Page 15 of 193

Adding Rates to an In-Currency

Setting the Expiry Date for a Currency

TEMENOS T24 User Guide Page 16 of 193

Summary of 'IN' currencies

Forward Exchange Rates

TEMENOS T24 User Guide Page 17 of 193

Displaying Euro equivalents

Display of Euro equivalent in applications

The Euro equivalent will not be displayed if:

• There is already enrichment for the field.

TEMENOS T24 User Guide Page 18 of 193

Adding a EURO enrichment to a version

Displayed Euro equivalent

Displaying Euro Equivalents in Enquiries

Fixed (Euro) Equivalent

TEMENOS T24 User Guide Page 19 of 193

Input Amount fields

Adding Euro equivalent to an enquiry