Basware Purchase-to-Pay 23.4 New Features


Contents

1 Introduction

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

2 Procurement

2.1 DPS - Filters and export option added to supplier list

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

The buyers using Dynamic Purchasing System (DPS) can now export the list of suppliers from an agreement to a CSV file.

The suppliers can now be sorted by expiry date and registered date and they can be filtered with options Expiring soon and Excluded. The Expiring soon filter shows the suppliers who are about to expire within 30 days and it is only shown when the questionnaire supports expiry.

 

2.2 Quick Source for Buyers enhancements

Module(s): Marketplace
Feature ID: ALUSTA-104744
Release: P2P 23.4
Feature Implementation: Basware consultant work is needed

The following enhancements were done in Quick Source for buyers:

1) Contract reference field has been added if user creates a request by clicking Create Request on the Dashboard page.

2) When suppliers have quoted back, the buyer can now see the savings for quoted price and the maximum price if a maximum price is filled in. A new column, Price against target has been added to show the difference between the maximum price given by the buyer and the total price quoted by the supplier.

3) Two more columns Supplier Type and Supplier DUNS/ID have been added to show if the supplier has registered or not. The Supplier type shows “Registered” or “Unregistered” for the supplier and Supplier DUNS/ID gives the DUNS number or ID of the registered supplier. If a supplier has not registered, the value in the field is “unknown”.

4) The user can now add a customized description by using Markdown text.

2.3 Weighing levels of Preferred Items

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

The number of levels of preferred items has been added because in the procurement business the customers usually have one or two backup suppliers for the same items other than the Preferred Item.

With the implementation of weighing the preferred item, the option to prefer items will have three levels. The users who have access to Product Manager and created agreements will see the Preferred drop-down with four options:

Note: The Preferred option will be reflected on the following agreements: Organization, Agent, Framework and Punchout.

By default, “Not preferred” is selected.

The items in the agreements that have the preferred toggle option on are changed to a drop-down with the four options. 

On the Shopping site, when the buyer checks the Show Preferred Items filter, they will see all the most preferred items with three green colored thumb icons and a label “Most preferred” under the item/ external webshop name.

In the Super Content Loader and the content tag file the preferred column will have three options for high, medium, and low preferred items: “High” or “H” for highly preferred items, “Medium” or “M” for moderately preferred items, “Low” or “L” for slightly preferred items. Otherwise the field can be left blank.

Note:

For the existing agreements and items that have the preferred toggle option on, the selection will be set to “Most preferred” option.

If an agreement has a preference level set, and an item in the agreement has another level set, then the higher preference level will take effect in the Marketplace item searches.

 

2.4 Company-specific purchase requisition and purchase order entity configurations

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

Now it is possible to have different entity configuration on different administrative sites in an organization. This way for instance there can be company-specific entities within an organization.

2.5 Contact task recipient functionality in Purchase professional

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

Procurement professional users can now click Contact task recipients to send an email message to a recipient that has a pending task for the selected document.

2.6 Support for check box in coding row

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

A field that is configured as a checkbox in the Configuration tool will be shown as a checkbox in the coding row grid.

2.7 Select allowed suppliers in free-text form properties

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

Earlier, it has been possible to select one supplier to a free-text form and make the supplier selection not editable for the requester. Now an administrative user can select several suppliers that the requester can then select from on a particular free-text form. This can be used for example for allowing only the suppliers that should be used for a certain service or product. It can also be used for allowing only the suppliers that do not have catalogs or external webshops.

2.8 Passing PO custom fields from Purchase to Matching

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

Custom fields from the purchase order’s header and lines will now be passed to order matching. This enables more advanced order matching scenarios.

2.9 Address ID in predefined delivery and invoicing addresses

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

It is now possible to have an ID for delivery and invoicing addresses. Some customers prefer to use an agreed ID for the addresses, instead of a concrete postal address.

2.10 Improved name and value pair support in P2P Purchase

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

Many items have additional properties - such as “Color” being “Red” - in catalogs and in external webshops. It is now possible to configure which name and value pairs are read to the purchase requisition and eventually sent in the order document to the supplier.

3 AP Automation

3.1 New fields for invoice header data

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

Now P2P can store more invoice information than before. We have enabled 40 new fields to invoice header data, 30 new text fields, and 10 fields are reserved for numeric data. 

Contact Basware Support to activate the new invoice fields for your organization. 

3.2 Ensure that invoice is within blanket purchase order’s validity period

Module(s): Match Orders
Feature ID: ALUSTA-102674
Release: P2P 23.4
Feature Implementation: Basware consultant work is needed before customer can take into use

Previously, when matching an invoice with a purchase order, P2P compared the invoice voucher data with the blanket purchase order line’s validity period. Now it is possible to define the date field that is picked up from the invoice to be validated. The validation logic works like before, if the date selected from the invoice is outside the blanket purchase order’s validity period, the system raises an error. To enable this feature or change the current settings for your organization, contact Basware Support.