Basware Purchase-to-Pay 24.1 New Features


Contents

1 Introduction

This document contains descriptions of new features in Basware Purchase-to-Pay 24.1 and its maintenance releases.

2 Procurement

2.1 Assign multiple contract references to punchout or framework agreements

Module(s): Marketplace
Feature ID: ALUSTA-109919
Release: P2P 24.1
Feature Implementation: Feature is in use automatically

The Product Manager user has the ability to add multiple contract references to all types of agreements. The agreement can then be linked to a contract in their system when the basket is returned. This functionality for agreements can be linked to multiple suppliers or to a supplier who may have more than one contract.

The contract reference has been removed from the Attribute section and a new section Contract References has been created on the agreement page. The existing contract is shown in the Default field which can be changed if needed. 

When the user clicks , the Contract References page opens where the user can add other contract references . Click to add a new line for contract reference. Supplier code and Contract reference are mandatory fields for the line added. The value added for each supplier code must be unique. The user has the option to upload and download the contract references. 

The item details will show the default contract reference, but once the item is added to the basket, the contract reference added will be shown. 

     

The default contract reference will be overridden by the contract reference set with the supplier code. If no contract reference is given, the default contract reference will be shown.

2.2 Reason for rejection for supplier’s price list

Module(s): Marketplace
Feature ID: ALUSTA-109943
Release: P2P 24.1
Feature Implementation: Feature is in use automatically

While rejecting the supplier’s price list, the approver can now add the reason for rejection for the price list. The rejection message is shown in the history section which can be viewed by other users who have access to Product Manager agreements. The rejection message is not mandatory and can be left blank.

The reason for rejection is also shown in the history section on the agreements of the supplier. 

2.3 Default expressions on purchase requisition and when adding lines to purchase order

Module(s): Purchase
Feature ID: ALUSTA-104680
Release: P2P 24.1
Feature Implementation: Basware consultant work is needed

P2P Purchase now has the support for a default expression in many fields in header data, lines, and coding. With the default expression, you can set an initial value to fields like Account code when the requisition is created or a line is added to the requisition or order. 

2.4 Exclude attachments when copying purchase requisition or order as draft requisition

Module(s): Purchase
Feature ID: ALUSTA-107639
Release: P2P 24.1
Feature Implementation: Feature is in use automatically

When copying a purchase requisition or order as a draft, users now have the flexibility to choose whether the attachments are replicated to the new draft requisition.

2.5 Professional tasks list for purchase personal users

Module(s): Purchase
Feature ID: ALUSTA-109855
Release: P2P 24.1
Feature Implementation: Feature is in use automatically

The user experience for purchase personal users who handle tasks on a daily basis has been enhanced in this release. The users now have a desktop-optimized view of the task list where they will see more information about their tasks in the list view. To enable the view, select Professional view from User settings > Views in desktop mode.

When the setting is enabled, the enhanced task list view for purchase requisitions, purchase orders, and goods receipts will be displayed.  

Users with appropriate user rights can configure the columns of the task list in Configuration Tool. 

The new grid has the following capabilities:

3 Networked AP

3.1 Query invoice status through Invoice status API

Module(s): Integrations
Feature ID: ALUSTA-109398
Release: P2P 24.1
Feature Implementation: Basware consultant work is needed

High-level invoice status can now be queried through Basware API. The API receives search criteria such as company code, invoice number, invoice date, and gross sum. and returns the status, that is, “In Approval Process”, “Ready For Payment”, “Paid”, or “Rejected”.

A typical use case is providing self-service access to suppliers by integrating the API to an existing dedicated supplier portal. Typically this will reduce queries that the AP team has to handle manually.

To enable this feature for your organization, please contact your Basware consultant or Basware Support.

3.2 Improved visibility to invoices in automatic transfer

Module(s): Invoice Automation
Feature ID: ALUSTA-81155
Release: P2P 24.1
Feature Implementation: Feature is in use automatically

Visibility into invoices in the Transfer in progress status has been improved by including the invoices that are in automatic transfer.

The invoices with the In automatic transfer and Waiting for ERP statuses are now included in the searches done with the main status Transfer and the sub-status Transfer in progressPreviously, only manually transferred invoices were included in the status charts, and the invoices in automatic transfer could only be searched with Advanced search

This change helps users to easily discover and access all the invoices that have the Transfer in progress or Waiting for ERP status, as their combined count is now visible in the status chart

3.3 Spend plan creator’s capability to approve own spend plans

Module(s): Spend Plans
Feature ID: ALUSTA-79212
Release: P2P 24.1
Feature Implementation: Basware consultant work is needed

Spend plans have been enhanced by making it possible for spend plan creators to approve the plans they have created. This can be useful, for example, in cases when invoice approvers request for new spend plans which they would need to approve. Earlier, it was not allowed for spend plan creators to approve the plans they created.

There is a new parameter “Allow users to approve the spend plan they created or requested” in Spend plan configuration. The parameter can be used for controlling whether the spend plan creators can approve the plans they have created.

By default, this enhancement is not enabled. In this case, the spend plan creator cannot approve the plans they have created and the spend plan creator is not available in the user selection lists for approval tasks.

When this enhancement is enabled, the spend plan creator becomes available in the user selection lists for approval tasks, and the spend plan creator can approve the spend plans they have created. To enable this enhancement for your organization, please contact your Basware consultant or Basware Support