Академический Документы
Профессиональный Документы
Культура Документы
V 1.0 (2014-03-22)
Table of Contents
Part 1 Newsletter____________________________________________________________ 4 Part 2 Release Note __________________________________________________________ 5
General Description ________________________________________________________________ 5
General _________________________________________________________________________________ 5 New Features ___________________________________________________________________________ 5 Modifications/Enhancements of Existing Features _____________________________________________ 6 Bug Fixing ______________________________________________________________________________ 7 Short Term ______________________________________________________________________________ 8 New Features ___________________________________________________________________________ 8 Modifications/Enhancements of Existing Features ____________________________________________ 10 Bug Fixing _____________________________________________________________________________ 10 Frequently Asked Questions ______________________________________________________________ 11 Bonds __________________________________________________________________________________ 12 New Features __________________________________________________________________________ 12 Modifications/Enhancements of Existing Features ___________________________________________ 12 Bug Fixing ____________________________________________________________________________ 13 Known Issues __________________________________________________________________________ 14 Loans __________________________________________________________________________________ 14 New Features __________________________________________________________________________ 14 Modifications/Enhancements of Existing Features ___________________________________________ 15 Bug Fixing ____________________________________________________________________________ 15 Swaps__________________________________________________________________________________ 15 New Features __________________________________________________________________________ 15 Modifications/Enhancements of Existing Features ___________________________________________ 16 Bug Fixing ____________________________________________________________________________ 16 Exposure _______________________________________________________________________________ 17 New Features __________________________________________________________________________ 17 Modifications/Enhancements of Existing Features ___________________________________________ 17 Bug Fixing ____________________________________________________________________________ 17 OCP ____________________________________________________________________________________ 18 New Features __________________________________________________________________________ 18 Rates and Prices ________________________________________________________________________ 18 Modifications/Enhancements of Existing Features ___________________________________________ 18 Payments ______________________________________________________________________________ 19 New Features __________________________________________________________________________ 19 Bug Fixing ____________________________________________________________________________ 19 Accounting _____________________________________________________________________________ 19 Bug Fixing ____________________________________________________________________________ 20
2|Page
Financial Applications
3|Page
Financial Applications
4|Page
Financial Applications
General New Features 1. The number of decimals used for the display/capture of rates, prices, and amounts was reviewed once more, now implemented as fully parametrisable. For payment amounts, now also the amounts in TWA are handled based on the number of decimals defined for the currency of the payment. Our current database standard is 2 for payment amounts, 5 for interest rate codes, 7 for exchange and cash rates and 8 for Prices. There is an upper limitation set to 9 decimals. If the number of decimals is changed, old Deals still will show the rate precision using the old standard, (the create time of the message is relevant). If a new Deal is created, the Remarks always reflect current database settings. An information about the current parameter settings related to the precision is returned by the Mercury Service getInfo(), the key being DealwarePrecision. 2. Up to now, Ticket data was containing the Registration Date. With TRP January 2013, the attribute storing the Registration Date has been changed and in now keeping the Registration Time. The Registration Time is shown in List Tickets, Pending Confirmation and in the Ticket Printouts/Previews for Short Term Tickets (including the new FS Ticket). 3. The Calendar Control, used in different Dealware dialogs for the selection of dates, has been changed in order to be in line with the ISO standard weeks are now starting on Mondays, and not on Sundays, like previously. 4. To make screenshots from Dealware easier to analyse, the DATAVERSION has been included as additional information in the status bar. 5. An additional parametrisable DateAdjust has been created, in order to restrict the number of bank working days between an interest accrual date and the corresponding interest payment date for MM/LN/BN/BO. This restriction is working in both directions, back and forth. A default value of 5, if no specific parametrisation is found. An information about the current parameter settings returned by the Mercury Service getInfo(), the key being DealwareDealDateAdjust.
5|Page
Financial Applications
Modifications/Enhancements of Existing Features 1. User-defined columns in List Tickets. By using a specific substring format in the comments (<ColumnName>=[ColumnContents]), users are able to dynamically add more columns into this dialog. Previoulsy, <ColumnName> was restricted to 7bit ASCII text without special characters and whitespaces and the whitespace being the only allowed separator. Therefore, e.g., userdefined Cyrillic Column Names were not possible. This has been changed now: The column name can contain any character except whitespaces, ;, ,, and *,; additionally, the set of allowed delimiters is now whitespace, ;, and ,. 2. Previously, just an empty page was shown by TWA if logging in with Read-Only access rights. Now, users can login, but cannot do anything more, and a message is displayed to explain the situation, e.g. asking them to ask for a permission change. 3. In the login dialog, where the password can be changed, there is now a help button explaining the password complexity rules, in the same manner as it was displayed up to now after a missed attempt by the user, but allowing an earlier information. 4. In the Account dialog, the Product Type control has been moved up and is located now directly under the Account Type control. This has been made to facilitate the Create if Accounts, where the Product Type represents a kind of Account Sub-type or sub-category. 5. Additional Party Types have been included: CentralBank, DomesticBank, PublicInstitution. They are needed in relationship to the implementation of Automatic Bookings, and in order to make a differentiation between the Institutions ruling a certain currency (FinancialCentre) and the Central Banks acting in a similar role as a Commercial Bank. 6. An additional Account Type has been created: Transitory. This Account Type is needed as counter-account for payments to and from Loro Accounts. Deal Accounts of type Transitory can be created, with the following restrictions: Own Bank as Account Holder as well as Account Provider, Product Type Standard, related to Trade Group TG900 (NoRisk). In TRP January, 6|Page
Financial Applications
Bug Fixing 1. The Mercury Service getCounterPartyInfo() was not returning updated information after a limit registration; realized during debugging of IW load in PCH (loan failed after a limit update via DW, only solution was restarting Mercury). Fixed. 2. Previously, the crosscheck of access rights during login was not deep enough, the Valid-To-Date was not taken into account. Corrected. 3. For databases parametrised years ago, some Dealware users may not have a defined Short Code. For Users without Short Code it is not possible e.g. to change the Dealer Type. The Short Code is needed only for Front Officer when registering a Trade, before sending this Trade to confirmation by Back Office; in this pre-ticket situation, the temporary Deal ID is constructed based on the TimeStamp and the Short Code. Following change has been implemented: When a Dealer Type is changed, and there is no Short Code, the Short Code field is automatically filled with a short code proposal and the user has the possibility to edit this proposed short code. The Short Code control is enabled in the described way whenever there is a change in the Dealer Type or a change in the Short Name of the Dealer. 4. There is a specific scenario where the user can avoid the forced shutdown which we included for users not shutting down Dealware in the evening, before leaving. If there is an open dialog, with not applied changes, the functionality of the forced shutdown displays in the morning a message 7|Page
Financial Applications
Short Term New Features 1. The new feature refers to Short Term Deals (MM including Rollover, FX, TR, CI, CH, CN): Short-term tickets still not confirmed by Back Office, but already Sent by Front Office are now displayed also in the list of "Pending Confirmations", and - when selected - the "Confirm" button enables. If the "Confirm" button is used or if the selected Ticket is double-clicked, in the List of Confirmations, the Ticket Printout is displayed, with an additional header allowing the registration of a Comment, and the usage of the "Reject" or the "Confirm" button. If the 8|Page
Financial Applications
9|Page
Financial Applications
Modifications/Enhancements of Existing Features 1. In Ticket Printouts related to Short Term Tickets (incl. FS), the field Registration Date has been changed to Registration Time. For Tickets already registered with Dealware 4.3.2 or higher, where the Registration Time is captured, the exact timestamp will be displayed. For Tickets registered before, the date and a text message is displayed in the box Registration Time (e.g. 2014-02-20 (Registration Date)). 2. As the menu option Cash Nostro (DealTickets related to cash deposits/withdrawals to/from Nostros) is now required by almost all Banks, this option existing since Dealware 3.8.0 - has been included as standard. The menu option can be removed for specific Banks, on demand, via a compiled script.
Bug Fixing 1. Realized during the testing phase in PCB UKR, but later also mentioned by users in PCB DEU: If Operative System User Names do contain non-7bit-ASCII symbols, TRP April, TRP August, and TRP October have problems with Logins, the attachment of Files to Deal Tickets, the usage of the SWIFT confirmation messages, comments/remarks related to Deal Tickets, and some more features related on one or the other form to paths.
10 | P a g e
Financial Applications
11 | P a g e
Financial Applications
Modifications/Enhancements of Existing Features 1. List Bond Deals has been enlarged with the columns Notional Traded, Trade date, Maturity Date) and allows filtering by Issuer, Currency, ISIN, Counterparty. 2. List Registered Bonds improved, the column Notional has been renamed to Notional Owned, and the report allows filtering by Issuer, Currency, ISIN, Bond Type. 3. For BN-Bonds, the Payment Agent has been removed (Database, Mercury, and TWA). For BOBonds, the Counterparty is called Payment Agent, based on his role, like before. 4. It is possible now to refresh the settlement accounts in a user-friendly way. An extra control has been placed near the [SEND] and [UPDATE] buttons, allowing users optionally to fix a new account for the We receive On part. The account WeReceiveOn can be changed for next next 12 | P a g e
Financial Applications
Bug Fixing 1. Bug with the cursor when choosing a date. In the example reported, the Maturity Date falls on a Sunday; the cursor was active for Saturday but not for Sunday, and the user was forced to enter manually the date. 2. The Trade Date must now be on or before the Settlement Date of a bond. 3. Previously it was possible to register Starting Date earlier than Trade Date, but not anymore. 4. The First Coupon Date has been restricted to be strictly greater than the Issue Date and less or equal to the Maturity Date. 5. Based on a problem in Beta Test Unit, for a zero bond which could not be saved: Now, an error message is shown when the Bond is Adjusted and the maturity date is on a holiday, causing the [SAVE] button to be disabled.
13 | P a g e
Financial Applications
Loans New Features 1. For Loans (and technically also for Bonds, but probably not needed), a new database attribute has been added, allowing the possibility to make a differentiation between payment plans having just one single principal repayment and payment plans initially agreed with several
14 | P a g e
Financial Applications
Bug Fixing 1. During the registration of a new Loan, it was possible to change the counterparty and/or the currency, without a removal of the data registered before in the We Pay To control. Fixed, now the We Pay To control resets in these cases.
Swaps New Features 1. A special Deal Ticket printout has been implemented for FX Swaps, containing details for the Near Leg as well as for the Far Leg (including the FX Ticket ID and Status) in separated boxes. The FS-Deal ID is now included in the header part and the Ticket Type is displayed as FX SWAP DEAL TICKET. In the box where the activity is shown for FX Tickets, we do have in this case SWAP. Swap Points and Profit/Loss are displayed in a box between the Legs and the Signature part. This Ticket Printout can be viewed from List Tickets (FS mode) as well as Swap using the standard button *SWIFT/Ticket+.This new FS ticket layout includes also the Registration Time (instead of the previously existing Registration Date), displaying a timestamp for Tickets registered with Dealware versions 3.2 or higher. For Tickets registered before the change of the database field was implemented, the date and a text message is displayed in the box Registration Time (e.g. 2014-02-20 (Registration Date). This Ticket Printout can be reached via the button *Ticket/SWIFT+ from the FS-Ticket dialog or from List Tickets in FS-Mode. 2. New mode FS (swap) included in List Tickets. In order to be able to include certain details relevant only for the FX Swap case, this separated mode has been included. This special mode can be reached via selection of FS in the Deal Group control or by using FS as prefix for the search string in Ticket ID Prefix. The mark [ERROR9] is displayed for cases where there is no matching amount between the Near Leg and the Far Leg (should not be the case, but was technically possible before); for these Swaps, the 2 FX Tickets need to be unlinked: Use [Open 15 | P a g e
Financial Applications
3. Remarks can now be attached to the FS-Ticket itself (new media message type called SwapIndividual). This kind of remarks are created being in the TicketPrintout (similar as we are doing for LN/BO/BN), and stored simultaneously in both FX-Tickets; they are visible from each of the involved FX, marked with the prefix *SWAP+. For this type of remarks, the Print Flag cannot be changed from inside one of the FX-Tickets. Re: messages can be created in one of the FX but are then only valid for this FX (and not visible in the FS or the other FX ticket). The Print Flag can be changed inside the FS Ticket Printout. No additional Re: messages can be created inside the FS (this feature can be added on demand later).
Modifications/Enhancements of Existing Features 1. Reviewed Swap dialog: All references to a Deal for both legs changed to Ticket. FS Swap Ticket ID displayed now additionally above both legs, SwapPoints/Profit/Loss line moved below both legs. *Details+ buttons for both legs removed, new button *SWIFT/Ticket+ created, opening the Ticket Printout for FS. 2. For List Tickets, in modes (all exc. swap) and FX, the underlying FX Tickets are shown instead of the FS-Ticket, but marked like e.g. FX-20710 *FS+. 3. For List Tickets, uniformly for all modes, Short Term Tickets (incl. FS) can be reached via the button *Open Ticket+, and all Ticket Printouts can be reached via the button *Ticket/SWIFT+
Bug Fixing 1. Some minor bugs fixed in List Tickets, for FX Swaps.
16 | P a g e
Financial Applications
Exposure New Features 1. The third grid inside Product-Specific Exposure report has got a button for showing details of the mentioned Tickets, similar as already before existing for Country Exposure and Daily Exposure, but also including information for e.g. Nostros (the Account Statement is shown).
Modifications/Enhancements of Existing Features 1. Counterparties with Exposures but without at least Global Exposures should theoretically - not exist. Previously, they were not shown in Product-Specific Exposure. Now they have been included. When there is no Limit defined, the exposure shows up as negative amount in Free Total Limit. 2. Counterparties without Exposures and without Limits are not anymore shown in the first grid of Product-Specific Exposure. 3. In Product-specific Exposures, when a Trade Group is selected in the second grid, the status shown for the 3rd grid is now displayed as Retrieving data (as it can be quite lengthy to fill the 3rd grid with all the Deals making up the Exposure shown in the second grid).This way the user knows that something is being calculated. 4. In Product-specific Exposure, Daily Exposure, and Country Exposure, the previously displayed Complete Name for a Financial Party has been replaced by the Short Name .
Bug Fixing 1. By mistake, the report Product-Specific Exposure was showing always figures as of today, independently of the Report Date selection in the header part of the dialog. This has been fixed, the specific settlement date is now taken into account for the decrease of an exposure. 2. In previous versions, Nostros being overdrawn were also taken into consideration for the Exposure, with their real (negative) balance, leading to wrong (too low) exposures and high unused limits. Fixed now. 3. A bug was fixed related to the selection of Counterparties shown in the first grid. 4. A bug was fixed related to the parametrization of the Duration Code for Limit Agreements. In the TRP October, the Duration Codes 7D and 14D have been replaced by the corresponding 17 | P a g e
Financial Applications
OCP New Features 1. The impact of Accrued Interests for LN/BO/BN/MM is now included in Balance Position report. Additionally, the FX Contra Account Balances are calculated based on the Report Day Official Exchange Rates, from the FX Position Account Balances (and not anymore transaction-based as before). A line for totals has been added, amounts are calculated and shown only for Local Currency columns. The Entry Type box in the header has been replaced by the Viewpoint, allowing the selections Include Agreed Entries (default: marked), Include Expected Entries (default: not marked), and Include Accrued Interest (default: marked).The previously existing, right-side button *Trades+ has been replaced by *Show Details+, enabled if there is anything displayed in the grid, opening the Accounting Balances report, carrying over the Report Date and for the case a row in the grid is highlighted carrying over also the Currency from this line. If the checkbox for the accrued interests has been marked, on top of the FX Position Account Balances, the accrued interest for Value Date = Report Date are calculated and added to the displayed amounts (same calculation as in Accounting Balances).
Rates and Prices Modifications/Enhancements of Existing Features 1. TwisterCWN is now importing also the Commercial Rates used in the Banking Module for FX Operations, and storing it in DW database. The report List Account Entries is showing this rate in the comment part. This info is especially important for the case of FC/FC Trades with Customers, not showing any rate in the Rate column of the report. 2. Price Import: When price for a value date and published datetime is available, if the MercuryPriceImport tries to update the price again for same ISIN and if published date is different than the one in the table for the same value date then it updates the price instead skipping (like before). Tool was adapted to import the price together with yield or price alone.
18 | P a g e
Financial Applications
Payments New Features 1. An additional parameter can now be stored, describing the maximum amount of different allowed for the (later to be implemented) feature of automatic Reconciliation between an agreed payment and a performed payment. Default is 0.99
Bug Fixing 1. TwisterCWN was showing an error when run in RESYNC mode. Fixed in version TwisterUserSrvCWN 0.6.6 & TwisterCWN 0.6.10 2. The initial balance in the report Account Statement, for the case the checkbox include agreed ones being NOT checked, was including the agreed entries in the calculation. Now, also for Banks not being up to date with the confirmation of payments (a situation which is frequent during Implementation Projects), the verification of Balances is possible and accurate. The initial balance calculation is now refreshed every time the checkbox include agreed payments changed.
Accounting Modifications/Enhancements of Existing Features 1. Accrued Interest amounts for MM are now included in Accounting Balances. For the special case that a Money Market has Value Date as well as Maturity Date in the period selected for the evaluation, the accrued interest appears in the Paid in Period column, if the Money Market is still outstanding, the accrued interest appears in the Amount (Value Date End) column. For all other cases, the behavior of the report is the same as already known for Bonds and Loans. 2. Accounting Balances: By Currency Filtering and Total Open Position. In order to improve the link resp. comparison with the Balance Position report, The Type box in the left header part is now separated in two sections, left-handed the Assets and right-handed the Liabilities. A Currency control has been added, default selection (all). If a single Currency has been selected, the new Open Position control displays the total in this currency, for the type of 19 | P a g e
Financial Applications
Bug Fixing 1. Nostro balance bug fixed. Mismatch in the NostroBalance when compared to AccountStatement dialog. The bug was final balance on the blocking date was not included.
Reporting New Features 1. The database has been modified in order to allow the storage of local accounting and reporting criteria, together with their relationship to international accounting and reporting characteristics. The functionality for filling/adapting these criteria via the applications, and the publication of these criteria via Mercury WebServices will be included in the next Treasury Release Package. 2. Another database modification was made to have the possibility to capture the 2-digit alphanumeric country ISO code, needed for official reporting in e.g. ECU. 3. The new WebService getPayment() is now publishing both the incoming payments and outgoing payments. By default, the outgoing payment is returned, by specifying the Payment Type as 'incoming', incoming payments returned and when None, both the outgoing and incoming payments is returned. When comparing to the getOutgoingPayments Call, the prefixes 'Omt' and 'Imt' have been added to all the attributes, in order to have an easier differentiation between attributes related to the incoming money transfers and attributes related to the outgoing money transfers. For Incoming Payments, if existing (and this is the case if a SSI account has been defined for this Counterparty), the Source Account will be also published.
Modifications/Enhancements of Existing Features 1. The Mercury WebService getBalances() is now publishing accrued interest for MM/LN/BO/BN, additionally. The dataset published now is: PrincipalOutstanding', 'AccruedNotPaidInterest', 'DealId', 'Currency', PrincipalContractual', 'AccruedInterestContractual', 'ProductId'.
20 | P a g e
Financial Applications
Bug Fixing 1. The Mercury WebService getBondPayments() was not returning the part of the payment related to the accrued coupon in the moment of buying/selling, now fixed. 2. Already in Mercury V.1.5.2.8, but not detected before, and fixed now for TRP October (Mercury V.2.0.2.1) as well as for TRP January: The Mercury Web Services getExchangeRates() and getInterestRate(), getInterestRates() were showing an exception when used. 3. Mercury 2.0.2 was by mistake returning unsigned amounts in getExchangePayments(), detected by the IW/BRP in PCB DEU. Fixed for version 2.0.2.1 (TRP October) and version 2.1.2 (TRP January).
SWIFT Modifications/Enhancements of Existing Features 1. Previously, the SWIFT message for Confirmation of an FX Deal (MT300) and the SWIFT message containing the settlement instruction for the outgoing payment related to an FX Deal (MT202) were generated together. Now, the MT202 part has been removed, as for Banks using Customware.Net the MT202 is generated by the Payments Module (on Value Date). The part related to the Confirmation of the Deal is like before generated by the Treasury Module (on Trade Date). Also included in DW 4.2.5.5. Bug Fixing 1. The generated MT300, for confirmation of FX Deals, was never tested before (but already existing for several years). Now, it was tested by several Banks, and PCB DEU compiled a detailed gap analysis between the implemented MT300 and a modified MT300 accepted by the SWTFT Server. Based on this description, MT300 has been adapted and can now be used to interchange
21 | P a g e
Financial Applications
22 | P a g e
Financial Applications
Modifications/Enhancements of Existing Features 1. The Rate Import tool for Ecuador needed an adaptation, the website rates were previously taken from was not working anymore. Adaptations for the new location has been included in QuipuRateImportForECU (V1.2.1). 2. All interest rates needed for NSR purposes as raw data for the calculation of the monthly historical swap curves are now captured additionally with the tool QuipuRateImporForDEU (V2.2.0), taking the data from the Bloomberg FTP and storing them in a separated Rate Stream called Isdafix inside the PCH DW database. The tool runs automatically in the background, capturing USDSwap (published at 20:00), EURSwap (published at 12:30), and USDLibor (published at 13:30) rates. 3. The Rate Import tool for Romania needed an additional function for the Proxy user authentication, to provide encrypted password instead clear text password. Adaptation was included in QuipuRateImportForROU (1.2.0). 4. Mercury Client importing Prices from text files (very similar to the case of the RateImports). Last changes: Yield can also be imported in addition to the price if available, when not only price can be imported skipping the yield information. Adaptation was included in MercuryPriceImport.exe (1.1.0). 5. Mercury password, possibility to specify clear text password instead MD5 password. For Proxy authentication password, possibility to specify encrypted password instead clear text. The creation of encrypted password is described in the user manual delivered together with the tool. Adaptation was included in QuipuRateImportForALB (1.2.0).
23 | P a g e
Financial Applications
24 | P a g e
Financial Applications
2014-01-30 Inga 2014-02-15 Inga 2014-03-11 Inga 2014-03-12 Christian 2014-03-12 Inga 2014-03-15 Sudhakar 2014-03-17 Inga 2014-03-20 Inga 2014-03-22 Inga
25 | P a g e
Financial Applications