• 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

New email server for outgoing emails

From this release onwards, emails from Source to Contract will be sent via a different email server. The sender address remains the same and no action is required. For organisations that send emails through their own mail environment, such as SMTP, Exchange Web Services or Microsoft 365, nothing will change. If emails are not received or end up in spam, please contact support.

 

Retrieve only recently changed vendors and contracts via the API

Integrations connecting to ISPnext via the API can now request only the vendors or contracts that have recently changed by specifying a number of calendar days, for example 3. With 0 days, only records changed today are returned, and without specifying a number everything works as before. A negative number or text produces a clear error message; the same applies when the option is used with a list other than vendors or contracts.
This change means that a separate report is no longer needed to find recent changes and retrieve each record individually.

 

Fixes

Description	Module
Fixed an issue where the selected columns and column order in Budget Management tables were not retained per user between sessions. This applies to the budget overview and the tables for completed invoices, invoices in progress, hard commitments and soft commitments in the budget details. The settings are now retained.	Budget Management

 

New

Clearer contract overview for long text fields

Long text fields in the contract overview will now be truncated at 200 characters, followed by an ellipsis. This applies to the description, comments and custom fields of the text-box type; fields with formatting (HTML) remain unchanged.
This change keeps the contract overview clear when fields contain a lot of text.

 

 

New

Archived events count towards target progress

Results from archived events will now count towards target progress, target statistics and the savings timeline. Whether an event is archived no longer matters for a target; only the event status determines whether a result counts. Results from completed events count as approved, results from events that have not yet been completed count as in progress, and results from rejected events never count.

A target of €100,000 with an approved result of €30,000 therefore remains at €30,000 after the event has been archived.
This change keeps target progress stable when events are cleared up.

 

Date columns correctly formatted in report exports

In the total report table in Procurement Value Management, columns containing a date, such as the start date and end date of a result, will now be exported to Excel as date columns. This means that these columns can be filtered and sorted directly in the exported file.
This change makes the exported report immediately usable without first converting the date columns.

 

Fixes

Description
Fixed an issue where the savings percentage chart in the details of a target also displayed data outside the target period when results had a longer duration than the target. The chart now displays and calculates only the part of each result that falls within the target period.

 

New

Edit contacts from the total contacts overview

Each row in the total contacts overview can now be clicked, opening the same edit form as when opening a contact in the vendor details. This is available to users with the Vendor Management Moderator role, and the mouse pointer changes to a hand when hovering over a row. After closing the form, including via the close button or cross, and after deleting a contact, the overview is refreshed.
This change makes editing contacts easier, as it is no longer necessary to open each vendor separately.

 

View contacts without the moderator role

Users with the Vendor Management Viewer or Vendor Management Register role can now view a vendor's contacts via a new 'View' button in the vendor details. The forms that open afterwards are read-only. The edit buttons, invitation function (envelope), switch in the 'In Supplier Portal' column and delete button are available only to users with the Vendor Management Moderator role.
This change gives users without the moderator role insight into a vendor's contact details without allowing them to change data.

 

Surepay option in the Supplier Data Portal

Surepay verification for bank accounts in the Supplier Data Portal can once again be activated via a new checkbox in the Surepay integration settings in the administration environment. The checkbox is disabled by default.

When the checkbox is enabled, Surepay functionality is visible in the bank-account entry and edit form in the Supplier Data Portal. This setting has no effect on Surepay functionality in the Supplier Portal.
This change gives organisations the option of making Surepay verification available to vendors in the Supplier Data Portal as well.

 

Contact persons in the Vendors API

The Vendors API now supports an optional section for contact persons, in addition to the existing sections for categories and companies. Multiple contact persons can be provided for each vendor in a single request, with the email address and display name always being mandatory. The API retrieval function also returns the contact persons.

During an update, existing contact persons are matched by email address. A contact person with an error is skipped with a clear warning, without blocking the rest of the request. Values for choice fields such as contact type and title must already exist and are not created automatically. The existing connection with P2P remains unchanged because the section is optional.
This change makes it possible to provide and retrieve vendor contact details via the API as well.

 

Fixes

Description
Fixed an issue where starting a vendor assessment stalled at step 2 because the list of vendors (or contracts) did not load. The list now loads within a few seconds, shows only vendors that are not yet included in the assessment and lists each vendor once; for separated contracts, the contracts remain visible per vendor.
Fixed an issue where valid IBANs from some countries, such as Benin, were rejected with a message about an unknown country code, preventing those records from being imported. All valid IBAN country codes are now recognised.
Fixed an issue where a cleared custom field in an information request retained its old value at the vendor and in new information requests after approval. The field is now also cleared at the vendor after approval.

• Various text corrections have been made.
• Various translation corrections have been made.
• Various performance improvements have been made.

New

Renewed advanced routes for AP Automation and Procurement

The renewed advanced routes provide a new, more flexible way to configure approval and read flows within AP Automation and Procurement. The functionality is available for invoices, purchase requests, purchase orders and goods receipts. Organisations with complex approval flows, including flows spanning multiple companies, can configure and maintain routes more easily.

A route is built from reusable components:

• Criteria groups determine when a route or reader applies, based on criteria such as company, dimension, vendor, custom fields, document type and discrepancy type.
• Approver groups determine who approves. An approver group contains an ordered list of approvers by job title or user, with limits per approver. The order can be changed by dragging, and a workflow visualisation immediately shows the configured route.
• Reader groups and readers determine who receives read access to documents. A reader group contains the users, and a reader links them to one or more criteria groups.
• Advanced routes link criteria groups to an approver group. The Match one or all setting determines whether all or at least one criteria group must be met. The weight determines the priority when multiple routes apply.

All components have the same structure of overview screens, with filters, column options and bulk actions to activate or deactivate items. Items can be exported to Excel in bulk, prepared using a template and imported again.

Every change is recorded in an audit trail with version history, date, employee and a mandatory reason for the change. A previous version can be opened as a snapshot of the configuration at that time, including all field values.

The options available, such as criteria, document types and approver types, are determined per environment in the routing configuration. Permissions can be used per component to specify who may view and who may edit it. More information about configuration can be found in the guide Advanced Routes 2.0.
This change makes configuring complex approval and read flows more flexible, clearer and easier to trace. Because components are reused, changes can be made in one place and every change remains auditable for administrators and auditors.

 

New feedback message for Excel imports

When importing an Excel file in the renewed screens, a clear feedback message will now appear. If an import fails, the message shows a status icon, description and explanation for each line. The message does not close automatically, so the errors can be reviewed calmly, and a brief confirmation appears after a successful import.
This change makes it immediately clear which lines have been processed and which require attention.

 

DTC authorisation errors in the log file

DTC will now write authorisation errors, for example when a new token cannot be retrieved, to the log file instead of displaying them only in the console window.
This change makes it quicker for customers and support to see why DTC is no longer working, for example because of invalid login details.

 

Multiple VAT numbers per vendor from Dynamics 365 Finance & Operations

The connection with Dynamics 365 Finance & Operations supports multiple VAT numbers per vendor. Additional VAT numbers are retrieved when vendor data is imported, and the vendor's VAT number is sent to the ERP system when invoices are posted.

This works only in combination with an additional extension in the ERP system; environments without this extension continue to work as before. Because a vendor is currently created as a separate record per VAT number, the number of vendor records may increase.
This change makes it possible to link and post vendors with multiple VAT numbers correctly.

 

Fixes

Description	Module
Fixed an issue where dates in the audit overviews of the renewed screens, such as maintenance mode, input restrictions and catalogues, were not displayed according to the user's language. In German, dates are now shown as 01.07.2026, 07:41:30 instead of 1-7-2026, 07:41:30.	Audit
Fixed an issue where dragging approver groups mixed up the order and the associated default limits. Approvers and limits now move together to the new position.	Approver groups
Fixed an issue where, for custom fields, the choices on which a field can be based (purchase order, order line, goods receipt and receipt line) were unavailable in environments without Procurement and without an order database. These choices are now available when the ERP system supports custom fields based on order data.	Custom fields
Fixed an issue where a DTS mapping for a goods receipt without a link for the goods receipt date produced an error when importing a file. The goods receipt date is optional and now remains empty when it is not linked.	DTS

 

New

Renewed invoice view in AP Automation

The invoice view in AP Automation has been completely renewed to improve performance for invoices with a large number of PO lines or receipt lines. The screen is intended for AP employees processing invoices with many lines, and for organisations experiencing performance issues with large invoices. The difference in loading time is most noticeable for invoices with more than 50 PO lines.

The following is new in the renewed invoice view:

• Switch: each invoice can be switched between the old and renewed screen. The switch will remain available for the time being.
• Pagination: PO lines are divided across pages, resulting in significantly faster display, even with hundreds of lines.
• Collapse header: the section containing the invoice details can be collapsed to provide more space for the lines.
• Adjust columns: columns can be dragged and their width can be adjusted. The personal layout is retained per user.
• Renewed icons and validations: all icons have been redesigned and error messages are displayed directly next to the relevant field.
• Refresh PO lookup: a refresh icon next to the PO lookup reloads the linked orders and order lines without opening the screen with outstanding orders. The corresponding invoice lines are then selected automatically.
• Select lines per order: when lines are filtered by order number, the select-all action applies only to the lines of the selected order.
• Renewed search screen for outstanding orders: with additional columns for the PO amount and line amount excluding VAT and the delivery date.
• Amount fields: amounts are recalculated only when leaving the field, allowing them to be entered calmly, including the decimal comma.
• Budget icon: when Budget Management is enabled, the budget icon is also available in the renewed view.

Various other improvements have also been made. The payment date is now visible, dimensions in the header follow the screen configuration, numerical column headings are left-aligned and custom fields on PO lines can be displayed as a popover.
This change provides faster, clearer and more personalised processing of invoices with many lines, without requiring a change to the existing way of working.

 

Renewed search screen for outstanding orders

The search screen for outstanding orders has been renewed while retaining all existing search, filter, sort and pagination functions. Three columns have been added: the order total excluding VAT (header), the line amount excluding VAT (line) and the delivery date (header and line).
This change makes searching for outstanding orders while processing invoices more comprehensive and consistent with the other renewed screens.

 

Order data from M3 Cloud available in Procurement

For Infor M3 Cloud, order data is now synchronised to Procurement in the same way as for Dynamics 365 Finance & Operations and AX2012. This makes it possible to look up purchase orders while processing invoices for M3 Cloud, both using the standard purchase order number and alternative references. Surcharge lines at header and receipt-line level from M3 are also supported and stored correctly.
This change reduces the need to search manually for the correct order for invoices containing a vendor reference instead of the purchase order number.

 

Calculate G-split based on net or gross amount

The G-split calculation can now be based on the net or gross amount of the invoice. The choice is configured per company in the company settings, with net as the default.

A new option is available in the vendor settings to use the company setting. Existing settings are converted automatically, so the behaviour remains unchanged. The functionality, previously available only for SAP environments, is now available to all customers using G-split.
This change provides a more automatic and flexible split of G-accounts.

 

G-split in the ISPnext API for DTS

The ISPnext API for DTS has been extended with G-split, allowing G-split data to be linked from DTS.

 

nextAI invoices with the same additional coding as SmartScan

PDF invoices processed via nextAI now receive the same additional coding value as PDF invoices processed via SmartScan. Existing workflow conditions based on this therefore work in the same way for both processing methods.
This change ensures that an invoice passes through the coding by the AP employee only once.

 

One administrative notification per email for storage errors

When an incoming email containing invoices cannot be stored, for example because of damaged content or an invalid format, one error message will now be sent to the configured administrative address. The message contains the subject, sender address and description of the error; the error is logged once and the email is marked as read, so that the message does not recur during every read cycle. If no administrative address is configured, no email is sent.
This change prevents administrators from being overwhelmed by repeated notifications.

 

In development: importing line-level dimensions from XML

Work is under way to import line-level dimensions from the ISPinvoice XML file, so that the cost allocation per line is transferred directly. Business rules will make it possible to filter, change, add or remove dimensions on a line without affecting the other dimensions on that line. If a dimension or dimension value cannot be found, a clear validation message will appear on the invoice.
This change is intended to eliminate the need to dimension coding lines manually for self-supplied XML documents.

 

Fixes

Description
Fixed an issue where the VAT split indicator and plus button in the invoice header, and the contents of the input field for the entered VAT split, disappeared after saving an invoice with a VAT split. The indicator and contents now remain visible without refreshing the page.
Fixed an issue where the non-deductible VAT amount in the invoice header was not calculated automatically when importing an invoice for which a VAT code with a non-deductible percentage applied. The amount is now calculated as soon as the VAT code, percentage, total amount and VAT amount are known.
Fixed an issue where a purchase order was not found during the step for updating Procurement when the company on the order header differed from the company on the order line, causing the invoice to stall. The purchase order is now found and updated, and ordering for multiple companies in one shopping basket remains possible.
Fixed an issue where validation of recognised data against vendor data was not triggered when processing via nextAI if the IBAN or VAT number on the invoice differed from that of the vendor. Validation now compares the data recognised by nextAI with the vendor data, checking all the vendor's bank accounts for the IBAN.
Fixed an issue where 'select all' and 'deselect all' for lines always changed all invoice lines, even when filtering by an order number. These actions now apply only to the lines visible under the active filter, for purchase order lines, surcharge lines, header costs and coding lines, and applied filters are retained.
Fixed an issue where the nextAI feedback button opened a blank screen for certain invoices, such as invoices that had previously been rejected or deleted, preventing nextAI templates from being created or modified. The feedback button now opens for every invoice.

• Various budget-related calculations have been optimised.

New

Send cXML orders without an OCI connection

Application administrators can now configure in the Procurement vendor settings that purchase orders are sent as cXML without enabling 'OCI active' and without a mandatory webshop URL. Three new settings are available: send cXML, the transmission type for catalogue orders and the transmission type for orders from a free request. Both transmission types have the same options as the existing punchout type and are set to email by default.

If the web service type is selected for either one, the same web service and cXML fields used for OCI appear. The setting applies to orders with catalogue items and orders from a free request.
This change makes it possible for vendors managed through manual item management to receive orders as cXML as well.

 

Default item-category values in nextAI Quote Capture

When nextAI Quote Capture adds a line to the shopping basket, the default values of the item category used will now be applied automatically, such as the dimensions and general ledger account. The result is the same as manually selecting the item category. If the item category on the line is changed, the associated default values are applied again.
This change ensures that the purchase request is complete immediately after importing, without having to select the item category again.

 

Default item-category values when bulk-updating the shopping basket

When selecting an item category in the shopping basket's bulk-update form, the associated coding standards (dimensions) are displayed. A checkbox can be used per field to determine whether the default value is applied, and only the checked fields are written to the selected lines upon confirmation.
This change prevents the coding from having to be completed manually line by line after a bulk update.

 

Accrual schedule and accrual start date in the shopping basket Excel import

The Excel import for shopping-basket lines now also reads the accrual schedule and accrual start date and applies them to the corresponding lines, in the same way as the fields already supported. Re-importing a file exported from the shopping basket returns the same values. If a cell is empty or invalid, the line is imported normally and a clear message indicates which field was skipped.
This change prevents these two fields from having to be entered manually again after the import.

 

Fixes

Description
Fixed an issue where using the fully encoded HOOK_URL with an OCI punchout did not return all data to the shopping basket, causing an error message to appear in Procurement when ordering items. For this variant, the HOOK_URL is now sent fully URL-encoded and the shopping basket returns correctly to the purchase request; the partially encoded variant remains unchanged.
Fixed an issue where the customer-number overview displayed an error for users with company-specific permissions. Users without company-specific permission see all records, while users with company-specific permissions see only the records and choices for their companies.
Fixed an issue where the company filter in the Obligo report remained empty for users with the generic permission for the Obligo report. These users now see all companies in the filter, while users with company-specific permissions see only their own companies.
Fixed an issue where the custom fields in a free request moved to the centre of the screen when the number of lines was set to more than 1, because the period field became visible. The custom fields now remain in place.