NEXT 202606 – Release date: 04-02-2026
Source to Contract
‘Concept’ field now customisable
The Concept field has been added to the standard customisation options within Contract Management. The field can be hidden or provided with an explanation.
Procure to Pay
Open multiple invoices in new tabs
The invoice overview now supports the option to open invoices (up to ten at a time) in new tabs via right-click.
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.
New
Automatic mail server check with notification to Support
When a customer uses their own email server and an error occurs in outgoing mail, a warning is automatically sent to ISPnext Support. This happens once per day per customer.
The message to Support contains all relevant information so they can act quickly and inform the customer.
Extended validation for environments working with Category Authorisation
Various checks have been added to ensure data consistency. The default category can no longer be deleted or emptied, actions in Spend Analytics are blocked when no default category is configured, and tooltips inform users about missing configurations.
New status ‘In progress’ for tasks
Tasks can now be visually marked as in progress. When selected, the status changes, the user is registered as the executor, and this status appears in all relevant overviews. All action buttons are also registered in the edit log.
Improved logging for 'Switch to user'
The edit log now records when a user is taken over via the Switch function.
Actions where Client Admins take over each other are no longer allowed.
Fixes
| Description | Location |
|---|---|
OpenAPI specification now uses correct content types and no longer causes blockages. |
|
| Issue resolved where ContractEndDate notifications were not sent if no period was set in the notification, even if the contract did have a period via the procedure. The logic has been adjusted so the notification is processed as soon as the notification or contract has a valid period. | Notifications |
| An issue resolved where a certain 'stored procedure' caused timeouts with large datasets. The query has been optimised in several ways. As a result, retrieving cost centre groups is now faster and more reliable. | Data Imports |
| Resolved: when importing data, a clear message now appears if a column contains data that is too long, instead of an unclear technical error message. | Data Imports |
| Resolved: the VL:URLLINK placeholder in task notification emails was not replaced, causing the LOGIN button not to work. The correct links are now displayed in task assignments. | Notifications |
Vendors
New
Category visible in checklist item overview
The checklist item overview within Vendor Management now contains a column for supplier categories with filter options. The column is hidden by default but can be activated via the column picker.
Establishment number / location code added to vendor query table
The query module now supports filtering, sorting, and reporting on establishment number or location code. This is especially valuable for datasets using Chamber of Commerce data.
Fixes
| Description | Location |
|---|---|
| Resolved: the mandatory field 'Country of origin' remained visible when selecting a supplier. This field is now only shown when needed and disappears correctly upon supplier selection. | Vendors |
| Issue resolved where adding a supplier in Vendor Management did not work for French users. French language support has been restored and the form now works correctly. | Vendors |
Contracts
New
‘Concept’ field now customisable
The Concept field is now part of the standard fields that can be managed via the customisation panel. Administrators can hide the field or provide an explanation via an information icon.
Obligation ID visible in screens and queries
A unique obligation ID is now directly visible in both the contract details and query commands. This makes obligations easier to identify, consult, and report on.
Fixes
| Description | Location |
|---|---|
Contract details load correctly when a custom field contains a list. |
Contracts |
| The issue where the reference column for contracts used the same values as the supplier reference has been resolved. There is now a separate value for the contract reference, so both labels can be managed separately. | Contracts |
| Issue resolved where the contract form was displayed incorrectly when the language was set to Dutch. | Contracts |
Spend
Fixes
| Description | Location |
|---|---|
| Resolved: an issue where a comma in a cost reference resulted in an empty display without an error message. The field value is now correctly processed and displayed, including commas. | Spend |
| Issue resolved where the Spend report planner failed with non-numeric cost centre references. Input validation has been improved to prevent typing errors and ensure reliable report processing. | Spend |
DORA
New
Improved DORA reporting without duplicate rows
Contracts managed by multiple contract managers are no longer displayed in multiple rows. The names of all contract managers are now shown as comma-separated values within a single row. This makes the report clearer and ensures more accurate analysis.
Fixes
| Description | Location |
|---|---|
| Resolved: the DORA tab in contract details is now only editable for users with the contract management moderator role, instead of vendor management moderator. | Contracts/DORA |
Procure to Pay (P2P)
General
New
New permission for managing Custom Fields
The management of Custom Fields has been expanded with a new permission, giving organisations more independence in configuring field structures.
customfields:can_editUsers with this permission have access to the Custom Fields menu, where new fields can be added and existing fields can be edited. This avoids dependence on partners or support and speeds up the change process within the application.
Advanced autocompletion with requester/start user
Workflows can automatically proceed through steps when the requester is the same person as the one responsible for the next activity. This prevents unnecessary manual actions and speeds up routing, mainly for purchase requests.
Fixes
| Description |
|---|
| Issue resolved where changing a user's department was not saved correctly. The permission key has been corrected, so the department is now saved correctly. |
AP Automation
New
Clickable URLs in notification emails
URLs in notification emails are now displayed as clickable HTML links.
This provides a more direct route to the information from the notification email.
The URLs now also work in modern email clients such as Outlook, where links from no-reply mailboxes often did not (properly) function.
Users can navigate directly from notifications to the correct invoice, task, or workflow without having to copy a URL.
Configurable discount calculation based on amounts including or excluding VAT
A new setting in payment terms determines whether payment discounts are calculated on the amount excluding or including VAT.
This setting is visible in both the management environment and the front end (if manual master data is enabled) and is used by both the UI and APIs. This ensures discount calculations better align with legal requirements in different countries.
This setting is visible in both the management environment and the front end (if manual master data is enabled) and is used by both the UI and APIs. This ensures discount calculations better align with legal requirements in different countries.
Open multiple invoices in new tabs
Invoice processing is more efficient thanks to the ability to open multiple invoices at once in new tabs. Via the context menu, users can open up to ten invoices at a time, with dynamic labelling (singular/plural). This supports comparisons, parallel processing, and quicker handling.
Classification settings available in the front end
⚠️
Note:
The menu 'Inbox settings' has been renamed to 'Classification settings'
The menu 'Inbox settings' has been renamed to 'Classification settings'
The previous Inbox settings have been renamed to Classification settings, and important parameters, such as ignored file extensions, timeouts, expiry rules and keyword lists for invoice recognition, are now directly configurable.
The following updated permission gives access to all editable fields:
The following updated permission gives access to all editable fields:
classification:can_use_classification
Support for VAT codes with 100 percent or full exemption
VAT codes with an exemption percentage of exactly 100 are now supported during import and processing. This is especially important for regions and ERP systems that require fully non-deductible VAT. Values outside the range 0–100 remain excluded for data quality.
SAP dimension ‘Personnel’ available in import and export*
The SAP Personnel dimension has been added to both the master data importer and the invoice exporter. The value is validated and displayed according to the configuration of the relevant general ledger account.
Fixes
| Description |
|---|
| An issue when exporting large invoices with many logistic lines to Spend has been resolved. Large invoices are now reliably exported without memory problems. |
| Resolved: IBAN values recognised by AI are now cleaned by removing unnecessary characters, so they match supplier data correctly. |
Fixed an issue where matching tolerances could not be created or updated when custom fields of type date or decimal were enabled for coding lines. The validation logic incorrectly used an condition; this has been corrected, ensuring matching tolerances function normally again. |
Procurement
New
Visibility of price and quantity configurable per request line
Each line within a purchase request now has options to show or hide price and quantity. By default, these values are inherited from supplier settings but can be adjusted per line. The PDF output follows exactly what is set per line.
This gives better control over which information may or may not be visible to suppliers.
"On behalf of" for purchase requests
When creating a Purchase Request, another colleague can now be selected as the formal requester. This is fully integrated into routing, PDF output and authorisations. The actual submitter is not shown on the PDF, so the request remains administratively correct. This smoothly supports absences, substitutions and delegated tasks.
The new permission below determines who may use this feature:
procurement:can_use_on_behalf_of
Improved currency logic when selecting suppliers
When a supplier is selected, a new mechanism automatically determines which currency should be used. The system checks, among other things, supplier settings, user settings and company settings. This results in consistent and error-free currency choices.
Approval information on the Purchase Order PDF
In company settings, it is now possible to choose which approval information should be included on the PDF: none, the last active approvers from the workflow, or a manually set approver with optional signature. The PDF contains fields for name, date and signature image and is filled in automatically.
Receipt lines can be completed with zero quantity
Receipt lines can now be completed with zero quantity or amount. This makes it possible to neatly close cancelled or undelivered order lines and prevents open lines in the receipt administration.
DTS support for Vendor Settings*
Vendor Settings are now available as a new file type within DTS. All relevant vendor settings can be mapped and processed via the API. An additional backend setting determines which fields may be safely updated.
ℹ️
*This feature requires extra configuration and may need a licence extension. To enable it, please submit a configuration change request in the Help Centre.
Fixes
| Description |
|---|
| Resolved: default values from the user configuration were sometimes not applied at step 2 of the shopping cart. These are now set immediately before backend data is loaded, for consistent operation. |
| Issue resolved where rejecting a goods receipt incorrectly changed the values of other order lines. Receipt values now remain correct after rejection. |
| Issue resolved where default company, currency and delivery location were not automatically set in the shopping cart. Values from the article or user default are now correctly applied, with article values taking precedence. |
| Resolved: ISPnext no longer crashed when the budget service was offline or returned a 500 error. Budget errors are now handled gracefully without crashing the application. |