NEXT 202642 - Release date: DD-MM-2026
Source to Contract
Targets with target percentage in Procurement Value Management
For a target in Procurement Value Management, a target percentage can now be set in addition to the amount. The cumulative savings percentage achieved is shown on the target card and in the details, including a graph showing the progress per month.
Procure to Pay
Customer numbers per delivery location
A customer number can be recorded for each combination of company, supplier and delivery location. This number is shown on the purchase requisition and purchase order and included in the order PDF and cXML order message.
Source to Contract (S2C)
General
- Various text corrections have been implemented.
- Various translation corrections have been implemented.
- Various layout corrections have been implemented.
- Various performance improvements have been implemented.
Fixes
| Description | Component |
|---|---|
| Resolved an issue where filtering on default values (such as 'This year') in Query resulted in an error message and the query could not be executed. Filters on default values now work correctly again. | Query |
| Resolved an issue where saving an item in the knowledge portal failed without notification and all entered data was lost when the limit of 250 characters for 'Short text' or 100 characters for 'Title' was exceeded. Input is now limited to the maximum length and a notification appears when the limit is reached. | Knowledge portal |
| Resolved an issue where the roles matrix showed a different number of users than the customer user overview because supplier users were also shown. The roles matrix now shows the same users as the customer user overview. | Roles matrix |
| Resolved an issue where parts of Budget Management were not displayed in Dutch after switching languages, despite translations being available. The Dutch translations are now picked up correctly. | Budget Management |
Contracts
New
Archiving a parent contract with active subcontracts
When archiving a parent contract with active subcontracts, you can now choose 'Yes, archive all' (the parent contract and all subcontracts) or 'No, archive parent only'. A third button closes the window without taking any action. The archived parent contract remains visible in the parent contract field of the remaining active contracts.
This change makes it possible to archive a contract without first removing all links to subcontracts.
Larger text fields for description and comments
The standard 'Description' and 'Comments' fields of a contract are now the same width as the contract name field and twice as high.
This change prevents these fields from having to be enlarged manually for each contract.
Query - links between suppliers and contracts available
The table containing links between suppliers and contracts is now available in Query.
This change makes it possible to combine these links with other tables in custom reports.
Fixes
| Description |
|---|
| Resolved an issue where text could be entered in the 'Number of possible extensions' field of a contract, preventing the contract from being submitted. The field now accepts numbers only. |
| Resolved an issue where creating a contract workflow failed without notification when an action referred to a workflow step that had since been deleted or to an archived user. References to deleted steps are now automatically cleaned up, and when a user is archived without a replacement, the assignment is removed from the workflow settings. |
| Resolved an issue where attachment file names on a workflow step were limited to 50 characters, while 255 characters are allowed for suppliers and contracts. File names can now contain 255 characters on workflow steps as well. |
| Resolved an issue where a forward slash (/) in contract text fields was shown in the contract overview but not in the contract details. The forward slash is now also displayed in the contract details. |
Procurement Value Management
New
Targets with target and savings percentages
For a target, a target percentage can now be set in addition to the amount. The amount remains mandatory, the percentage may contain a maximum of two decimal places and cannot be negative. When a target percentage has been entered, the target card shows the cumulative savings percentage achieved in relation to that target percentage, with colour coding in which a percentage below the target percentage is shown in red.
A graph has been added to the target details showing the savings percentage per month and the cumulative average, with the target percentage shown as a horizontal line. The cumulative percentage is calculated over the total amounts and not as the average of the individual percentages: 100,000 renegotiated to 90,000 (10%) and 1,000,000 to 800,000 (20%) together gives 19.09% instead of 15%. The results table in the details also contains a column with the savings percentage per result.
This change provides insight into savings achieved in percentages in addition to absolute amounts.
Calculation method for the contribution to a target
When setting a target, a calculation method can be selected. With the first method, the full result is counted when the result period overlaps the target period by at least one day. With the second method, the result is distributed evenly over the result period and only the part within the target period is counted. A result of €120,000 over three years therefore counts as €40,000 towards a one-year target instead of the full amount.
For existing targets, the first method remains the default. The target card shows a label indicating which method is used, and with the second method the details table shows only the result values that actually belong to the target.
This change accommodates the different ways in which organisations allocate savings to targets.
Import results
Results can now be imported in bulk using the new 'Import results' button, located between the buttons for importing events and adding an event. The button is available to users with the Value Management manager role. Results are linked to an existing event using the event ID, and that event must have the status 'Open'.
The import is additive only, so existing results are not changed. Imported values are included in event totals, targets and results reporting. In the event of errors, the relevant rows are shown so that they can be processed again.
This change makes it possible to load historical savings data quickly.
Budget amount on result
For a result of the price movement type, an optional budget amount can now be recorded in addition to the existing amount fields. An explanation of how the field works is shown next to it. The expanded result details show the budget amount, the amount saved compared with the budget and the corresponding savings percentage. The same data is included as columns in the results report.
This change provides insight into the total added value compared with the budget, in addition to the savings compared with the original offer.
Company as a setting for targets
Companies can now also be selected for a target, so that only results from events for those companies are counted. If no selection is made, all companies are included, and if no selected impact type is specified, all impact types are included. A company filter has been added to the target overview. Targets without a company selection remain visible at all times, regardless of the selected company filter.
This change makes it possible to track targets per company.
Vendors
New
'(De)Select all' buttons in additional locations
The '(De)Select all' button has been added to product selection for a new information request in the Supplier Portal and to both lists for selecting contracts in an email campaign.
This change makes selecting large numbers of items faster.
Information request remembers opened sections
For each user, the sections of an information request that were open (such as supplier details, contacts, questionnaires and documents) are remembered. When opening a subsequent information request, the same sections are opened.
This change reduces the number of clicks when processing multiple information requests.
Default order for bank account type
When entering or editing a bank account, IBAN is now at the top of the selection list for the type and is therefore selected automatically. This applies to the forms in the application, the Supplier Portal and the Supplier Data Portal.
This change makes entering bank accounts faster.
Fixes
| Description |
|---|
| Resolved an issue where a supplier contact added as a respondent to a supplier assessment subsequently also appeared in internal user lists, such as those for vendor managers, contract managers and contract owners. Respondents are now used exclusively to send the questionnaire. |
| Resolved an issue where saving a filter with multiple selected values (such as multiple categories) in the contacts overview caused the search results to disappear and clearing the selection did not work. The filter is now applied correctly and can be cleared again. |
| Resolved an issue where the 'All fields' export in Vendor Management could also contain archived suppliers. The export now contains active suppliers only. |
| Resolved an issue where the supplier overview displayed an error message for users with Italian, Polish, Czech or Spanish as their language. The overview now works for all available languages. |
| Resolved an issue where a request in the Supplier Data Portal could become stuck when processing the approved data in Vendor Management failed after the workflow had been completed. If processing fails, the final workflow step now remains open so that the request can be picked up again. |
Procure to Pay (P2P)
General
- Various text corrections have been implemented.
- Various translation corrections have been implemented.
- Various performance improvements have been implemented.
New
P2P modules added in the same order as S2C and Value Management
The modules in the P2P navigation are now in the same order as in S2C. Value Management is new in the P2P navigation and is visible only to users with the s2c:can_use_value_management permission. For existing environments, this permission is disabled by default. In addition, the permissions for the S2C modules have been renamed.
This change ensures consistent navigation between S2C and P2P.
Predictable precedence of permissions
When a user has both a generic and a company-specific permission, the e-invoice and coding template overviews now take the generic permission into account instead of limiting the data to the company-specific permission. Adding a company-specific role therefore no longer results in an unexpected loss of access.
This change makes the effect of permission configuration more predictable.
Assign document directly to the user from a user field
In workflows, a document (purchase requisition, purchase order, goods receipt or invoice) can now be assigned to the user specified in a user field on the document, such as the person on whose behalf the purchase is being made. Absence is taken into account.
This change makes routing possible without using functions or fixed approvers as an intermediary.
Recurring maintenance mode across midnight
A recurring maintenance mode can now run across midnight in a single entry, for example from 18:00 to 07:00 the following morning. Instead of an end time, a duration is set, with the end time shown as a read-only field.
This change prevents background processes from briefly becoming active again around midnight.
Improved preview of advanced routes
The preview of advanced routes for purchase requisitions, purchase orders and invoices has been improved: whitespace, alignment and separator lines have been adjusted, and approver numbering now logically starts at 1. The term 'Function descriptions' has been removed to save space.
This change makes the preview clearer.
nextAI transparency banner
A standard transparency banner has been added to screens where nextAI is used, namely to the checkout page of Quote Capture and below the feedback button in AP Automation. The banner links to the article about the responsible use of nextAI, in Dutch or English depending on the language.
This change supports the transparency requirements surrounding the use of AI.
Filter by supplier status for AX2012 import
When importing suppliers from AX2012, you can now filter by a supplier's blocking status, so that only suppliers with the desired statuses are imported. Suppliers marked as inactive or blocked can therefore be excluded from the import.
This change prevents unnecessary clean-up and incorrect supplier visibility for requesters.
AP Automation
New
Amount fields recalculated only after leaving the field
Amount fields in invoice processing are now recalculated only after leaving the field, rather than while typing. The decimal comma is read as the decimal separator, and dependent totals are recalculated when leaving the cell.
This change prevents partially entered amounts from being unintentionally supplemented with 00 or processed without a comma.
Approvers of split invoices visible in the redesigned invoice view
In the redesigned invoice view, for a split (parallel-approved) invoice, you can see who approved each part through the audit of the logistics lines and coding lines. This was previously available only in the classic view.
This change gives AP staff full insight into the approval steps for split invoices.
Supplier recognition using unique identification (nextAI)
When recognising the invoice header using nextAI, the unique identification of a supplier is now taken into account. If the IBAN, VAT number or Chamber of Commerce number returns multiple suppliers, the unique identification determines the correct supplier; if these details are missing from the invoice, the unique identification is searched for in the recognised data.
This change increases the number of invoices for which the supplier is recognised correctly straight away.
Validation of invalid characters in the invoice number
Validation has been added to check whether an invoice number contains invalid characters, such as an unusual hyphen. When validation is enabled, an invoice with an invalid invoice number is marked as invalid upon import and submitted to an AP employee for processing.
This change prevents transaction data from the ERP system from being unable to link to the invoice.
M3 dimension ranges via OpenAPI
Dimension value ranges from Infor M3 are now accepted by the OpenAPI and processed in the M3 import. During an import, dimension value links are created, updated and removed so that they correspond to the ranges supplied by M3. This also applies when there are multiple ranges per dimension. When coding an invoice line, only dimension values within the imported ranges can therefore be selected.
This change aligns with the existing support for other ERP systems.
Fixes
| Description |
|---|
| Resolved an issue where 'Update purchase order' also included order numbers that appear in the invoice header but are not used on any invoice line. Only order numbers actually used on the lines are now included. |
| Resolved an issue where advanced dimension rules from the ERP system could result in unintentionally mandatory dimensions and too many values being filtered out during coding. Importing advanced dimension rules can now be disabled per ERP connection. |
| Resolved an issue where, in the field for advisers by function, all functions could be selected when requesting advice, including functions for which the advice setting was not enabled. Only functions with that setting enabled can now be selected. |
| Resolved an issue where, in the new invoice overview layout, a column filter on a custom field and a saved filter on scan date were not applied correctly and all invoices continued to be shown. Both filters now correctly limit the list. |
| Resolved an issue where an XML invoice was not processed when the corresponding PDF file name contained a trailing space. Leading and trailing spaces are now removed from file names. |
Procurement
New
Customer numbers per delivery location
Application administrators can use a new administration page to record a customer number for each combination of company, supplier and delivery location, with the delivery location being optional. A customer number for the delivery address and a customer number for the invoice address can be entered per record. Records can also be managed through import and export.
The customer number is shown on the purchase requisition and purchase order, printed on the order PDF and included in the cXML order message, where it replaces the delivery location code once a customer number has been entered. The masterdata:can_edit_customer_numbers permission is required to create and edit customer numbers.
This change enables suppliers to link incoming orders to the correct customer more quickly.
Obligo report with filters and dimension descriptions
When creating the Obligo report, an intermediate screen appears with four optional filters: company, delivery date, order creation date and supplier. The report contains only outstanding lines within the selected criteria and is generated as a requested file. For each dimension, the export contains both the code and the description in separate columns. The permission for the Obligo report can be granted per company, meaning that only companies for which the user has authorisation can be selected.
This change makes the report more useful for month-end closing and supports the separation of permissions per company.
Fully URL-encoded HOOK_URL for OCI punchout
For OCI punchout connections, each supplier setting can now be configured to use a fully URL-encoded HOOK_URL, in addition to the existing partially encoded variant. Existing connections remain unchanged.
This change makes it possible to connect suppliers whose OCI implementation requires a fully encoded HOOK_URL.
Fixes
| Description |
|---|
| Resolved an issue where the total amount was shown on the order PDF even though the amount on one or more order lines was hidden. The total amount now contains only the amounts of lines that are not hidden. |
| Resolved an issue where users with permission to read all goods receipts could see only the goods receipts in which they themselves were involved. The permission now shows all goods receipts within the companies for which read access exists. |
| Resolved an issue where, after deleting the first line of a purchase requisition with multiple suppliers, the email address of the deleted line remained on the purchase order. The email address, subject and content are now updated to those of the new first supplier. |
| Resolved an issue where budgets were not refreshed after adding or removing a free-text line on a purchase requisition or purchase order, which could result in outdated budget data being displayed. Budgets are now updated immediately. |