Extensive improvements within Procurement Value Management for roles, goals, workflows, and insight

Within Procurement Value Management, several improvements have been made that together provide more clarity, better insight into progress, and a more flexible workflow process.

User roles within Procurement Value Management have been renamed to clearly align with the module, including consistent naming in the role matrix and associated navigation.
This contributes to clearer authorisations and recognisability for users.

The display of goals has been expanded with additional insight into progress relative to the term.
The goal card now shows how the realised impact relates to the required progress to achieve the goal within the set period, including both approved and ongoing results.
Additionally, an extra chart has been added in the goal details that compares results per period against a linear target over the entire term. This makes it immediately clear whether the realisation is ahead or behind, without distinction between impact types but with a clear separation between ongoing and approved results.

Insight into activities within Procurement Value Management has been improved.
An activity section is now available in the overview with a continuous timeline of relevant actions, such as registered results, workflow approvals and rejections, completion of workflows, and achievement of target amounts. Activities include date, relative time indication, and direct navigation to the associated context, supporting infinite scrolling.

The authorisation model has been refined for users with read-only roles.
These users now have full insight into all active and archived events and can perform workflow actions when they are part of a workflow, while editing event data, results, documents, and notes is excluded. The results report contains data from all events and the overview has been adjusted so that it always navigates to all events.

In the settings of Procurement Value Management, the team structure is now also visually displayed. Below the existing table, a graphical representation is shown in which the hierarchy of teams and individual users is visible, allowing faster checking and understanding of the configuration.

Workflows have been functionally extended with the possibility to request advice in an active workflow step.
From a workflow step, an advice request can be initiated involving one or more users. During an active advice request, approval and rejection actions are temporarily disabled and communication is recorded, including notifications and registration in the edit log. After response or cancellation, the workflow step resumes.

Additionally, the setting for read-only workflow steps is now active.
When this option is enabled, all edits, additions, and deletions within the event are blocked and only workflow actions remain available, both in the interface and via backend validation.

These adjustments together enhance the user experience of Procurement Value Management by providing better progress insights, clearer roles, richer workflow functionality, and more transparency in activities and teams.

ℹ️

Extensive improvements within Budget Management for settings, insight, and navigation

Within Budget Management, several improvements have been made that provide more flexibility in configuration, better insight into budget data, and easier navigation to underlying processes.

A new settings menu has been added in which financial dimensions can be centrally managed.
In this menu, it is possible to activate or deactivate financial dimensions, adjust names, and determine the order of dimensions by drag and drop. These settings are immediately applied to the input form, the edit form, and the overviews within Budget Management. Contracts and suppliers can now also be used as financial dimensions. By default, all dimensions are active upon rollout.

The configuration of budget details has been expanded with two new fields: budget type and budget category.
These options can be managed via separate tabs in the settings and make it possible to better classify budgets and prepare for future new authorisation extensions.
The fields only appear when values have been configured and can optionally be made mandatory when creating or editing a budget. Values cannot be removed as long as they are still used by active budgets. Both fields are available in budget imports, in the budget overview, and are provided with searchable dropdowns and filters.

Insight into budget details has been improved by enabling navigation to underlying documents. From the detail tables for settled invoices, invoices in circulation, hard commitments, and soft commitments, it is now possible to navigate directly to the associated purchase request, purchase order, or invoice in Procurement or AP Automation. The navigation opens in a new tab and shows a clear action button per line. When the required URL configuration is missing, this is made visible with an explanation.

The budget overview has been expanded with a large number of additional columns to provide more complete insight and better reporting capabilities.
New columns show, among other things, budget owners, currency, VAT inclusion, allowed overspending, available budget space, and amounts for invoices, commitments, and corrections. Additionally, several financial dimensions have been added as columns, such as companies, suppliers, contracts, cost centres, projects, and free dimensions. Columns are configurable per user, including visibility and order, and these settings are saved per user.
Filters are tailored to the type of data and Excel export is enabled, with exported values remaining suitable for reuse in imports.
The overview for archived budgets supports the same functionality.

These adjustments make Budget Management more flexible in configuration, richer in insight, and more efficient in daily use, both for management and for analysis and further processing.

ℹ️

Status bar added to all renewed tables and enabled by default for new tables

A status bar has now been added to all renewed tables without pagination. The status bar shows by default the total and filtered number of rows, the number of selected rows, and aggregations on columns. This functionality is immediately available in all existing overviews that use the renewed tables and will be applied by default to new tables added to the application.

This adjustment provides more insight into selected and filtered data and supports more efficient working with large datasets.

Query is only executed after explicit action

When opening a query, the query is no longer executed automatically. The query now only starts when the Execute button is used. During execution, the overlay with the cancel option remains available.

This adjustment prevents unintended heavy or incorrect queries when opening details and improves the availability and stability of the query functionality.

Origin and creation date recorded for vendors and contracts

For both vendors and contracts, it is now structurally recorded when a record was created and through which source. This applies to creation via the user interface, imports, API connections, and other automatic processes.

• When a record is created by a user, the respective user is recorded.
• When created via non-interactive processes, the source is displayed, such as API or import.

This information is permanently stored on the vendor and contract record itself and is visible above the change history, without extra mentions in the edit log. Additionally, the origin information has been added to the query overviews for vendors and contracts.

This adjustment improves the traceability of master data and supports analysis, management, and support in tracing changes and origins.

Vertical navigation structure added to Analytics* and other V2 components*

Within Analytics* and other V2 components*, a vertical navigation structure has been implemented replacing the previous horizontal navigation. The sidebar supports multiple menu levels, is collapsible, and retains visible icons when collapsed. On hover, underlying levels become visible and directly clickable. The navigation status is saved so that the set width and open or closed sections remain after refreshing. Role controls determine which menu items are visible per user and direct links continue to function correctly with associated highlighting in the menu.
The new navigation has been applied within Analytics*, Procurement Value Management* and the renewed homepage*, with the secondary navigation bar removed.

This adjustment provides clearer navigation, better scalability of menus, and a consistent user experience within all V2 components.

Fixes

Column 'Silent renewal' adjusted with Yes/No and filter

In the contract overview, the column Silent renewal now shows the values Yes and No instead of true and false, in line with the display in the contract details.
Additionally, a filter has been added that allows easy filtering of contracts with or without silent renewal.

This adjustment improves consistency and makes the overview more usable when selecting and analysing contracts.

Renewed PDF file viewer added to terms analysis

Within the functionality for terms analysis, a renewed PDF file viewer has been added so that the analysed document can be consulted directly from the results overview.
The uploaded document is stored and linked to the analysis, after which it can be opened via a collapsible viewer under the result indicators. This makes it easy to check where specific results in the original document come from without leaving the page.
The viewer supports PDF files and is set up for reuse for future expansions in other locations or other file types.

This adjustment increases transparency and makes validating analysis outcomes within Contract Management clearer and more efficient.

Companies included in the authorisation layer of Contract Management

In Contract Management , linked companies are now included in the authorisation layer of contracts. The visibility of contracts is now also determined based on the relationship between companies linked to a contract and companies linked to a user, in addition to existing authorisation criteria such as categories, templates, and labels.

• If a contract has no linked companies, this criterion is not applied.
• If companies are linked, at least one company must match the user's companies to make the contract visible. 

This check has been implemented in all relevant parts, including the contract overview, direct contract links, document overviews, contract planning, and contract tables within vendor management.

This adjustment improves authorisation, refines contract viewing, and aligns with the existing ISPnext logic.

Contract data import renewed to 'Data import 2' for insert and update*

The import processes for inserting and updating* contracts have been renewed and transferred to the
'Data import 2' import mechanism.
This makes the imports better aligned with the current contract functionality and provides additional contract fields that could not be imported before. Both the insert and update* imports now support additional data, including multiple values for the country of applicable law and cost centres, supplier termination periods, contract status, termination, number of extensions, retention periods, second contracting party, and linked cost centres.
Multiple values are correctly processed when provided separated.

This adjustment ensures more complete and future-proof contract imports and reduces the need for manual additions after import.

AX2012 dimension import made more robust

The import of dimensions from AX2012 has been made more robust to better handle incomplete or deviating data. In situations where expected segment fields are missing, this is now handled defensively so that the import no longer fails with a KeyError. This keeps processing stable and supports edge cases correctly.

This adjustment improves the reliability of the AX2012 dimension import and prevents disruptions for customers working with varying source data.

Default values for custom fields reapplied when changing supplier

When changing the supplier on an invoice, custom fields are now again correctly filled with the default values from the supplier settings. In the previous version of Custom fields 2.0, these values were not consistently taken over, which could lead to missing data on the invoice header.
The expected behaviour, as known from Custom fields 1.0, is thus restored.

This adjustment ensures consistent adoption of supplier-specific custom fields and prevents missing data when working with invoices within AP Automation.

Base country set from company configuration before VAT determination

When determining VAT on invoices, the base country is now first set based on the company configuration before the VAT logic is applied. This allows the correct VAT code to be selected correctly, even for invoices processed via nextAI. This prevents incorrect VAT determination when the base country was not yet available at the time of calculation.

This adjustment improves the accuracy of VAT calculations and restores the expected behaviour during automatic invoice processing with nextAI.

Support added for Polish XML invoice format KSeF FA(3)

Support has been added for the Polish XML invoice format KSeF FA(3). This allows FA(3)-compliant XML invoices to be correctly processed within the platform. This expansion makes it possible to comply with Polish e-invoicing requirements and supports customers who are obliged to submit invoices via KSeF.

This adjustment ensures that XML invoices according to the Polish standard can be reliably read and processed within AP Automation.

Search and filter options added for custom fields in PO and Non-PO lines

Within the renewed tables, search and filter options have been added for custom fields, making data easier to find and analyse. It is now possible to filter directly on custom field values, supporting the daily processing of invoices. This functionality improves usability and speeds up finding relevant lines when working with custom fields within AP Automation.

This adjustment makes working with invoices clearer and supports faster data findability during analysis and control.

Fixes

Permissions within Procurement have been refined to precisely determine per user or role which types of purchase requests may be created. The previous generic permission has been split into three separate permissions:

• procure:can_use_freerequest - allow free purchase requests
• procure:can_use_products - allow catalogue requests
• procure:can_use_webshop - allow webshop requests

Based on these permissions, only the corresponding request options are visible and available in Procurement. This allows targeted steering of free requests and better alignment of the request process with role, experience, and policy.

This adjustment gives Procurement teams more control over request types and supports a more consistent and manageable purchasing process.