• 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

Contract management - filters in 'Total Spend' overview

In the financial tab of a contract, the 'Total Spend' overview has been expanded with filter options. Via a multi-select dropdown, filtering can be done by contract name and year, allowing the data to be better tailored to the desired period or contract selection.

This adjustment makes the financial overview of contracts clearer and more usable for analyses across multiple years or contracts.

Contract management - creation date not overwritten when activating draft contract

When activating an existing draft contract, the contract's creation date was overwritten with the activation date. This had no impact on the contract itself but caused incorrect time registration in the underlying data. The creation date will now remain unchanged upon activation.

This adjustment ensures correct display of the contract history and prevents discrepancies in reports based on the creation date.

Contract management - task execution date based on contract end date

When a task is automatically created via a contract notification upon approaching the contract end date, the execution date of the task will now be set to the contract's end date instead of the notification dispatch date. If no end date is available, the notification date is used as a fallback.

This adjustment ensures that automatically created tasks have a logical execution date that aligns with the actual contract situation.

nextAI - Contract AI - improved processing of secured PDFs

The detection of potentially harmful content in PDF files uploaded for analysis via nextAI has been improved. PDF files with scripts or other secured content were previously incorrectly flagged as harmful, even when the document was safe. The detection logic has been refined to prevent unnecessary rejections.

This adjustment ensures that PDF files that are safe but contain certain technical characteristics are now correctly processed by the Contract AI.

Creation date and creator visible on tasks

Tasks will now be provided with a creation date and the user who created the task. This information is stored for both manually created tasks and tasks automatically generated by a recurring task schedule. The creation date is available as an optional column in the task overview for tasks, suppliers, and contracts, and is hidden by default.

This adjustment gives contract administrators better insight into the origin and age of tasks, contributing to more effective follow-up and analysis of task activity.

Task management - improved status determination in task overview

The logic determining the status of tasks in the task overview has been expanded. Tasks with an execution date within one month will now automatically receive the status 'To do', unless the status has already been manually set to 'In progress'. This ensures a more consistent display of upcoming tasks.

This adjustment makes the task overview more reliable as a worklist because tasks due in the short term are more clearly visible.

Query - tables for recurring tasks and document links available

Two new tables are available in the Query functionality: the table for recurring task schedules and the table for supplier document links. Both tables can be combined with other tables to create customised reports.

This adjustment increases reporting and analysis possibilities by making more contract-related data available via the Query module.

Procurement Value Management - import of event details

An import function for event data is available in Procurement Value Management. Events can be created in bulk using an import template with fields such as name, event type, description, start date, event managers, expected impact value, companies, and suppliers. The import button is only visible to users with the role Procurement Value Manager.

This adjustment makes creating large numbers of events significantly more efficient and reduces manual input when building an event overview.

Fixes

New

Vendor management - improved performance of change log

The change log in Vendor Management has been optimised by adding a database index on the change type. This results in significantly faster loading times of the change log, especially for suppliers with a large number of recorded changes.

This adjustment makes the change log usable in environments with extensive change history without the page slowing down or freezing.

Fixes

Fixes

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

New

Mandatory attachment for purchase requests above threshold amount

Per company, a threshold amount can be set in the settings above which an attachment is mandatory when submitting a purchase request. When the total amount of the purchase request exceeds the set threshold, an attachment must be added before the request can be submitted or forwarded in the workflow. The validation applies both in the shopping cart and in the purchase request itself.

This adjustment ensures that high-value purchase requests are always provided with the necessary substantiation, speeding up the approval process and improving auditability.

Improved processing of ERP responses in system steps

System steps in the workflow that wait for a response from the ERP system (such as registration, posting, and exporting) are now processed more efficiently. As soon as an ERP response arrives, the relevant workflow step is immediately continued instead of waiting for the next processing round. As a fallback, workflow steps that unexpectedly remain waiting are automatically released daily.

This adjustment reduces the processing time of invoices and purchase orders in integrations with external ERP systems and lowers system load with large volumes.

New

AP Automation overview page - improved display and functionality

The overview page for invoice processing has been improved in multiple areas: the due date indicator and discount indicator have been restored, the 'Waiting for credit' status has an explanation when assigning, icons are colour-coded (green for claimable invoices, orange for takeover claims), the display of quick access blocks is more consistent and clearer, and a filter option on attachments has been added. Additionally, the page shows the latest comment when assigning an invoice and a refresh button is available. Finally, an export function to Excel has been added, allowing export of visible columns including active filters.

This adjustment makes daily invoice processing clearer and faster by making relevant status signals and filter options immediately available.

Preserving booking dates per line when closing booking period

When closing a booking period, previously all lines of an invoice were moved to the new period, even if the booking date of a line was already within the new period. From now on, each line is assessed to determine if the booking date falls outside the closed period. Only lines actually in the closed period are updated; lines with a booking date already in the new period remain unchanged.

This adjustment ensures correct distribution of booking lines across multiple periods for invoices with deliberately spread bookings, such as annual licences or spread cost allocations.

nextAI feedback button available based on permission

The feedback button for nextAI in invoice processing is linked to a new permission. As a result, only employees with the appropriate access rights see the button, while approvers no longer see it. Existing users with access to invoice processing are automatically assigned the permission.

This adjustment enables targeted use of the nextAI feedback functionality and prevents approvers from unintentionally using the feature.

Maximum number of attempts when rejecting e-invoices (Routty)

When rejecting an e-invoice, a notification is sent to the e-invoicing provider Routty. If this notification could not be delivered, it was previously retried indefinitely. From now on, the maximum number of attempts is set to three. Upon exceeding this, the e-invoice is marked with an error message and the administrator receives a notification. Via the interface, it is then possible to manually retry sending.

This adjustment prevents failed notifications from being retried infinitely and gives administrators better insight and control over the status of e-invoicing messages.

API endpoint for querying e-invoicing statuses

External systems can now query the processing status of invoices submitted via the e-invoicing API through a new GET API endpoint. The endpoint returns per invoice the document ID, current status (In process, Released, Completed, or Rejected), and the date of the last status change. For rejected invoices, the most recent rejection comment is also included.

This adjustment enables integration systems to query the processing status of submitted e-invoices, which is necessary for compliance with French e-invoicing regulations.

Order type recognisable via nextAI

The 'Order type' field on the invoice header can now be automatically recognised via nextAI. Recognition is only activated when the 'Order type' field is enabled in the screen configuration of the relevant environment.

This adjustment reduces manual entry for invoices where the order type is stated on the document and supports more accurate automatic invoice processing.

Net Landed Costs importable via order database

Net Landed Costs (NLC) can now be imported via the order database. Order numbers are no longer unique on their own but are combined with the order type as a unique key pair, allowing NLC orders to be correctly distinguished from other orders.

This adjustment enables processing and linking of NLC orders via the order database, in line with existing support for other order types.

Fixes

New

Attachments added to goods receipt

When creating or editing a goods receipt, one or more attachments can now be uploaded, such as packing slips, delivery notes, quality certificates, or signed transport documents. The attachments are visible on the goods receipt detail page and via the related documents page of the associated purchase request, purchase order, and invoice. With an additional permission, attachments can also be added to closed receipts.

This adjustment enables central storage of delivery documentation within the platform, eliminating the need to keep documents outside ISPnext.

Order confirmation visible in related documents

Order confirmations are now visible via the related documents page of a purchase request, purchase order, goods receipt, and invoice. From the related documents, it is possible to navigate to the order confirmation detail page. The link works one way: from other documents to the order confirmation.

This adjustment makes it easier to view the complete document flow around a purchase order, including the associated supplier confirmation.

Catalogue linked to OCI webshop connections

In the supplier settings, a catalogue can be linked to an active OCI webshop connection. When a user has a requester restriction group with a catalogue limit, that user sees only the suppliers and webshops connected to the linked catalogue in the search bar and webshop tab. Users without a restriction group see all available webshops.

This adjustment enables restricting access to OCI webshops per user or role, in line with existing catalogue restrictions for items and purchase requests.

Contract reference and contract number both visible during contract selection

When searching for and selecting a contract in a purchase request or purchase order, both the contract reference (the primary business identifier) and the contract number are now displayed. The search supports both values alongside the contract name and supplier number. The contract reference remains the primary sorting key.

This adjustment makes it easier to identify the correct contract, especially for organisations that use both the contract reference and the internal contract number when processing purchase orders and invoices.

PO indexation processed only after approval

When indexing a purchase order, the updated value was applied directly to the order before approval by a responsible party. From now on, the indexed value is only processed on the purchase order and any linked invoices after the approval step in the workflow is completed. When the indexation is rejected, the request returns to the submitter for adjustment or withdrawal.

This adjustment ensures price changes via indexation are only visible after formal approval, improving control over order values and preventing unintended changes.

Exclusive dimension validation works correctly via OpenAPI connection

In the coding interface, general ledger account and fixed asset cannot be filled in simultaneously: selecting one field automatically collapses the other. Mandatory field validation did not account for this behaviour at customers with an OpenAPI connection (such as a generic ERP connection), causing collapsed fields to still be marked as required. Validation is now skipped for fields collapsed via the exclusive setting.

This adjustment allows invoices with a general ledger account or a fixed asset to be correctly processed via an OpenAPI connection without extra manual corrections.

cXML OCI output adjusted in accordance with cXML specification

The cXML output generated during an OCI PunchOut roundtrip has been adjusted to comply with the cXML 1.2 specification. Delivery addresses are now provided with an ISO country code and an address ID based on the delivery location code. A new field is available in the delivery location settings to link the ISO country code.

This adjustment prevents cXML messages from being rejected by supplier systems that apply strict validation on the format of incoming orders.

Creating items via API with update statement

The items API endpoint now supports creating a new item via an update request when the item does not yet exist. This is consistent with the behaviour of other API endpoints in the platform. When an item is created via an update request, this is recorded in the audit log.

This adjustment simplifies setting up item data flows without having to distinguish between creating and updating, easing integration configuration.

Advanced routes - weight of 0 no longer allowed

In the advanced routing settings, the weight of a route can no longer be set to 0. Negative values and decimals are also not allowed. The default weight is set to 1. Existing routes with a weight of 0 are updated to 1 via an automatic migration.

This adjustment prevents configuration errors where routes with a weight of 0 are never selected, disrupting routing.

Fixes