Basware Purchase-to-Pay 16.10 New Features


Contents

1 Introduction

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

2 Procurement

2.1 Approval password is required (if enabled) on header level when approving purchase requisition in Edge

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

The Edge client now supports the use of approval password when approving purchase requisitions on header level.

If approval passwords are in use, the users must enter the approval password when attempting to approve a purchase requisition. Users can also forward any task to a different user or return the task back to the purchase requisition owner.

The same approval password is used also in the Workplace client. The password reset and expiration procedures are the same as in the Workplace client.

2.2 Dimension total check in approval with possibility to share cost

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

Now it is possible to define on dimension-based row approval step if dimension total cost can be shared with persons having limit to that same dimension. This way for instance two managers having limit to the same cost center can approve up to their limit sum (share) on the PR instead of being able to approve only PRs whose dimension full cost is up to their limit.

2.3 View coding on PR line details in Edge

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

The purchase approver can now view the purchase requisition’s coding details on line level in Edge. Also costs that are split are shown in the coding details. Dimensions shown on the coding panel are not configurable in this release.

2.4 Order data export

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

The Purchase process now supports the communication of the PO data to an external party by creating a PO XML document at the moment the order is created or modified in some way.

The PO XML document contains all relevant PO data available, including the PO header level data, the PO line data, as well as the coding rows and the related GR, if any.

3 AP Automation

3.1 Batch forward support for multiple recipients

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

Task management has been enhanced so that it is now possible to update tasks in batch mode. Using the Update task recipients action, a Professional Mode user can move several pending tasks from one recipient to another. This action can also be used when the task recipient is missing or there are several task recipients for a single invoice. The action is available on the Workflow list page.

3.2 Coding import/export improvements

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

Importing of coding rows has been improved in Basware P2P. Earlier it was possible to import an Excel file only although coding could be exported as an XML file. Now both Excel and XML files can be imported. 

3.3 Duplicate invoice check based on only supplier number and invoice number

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

A new parameter has been introduced in the Basware P2P Configuration Tool to enhance duplicate invoice checking. A duplicate invoice can now be recognized based on the supplier and invoice number only.

3.4 Search P2P invoice documents in Edge

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

Invoice search function has been enabled in the Edge client. Users can now search for their tasks and invoices created by them based on supplier, invoice number, gross total, and creation date. If the user has the View your organization’s invoices user right, the user can search also all other invoices in the organizations the user has rights for.

3.5 Show sum that is matched with the open invoice on PO item

Module(s): Match Orders
Feature ID: ALUSTA-13704
Release: P2P 16.10
Feature Implementation: Feature is in use automatically

Now it is possible to see the matched quantity and sum of the current invoice on each purchase order line. This makes it easy to evaluate if the invoiced total is correct when compared to the matched purchase order lines. If there are no invoice lines, the user is able to view the invoice image and ensure that the values in the invoice image are equal with the matched values.

The matched quantity and matched sum present values covering the invoice as one unit. There is no possibility to drill down to invoice line level if it happens that there are two invoice lines that are associated with the same purchase order line.

3.6 Advanced search for purchase order data in Manual Matching with a range of key values

Module(s): Match Orders
Feature ID: ALUSTA-12703
Release: P2P 16.10
Feature Implementation: Feature is in use automatically

Now it is possible to search purchase orders and goods receipts using a list of key values. User is able to define an accurate list of values in search criteria as well as setting a start and an end value for a range. A list of values can be copied over for example from a spreadsheet.

3.7 Search goods receipts with purchase order number in Manual Matching view

Module(s): Match Orders
Feature ID: ALUSTA-12704
Release: P2P 16.10
Feature Implementation: Feature is in use automatically

Now it is possible to search goods receipts with a purchase order number range in the Advanced Search of the Goods Receipts dialog. User is able to set a start and an end value for a range or define many accurate purchase order numbers to retrieve goods receipts for specific purchase orders. Similar search options were applied also for the Delivery note number field.