Basware Purchase-to-Pay 16.8 New Features


Contents

1 Introduction

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

2 AP Automation

2.1 Add row action added to row approval

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

The row approval function has been enhanced by guiding the user to add coding rows to invoices which come to approval without any coding rows. For such invoices, the Add coding action is available as the primary action in the task list and in the invoice details view.

2.2 Matched lines should not be validated

Module(s): Match Plans
Feature ID: ALUSTA-12570
Release: P2P 16.8
Feature Implementation: Feature is in use automatically

Validation of schedule-based and self-billing payment plans has been enhanced. Now the matched lines are not validated any more when a user performs an action. Previously the matched lines were validated.

2.3 Row approval recipient fetching using limits

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

Recipient fetching for the invoice row approval in the limit mode has been enhanced. Now the system fetches a task recipient only after a sum has been entered in the coding row. If the system finds many suitable task recipients, then it selects the one that has the lowest priority index in the Advanced User Rights table. Previously, the system did not select a recipient with the lowest priority index.

2.4 Row approve validity check

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

Row level task handling has been enhanced by checking that the tasks coming for approval are valid. It is now checked that the recipients for the row level tasks have not performed tasks earlier on the same invoice. If earlier tasks exist, a new recipient is found for the row.

It is also checked that all row level tasks related to the invoice have existing coding rows. The tasks which have no rows are removed.

2.5 Row review support in Edge

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

Users can now review invoices on coding row level in the Edge client. The Review action is available in the task list and in the invoice details view. Users can also manage the row review tasks by creating, editing, or deleting coding rows. The user’s own row review task will be canceled if the user deletes or forwards all their own coding rows.

2.6 View full document history in Edge

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

Invoice history is now available in Edge. Invoice history is accessed from the invoice details view. Invoice history opens in a new browser window. Users can view the history events and filter them based on user actions and system actions.

2.7 Link to Edge from Workplace

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

Personal mode users can now navigate from the Workplace client to the Edge client. A link to the Edge client can be found from top of the screen.

2.8 Matching an invoice with a service purchase order line

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

Now it is possible to match an invoice to a service purchase order. A service purchase order line is similar to the already supported framework purchase order line. Both of them are sum based and quantity is not effective during matching. The difference between these two is that the service purchase order line requires receiving the ordered services. The coding is copied over to the invoice from the coding details instead of having the coding definition from purchase order line. When the user views the service purchase order lines in the Manual Matching view, there is a slightly different three-layered navigation structure.

The purchase order is viewed in a similar way than before. The service receipt can be seen when the user drills down to the purchase order lines view. The original order line is replaced with one or many service receipts.

When the user drills down from the service receipt, the user is able to view the receipt-specific accounting details. Matching is possible also on details level.

Goods receipt search shows the service receipts. It is not possible to drill down to accounting details from this view.

2.9 Search purchase order data with many exact values

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

A user can now set many values in search criteria when searching purchase order data in the Manual Matching view. The user can also copy a list of values from another application, such as a spreadsheet. The pasted search criteria are shown as comma separated values in the search field.

This enhancement is available when searching purchase orders in the Manual Matching view.

Many values as search criteria are supported also when searching goods receipts.

3 Procurement

3.1 Shopping cart item validity check in Edge

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

Previously, Edge Shop did not validate the items in the shopping cart before creating a purchase requisition. Now, the items are validated and invalid items are not sent as a purchase requisition to workflow.

3.2 Search in budget view

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

In the budget view the user can search for certain budget by providing appropriate search criteria for the budgets.

The user is provided with a search field for searching a budget based on its name as well as with a selection of filtering criteria for finding a budget with specific characteristics.