Follow the latest updates about new features and system improvements dedicated to our Product Hubs.
I. Confirmation hub
1. Enhanced document version handling for incoming PDF confirmations
We've refined the versioning logic for documents for received PDF confirmations to prevent conflicts and improve user clarity:
-
If the existing document is 'Matched', any new version will now enter 'Draft' with an 'Action Required' status, and 'Confirm & Submit' will be disabled to avoid duplicate confirmations.
-
For documents in statuses such as 'Unmatched', 'Error', 'Mismatched', 'Draft' or 'Cancelled', the system will automatically create a new version (v+1) and trigger the 'Action Required' workflow.
This improvement ensures smoother version control and clearer guidance on next steps to be taken by the user.
2. Applying business rules to ‘Draft’ matching status documents for incoming PDF confirmations
We've enhanced the handling of OCR-processed files by re-enabling the ability to edit business rules when validation fails. Now, if a file enters 'Draft' status due to missing or incomplete business rules, users can once again correct the rules directly within the interface using the 'Apply business rules' when editing the document.
3. Outgoing signed PDF document accessible from document details view
To simplify document retrieval and reduce manual effort, we’ve improved the way signed PDFs are handled for outgoing PDF confirmations.
When GEN creates and sends a signed PDF (based on configured static data), it will replace the originally received PDF attachment (top right) with the signed version in the document details view. This ensures that the most relevant version of the document is always easily accessible.
4. 4-eye approval for outgoing confirmation document changes
A new 4-eye check is now available for modifying or versioning outgoing confirmation documents, adding an extra layer of control and compliance.
The new setting is located under Company Preferences > Settings > General, the “Mandatory user approval for outgoing documents” section lets you require 4-eye user approval for edits or version updates.
When enabled, any Edit or New Version action triggers an 'Approval Required' status. A second user must Approve or Decline the changes before submission.
Actions are fully audited, and approvals must come from a different user than the initiator.
This enhancement improves oversight and streamlines control over confirmation workflows.
II. Regulatory reporting hub
1. Improved status alignment for REMIT transactions in UI
We've enhanced the user interface to ensure consistency in status display for REMIT files. When both the 'Processing' and 'Repository' statuses are marked as 'Accepted', the 'Channel' status will now also correctly reflect 'Accepted'. This change provides a clearer, more intuitive view for users, without altering any backend logic or processing flow.