Release Notes 23-Feb-2026

I. General

1. Introducing a team-based, permission-driven access structure

User access management has been enhanced by moving from a fixed role-based model to a team-based, permission-driven structure. You can now assign users to one or more Teams, with permissions configured at team level and, where needed, at individual level. This enables clearer separation of responsibilities, more granular control over actions, and stronger support for internal controls and audits. Your current access and permissions remain unchanged, and daily workflows continue as before. If you manage user access, we recommend reviewing your team configuration to ensure alignment with your internal control structure.

II. Confirmation hub

1. Extending routing rules with Agreement as a new condition

You can now use Agreement as an additional routing parameter to control how documents are processed. Agreement can be configured as a free-text condition, supports multiple values (logical OR), and works with the same text operators as other string fields. It can also be combined with existing routing parameters such as commodity, product type, or counterparty. Configured Agreement values are visible in the routing table view. Existing routing rules remain unchanged unless Agreement conditions are explicitly added.

2. Introducing electronic signature (Skribble) for confirmations

Electronic signature is now available as a new answer type for confirmation documents. When a document reaches Matched status and e-signature is configured, a signature request is automatically sent to Skribble. The document status is updated automatically based on the signature request result. This enables compliant, fully digital signing directly within the confirmation workflow.

III. Regulatory reporting hub

1. Introducing ELCOM reporting

Reporting to ELCOM is now supported alongside existing ACER reporting. Based on transaction information, the system determines whether a trade must be reported to ACER, ELCOM, or both. Where required, reporting is triggered accordingly. This ensures compliant handling of Swiss physical gas and power transactions, including cross-border cases involving EU and Swiss counterparties.

2. Introducing manual import of historical REMIT report

You can now import your previously reported documents into REMIT hub, allowing you to manage historical and future reporting in one place. Imported reports are marked as ACCEPTED, and no new reporting is triggered. You can attach or remove the original receipt directly from the document details view. Each import is logged in both the general and document-specific audit trail. Standard duplicate checks remain in place, and uploaded files must comply with the required technical schema. This helps you maintain a complete reporting history and consistent audit trail.

3. Displaying Trade ID and Source System information

You can now view and manage reports using Trade ID and Source System information. These fields are visible in both the documents overview and details view, can be used for sorting and filtering, and are included in exports. This makes it easier to identify and reconcile reports across systems, reducing manual work and delays.

4. Improved visibility of delegated EMIR reporting

If your transactions are reported by a delegated party, you can now see those reports directly in your documents overview. Previously, only the reporting party had full visibility of submitted files. Reports are now also visible to the party on whose behalf the transaction was submitted, improving alignment and transparency. This provides a clearer overview of your EMIR reporting activity and helps reduce reconciliation gaps with your delegated reporting partner.