Contents:

• 1 Introduction
• 2 Procurement
  
  • 2.1 Purchase order data import
  • 2.2 Custom delivery addresses to FTF in Edge
  • 2.3 Free-text form attachments in Edge
  • 2.4 Free-text form's configuration to support a form specific image usable in Edge
  • 2.5 Import existing FTF from WP to Edge
  • 2.6 Copy purchase requisition coding from a line to all other lines in Edge
  • 2.7 Editing data on Header panel in draft and approval phases in Edge
  • 2.8 Editing data on Purchase orders panel and changing goods receiver in Edge
  • 2.9 Show and edit coding in purchase requisition header level in Edge
  • 2.10 Show invoice address details in Edge
• 3 AP Automation
  
  • 3.1 Absolute approval limit
  • 3.2 Sort and filter the task list
  • 3.3 Recurrence button on matched payment schedule line
  • 3.4 Organization mandatory

2.1 Purchase order data import:

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

Now it is possible to import single order data to P2P Purchase, for instance order data from an inventory system to be sent to the supplier. The order import prevalidates the imported purchase order for all sufficient data for a single order after which the related requisition and goods receipt task gets generated and the order is sent automatically to the supplier. If prevalidation fails, the data is not imported but an error message is returned to Alusta anyERP. After sending the order, the order data export gets triggered and has an external order number. The order data export has been changed to produce order data XML to outbound directory, instead of inbound.

2.2 Custom delivery addresses to FTF in Edge:

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

Location control is now available in Edge free-text form administration. A buyer can add location control to an Edge free-text form. On the location control, address part level data is shown. Both the buyer and requisitioner can use either a predefined organization delivery address or a custom delivery address.

2.3 Free-text form attachments in Edge:

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

Now the attachment can be added to Edge free-text forms.  

2.4 Free-text form's configuration to support a form specific image usable in Edge:

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

Now it is possible to define an image to Edge free-text form in Edge free-text administration. The image can help Purchasing users to select the right free-text form for their purpose. 

2.5 Import existing FTF from WP to Edge:

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

Now the purchase administrator can import Workplace free-text forms to Edge. Import will copy all selected Workplace free-text forms to Edge and transform these to new Edge free-text form format. 

2.6 Copy purchase requisition coding from a line to all other lines in Edge:

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

Now in the Lines panel, there is a line level action Copy coding that enables copying coding from a requisition line to another. Coding is copied only to non-rejected lines that are owned by the user.

2.7 Editing data on Header panel in draft and approval phases in Edge:

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

It is now possible to configure what fields are editable in purchase requisition's header data in Edge. Earlier, only the Purpose and Desired delivery date fields were editable.

The header panel now also supports executing expressions.

2.8 Editing data on Purchase orders panel and changing goods receiver in Edge:

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

The logic how the lines in the former Supplier and delivery panel are shown, is changed. Earlier, it showed a list of suppliers but now it shows a list of eventual purchase orders. As a result of the logic change, the name of the panel has been changed from Supplier and delivery to Purchase orders.

The fields in the panel are editable and the edited data goes to the eventual purchase order.

The panel now shows also the Order type (Email or XML) field.

The panel also has a new field Goods receiver. By default its value is the owner of the requisition, but the user can change the person who will receive the goods.

2.9 Show and edit coding in purchase requisition header level in Edge:

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

An expand section has been added in the Lines panel to all lines. The section shows the coding for that line. By selecting Edit coding, the user can also edit coding in the Lines panel without the need to go to line level details in order to edit coding.

2.10 Show invoice address details in Edge:

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

Earlier in purchase requisition header level, in the Addresses panel, the invoicing address was shown only as a name, but the address details were not shown. Now invoicing address details are shown the same way as the delivery address details.

3.1 Absolute approval limit:

Module(s): Invoice Automation
Feature ID: ALUSTA-5915
Release: P2P 18.6
Feature Implementation: Basware consultant work is needed before customer can take into use

Approval limit can now be set to work so that the approval limit defined for the user applies both positive and negative invoice sums. If the approval limit is set to 10 000, the user is able to approve any invoice between -10 000 and +10 000. 

This feature needs to be taken in use separately per activity. It works with header approval, row approval, conditional approval, and additional approval.

3.2 Sort and filter the task list:

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

To better organize their work, users can now filter the tasks by organization and sort the list by supplier in addition to the default sorting by urgency.

Set the filter:

View which filter is on:

Sort by supplier or urgency:

Urgency is the default sorting order. The date by which the documents are sorted by urgency:

• Purchase requisition - Desired delivery date
• Goods receipts – Confirmed delivery date or Desired delivery date
• Payment plan (Schedule-based) - Expected date of the earliest unmatched schedule row - date tolerance
• Payment plan (Self-billing) - Invoice date of the earliest unmatched invoice
• Payment plan (Budget-based) - Start date of the earliest unmatched or partly matched budget row
• Invoice - Due date

3.3 Recurrence button on matched payment schedule line:

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

The Recurrence button is now enabled on the last payment schedule line and self-billing invoice line, even if the line would be already matched. Therefore, creating new payment schedule lines or self-billing invoices to a fully matched payment plan is now easier than ever before. Earlier, the Recurrence button was disabled on all matched lines.

3.4 Organization mandatory:

Module(s): Invoice Automation
Feature ID: ALUSTA-42483
Release: P2P 18.5.3, 18.6.1
Feature Implementation: Feature is in use automatically

Organization is now mandatory when searching for invoices, both in Workplace and Edge. By default, the user's home organization is used in search. The user can still search from multiple organizations by selecting many organizations in the picker.

If advanced search is used, the user can search without organizations.