TR Accuracy PRODUCT RELEASE – 15.01.2021
January 8, 2021
We have a product release due for release on the 15th January 2020 at 1700 UK local time.
If you have downloaded the latest version of the TRAC tool (after 18.12.2020), please update only reference data (see ‘Reference data requirements’ document).
If your TRAC version is from before 18 of December 2020, please download new version from CN Portal: ‘Resources->Downloads’.
Your current TRAC version will no longer work following release date.
For features which are configurable (TR Accuracy MI report and validations etc), you will be able to log into your management portal and turn them off if you do not wish to see the functionality.
|Update to reference data required||Yes.
Please see Portal: ‘Resources->Downloads’
|TRD-79||New validation E171: Fund Manager identified as executing entity for agency execution – ESMA Data||TRA EMIR: New validation using ESMA reference data to identify incorrect fund managers reports|
|TRD-93||New Reference Data File: Fund Managers and 4 new validations||TRA EMIR: New reference data file allowing clients who are Funds or Fund manager to define their relationship with clients, enabling 4 new validations: E170, E174, E176, E178|
|TRD-91||New reference data: Portfolio Management Reference Data and 4 new validations||TRA EMIR: New reference data file allowing clients who are Portfolio Managers to define their relationship with clients, enabling 4 new validations: E168, E169, E172, E173|
|TRD-120||E93 ETD not with CCP – correction to not flag for SIs and to match against CCP field||TRA EMIR Validation amendment: remove flagging for SIs and amend check on CCP field|
|TRD-36||E41: use the new OTC definition||TRA EMIR: Improved identification of OTC trades according to EMIR definitions.|
|TRD-32||E73, E74, E76, E77, E78, E79 – allow 0 for margin values where blanks were required||TRA EMIR: Modification to validations: E73, E74, E76, E77, E78, E79 to treat margin values = ‘0’ as blank and not flag them when validation expects blanks.|
|TRD-31||E109 – validation logic correction||TRA EMIR: Improved logic determining if segment MIC is available.|
|TRD-30||E1 Business logic change||TRA EMIR: CN modifying validation to source branch indication from LEI Level 2 database.|
|TRD-28||E138 – Business logic adjustment||TRA EMIR: Added clause to avoid flagging government bonds which are correctly reported with “Asset class” = ‘IR’ (See Q&A TR1)|
|TRD-27||E117, E120 – add relation to avoid double flagging||TRA EMIR: Adding a clause to E120 to not flag the same reports that have already been flagged by E117 (related fields likely to trigger the same reports)|
|TRD-26||E119, E121 – add relation to avoid double flagging||TRA EMIR: Adding a clause to E121 to not flag the same reports that have already been flagged by E119 (related fields likely to trigger the same reports)|
|TRD-25||E8 – validation update||TRA EMIR: Modification to validation to avoid false-positives where Collateralisation = U|
|TRD-23||E124, E129, E130 – FIRDS vs report values matching||TRA EMIR: Enhancement to translate FIRDS values to EMIR expected values|
|TRD-33||New global reference data: ISO_4217_currency_codes||TRA: New Global Reference data file introduced – listing all ISO currency codes|
|TRD-22||E148-E159 New validations – check validity of the currency||TRA EMIR: 12 new validations to verify ISO currency codes used in the report.|
|TRD-34||New validation: E147 – Exchange rate basis must use valid currency codes||TRA EMIR: New validation to verify correctness of “Exchange rate basis” field: both currencies being different and present on ISO 4217 list.|