Basware Purchase-to-Pay 17.3 New Features


Contents

1 Introduction

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

2 Procurement

2.1 “Purchase Classification” as a new header level dedicated field in purchase requisition and purchase order

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

The user can now enter purchase requisition and purchase order classification information that can be used to categorize and allocate items.

2.2 Allow second PR approval in backup role

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

Now it is possible to set the system to allow a user to perform a normal approval once and a backup approval once for the same line if the user has sufficient rights. This way the system does not prevent the user to approve the line if the user has approved the line as a backup person in the previous process phase. 

2.3 Buyer product code transferred to PR/PO line in Workplace Shop

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

Now users can view buyer product code on purchase requisition and order line in the Workplace client if it has been configured as visible in Configuration tool’s Entities and it has been received from BCatMan. For free-text items and items from external webshops, users may type buyer product code on the purchase requisition - if applicable.

2.4 Creating new purchase requisition based on old purchase requisition

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

Now it is possible to copy any of your own requisitions, requisitions that you have a task on, or requisitions that you have view all rights as a draft to yourself. In the copy functionality, the system copies the requisition as a draft to the same organization than what the original was created in. The copier must have the right to create requisition to that organization. The system copies the data to the draft as it is. There are no default values or list validating. The copier becomes the owner of the draft requisition.

2.5 Custom PO PDF template to support additional dedicated and custom fields

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

Now Basware consultants may configure all dedicated and custom fields which are available on the purchase order entity to be on the customer’s custom PO PDF. Buyer product code is also available as Buyer’s Item Identification in the XML 2.0 Orders.

2.6 Dimension-based self-approve in purchase requisition draft view

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

Now it is possible to set self-approval to be based on self-approve dimension user rights and self-approve dimension limits alternatively to requisition total on self-approve organization limits. To self-approve a requisition draft, the user needs dimension user rights and dimension limit to all the lines. When the user does not have right or limit to some lines (for example 3, 4, 5) or some splits (for example 2.1), the system indicates them to the user in the validation summary. Then the user can either edit the requisition or send it to normal workflow.

2.7 Goods receipt document supports new line-level dedicated fields

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

Now a user who marks ordered products as received in Basware P2P may enter the delivery note number and product serial numbers when receiving goods in P2P. This information is saved on the goods receipt document. Goods receipt (GR) export as well as order data export transmits the delivery note number, product serial number, and buyer product code to external systems. Delivery note number and product serial numbers are also provided to Matching.

2.8 Purchase requisition history page in Edge

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

Purchase requisition history is now available in Edge. Purchase requisition history is accessed from the purchase requisition header details view. Purchase requisition history opens in a new browser window. Approver can view the history events and filter the events based on user actions and system actions.

2.9 Recalling and reusing a purchase requisition

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

The requester can now recall the purchase requisition sent to process if the purchase requisition has not been approved yet. This prevents the requisition to get stuck in the process when the approver is for example on vacation.

2.10 Work order fields in free-text forms in Workplace and Edge

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

The dedicated invoicing field Work order is now available in free-text forms both in Workplace and in Edge. With this feature, the requester does not have to go to the purchase requisition draft to fill in the necessary information but the they can select the value in the free-text form.

2.11 “Receive automatically on desired delivery date” as a scheduled task

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

It is now possible to set the goods to be received automatically. When the functionality is turned on, the purchase line is received by the system on the desired delivery date that is set for the purchase line. This allows customers with certain process to reduce the unnecessary manual work of receiving orders manually. Manual receiving is still possible before the desired delivery date.

2.12 Currency code and mime codes as PEPPOL BIS order data

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

The allowed attachment types for tenants using EHF Ordering now are:

.docx.xls.ppt.doc.rar.png.jpg
.bmp.xlsx.pptx.xps.pdf.gif.tif
.xml.csv.vsd.zip.xslt.html.tiff

Basware P2P automatically allows only these attachment types and validates currency codes on the order creation if AllowEHFOrdering tenant setting in Configuration tool is set on. 

2.13 Mark on requisition that partial delivery is not allowed (PEPPOL BIS/EHF)

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

In the case of EHF orders, it is now possible for the person who requisitions to indicate on the purchase requisition that the order line items must be delivered in a single shipment. By default, partial delivery is allowed. However, Basware P2P does not prevent the receiver to receive partially.

2.14 Select quantity unit / unit of measure from list on requisition

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

Quantity unit can now be selected from selection list on the purchase requisition and order. Consultants can now upload a list for quantity units / units of measure for a tenant in Configuration tool. Quantity unit selection list for free-text form will be available in future releases. Localization of quantity units is not yet supported.

3 AP Automation

3.1 Edge Invoice enhanced screen configurations

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

Configuration of invoice data in the Edge client has been improved. It is now possible for the customer to select whether to show net-based or gross-based totals on the UI, customize the first two dimensions of the coding summary, and use customized supplier names if needed.

Configuration improvements on the task list page:

Configuration improvements on the details page: 

These fields can be configured in Configuration tool > Invoice Automation > Screens > Edge views: Invoice.

3.2 Edge landing page

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

The Edge client now contains a tutorial that introduces the basic features and functions available. The tutorial is shown when a user logs in for the first time. Users can access the tutorial also by clicking the Getting started link in the right panel on the task list page or from the navigation menu in the top right corner.

3.3 Automatic company and supplier filter for purchase order search

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

Now a user can filter search results by the invoiced organization and invoicing supplier when searching for matching purchase orders and goods receipts for an open invoice in the Matching view. Once the user activates these two filters, the system will remember the selected settings during the session.

3.4 Budget-based payment plan full details view in Edge

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

Now reviewers and approvers can see a budget-based payment plan's header data, budgets, workflow, history, attachments, coding rows, and matched invoices in the payment plan's details view in the Edge client. Earlier, only a summary view of the budget-based payment plan was available.

Coding rows and matched invoices can be seen from the budget's details view.

3.5 Schedule-based payment plan full details view in Edge

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

Now reviewers and approvers can see a schedule-based payment plan’s header data, payment schedule lines, workflow, history, attachments, coding rows, and matched invoices in the payment plan details view in the Edge client. Earlier, only a summary view of the schedule-based payment plan was available.

Coding rows and matched invoices can be seen from the payment schedule row's details view.

3.6 Self-billing payment plan full details view in Edge

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

Now reviewers and approvers can see a self-billing payment plan’s header data, invoices, workflow, history, attachments, coding rows, invoice lines, and matched invoices in the payment plan details view in the Edge client. Earlier, only a summary view of the self-billing payment plan was available.

Coding rows and matched invoices can be seen from the invoice's details view.

4 Platform

4.1 Workplace browser support

Module(s): Platform
Feature ID: ALUSTA-7340
Release: P2P 17.3
Feature Implementation: Feature is in use automatically

Basware Workplace client uses Silverlight browser plugin technology. Mozilla Foundation has made decision to drop Silverlight support from Firefox starting from release 52 (March 7 2017). Firefox Extended Support Release 52 continues to support Silverlight. Workplace client informs users if Silverlight plugin is not installed and this note has been renewed to reflect the latest changes in browsers. Basware Edge client is not affected by the browser changes.