Basware Purchase-to-Pay 19.9 New Features


Contents

1 Introduction

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

2 Procurement

2.1 Add refund lines to purchase documents

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

Now it is possible to add refund lines to purchase requisitions or purchase orders. When a line is added to a requisition or order, the user can check the option Refund line. Then, the user can enter all the information for the refund and enter a negative price for the line. The total sum of the purchase requisition or purchase order must still be positive. Refund lines are automatically received, but can be reversed and received manually if needed. 

This new feature is only available in the Edge user interface.

2.2 Assign reopened goods receipt task to backup user

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

If a receiving task is regenerated and the original receiver has a backup person set, the task is now assigned to the backup person instead of the original receiver. Receiving tasks are regenerated when a closed purchase order is reopened or receiving is reversed on a line.

2.3 Define mapping for external webshops’ OCI inbound fields in Edge

Module(s): Purchase
Feature ID: ALUSTA-53291
Release: P2P 19.9
Feature Implementation: Customer can take into use

Previously, OCI inbound field mappings for external webshops could not be edited. Now, users with the “Manage external webshops” user right can define inbound mappings for external webshops in the Edge interface. The user can only edit the OCI inbound mapping for a webshop when that webshop is not in use by requestors, such as if a requestor has an item from the external webshop in their requisition drafts.  

Users can also add custom inbound fields to the mapping by entering the name of the custom field and clicking Add custom OCI field.

 

2.4 Execute header level expressions after changes in line details

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

Now, when a user changes purchase requisition or purchase order line details, any expressions in the document’s header fields are executed again. Sometimes header-level fields depend directly on the values of line-level fields, such as the net total, which need to be updated after the line-level values are changed.

This enhancement is only available in the Edge user interface.

2.5 Period or comma decimal separator allowed on all browsers for Edge personal screens

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

Basware P2P Purchase now supports commas as a decimal mark in numeric fields across all common web browsers. Whether a user must use a comma or a period as a decimal mark is determined by the user’s region, as set on the User settings page.

For example, if a user’s region is set to “en-US English”, the user can enter a value such as 123.50. If a user’s region is set to “fi-FI Finnish”, the user can enter the value as 123,50. 

2.6 Receive goods by sum or percentage

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

Earlier, users could only receive items by quantity. Now users can choose to receive items instead by gross sum, net sum, or percentage. Users choose the receiving method when receiving each line for the first time. After the first goods receipt, the user cannot change the receiving method. By default, receiving is done by quantity. This feature is available to all customers without any configuration changes.

This new feature is only available in the Edge user interface.

2.7 Renamed user right “Review validity of purchase requisitions” to “Validate and finalize purchase requisitions”

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

User right “Review validity of purchase requisitions” has been renamed to “Validate and finalize purchase requisitions.” The new name more clearly identifies the user right as needed to perform Review and Finalize tasks in Basware P2P. 

2.8 Select goods receivers by groups

Module(s): Purchase
Feature ID: ALUSTA-54892
Release: P2P 19.9
Feature Implementation: Customer can take into use

It is now possible to set groups of users as goods receivers for purchase orders. First, an administrator must enable the option Use as recipient user group for the user group in P2P Admin. Then, a user can select the group when changing goods receivers while editing the purchase requisition or purchase order. After selecting a group, the user can expand the group to see the individual users in it, then remove or add receivers as needed. The total number of individual receivers may not exceed 20.

Individual and group receivers can be changed, added, or removed by both personal and professional users. Previously, professional users could not remove goods receivers. 

2.9 View change details in purchase requisition and purchase order history

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

Users can now view the details of edits that have been made to purchase requisition and purchase order documents. To do so, users navigate to the History page of the document and click View Changes beside each edit listed in the table.

This enhancement is only available in the Edge user interface.

2.10 Purchase document numbering data management in Edge

Module(s): Purchase
Feature ID: ALUSTA-47817
Release: P2P 19.9
Feature Implementation: N/A

Users with the user right “Manage purchase documents” can now define custom document numbering formats in the Edge interface, in the Data Management area. Previously this configuration was only possible from Workplace. Users can choose what information is included in document formats for each organization and copy formats from one organization to others. If no document numbering is defined for an organization, the user can also create new document numbering rules.

3 AP Automation

3.1 Configure NUM fields as check boxes in Edge personal interface

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

Earlier in the Edge personal interface, NUM fields in the invoice header could only be configured as text fields. Now it is possible to also configure NUM fields as checkboxes. Entity rules are supported for these fields. 

3.2 Numeric input in Edge personal mode

Module(s): Invoice Automation
Feature ID: ALUSTA-52992
Release: P2P 19.9
Feature Implementation: N/A

Basware P2P Invoice now supports commas as a decimal mark in numeric fields across all common web browsers. Whether a user must use a comma or a period as a decimal mark is determined by the user’s region, as set on the User settings page.

For example, if a user’s region is set to “en-US English”, the user can enter a value such as 123.50. If a user’s region is set to “fi-FI Finnish”, the user can enter the value as 123,50. 

3.3 P2P language support - Russian

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

Russian language is now supported in Basware Purchase-to-Pay. A user can select Russian as the UI language from User settings when the Russian language has been installed to the customer environment. 

3.4 Change current task recipient for an invoice coding line

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

Earlier it was not possible to select the recipient of line-level review or approval tasks in Edge. Now, business users can forward line-level review and approval tasks to other users. When user modifies a coding line, they can also change the current recipient. The dropdown lists all users who have permission to complete the task.  

This feature needs to be taken in use separately.

3.5 Set user as row approver despite the priority for a coding row created or modified by the user

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

Now users do not need to pick their own name for the current task recipient field when they create or modify coding lines during an invoice row approval task. When coding dimensions change, the logged-in user is selected by default over the priority order whenever the user has permission to complete the invoice row approval action. 

 

3.6 Show more tasks on the task list by default

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

Now the task list can show up to 50 tasks on the page. If the user has more than 50 tasks, they can click Show more to see the additional tasks. 

3.7 Automatic matching can use order number or delivery note number from invoice line details

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

Earlier the automatic matching logic required reference details to be placed in the invoice header data. Now automatic matching can read the purchase order order number and delivery note number from the invoice line details. In the line details, only one reference number can be given within a field.