NEXT 202609 - Release date: 25-02-2026
Source to Contract
Show notes in reminder emails
Reminder emails for supplier and contract notes now contain details of the note. The content of the note is shown directly in the email, along with extra information such as the note type, contract number and name and supplier. This makes reminders clear, informative, and immediately actionable.
Procure to Pay
Advanced Search function added to 'Procurement'
A full Advanced Search function has been added to the 'Procurement' module. This new functionality allows for more detailed and efficient searching within the procurement process. Users can now enter specific search criteria, making it easier and faster to find relevant information.
The full contents of this release are explained below.
Contents
General
New
Procurement Value Management – core improvements
Various improvements have been implemented in Procurement Value Management regarding goals, workflows, events, supplier selection, and reporting. These improvements focus on supporting complex real-life situations such as negative impact, more extensive selection, and more accurate value creation recording. This provides a more robust basis for further rollout and reporting.
ℹ️
*Procurement Value Management is currently in the 'Controlled Release' phase and is not available in every environment.
Dimension reference numbers in Budget Management
In Budget Management, when linking and displaying dimensions, reference numbers are now visible alongside the name for companies, suppliers, contracts, cost centres, cost types, cost centres, projects, and free dimensions. Dimensions are sorted by reference number and the budget detail header contains a tooltip with reference and name. This increases recognisability and reduces selection errors in large datasets.
ℹ️
*Budget Management is currently in the 'Controlled Release' phase and is not available in every environment.
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 made.
New
Mandatory task description
The Description field is now mandatory for all types of tasks, regardless of whether the task is created or edited from general tasks, suppliers, contracts, planning board, or default settings.
This ensures all tasks contain clear context and follow-up is more consistent.
Simplified login page with updated references
The header of the login page for both the customer portal and supplier portal has been cleaned up.
References to Home, Pricing, Blog, Contact, and Login have been removed; the Support button now links directly to the help centre and the ISPnext logo leads to ispnext.com. This provides a calmer and more focused start screen.
Note content in reminder emails
Reminder emails for supplier and contract notes now directly contain the full note text, supplemented with note type, contract number and name, and supplier name. The email is thus immediately usable without extra clicks to the application.
Fixes
| Description | Location |
|---|---|
| Fixed: disabling editing in workflow steps also blocked viewing and downloading documents. Users can now always open and download documents within an information request, even if editing is disabled. Action buttons next to the document link remain disabled as expected. | Workflows |
| Fixed: the api/vendors/vendors endpoint gave a technical error with overly long text fields. A clear validation error now appears if the input is too long. | API |
| Fixed: the issue where an Excel export could fail if the overview name was longer than 31 characters. Table names are now automatically shortened so the export always works, even with long names. | Exports |
| Fixed: the issue where bullet points within HTML formatted text were not displayed correctly in previews and overview tables. Entering multiple blank lines has also been improved so the cursor now behaves correctly. Both display and input are now consistent and predictable when editing HTML formatted text. | HTML text fields |
Vendors
New
Prevent sending errors when requesting information without email addresses
It is no longer possible to send information requests to suppliers who do not have an email address. When sending, it is checked whether all linked suppliers have at least one contact with a valid email address. If not, the send button is disabled and a message appears that one or more suppliers do not have an email address.
This adjustment prevents the same information request from being sent multiple times by mistake and reduces errors in information requests that include multiple suppliers.
Fixes
| Description | Location |
|---|---|
| Fixed: the issue where unclear error messages appeared when returning an information request to the customer. Exceptions are now correctly logged and shown to the user as a clear message. | Information request |
| Fixed: surveys were shown for suppliers even if the corresponding audit record was missing. The system now checks whether the linked survey audit id exists, so only valid surveys are visible. | Vendor details |
| Fixed: the issue where sending login codes to supplier portal users did not work. This now works as expected again. | Supplier Portal |
Contracts
New
Aligned authorisation labels for contract and supplier documents
Authorisation labels now work for contract documents in the same way as for supplier documents. Labels are multi-select, visibility is based only on your own label assignments, and the document overviews have a new column for authorisation labels.
Document access thus follows a smooth authorisation pattern for both supplier and contract documents.
Spend
Fixes
| Description |
|---|
| Fixed: the issue where the chart SM: % OrderInvoices per company per period {period} in Spend gave incorrect results because empty invc_orders_log values were counted as invoices with orders. The stored procedure has been adjusted for correct recognition of empty order logs. Other related chart procedures have also been checked for similar problems. |
| Fixed: the issue where spend data from information requests was not saved in the contract after workflow approval. The audit was successful, but the totals were not saved. A check has now been added to find and update the correct contract/year. |
DORA
New
DORA report: only data for critical function identifiers
The DORA report now only shows detailed data for function identifiers marked as critical. For rows where field 02.02.0050 is not critical, various subsequent fields remain empty and tab 07.01 is only filled if at least one critical function is linked. This keeps the report clear and better matches current reporting requirements.
Procure to Pay (P2P)
General
Fixes
| Description |
|---|
| Fixed: the MultiReferenceAutoComplete component could not be set as mandatory. The field incorrectly gave errors on loading, did not revalidate after changes, and did not work with the form processor, causing error messages to remain. The component now supports mandatory validation, integrates with the form processor, and validates correctly on changes. |
AP Automation
New
Support for alternative quantities in detail mapping
Detail mapping now supports alternative quantities and units on invoice lines from XML invoices.
These fields are available in the mapping, supported in BRE rules, and integrated into the import pipeline. This means invoice lines better match supplier data and less manual correction is needed.
AI recognition for landscape invoices
nextAI now automatically detects whether an invoice is portrait or landscape and processes both variants without extra steps. The conversion logic maintains the correct proportions so invoice data can be fully read from landscape PDFs. This prevents extra steps for users.
Localisation VAT ID in supplier data and AP Automation
A new field VAT code (local) has been added to both Vendor master data and Vendor Settings.
This field (localisation_vat_id) is supported in the Vendor APIs, shown in the invoice header and supplier information, and can be imported via DTS.
For master data import, the value from Vendor Settings is used when the ERP does not provide a localisation VAT ID. This provides complete support for country‑specific tax identifiers, such as NIP.
ℹ️
*Please note:
This feature may require a configuration change that must be requested via a ticket.
This feature may require a configuration change that must be requested via a ticket.
Convert XML invoice lines directly to cost invoice lines
XML invoice lines can now be converted directly to coding lines when no purchase order is linked. A company-level and per-supplier setting determines whether this functionality is active, with supplier settings taking precedence. If exactly one coding template is available, it is applied automatically so cost invoices are quickly and consistently populated.
ℹ️
*Please note:
This feature may require a configuration change that must be requested via a ticket.
This feature may require a configuration change that must be requested via a ticket.
Split coding lines in AP Automation
Non-PO coding lines and extra cost lines in AP Automation can now be split over multiple lines using a split icon. In the split screen, you set the number of lines, start posting date, and any periodic date increase.
The amount (and VAT amount) is automatically distributed, including rounding; quantity remains editable.
This matches the existing split functionality within Procurement.
The amount (and VAT amount) is automatically distributed, including rounding; quantity remains editable.
This matches the existing split functionality within Procurement.
Show document type when processed via NextAI
nextAI-processed invoices now display the document type “PDF via nextAI” in the document preview, making it clear that the invoice has been processed by nextAI.
Fixes
| Description |
|---|
| Fixed: import_invoice and the front-end did not apply ERPConfig for VAT lines correctly. With the setting “only for cost invoices”, VAT lines were still imported for purchase order invoices and could not be removed from the application. The system now checks the invoice type before processing VAT lines and automatically removes VAT lines when changing to an invoice type that does not support them. |
| Fixed: editing an invoice without a company took too long with many payment terms. The system loaded all details, causing delays. Background processes have been optimised so it now works quickly, even with many payment terms. |
| Fixed: the issue where saving invoice lines (PO and coding lines) deleted and recreated all lines, even with only one change. Invoice lines now receive an ID and are updated incrementally: new lines are added, changed lines are updated, and unchanged lines remain. This improves performance and audit quality. |
| Fixed: the issue where matching tolerances could not be created or updated if date or decimal custom fields were enabled for coding lines. The validation logic has been adjusted, restoring the functionality. |
Procurement
New
Configurable language of the purchase order PDF per company
The language of the purchase order PDF can now be set per company, so international procurement processes better match suppliers and internal preferences. In the company settings under the Procurement tab, two options have been added: a Default PO Language and a PO Language Sorting setting that determines whether supplier settings are followed first or the company default is always used. This ensures consistent, automatically correct language selection on all purchase order PDFs.
Configurable 'return target' for OCI roundtrips
For OCI suppliers/webshops, a new setting Return target is available in Vendor Settings. This determines whether a webshop is opened in a new tab or loaded in the current tab. The chosen behaviour is passed on in the OCI roundtrip and prevents extra tabs or lost context in ISPnext, with room to take into account suppliers who do not support tab closure.
Source reference in 'Purchase Request', 'Purchase Order', and 'Receipts'
A new read-only field Source name is available in the screen configuration for 'Purchase Request', 'Purchase Order', and 'Receipts'. This field shows whether a document originates from an ERP, via the Open API, or directly from Procurement (ISPnext).
This makes the origin of requests and orders always clearly visible, even in environments with multiple source systems.
This makes the origin of requests and orders always clearly visible, even in environments with multiple source systems.
Purchase request number and external ID visible in the application
Purchase requests now receive a configurable Purchase request number, with a number format similar to that of purchase orders. The number is automatically generated for new requests, including API requests (unless an external number is supplied), and can be used in various overviews and search fields. The field is read-only and can be enabled or disabled via the screen configuration.
Advanced Search in Procurement
The Procurement overviews for 'Purchase Requests', 'Purchase Orders', and 'Receipts' now have an Advanced Search similar to AP Automation.
Filtering is possible on, among others, company, supplier, numbers, requester, description, amount, creation and delivery dates, and, where available, Custom Fields and line dimensions.
The results are shown in the uniform Procurement view, so you can quickly navigate to the correct documents.
Filtering is possible on, among others, company, supplier, numbers, requester, description, amount, creation and delivery dates, and, where available, Custom Fields and line dimensions.
The results are shown in the uniform Procurement view, so you can quickly navigate to the correct documents.
Fixes
| Description |
|---|
|
Fixed: the uploaded logo in the vendors settings now matches the thumbnail in the application. Unique file names prevent confusion with multiple thumbnails. The processing of logos and thumbnails has been adjusted so the correct image is shown everywhere. |
| Fixed: hidden fields in the purchase request were still shown when opening the shopping cart. The visibility rules are now applied immediately, so hidden fields remain hidden without refreshing the page. |