NEXT 202551 - Release date: 17-12-2025
Source to Contract
Logging added for changes in DORA-specific fields
An improvement has been implemented to fully log changes in DORA-specific supplier fields and supply chain relationships.
All DORA-related supplier fields and relationship items are now included in the supplier log. When changes occur, old and new values are recorded. Additions, edits, and deletions in the Relationships tab are also logged.
Procure to Pay
Validation of order number format per company
An improvement has been implemented to check whether order numbers comply with a company-specific format. A regex can now be configured per company and is applied both during automatic recognition (OCR/PDF/XML) and manual entry.
The full content of this release is explained below.
Contents
Source to Contract (S2C)
General
- Various text corrections have been made.
- Various translation corrections have been made.
- Various layout corrections have been made.
- Various performance improvements have been implemented.
Fixes
| Description | Location |
|---|---|
The issue where a digital signature could not be saved has been resolved. |
E-Signing |
|
The issue where spaces could be entered in email fields has been resolved. This prevents errors when sending notifications and verification codes and ensures consistent and correct processing of email addresses. |
Spend
Fixes
| Description | Location |
|---|---|
The readability of the graphs in Spend Management has been improved. When building the graphs in the tabs for unique relationships (cost centres, cost types, and companies), dimension names are now truncated to a maximum of 35 characters (including name and reference). |
Spend |
Vendors
New
Field ‘Legal name’ added to export and query in vendor management
The field 'Legal name' has been added to the 'Export all fields' functionality in vendor management. When this field is set to visible via Admin › Vendors settings › Personalisation › Field visibility, it is now included in the export generated by the ‘Export all fields’ button.
Additionally, the field has been added to the vendor table query, ensuring that reports and analyses are complete.
This improvement provides a more complete dataset in exports and enhances information consistency.
GraydonCreditsafe data added to vendor details
The integration with Graydon has been replaced by the new GraydonCreditsafe Connect API.
In the vendor details, the field GraydonCreditsafe ID has been added (previously GraydonID) with a button to retrieve data. If no ID is present, an ID can be retrieved via the button based on vendor information such as name and country. When an ID is available, basic information such as name and address can be retrieved and displayed in a pop-up, similar to the KVK functionality.
Additionally, in the 'External info' tab, a button has been added: Retrieve GraydonCreditsafe data, which shows extensive information such as general vendor data, credit score and risk checks (PEP, sanctions, adverse media). The integration also supports partial data display when access to all data is restricted by the used access credentials.
Fixes
| Description | Location |
|---|---|
The issue where deleting a bank account did not always work has been resolved. |
Vendors |
The colour of the buttons in Vendor Rating has been adjusted for consistency. The button ‘Delete rating’ is now red, matching other delete buttons, and the button ‘Unarchive’ is yellow, as usual for archive/unarchive buttons. |
Vendors > Vendor Rating |
The explanatory text under the field ‘Currency’ in the vendor details is no longer always displayed. The text is now only available via the information icon, as with other fields. |
Vendors |
The scores in the survey results overview are now rounded to two decimals, just like in the detailed view. |
Vendors > Vendor Rating > Survey results |
Contracts
Fixes
| Description | Location |
|---|---|
| The issue where an ampersand (&) in a free field of a contract was incorrectly saved as & or ;amp; has been resolved. The value is now correctly processed and saved, ensuring proper display in contract overviews. | Contracts |
| The issue where contract conditions were not properly formatted has been resolved. | Contracts > Contract conditions |
Admin
Fixes
| Description | Location |
|---|---|
The issue where editing an existing currency led to the content of the edit form disappearing after saving a change has been resolved. |
Admin > Tables > Currency |
DORA
New
Improvements for navigation, validation and data completeness
The DORA functionality has been expanded with several improvements to optimise reporting and contract insights.
- A new column 'Open' has been added in the DORA report tabs, allowing direct navigation to the underlying contract or supplier record, depending on access rights.
- Validation for function identifications has been tightened: references must start with a capital F followed by a number, duplicates are prevented, and checks are also applied during import and in report field 06.01.0010.
- In supply chain entries, new fields have been added for the ultimate parent organisation, including name, identification code, and type code (LEI, EUid, VAT, CRN), visible for free-text suppliers and included in report fields 05.01.0110 and 05.01.0120.
- Additionally, the general contract overview has been expanded with extra DORA data points such as function identifications, critical functions (Yes/No), IT services, and entities/locations using the contract.
These improvements provide faster navigation, better data validation, and more complete reporting for financial institutions.
Logging added for changes in DORA fields
All DORA-related fields in supplier, contract, and admin data are now fully logged.
For each change, old and new values are recorded with readable names.
Additionally, insertions, edits, and deletions of data are registered at the appropriate level.
This expansion increases traceability and simplifies audits and problem analyses, improving the reliability of critical data.
Procure to Pay (P2P)
General
New
Department field in user configuration editable only with proper permission
The field Department in user settings is no longer editable by all users by default.
This field can now only be changed when the user has the following permission:
users:can_edit_all_usersThis change prevents unauthorized modifications. Regular users see the field as 'read-only', while authorised users can edit it.
Extension of audit for items with applicable workflow and used route
The edit log of items where workflows can be applied (such as invoices, purchase requests, purchase orders, and goods receipts) has been extended with a link to the used route.
Previously, it was not visible which EasyRoute or AdvancedRoute was applied during processing.
With this change, insight is provided into the applied route, similar to how matching tolerances are displayed.
This helps in analysing workflow behaviour.
Performance improvements for 'Quick Access' filters and invoice overview
Performance improvements have been implemented to significantly speed up loading times and optimise the user experience.
Loading of the invoice overview has been optimised, improving overall response time.
Additionally, the activity filter no longer shows only the activities of the filtered invoices but all activities. This reduces database load as activities are not recalculated with every refresh of the invoice overview.
These changes provide a faster and more stable user experience, especially when using personal 'Quick Access' filters.
Routty connector supports additional file types with multiple attachments
E-invoices from Routty now support multiple attachments besides PDF files.
Previously, all attachments without a filename were saved as PDF, which caused limitations when processing files such as Excel sheets.
This change ensures correct processing of various file types and improves integration with Routty for E-invoicing.
Fixes
| Description | Location |
|---|---|
An issue has been resolved where missing note fields blocked the migration of custom fields. The migration script has been adjusted so that note fields are correctly processed, even when they are absent. |
|
| The API now processes order, goods receipt, and purchase request data separately, so data from different sources are no longer merged. This ensures correct and independent processing of all records. | |
The issue where DTS could not export values from custom fields has been resolved. Custom fields are now supported, so linked values are correctly included in the export. |
AP Automation
New
Compliance report export without limit and improved filters
The compliance report is no longer limited to 2,500 rows and is now generated via
'My requested files', similar to the audit report.
This allows larger datasets to be fully exported without having to manually split the report into multiple separate reports.
The export now contains an additional criteria tab in Excel, making the applied filters clearly visible. Additionally, the filter component has been extended: the company can now be selected as a multi-select, and the following permission remains company-specific:
invoice:can_access_compliance_reportThis change makes use of this reporting function more efficient and better suited for financial analyses.
Validation of order number format per company
The order number format is now validated based on a regex that can be set per company in the company settings.
This validation applies to both automatic recognition (OCR/PDF/XML) and manual entry.
When an order number does not comply with the set format, processing is stopped.
This addition improves data quality and prevents errors when matching orders and invoices.
Workflow Update: Ignore Header Charges in the "Waiting for goods" step
The workflow action 'Waiting for Goods' now supports an extra parameter to exclude header charges when determining whether goods have been received.
Previously, this step was only executed correctly when logistic lines were present, meaning invoices with only header charges could not be automatically sent back to the ‘Waiting for goods’ step.
With this change, the workflow can correctly handle invoices that contain only header charges, making processing more consistent.
Fixes
| Description | Location |
|---|---|
| An issue has been resolved where the logo was not immediately saved for a new company configuration or vendor setting. Now, the logo becomes visible immediately after the first save without needing to upload again. | AP Automation > Company settings |
The issue where filtering invoices by a combination of companies and dimension values led to an error message has been resolved. Creating an advanced filter with multiple companies and dimension values now works correctly, displaying the correct dataset without errors. |
AP Automation > Advanced filter |
| The issue where the preview of a selected invoice was not correctly updated after deselecting invoices has been resolved. The preview now automatically adjusts to the first selected invoice. If no invoices are selected, the message “No invoice selected” appears. | AP Automation |
The issue where not all information was clearly displayed when linking invoices has been resolved. The block per invoice now shows, besides invoice number, invoice date, and total amount, also the scan date (date only, no time). Labels have been added to distinguish: “(invoice)” after invoice date and “(scan)” after scan date. |
AP Automation |
The issue where selecting a dimension value from a PDF caused a crash has been resolved. The behaviour has been adjusted so that selecting a value from a PDF no longer causes an error. |
AP Automation |
Procurement
New
Addition of salutation field in purchase order PDF
Relocation of Procurement permissions to Limited License
procure:can_read_all_goods_receipt procure:can_read_all_purchase_order procure:can_read_all_purchase_request procure:can_use_freetext_delivery_location
New permission for limited approval of purchase requests
A new permission has been added:
procure:can_use_shopping_cart
This permission restricts approval rights to purchase requests assigned to the user's specific workflow step.
Users with this permission can only approve requests that are in their assigned workflow step and have access to the purchase request overview, but see only requests relevant to their step.
This new permission improves workflow control and ensures approvals remain within the correct responsibility.
Loading indicator added when loading shopping cart
A loading indicator has been added that is visible while the shopping cart page is loading.
Previously, the page remained blank when a user went to the shopping cart after uploading an xlsx file via the confirmation form, which could cause confusion.
The loading indicator now clearly shows that the page is still loading, improving the user experience, especially with large shopping carts or slow network connections.
Fixes
| Description | Location |
|---|---|
The issue where the hook URL of OCI webshops was sometimes double encoded has been resolved. With this fix, the URL is processed correctly, preventing errors when opening the URL. |
Procurement |
ℹ️