Basware Purchase-to-Pay 16.7 New Features


Contents

1 Introduction

This document contains descriptions of new features in Basware Purchase-to-Pay 16.7.

2 AP Automation

2.1 Approve and Forward action is now supported in Edge

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

Edge Invoice now supports the Approve and Forward action, where the user can both approve the invoice and forward it to another user at the same time. This feature is only in use if it is allowed in the configuration.

When the next approver is resolved automatically and adding a comment for the approval is not mandatory, the user is only asked for a recipient to forward the task to and an optional comment for forwarding. If the next approver is not found automatically and/or the comment for approval is mandatory, the user can define those as well.

2.2 Force recovery support for invoices jammed in transfer/anyerp

Module(s): Invoice Automation
Feature ID: ALUSTA-7389
Release: P2P 16.7
Feature Implementation: Basware consultant work is needed

Earlier there were rare cases which caused some invoices to get stuck in the SaaS environment. Then, normal recovery tasks could not recover the invoices. Now, recovery tasks in P2P Admin have been enhanced by adding a way to force the recovery of an invoice. With the new parameters ForceInvoiceId and RecoveryMode, a consultant can force an invoice to be either canceled or completed. The new parameters are added to Transfer, Prebook, and anyERP recovery tasks.

2.3 Recently used values are available in recipient picker for invoices in Edge

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

Recently used values are now available also for the recipient selection list. Recently used values are filtered according to organizations and performed actions. Last five values are stored. The values that are stored are device-specific.

2.4 Return invoice to workflow from Transfer

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

A new Return to workflow action has been added for invoices in the Transfer view. Users can return an invoice to an earlier manual task from Transfer. It is also possible to choose a new recipient for the selected task.

2.5 User can change recipients within the dimension set for invoice row approval in Edge

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

Users can now change the recipient for row approval in the previous activity by selecting the Change next recipient action on the row.

Users can now also forward the coding row in the dimension set to the other approver set for the same dimension set.

3 Procurement

3.1 Enhancements for system responses to user actions in Edge Shop

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

Edge Shop now displays action responses for various user actions.

3.2 Free-text keywords field length increased to 2 000 characters

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

Previously in free-text form configuration, only 246 characters could be given as keywords for any given form. Now the limit is increased to 2 000 characters (max. of Oracle nvarchar2 in unicode).

3.3 View my purchase requisition line on the line details view when approving a purchase in Edge

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

The user can now view purchase requisition details on line level in Edge.

3.4 Budget excess as a warning or an error

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

The P2P budgets now have an additional attribute which determines how the excess of a budget is handled in the Purchase process. This attribute is set per budget, and by default makes the exceeding of a budget to result in an error. By setting the Enforcing attribute, the system will issue only a warning instead of an error when a budget is exceeded, thus allowing the purchase process to continue also in the case of an exceeded budget.