Contents

Source to Contract (S2C)

General

Spend

Vendors

Contracts

Sourcing

DORA

Procure to Pay (P2P)

AP Automation

Procurement

Source to Contract (S2C)

General

• Various text corrections have been implemented.
• Various translation corrections have been implemented.
• Various layout corrections have been implemented.
• Various performance improvements have been implemented.

New

Validation on duplicate bank accounts in the Vendors API

The Vendors API now performs clear validation when a bank account already exists. Instead of a general 400 error message, a descriptive message is now returned indicating that the bank account is already present. Additionally, other error messages within this functionality have also been revised to accurately reflect the underlying cause.

Fixes

Spend

New

Improved editing of the Spend Total table

The Spend Total table in information requests, contracts and the Supplier Portal has been renewed for more clarity and ease of use. Editing in the cell has been replaced by a clear Edit button that opens a form with twelve month fields that can be set. Adjustments are saved and displayed immediately. The visibility of these settings is dependent on user roles and admin settings.

Additionally, to provide more information about contracts, two new columns have been added: Contract Reference and Contract Manager. Column preferences are saved per user.

Fixes

Vendors

New

Complete Supplier Data Portal data in vendor detail page

The Edit Log tab on the vendor detail page has been renewed to show clear and complete information about requests from the Supplier Data Portal. Each row in the table can now be clicked to directly open the corresponding Supplier Data Portal process.

The table includes the following improvements:

• A new column with the last workflow user.

• The column New or Update now clearly shows “New” or “Update”.

• The column Accept has been renamed to Accepted? and displays “Yes” or “No”.

Extended import fields for vendors

Additional fields have been added to the vendor import processes to build a more complete and accurate vendor file. The following fields have been added at the following locations:

Import data → Vendors → Update vendors

• Euid

• HelliosID

• Establishment number

Import data 2 → [Vendors] Import new vendors

• Euid

• HelliosID

• Establishment number

These fields can now also be used when importing or updating vendor data.

Improved overviews for information requests

The overviews Workflow and Archive for information requests have been rebuilt to improve speed and reliability, especially with large numbers of requests or complex searches.
Each tab now features a search bar, an Excel export option, and a button for column selection. Existing column selections per status and all current column filters remain preserved. 

Fixes

Contracts

Fixes

Sourcing

Fixes

DORA

New

Include archived contracts in ROI report

The ROI report can now also include archived contracts, allowing historical contract data to be displayed more comprehensively. A new field “Include archived contracts after” has been added in the Admin report settings. This mandatory date field (default: 31-03-2025) determines which archived contracts are included: all contracts with an archiving date after this date are included in the report.

Additional validations ensure that field 02.02.0090 cannot be empty for archived contracts. Also, linked vendor data of archived contracts is included. All changes are visible in both the report view and the exported reports, for consistent and reliable reporting.

LEI code check via GLEIF API

A new connection is available with the GLEIF (Global Legal Entity Identifier Foundation) API to simplify retrieving and verifying LEI codes for vendors. This functionality increases data accuracy and reduces manual verification effort within Vendor Management.

The new capabilities include:

• A Get LEI Code button for vendors without an LEI that suggests possible matches based on vendor name and country, and a selected match automatically fills the LEI field.

• The Get LEI Code button is also visible when an LEI is already entered, although suggestions are solely based on vendor name and country.

• A Validate LEI Code button appears when an LEI is entered that can be validated via GLEIF. The returned company data such as name and country are displayed in a form.

• The GLEIF connection is activated via a simple checkbox and requires no login credentials.

DORA improvements

Several improvements have been made to make contract and vendor data within the DORA framework more easily accessible, manageable and reportable. These expansions provide more insight, less manual work and more efficient data entry for organisations within the financial sector.

Key improvements:

Visibility of Contract Owner/Manager

New columns for Contract Owner and Contract Manager are available in the Register of Information on multiple tabs (02.01, 02.02, 02.03, 03.01, 03.02, 03.03, 04.01, 05.02, 07.01).
Columns are selectable per tab and included in tab-specific exports (not in global exports).

Automatic Rank 1 entry in ROI

Rank 1 data from DORA contracts is automatically filled in ROI tab 05.02 when opening the report. Each row shows a combination of vendor and chosen IT service type. Only rank 2 and further ranks need to be filled in manually. Manually created rank 1 entries are removed to maintain consistency, with clarifying text about this automatic function.

Import for Vendor Relations

A new import process: [Vendors] Import Vendor Relations, allows bulk filling of data on the Relations tab in vendor details. The template supports:

• Vendor reference

• Relation type (three options)

• Ultimate parent flag (True/False)

• Existing vendor reference

• Vendor name

• Code type (four options)

• Identification code

• Country of origin (ISO selection)

• Remarks

Procure to Pay (P2P)

AP Automation

New

Extended supplier search function on invoices with VAT number

The supplier search function on the invoice header now also supports searching by VAT number. This extension is in addition to the existing search fields, including supplier ID, supplier name and bank account.
This makes it easier to find the correct supplier when only limited information is available.

Ongoing cost overviews extended with free fields

The Ongoing cost overviews now also show free fields for the invoice header, coding lines and PO lines. When free fields are active and used at any of these levels, they are automatically added to the overview.

The fields appear at the end of the header or line information in the same order as recorded in the configuration. This ensures more complete overviews without data needing to be manually supplemented outside ISPnext.

Company search function available for users with the correct permission

The company search function is now available for users with the permission 'company_configurations:can_edit_companyconfigurations'.
With this update, application administrators with this permission can manage Company Lookup settings themselves.

The permission works both in general and company-specific configurations. When the permission is set company-specific, the overview only shows the Company Lookups for the authorised companies, and the company selection list when creating or editing a Company Lookup is limited to the same companies.

Fixes

Procurement

New

Processing of purchase orders imported via OpenAPI

Purchase orders imported via the OpenAPI can now be automatically processed by the workflow. Previously, imported purchase orders were created but not picked up by the workflow. 

Language field for supplier and improved language determination for PDF documents

A new Language field has been added to the supplier settings. This allows the supplier's preferred language to be set based on the supported languages. This set language now takes precedence for the language used in generated PDF orders.

When the language field is not filled in, the system uses an order based on supplier location fields. The updated language determination works as follows:

1. Language from Supplier Settings

2. Delivering country

3. Country

4. English (default when all fields are empty)

With this change, PDF orders are generated in the correct language, even when the bank account country differs from the actual delivery country. The Language field is available on the General tab in Supplier Settings and is included in the Vendor Settings API.

Extended Fields for OCI Mapping in Orders

OCI field mapping now includes additional fields such as contract references, manufacturer details, attachments, quotation info, and custom fields.

Fixes