Follow the latest updates about new features and system improvements dedicated to our Product Hubs.
I. General
1. Enhanced user management with last login information
Users with 'user administration' role can now manage the 'Users' tab in Company Preferences with greater flexibility. You can sort, filter, and rearrange columns based on user name, email, and last login date. Additionally, users will receive a notification after 90 days of inactivity from any user, prompting action to update or delete the user. This makes managing your user base more efficient and keeps your system up to date.
II. Confirmation hub
1. Increased file upload limit for incoming PDF confirmations
To improve the handling of large PDF files, we've increased the maximum allowed size for incoming PDFs to 7 MB (previously 1 MB). If a file exceeds the size limit, users will now be notified with a dedicated email message. This ensures transparency, so users know when a document has been received but cannot be processed due to size constraints.
2. Multiple receiver email addresses in contact details of counterparty private data
Users can now set up a default email address and multiple CC email addresses for outgoing PDFs. The default email will be used in the 'To' field, while additional emails will be sent as CCs. Admins will be required to set one default email address (mandatory) and can optionally add multiple CCs. If no default email is set, no PDF will be sent. This enhancement makes email management more flexible for users handling confirmations.
3. Default 'Reconfirmation' workflow for outgoing PDF confirmations
A new 'Reconfirmation' option has been added to the counterparty contact details. Users who do not expect a response from their counterparty can disable the 'Reconfirmation' setting. By default this option is enabled. When this option is disabled, the confirmation document will be automatically marked as ‘MATCHED’ after being sent, and no counter document will be generated. This helps streamline the process when no response is needed from the counterparty. All actions will be logged in the audit trail for transparency.
4. Email updates with chat messages before counterparty reply
Users will now receive email updates containing chat messages even before the counterparty has replied to the confirmation email. Previously, chat messages were only included in the email updates after the counterparty responded. With this update, chat messages sent immediately after issuing a confirmation will be included in the email sent to the counterparty, ensuring real-time communication regardless of the confirmation status.
5. 'Manual AgreedMatch' process for GEN companies
To address a limitation in certain ETRM systems, we’ve introduced a 'Manual AgreedMatch' process that allows users to manually match incoming and outgoing documents directly in the GEN UI. This process is ideal for companies facing issues with automatic matching. Users can propose a match between two documents (one incoming, one outgoing), and both parties can approve or decline the match. If agreed, the documents will transition to a 'Matched' state, and all post-match processes will proceed as usual.
III. Regulatory reporting hub
1. Increased file upload limit for REMIT transactions
We’ve increased the maximum upload size for REMIT files from 10 MB to 12 MB, allowing users to submit large transactions. If a file exceeds the size limit, users will be prompted with a UI message.
2. Allow submission of non-'new' transaction action types
Users can now submit all transaction action types (e.g., M, E, C) to ACER, even if the action type is not ‘New’. Previously, GEN only allowed submissions of transactions with a ‘New’ action type, blocking users from reporting updates to existing transactions, initiated outside of GEN. This enhancement ensures that users can report all transactions, including those initiated before GEN was used as the RRM, without facing validation issues.
3. Allow legacy EMIR files with old UTI format to pass validation
To support customers with legacy EMIR files, the system will now allow files with the older UTI format (previously rejected) to pass schema validation during upload. This change ensures that EMIR files reported under the old EMIR Refit rules can be uploaded without blocking, even if the 'UnqTxIdr' field does not meet the current UTI validation standards. This improvement helps streamline the upload process for users with historical data.