A Message to Our Esteemed Customers
We have released a new build as part of our continual product development cycle; BRSANALYTICS V2.8.8 is now available for installation.
This release provides FINREP work including the latest taxonomy for Q4 2018 and AnaCredit enhancements. New BRS Toolbar functionalities and improvements (e.g. fast Publishing) throughout.
Provided below is a list of new items available as product fixes and / or enhancements.
Please contact one of our representatives to book an appointment to update your current setup. Updates take approximately 2 days per server to complete (including a health-check) depending on the setup you are currently running on.
We will provide more exact time-frames based on your present setup once we receive confirmation from the client’s end to upgrade.
Fixes and Enhancements in the Application:
|#1183||Category 28 Business Rule||When running ACCS rule after EOPB, there was a limitation which did not allow updating of certain data. This has been fixed.|
|#1181||AnaCredit Record Hash||Error when comparing current hash with previous hash (to determine if record changed and is therefore reportable) when multiple periods were previously processed.|
|#1184||ACCS. ImpairmentMethod||Inclusion of this field in FINREP License not just AnaCredit|
|#1180||CRS XML File encoding||XML file to be generated in UTF8 not UTF8-BOM|
|#1186||EODC Collateralised Amounts||For EODC we were calculating Collateralised Carrying Amount and Collateralised Gross Carrying Amount. This was not being calculated correctly as this was based on amended collateral which excluded accrued interest and any provisions and therefore the value was not correct.|
|#1046||Convert back to Excel||Inclusion of new button functionality to convert from XBRL back to Excel.|
|#1182||Toolbar Settings||In the toolbar setting form we now ensure that:
- Either the Database and analysis settings are entered
- OR one or more webservice URLs are entered
The only exception is the DCS webservice where the database connection settings are allowed
|#1195||AnaCredit Load Data||Issue in SQL Indexing on AnaCredit table was causing performance issues and crashes in Excel|
|#1196||AnaCredit Convert to XML||Issue with “An item with the same key has already been added” resolved|
|#1191||Master Facility Reference||This only supported numerical values – alphanumerical characters are now accepted|
|#1192||EODC – Account not found||There was an issue when the account was not found and resulted in a process crash|
|#1038||XBRL Java Process||XBRL currently checks running Java.exe processes. The code should somehow try to distinguish between a Java process that is related to the UBPartner toolkit, and one which is not.|
|#1199||AnaCredit Load Data||When loading the data, the following fields are now loaded rounded to the nearest integer as per data dictionary specifications:
INSTRUMENT PROTECTION RECEIVED
|Nationality Scripts||Inclusion of scripts to categorise MTROW and ROW with GROUP3 as ‘OTHER_NON_SPECIFIED’|
|#1202||AnaCredit IntraLoans||Tweak in Intraloans to exclude ‘NONE’ entries.|
|#1205||AnaCredit Reportable NO||Fix when Reportable NO, removing of these lines from the XML|
Convert to XML
|Tweak when generating “Submitted” Excel version|
|#1178||AnaCredit – Intermediary File||A way was required such that the users can have a visual representation of what is actually going out to the regulator.
This is generated as part of the results:
• Exclude the rows that were marked as reportable NO
• Exclude the rows that were not updated (were applicable e.g. COUNTERPARTY)
• Display the values of Not Required / Not Applicable that we transformed
This helps the business users tremendously especially for any queries of submissions done.
|#1206||Toolbar Published||Several speed optimisations whilst publishing|
|#1193||Collateral Issue on Carrying and GrossCarrying||Fixes to properly collateralise based on the Carrying and GrossCarryingAmount|
|#1190||Toolbar Special Characters support||Currently when one Opens a BRS file containing special characters this works OK, but when Generating the BRS file, this was not saving with the right conversion parameters.|
|#1213||AnaCredit Process||HeadOffice Identifier and Immediate Parent Identifier and Ultimate Parent Identifier should be ignored when ‘NONE’ and not display a warning|
|#1197||Sector Update in Table||Removal of the following sector labels which were never used:
• HOUSEHOLD (as this should be B24)
• INSURANCE_PENSION (as these have separate BRS codes)
• NFC (this has a specific BRS Code)
• OTHER_FINANCE (this also has a specific BRS Code)
|#1225||Inception Date default DEBTOR categorisation||For AnaCredit, if no inception date was present, this was not categorising a DEBTOR due to the lack of date. This has now been defaulted to DEBTOR AFTER SEPT|
|#1208||DT_ORGNL_PRTCTN_VL||The default value for not required / not applicable was not correct|
|#1198||Webservice Releases||Modification of package utility and documentation, to start including web sevices also as part of BRS releases|
|#1222||ACCS Field Index||Modify BRSV2_FileValidation field index for ACCS.WithholdingTaxRate' to 86, due to a duplicate field index|
|#1227||CRD Rules Engine||Issue with some RowStartDate / RowEndDate in retail rules|
|AnaCredit Collateral values||Protection Allocated Value and Protection Value should be loaded * 1000|
|#1233||D_Collateral||Update in Table, SQL Script to add AnaCredit Collateral Codes|
|#1231||AnaCredit Collaterals||Fix in displaying collateral codes when loading AnaCredit Protection Received data|
|#1210||CLTS Validation||If the postcode was too long this would crash rather than stopping at validation level|
|Default value was incorrectly set to “NO” rather than “NONE” and inclusion of a data fix|
|Internal Enhancements||Minor internal improvements for performance|
|Edit Mappings through Excel||We are slowly shifting some of the BRS functionalities to the toolbar, such as mappings. See below related incident for overview of functionality|
|Unmapped Items / Unconfirmed mappings||Addition of functionality to remind users to map new unmapped items. See Details below.|
Changes in Core Structure / Fixes in Formula Files:
|A new functionality has been included to make it easier to identify any missing mappings when these are uploaded. Previously, if e.g. a sector or industry new mapping was added in EOP but not mapped, this was displayed once but no longer visible to the user, making it easy to forget that a sector / industry / collateral etc was not mapped, resulting in check errors.
Therefore, upon loading a new unmapped item, the following Warning is displayed:
|Clicking on the warning:|
|In order to rectify this, the user may either use the tab ‘Reference Data’ or new Excel toolbar functionality (item #1179) find the unconfirmed / unverified mapped item, add its mapping and mark this as verified / confirmed.
Reference Data Tab:
|By filtering on the unmapped category (e.g. Sector / Industry / Collateral etc) and filtering where unverified, this will list item that are currently resulting in a warning.
1. Select the record you wish to modify
2. Set the BRS Code (documentation on BRS Codes provided separately)
3. Set Verified to TRUE as per the below:
|Excel Toolbar Mapping
1. Open Excel
2. Locate “Mappings”
|3. This displays a list of possible mappings available in the system. In the above example, this is a missing collateral mapping so below, COLLATERALS is selected|
|4. This will display a table with BankCode, BRS Code, the BRS Description (using a lookup to the adjacent sheet to guide you) and Confirmed|
|5. Locate the item which has ‘Confirmed’ = “NO” and set the BRSCode to appropriate mapping and set ‘Confirmed’ to “YES”. You may use the tab BRSCodes and provided Documentation to guide you in selecting the correct mapping for different Groups|
|6. Click ‘Save BRS Mappings’|
|8. Clicking ‘YES’ will confirm that the updating was done successfully:|
Changes in Documentation:
|LR||Fix in Memo Items ‘Expense’ rather than ‘Income’ based on recent CoA changed|
|LC||Update in Items 2.10.3 and 2.10.4|