22 March Version 1.8

Transcription

1 22 March 2018 Version 1.8

2 Version Control Document Filename: NEX Regulatory Reporting User Interface Guide v1.8 Version: 1.8 Version Date: 22 Mar. 18 Project: Documentation Status: In Progress Sub-Prog: - Document No: - Review Period: As required Classification: Commercial Document Purpose: Provide clear and concise guidance for users of the NEX Regulatory Reporting User Interface. Version History Date Updates since previous version Author Accompany v0.4 of the Portal and provide insight into upcoming releases Updated to accompany v0.5 of the Portal and provide insight into upcoming releases. EB EB Temporarily removed: EB Transparency Reporting (inc Product Analysis & Exceptions); Reference to Transaction audit trail; Transaction Grouped Failure View details Updated user timeout for non-activity EB Transaction: Re-designed sources; Grouped Failure View; Audit Log; Modify individual failures EB Transaction: Added in EMIR Failure Editing EB Transaction: Added in deleting of sources on QA; Explanation of NPD fields, General updates to functionality Transaction: Updated record state descriptions to include NRR & NCA Eligibility states; included MiFID modify of failed records Removed notes related to sections which are not yet live as these have been removed from the Portal until brought online. Also added information on the multi-model view Transaction: updated regarding masking of confidential data in MiFID. Transparency: updated Exceptions section & added in Add Trade/Quote EB EB EB EB Transaction: Details of bulk state change and override functionality. EB Transparency: updated file states & validation details for Portfolio Compression Included Useful Resources section Updated Support contact details. Highlighted useful hints Transparency: updated default date information for Status and Exceptions EB EB PAGE 1 22 MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

3 Version History Date Updates since previous version Author Transparency: updated Status section as table now refreshes only if viewing today s data General: Expanded on the user profile section & included notifications Transaction: Updated Source State tooltips, editing NPD fields & tooltip to show the full failure reason on the Record View Transparency: Included Cancel button for exceptions EB EB PAGE 2 22 MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

4 CONTENTS 3 1. OVERVIEW 5 Management Information NRR DATA FLOW 6 3. ACCESSING THE PORTAL 7 Browsers...7 User Management...7 Log In...7 Remember Me Option...8 Log Out...8 Future Features NAVIGATING THE PORTAL 9 Home...9 Navigation Sidebar...9 Tooltips User Specific My Profile My Notifications Logout Multi-Model TRANSACTION REPORTING 12 Sources All Sources Sources Record View Grouped Failed Validation View Grouped ISIN Eligibility Failure View Field Level View Audit Log Editing Individual Failed & Rejected Records Delete Sources TRANSPARENCY REPORTING 24 Records Status PAGE 3 22 MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

5 6. Status Table Add Trade/Quote Portfolio Compression Exceptions Exceptions Table Exceptions Management Exceptions Data Charts CONTACT NRR USEFUL RESOURCES USER ADMINISTRATION 29 PAGE 4 22 MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

6 The NEX Regulatory Reporting (NRR) User Interface (UI) or Portal is an HTML5 delivered, sophisticated application, designed as a customisable tool for managing the end to end reporting lifecycle and facilitating analytical insight. The Portal will be accessed via a secure single-entry point through NEX Regulatory Reporting s service offering, and be available to users across operations, compliance, support and management. It will be an essential tool providing insights into transaction pre/post trade status with the regulator, both historically and in real-time. The NRR Portal incorporates responsive design, offering an intuitive experience for the user to quickly identify errors for correction, whilst constantly being mindful of data security and integrity. MANAGEMENT INFORMATION A key component of the NRR Portal is management information: providing users with an essential overview of the transaction reporting process. The UI aims to fully facilitate the reporting process, regulatory requirements and more, offering a rich and highly configurable interface packed with meaningful insight and analytics. The Portal will include the following high-level functionality: Customisable web-based user interface, bespoke per user Data visualizations, interactive reporting, ad hoc analysis, and tailored dashboards. A view of current and historic data quality and validation failures at both a holistic and granular level PAGE 5 22 MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

7 The Portal allows users to view data at all stages of processing: from submission to NEX, during processing within the reporting HUB and confirmation of the status at the relevant regulatory endpoint. Currently the UI supports both EMIR and MiFIR reporting and is designed to be regime agnostic, allowing other regimes to be incorporated at a future date with relative ease and consistency which will enhance the experience for users working across multiple regimes. User Interface REST API Reporting HUB Data Ingestion MiFID ARM Determination MiFID II ARM Streaming Data Enrichment MiFID II APA Client Universe Batch Data Validation EMIR TR Reports Exception Management REMIT RRM Routing DFA, CAN Reconciliation ASIC/MAS/HKMA MIS FINFRAG,BOI PAGE 6 22 MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

8 BROWSERS The NRR Portal has been designed to work with the following browsers 1 : Chrome Firefox Internet Explorer 11 and above We recommend that you always use the current version of browsers to make sure that the functions and features of the Portal work as intended. USER MANAGEMENT Initially user authentication to connect to the Portal is being handled by Active Directory (AD). This includes password authentication with password policy and automatic user account lockout if three consecutive attempts to log on with a valid user name fail password checks. User accounts are currently created and managed by NRR, along with user entitlements. We are currently developing a user management module within the Portal itself, which will allow client users, with the appropriate entitlements, to create and manage users within their own organisation. See User Administration for further information. LOG IN To access the NEX Portal, please navigate to the URL provided using your chosen web browser. The following screen will be displayed: Login To log in, users should enter their Username and Password, as provided by the Onboarding team, in the relevant boxes and press Enter or use the Log in button. 1 Chrome or Firefox would be our recommended browsers for accessing the Portal. PAGE 7 22 MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

9 REMEMBER ME OPTION Selecting the Remember Me option ensures that, once logged in successfully, the user s Username is pre-populated when they return to the log in screen, requiring them to enter only the Password to re-gain access. Remember Me LOG OUT Once logged in to the Portal, users will be able to access a drop-down menu under their Username in the top right-hand corner of the screen. From here, selecting the Logout option will sign them out of the NRR Portal. Logout Note that users will be automatically logged out of the Portal after 2 hours of inactivity and will be required to log in again to continue accessing information. If there are any issues logging in or out of the Portal, please contact the Support team at: nrrsupport@nex.com FUTURE FEATURES Please note that the following features will be available in future releases of the Portal: Users to log in via Single Sign On (SSO) between their own Identify Provider (IdP) and Okta; Multi-Factor Authentication (MFA) to be enabled by default; and IP restriction to be introduced as Okta will allow adaptive authentication based on the request source. PAGE 8 22 MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

10 The NRR Portal is an intuitive tool which will provide users with complete visibility of all stages of the regulatory reporting process. Please note that various sections of the Portal are still in the development phase. These additional features will be released in a phased approach as soon as they become available. We would welcome your feedback and suggestions on all aspects of the Portal. Please send any comments to nrrsupport@ne.x.com HOME On logging in to the Portal, the user will be taken to one of the following screens depending on which type of reporting they have access to: Transaction Reporting > Sources > All Sources if the user has access to Transaction Reporting Transparency Reporting > Records > Status if the user only has access to Transparency Reporting NAVIGATION SIDEBAR Sidebar Navigating the Portal is generally achieved via the Sidebar on the left-hand side of the screen. The range of options visible in this Sidebar vary depending on a user s entitlements. Some options within the Sidebar have a subset of available options, which can be accessed by either clicking on the main option (e.g. Reports ) or the downward arrow next to the main option ( ). The current page will always be highlighted in the Sidebar to identify where the user is in terms of the site s hierarchy. At any time, a user can select a different option in the Sidebar to move to that page. If the user has been keying any changes to data, a prompt should appear asking for confirmation as to whether they wish to proceed, undoing any unsaved changes. Along the top bar of each page, the user will also note the path which has taken them to the current screen. Each level of the path is a hyperlink allowing the user to jump up multiple levels to previous pages with just one click. By default, the Sidebar is pinned to the page, ensuring that it is always visible. To hide the Sidebar, the user can click the push-pin icon (highlighted in blue in the Sidebar image). The Sidebar can still be accessed at any stage by clicking the tab in the top left-hand corner of the screen ( ). It can then be re-pinned as required. This functionality allows the user to maximise screen space whilst maintaining ease of navigation around the Portal. PAGE 9 22 MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

11 TOOLTIPS Users will notice tooltips (denoted by at various points across the Portal. Hovering over these icons will provide the user with further information. They are generally found in the following areas: next to column headers in tables to provide an explanation of what that particular data relates to; next to field names when viewing or creating individual records to provide information on the field, expected format and associated validation rules; and in the top right-hand corner of widgets to provide insight as to the information depicted in the widget. USER SPECIFIC Each user will not only have specific entitlements associated with their account, controlling their access accordingly, but will also have a user profile ( My Profile ) and various other user-specific sections. 1. MY PROFILE The My Profile section is accessed via the dropdown menu under their username in the top righthand corner of the screen. It provides key information such as which regimes the user has access to and which organisations the account is linked to. Additional details will become available under the user profile section in future releases. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

12 2. MY NOTIFICATIONS The Portal allows for notification messages to be sent to users by the NEX Support team or automated systems to communicate useful information, updates and issues. Users are alerted to a new notification in one of two ways: A badge on their user profile picture A notification pop-up in the top right-hand corner of the screen, if the notification arrives while the user is logged in Clicking on either of the notification methods mentioned above, or accessing the My Notifications option from the user drop down menu will take the user to a page listing notifications which have been sent to them directly. New or unread messages will be highlighted. Users can then mark the notification as read using the button. Alternatively, if the page remains open for 1 minute, unread messages are automatically marked as read. 3. LOGOUT Users will also note that the dropdown menu under their username in the top right-hand corner of the screen also provides them with the option to Logout. MULTI-MODEL This functionality relates to those NRR Clients who require restricted GUI access for their own clients. Each NRR sub-client receives a view of data only relevant to them while the principle NRR client users have an overarching view of all data submitted by their organisation, for themselves and subclients. Note that this is currently only available for Transaction Reporting. To support these views, data is required to be submitted in sub-client specific files. This allows NRR to ensure data segregation. This requires non-standard configuration of client environments. In addition to viewing the data, it is possible for client user accounts to be configured with the following permissions on a sub-client by sub-client basis: Editing of failed and rejected records Deleting of files (available in UAT only) PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

13 Only users with the specific entitlement will be able to view and access the Transaction Reporting options from the Sidebar. Content visible under this section is dependent on which regimes are reported to NEX, and also whether the individual user has been granted access to the particular regime(s). SOURCES The Sources section primarily offers an overview of transactional data which has been uploaded to NRR for processing, with the option to drill down to view individual record details. All Sources This page presents an essential view of the status of files and records which Clients have submitted to NRR for processing. As Clients may upload files or stream data in to NRR, for the purposes of the UI, we refer to incoming data as a source. The following Guide To Sources: Screenshot and Guide To Sources: Table explain how to navigate the All Sources page. Key points to note are: Users initially see an overview of Today s files. They can then choose to view all historic files or filter accordingly by clicking on the All tab. Data is shown on a regime basis. On the Today table, users can expand the information for any regime on the page by clicking anywhere on the relevant regime summary line. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

14 Guide to All Sources PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

15 Guide To Sources: Table Today or All Sourcename Filter Regime Filter (All) State Filter (All) Today is selected by default to give you an overview of all records processed today. Select All to view sources processed on previous days. Initially a summary by regime is presented for all records processed today. Each regime can be expanded to see a breakdown by Source by clicking anywhere on the line. If users have access to multiple regimes, the All screen will initially default to one for improved performance. To view Sources from a different regime, users can select the relevant value from the drop-down list, which will be populated according to their entitlements. Users have the option to filter on the state of sources, for example to view all files in Error or Complete ingestion state. A B C D Ingestion Date From Filter (All) Ingestion Date To Filter (All) Regime (Today) Regime (All) If wishing to only view files processed from a particular date, users may select an Ingestion Date From value using the calendar option. By default, the From date is set to 3 days prior to today to encompass weekends. This can also be selected in conjunction with an Ingestion Date To value to further reduce the results. If wishing to only view files processed up until a particular date, users may select an Ingestion Date To value using the calendar option. By default, the To date is set to tomorrow to include all sources uploaded today. This can also be selected in conjunction with an Ingestion Date From value to further reduce the results. Initially a summary by regime is presented for all records processed today. Each regime can be expanded to see a breakdown by Source by clicking anywhere on the line. When viewing historic Sources, the breakdown by Source also includes the relevant regime information. E F G H Sourcename Once a regime has been expanded, users will see a list of Sourcenames processed for that regime today. To view a list of all records for a given source, users can click the Sourcename or the Records total for that Sourcename. Ingestion Date Each Sourcename will also show the date and time when it was first processed by NRR, in descending order. J I Original Row Count Record States Hyperlinks to Records Pagination The total count of rows received per source or regime is shown depending on whether viewing the regime or individual Source row. Note that this number may include header rows if supplied. It does not include rows automatically generated by NRR during processing. Tooltips to the right of each state header give information as to what each state represents. Note that each state shown here may encompass several stages in the HUB but have been grouped to provide an overview. See also StateDescriptions Numbers which are underlined in this table serve as hyperlinks. If a user clicks one of these links, they will be taken to a list of the records from that Sourcename which fall into that state. The results in the All screen are paged, starting with the most recently received sources. Users may page through the results or jump to the first and last pages using the arrows in the bottom right-hand corner of the screen. Alternatively, they can key a specific page number. Or they may also choose to change the number of results shown per page from 20 or 50 to 100. K L M N PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

16 State Descriptions Not Reported records in this state have either been automatically determined as not reportable based on standard or clientspecific logic, or have been moved to this state at the request of clients. In Processing covers all records which are in a transient state within the HUB and ARM. The records should move to a terminal state shortly. Processing Errors are individual records which the HUB or ARM has not been able to successfully ingest, enrich, determine eligibility or otherwise process, perhaps because they do not meet the expected format. These records should be investigated as action may be required. Please liaise with the Support team. Failed Validation includes all records which have failed HUB validation, enrichment or determination, as well as ARM validation for MiFID records. Action will be required to resolve the failures. Please liaise with the Support team. Awaiting Eligibility Applies to MiFID records only, which have passed HUB validation and are awaiting ISIN eligibility checks against FIRDs reference data. Such records are held back until 9am CET on T+1 based on client configuration. At that point they will automatically continue processing as per the standard flow to the NCA. Failed Eligibility Applies to MiFID records only, which have passed HUB validation but failed ISIN eligibility checks against FIRDS reference data. Such records should be reviewed and either moved to not reported, re-processed if the reference data has been updated or the failure overridden, which will allow them to continue processing as per the standard flow to the NCA. Awaiting Regime is where records have passed HUB, and ARM validation in the case of MiFIR. The records have been sent to the necessary Endpoint and are awaiting the relevant response. NCA Held Records in this state have been sent to the NCA where they have been queued for processing by the NCA until 9am CET on T+1. NCA Pending These records have been sent to the NCA where they are pending ISIN reference data match. Records may remain in this state for up to 7 days until the ISIN is available in FIRDs or the transaction report is corrected. Regime Rejected records have been sent to the Endpoint but were rejected for not meeting the required validations. Any such rejections should be reviewed and corrected to allow the reports to be accepted. Regime Accepted is for records which have been accepted by the Endpoint. No further action is required. 1. SOURCES Sources may show in the following states: - ingested successfully - currently being ingested and processed - failed to ingest Our Support team constantly monitor ingestion and are alerted to failures which they can then investigate and raise in order to resolve. If you are unsure as to the status or whether any action is required, please contact our Support team. From either the Today or All Sources overview, users can drill into the underlying records in a particular state for each source by clicking any of the hyper-link numbers. Clicking either the Sourcename itself or the Original Records count will display a list of all records from that Source, regardless of the state of the individual records. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

17 Please note that if drilling into a file which is in an Error state, no records will be displayed as NRR has not been able to process them. Similarly, if drilling into a file which is Ingesting, an incomplete list will appear as not all records will yet have been ingested. In the UAT environment, users with the relevant entitlement, will also be able to select individual or multiple sources from the All tab and delete them from the database by clicking Delete Selected Files. See Delete Sources for further details. 2. RECORD VIEW From the Sources view, users can drill down into the underlying data either by clicking a Sourcename (hyperlink to a list of all records from that Source) or by selecting the number representing records from an individual Source in a particular state (hyperlink to a filtered list of records from that Source which are currently in that state). The list of records presented will include key details of each record meeting the filtering criteria, including: Transaction Reference Number (MiFID) or Trade ID (EMIR); Regime; State of the record; Failure reason (only if applicable); Ingestion Timestamp of the record; and Trading Date Time (MiFIR) or Execution Timestamp (EMIR). By hovering the pointer over a Transaction Reference Number (MiFID) or Trade ID (EMIR), users have the option to either copy the particular value to their clipboard ( ) or to open the Field Level View for that record in a new browser tab or window ( ). This allows users to view the details of multiple records and compare and analyse. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

18 When viewing records in Failed Validation, if only one field has failed the cause of the failure (Field name and error reason) will show on screen. If the reason is over a certain length it will show truncated. However, the full message can be seen by hovering over the tooltip, as shown below. For records under Failed Validation, there is also an alternative view the user can toggle between (see Grouped Failed Validation View ). Alternatively, users can select an individual record and view all fields associated with that record, along with a complete audit trail (see Field Level View). Any fields which had caused the record to fail HUB or ARM (for MiFIR only) validation would be highlighted in red, along with an explanation and details of any TR rejections for EMIR. 3. GROUPED FAILED VALIDATION VIEW From the Record View for failed enrichment and validation records, users may opt to toggle to a grouped failure view which presents all failure fields and reasons associated with those underlying records, along with a count of the number of records falling into each group (see Grouped Failure View Example). Grouped Failure View Example From here, users are able to select each failure group to see an expanded view with a summary of the individual records which failed for that field and reason. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

19 As with the Record View, within the expanded group view, users can select individual records and view all fields associated with that record, along with a complete audit trail. Any fields which had caused the record to fail HUB, or ARM (for MiFIR only) validation would be highlighted in red, along with an explanation and details of any TR rejections for EMIR or NCA rejections for MiFID. By hovering the pointer over a Transaction Reference Number (MiFID) or Trade ID (EMIR), users have the option to either copy the particular value to their clipboard ( ) or to open the Field Level View for that record in a new browser tab or window ( ). This allows users to view the details of multiple records and compare and analyse. For those users with the Bulk Modify entitlement, there will be two buttons on the Grouped Failure View: and. Before either button is selected, we recommend reviewing the records in the relevant group to ensure the same action should be applied to all records in that particular group. The Reprocess button will send the records back through HUB validation, and for MiFID records through enrichment. The reported data will not change unless any enrichments are applied. This option is useful for example for reference data or ISCI 2 failures where the referenced data has since been updated. The Not Reported option moves all records in the group to a not reported state for cases where the data should not have been reported or replacement records will be submitted and the user wishes to move the failed records so that the new ones are not blocked by history checks on the transaction identifier(s). Use of either option will prompt an entry into the audit table for all affected records showing the state change and user responsible for the action. This information is available on the individual record screens (see Audit Log). The Sources page will also reflect the updated states. We would recommend reviewing the Sources page and at least sample individual record pages to ensure any changes have been applied as intended. Should you have any queries or need to un-do any updates, please contact our Support team. 2 Industry Standard Common Identifier ( ISCI ) is a short code identifier service designed to protect anonymity, ensure optimal latency and future compliance with the General Data Protection Regulation (GDPR) coming into force on May 25th The solution supports Transaction Reporting under RTS 22 and Order Record Keeping under RTS 24. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

20 4. GROUPED ISIN ELIGIBILITY FAILURE VIEW When drilling down into MiFID records in Failed Eligibility, users are initially presented with the Record View as with records in Failed Validation. Similarly, there is the option to toggle to a grouped failure view, though for records in this state, the grouping is on the Instrument Identification Code or Underlying Instrument Code. As with the Grouped Failed Validation View, users with the appropriate Bulk Modify entitlement will see action buttons associated with each of the ISIN groups:, and. Before any action button is selected, we would recommend reviewing the records in the relevant group to ensure the same action should be applied to all records in that particular group. The Reprocess button will send the records back through HUB enrichment and validation. The reported data will not change unless any enrichments are applied. This option is useful for example if the FIRDs data used for the ISIN eligibility checks has since been updated. The Not Reported option moves all records in the group to a not reported state for cases where the data should not have been reported or replacement records will be submitted and the user wishes to move the failed records so that the new ones are not blocked by history checks on the transaction identifier(s). The Override button bypasses the failure, forcing the relevant records through to sending to the destined NCA. Use of any of these three actions will prompt an entry into the audit table for all affected records showing the state change and user responsible for the action. This information is available on the individual record screens (see Audit Log). The Sources page will also reflect the updated states. We would recommend reviewing the Sources page and at least sample individual record pages to ensure any changes have been applied as intended. Should you have any queries or need to un-do any updates, please contact our Support team. 5. FIELD LEVEL VIEW Reached by clicking on an individual record from the Record View or expanded Grouped Failed Validation View, the Field Level view provides all information associated with an individual record, including: Source name; Source row number (if applicable); State as per the database; Failure / Rejection reason(s) (if applicable); Ingestion Timestamp; Specific NCA details (MiFID records only once passed HUB validation); and PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

21 The values of all regime-specific fields, grouped into various sections including details of any failed or rejected values. Audit Log details, including all timestamped changes made by users or the system during processing of the record. Initially the fields and relevant values will be grouped into various sections. Any sections containing fields which failed either HUB or ARM validation will be highlighted in red with the relevant explanation shown. Users can then expand either individual sections by clicking on the relevant section header or choosing the option. Conversely, if at least one section has been expanded, users can click to return to the compacted view. Please note that, for data protection, values in the following Code and Date of Birth MiFID will show with 5 asterisks to mask personal data where the corresponding Code Type field is reported with a personal/national identifier type (CONCAT, NIND/NIDN and CCPT). If records are in a failed or rejected state, it is not currently possible to edit these fields. They will therefore be greyed out. Replacement records would need submitting in order to correct the data, with the original moved to a not reported state. Code Type Field Name Code Field Name Date of Birth Field Name Buyer Identification Code Type Buyer Identification Code Buyer Date Of Birth Buyer Decision Maker Code Type Buyer Decision Maker Code Buyer Decision Maker Date Of Birth Seller Identification Code Type Seller Identification Code Seller Date Of Birth Seller Decision Maker Code Type Seller Decision Maker Code Seller Decision Maker Date Of Birth Investment Decision Within Firm Type Investment Decision Within Firm - Execution Within Firm Type Execution Within Firm - Audit Log From this record page, users can also access the Audit Log for the record. This log will include timestamps and information for each stage of processing, along with details of any automatic enrichments. In addition, the log will capture any value changes which have been made via the UI and the user responsible for the change. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

22 Editing Individual Failed & Rejected Records Depending on the appropriate entitlements, users may have the option to edit failed and rejected EMIR and MiFID records via the Portal. This is achieved at an individual record level so the first step is to view the record that requires editing. See Field Level View. As an example, if an EMIR record failed for an invalid Report Type, the failed field would be highlighted in red when viewing the record, along with a description of the issue. Once the user begins editing a field, the Submit Edits buttons at the top of the page become available. and Discard Edits As several fields are inter-dependent, it is possible to also edit fields which have not necessarily failed or been rejected to allow users to pre-empt subsequent failures. Once all necessary fields have been updated, the user can select submit,, to commit the changes to the database and send the record for re-processing. Before any changes are submitted, the user will be asked to confirm that they wish to proceed. Either before confirming they wish to proceed, or at any stage of the editing, users may opt to revert or discard their changes,. If this is done, no updates are made to the database and the record remains in the failed state with the original values. For validation failures and TR rejections, once the changes have been submitted, the record will show with a state of Validation and will either then pass or perhaps fail again. If the record fails validation, on refreshing the page it will show with the updated reason(s) and will again be editable. Note that other failure types will go back to their previous state after being edited to see if they now pass. For example, a record in DeterminationEnrichmentFailure would be set back to DeterminationEnrichment. For EMIR, there are five fields which cannot be edited and are therefore greyed out. This is because the values could have impacted the processing of the record in other ways. The relevant fields are: Reporting Counterparty ID Contract Type Asset Class Transaction Type Lifecycle Event PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

23 If these fields require updating, we would recommend moving the failed records to not-reported and sending in a replacement file with the values corrected at source. For MiFID, all records are currently editable other than those which contain asterisked values and are greyed out. To explain, for data protection, values in the following Code and Date of Birth fields will show with 5 asterisks to mask personal data where the corresponding Code Type field is reported with a national identifier type (CONCAT, NIND/NIDN and CCPT). Even if records are in a failed or rejected state, it is not currently possible to edit these fields and the fields will be greyed out. Please note that the if multiple values have been reported (repeated fields) and at least one is a personal/national identifier, all values are currently blocked from editing. This will be reduced to only personal/national identifiers in the near future. If users wish to correct greyed-out fields, replacement records would need to be submitted, with the original moved to a not reported state so as not to block the correction(s). These 10 fields will become editable in a future release, regardless of the reported Code Type but with other controls in place to protect personal data. Code Type Field Name Code Field Name Date of Birth Field Name BuyerIdentificationCodeType BuyerIdentificationCode BuyerDateOfBirth BuyerDecisionMakerCodeType BuyerDecisionMakerCode BuyerDecisionMakerDateOfBirth SellerIdentificationCodeType SellerIdentificationCode SellerDateOfBirth SellerDecisionMakerCodeType SellerDecisionMakerCode SellerDecisionMakerDateOfBirth InvestmentDecisionWithinFirmType InvestmentDecisionWithinFirm - ExecutionWithinFirmType ExecutionWithinFirm - All changes to fields and the state are recorded in the Audit Log which is visible within the individual record pages. As an alternative to editing individual failures and rejections for large volumes, users may contact the Support team to discuss an alternate course of action. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

24 6. DELETE SOURCES Depending on the appropriate entitlements, users may have the option to delete sources. Please note that this functionality is available in the UAT environment only. Sources can be deleted by selecting the tick box at the end of any source row they wish to remove and then clicking the icon, which will automatically have become active. Multiple sources can be selected and deleted at a time though we would recommend caution before doing so, particularly for large files to avoid any performance issues. Before any sources are removed from the database, a dialogue box will pop-up asking the user to confirm whether they wish to proceed with the deletion. Once complete, all references to the source and related records will be removed from the database. The raw data would still be available for recovery from storage, however, if required. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

25 Only users with the specific entitlement will be able to view and access the Transparency Reporting options from the Sidebar. As with most pages in the Portal, content visible under this section is dependent on user entitlements. RECORDS Status 6. STATUS TABLE The Status table is the core source for viewing record level information. Not only does it serve as a blotter for records as they are received and processed by the APA, but it also acts as a gateway for drilling down into the field level view of individual records 3. By default, the table displays information relating to the current day. This can be overridden by selecting an alternate Date Submitted using the calendar option and then apply. The table itself holds all records submitted to NRR that day which have passed APA validation, or records which passed on a previous day but are yet to be published as they were deferred or are pending. By automatically updating on a regular basis (each minute) when viewing today s data, it ensures the most recent data is always visible. The page can also be manually refreshed and the table filtered to show a specific record or group of records based on any or all of the following criteria: Message ID Client Reference Type - Trade - Quote Status - Published - Ineligible - Deferred - Suspended - Waived Executed Date Time (for Trades only) Submitted Date Time Published Date Time (if applicable) Duration (difference in seconds between Executed and Published where available excl. records in deferred status) Instrument Code / Name Price Quantity Reason (for deferral, waiver etc.) 3 Note that as of Jan 2018, it is only possible to drill into Trade records. This functionality will be extended for Quotes in the near future. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

26 From the Status table, hovering over a particular Message ID, Client Reference or Instrument Code, users have the option to copy the particular value to their clipboard ( ). From this table, users can select individual Trade records by clicking anywhere along the entry. Doing so will take them to a field level view for that record. This functionality will be extended to Quotes in the near future. The fields and relevant values are grouped into sections with a header box displaying key information. Users can then expand either individual sections by clicking on the section or choose the option. Add Trade/Quote The Add Trade/Quote page allows users to manually enter either Trades or Quotes and submit the records to the APA to follow the standard data flow. This function is expected to be used in exceptional cases only due to its manual nature. Assuming they have the necessary entitlement, users begin by choosing which type of record they wish to manually create: Trade or Quote. The user is then required to complete all relevant fields following the available tooltips for that type of record. Should the user wish to complete the details at a later stage, it is possible to save the details entered thus far by selecting Save Draft. Draft records can then be accessed by the user who originally created them any time in the future via the dropdown under their user icon in the top right-hand corner of the screen ( My Draft Trades/Quotes'). Viewing previously saved draft records gives the user the option to continue editing and submit the record or delete as required. Once all fields have been completed accordingly, users can Submit a record using the button. Doing so will send the record for processing as per the standard flow. The status of the record would then be visible on the Status page. Instead of Save Draft or 'Submit', users also have the option to 'Discard' manually keyed records at any stage before submission by clicking. This will permanently delete the details from the user s account. Once a record has been submitted, it will either be visible in the Status or Exceptions table depending on whether it successfully passed the APA checks. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

27 PORTFOLIO COMPRESSION Assuming a user has the relevant entitlement, they will see and be able to select the Portfolio Compression option in the Sidebar. From this page, users have the option to browse for a local CSV file of Portfolio Compression records to upload using the button. Note, it is only possible to upload CSV files. Once uploaded, the file will show at the top of the table with the relevant filename, ingestion timestamp and number of records in the file. The file status will be one of the following: Passed Failed Processing Error - the file passed schema check and all records passed validation - the file passed schema check and at least one record failed validation and should be reviewed. A corrected, replacement file will be required. - the file is currently being validated. This is a temporary state. - the file failed schema check and should be reviewed Filters situated above the table allow users to search based on the source (file) name, status of the file or date of ingestion. Records in uploaded CSV files with the correct number of fields are validated, amongst other measures, against the following criteria: Derivative type is one of the following: COMMODITY SWAP; CREDIT SWAP; RATES SWAP; RATES OPTION; FX FORWARD; FX OPTION Valid ISO 4217 currency codes Valid integers for reported transaction counts Valid decimals for reported notional amounts (point for decimal separator, no commas) The main table includes an overview as to whether the records have passed or failed NRR validation. Users can drill into the underlying records in a particular state for each source by clicking any of the hyper-link numbers. Clicking either the Sourcename itself or the Original Row count will display a list of all records from that Source, regardless of the state of the individual records. By drilling down, users will be able to see all submitted values for each row in that state and source, along with an indication as to the status of the individual records and fields with failures highlighted in red. In the UAT environment, assuming the user has the relevant entitlement, they will also be able to select individual or multiple files and delete them from the environment by using the button which becomes active on selection of at least one source. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

28 EXCEPTIONS Through the Exceptions section, users have an overview of records in an exception state. Exceptions are those Trade or Quote records where at least one field has failed APA validation. Exceptions Table The Exceptions table is the heart of the Exceptions page, providing a summary of all outstanding exceptions so that remedial action can be taken. Currently this involves submitting a replacement record to the APA with the necessary corrections and flagging as a replacement. By default, the table displays information relating to the current day. This can be overridden by selecting an alternate Date Submitted using the calendar option and then apply. Other filters can also be applied to the table by completing or selecting any combination of the following fields: In the near future, users will be able to drill into see all submitted fields for records in exception state. And those users with the appropriate entitlements will also be able to modify exceptions and re-process the records to allow them to resolve issues. Exceptions Management For Trades exceptions, users with the appropriate entitlement will see a Cancel button on the far-right side of the listed Trade. This allows users to submit a Cancel for the relevant Trade in a few easy steps. Upon clicking the Cancel button, users will be asked to confirm that they wish to proceed. The relevant details will automatically be copied from the exception Trade and a record submitted to the APA as a Cancel. Exceptions Data Charts Please note that the Exceptions by Category chart on this page currently serves as examples of future functionality and is based on demo data. The Exceptions by Reason and Exceptions by Category widgets are designed to help show trends in the reason or category for any exceptions. The Exceptions by Reason bar chart gives a breakdown by reason for up to 100 exceptions recorded in the last 24 hours, or will show blank if no exceptions have been found during this time frame. As with all widgets in the Portal, in a future release users will be able to drill through into the underlying data from the Exceptions bar charts. The charts themselves providing an overview of areas of concern or which should be addressed so that any issues may be dealt with in a timely and pro-active manner. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

29 This section provides details for the various methods through which Clients can contact the NEX Regulatory Reporting team in case of any queries. Contact Us PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

30 This section of the Portal currently provides links to documents relevant to reporting through all aspects of the NRR HUB and APA. These documents will be updated in line with all system developments to ensure they remain current. We are in the process of developing a highly granular user access model. This will involve allocating a role type to each user. The expected user hierarchy which the Portal will support is shown in the User Hierarchy diagram below, along with the available user roles at each level. User Hierarchy Each role will be associated with a default set of entitlements, though it will be possible to override these on an individual basis when creating a user or at any stage for users with the relevant permission. PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8

31 The user entitlements will be rolled out in a phased approach due to the number and also to support the live, relevant functionality within the Portal as that is released. We are aiming to make user access and management as flexible as possible to accommodate the varying needs of our clients. To this end, once implemented, NRR will create admin users for Clients, who will then be able to create and manage other internal users directly via the Portal. An update will shortly be available on this development. Meanwhile, user management will be handled directly by NRR. Please contact nrrsupport@nex.com with any queries. For more information visit: nexregreporting.com/ Regulatory Reporting A NEX Group business. NEX Regulatory Reporting operates within NEX Optimisation which helps clients simplify complexity and optimise resources. We provide the regulatory reporting technology that ensures market participants can comply with their obligations. Abide acts as a reporting hub for EMIR, Approved Reporting Mechanism for MiFID and a Regulatory Reporting Mechanism for REMIT. Subject to ESMA s approval we are set to become a Trade Repository and are developing a MiFiD II offering. NEX NEX Group plc offers customers better ways to execute trades and manage risk. Our products and services underpin the entire trade lifecycle pre-, during and post-execution. Our electronic trading platforms are industry standards. Customers use our lifecycle management and information services to optimise portfolios, control risk and reduce costs. We partner with emerging technology companies to bring greater efficiency, transparency and scale to the world s capital markets. NEX is headquartered in London with offices worldwide. NEX. Empowering markets. For more information, go to NEX.com All information contained herein ( Information ) is for informational purposes only, is confidential and is the intellectual property of NEX Group plc and/or one of its group companies ( NEX ). The Information is directed to Eligible Counterparties and Professional Customers only and is not intended for Retail Clients (as each term is defined by the rules of the Financial Conduct Authority ("FCA")) or equivalent in a relevant jurisdiction. This Information is not, and should not be construed as, an offer or solicitation to sell or buy any product, investment, security or any other financial instrument or to participate in any particular trading strategy. The Information is not to be relied upon and is not warranted, either expressly or by implication, as to completeness, timeliness, accuracy, merchantability or fitness for any particular purpose. All representations and warranties are expressly disclaimed. Access to the Information by anyone other than the intended recipient is unauthorised and any disclosure, copying or redistribution is prohibited without NEX s prior written approval. If you receive this information in error, please immediately delete all copies of it and notify the sender. In no circumstances will NEX be liable for any indirect or direct loss, or consequential loss or damages including without limitation, loss of business or profits arising from the use of, any inability to use, or any inaccuracy in the Information. NEX and the NEX logo are trademarks of the NEX Group. Certain NEX Group companies are regulated by regulatory authorities. For further regulatory information, please see NEX Group plc PAGE MARCH 2018 CONFIDENTIAL NEX REGULATORY REPORTING USER INTERFACE GUIDE V1.8