2.1 Backup person support for purchase order approval workflow tasks

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

Now the backup setting for requisition review and approve tasks applies also to order approval tasks. When there has been a request for approval on order total increase by a buyer, the order approver’s backup person gets the approval task and the original approver gets an informative task. Now it is also possible to forward the order approval task to a user who has sufficient order approval limit to total order value.

2.2 Define delivery period on the requisition and send it on the XML order

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

In the Order now dialogue, users always see the Desired delivery date and Desired delivery end date fields in the Workplace client. Desired delivery date is automatically copied to Desired delivery end date, if  the latter is left empty. If a consultant configures a desired delivery end date for purchase requisition and purchase order header and lines, users can edit also desired delivery end date during the purchasing process. Desired delivery date and Desired delivery end date are available on XML orders as well as the purchase order PDF. Basware P2P does not any more overwrite desired delivery dates on the line with desired delivery dates on the header.

3.1 Bank account details imported from invoice

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

Now it is possible to import invoices into the Basware Purchase-to-Pay so that bank account on the invoice gets chosen if the IBAN or BBAN defined on the invoice is found from Basware P2P Administration. Supplier’s default bank account is chosen to the invoice in case the IBAN or BBAN on the invoice is not defined in Basware P2P Administration. If supplier’s default bank account is not defined, then the first bank account defined for the supplier in Basware Purchase-to-Pay gets chosen. Earlier, invoices were imported to the system so that invoices always got supplier’s default bank account from Basware P2P Administration.

Moreover, changing invoice type on the invoice does no longer change the bank account on the invoice to the supplier’s default one.

3.2 Edit recipients - UI enhancement in Edge

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

Discussions have been enhanced so that the discussion header shows more clearly who started the discussion and who are the participants in the discussion.

Also editing the participants has been enhanced so that the person who started the discussion can remove all participants and add participants, but other participants can only add more participants or leave the discussion.

3.3 Exclude users from performing an invoice task twice in the process

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

Conditional invoice approval has been enhanced by checking if the user has already performed a review or approval task on the invoice. If user has performed a task earlier, then the conditional approval task is created for the next person in priority in the Advanced User Settings table. Earlier the check was not done and the user could not perform the conditional approval.

3.4 Number of characters in discussions and comments is extended from 250 to 1 000 characters

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

The number of characters in adding comments and discussions has been extended so that the allowed number of characters is now 1 000 characters instead of the old 250.

3.5 Change invoice line type from additional cost back to normal invoice line

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

Now it is possible to revert an additional cost line back to a normal invoice line without deleting the invoice line first.

3.6 Match invoice using invoice line details when the lines are created by best-fit recognition methods

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

Now the user must match the invoice using the individual invoice lines when the invoice was previously associated with automatic best-fit recognition methods. If the user tries to match the invoice without selecting the specific invoice line to be matched, the system will guide the user to drill down to more detailed level. The user can also remove the invoice lines before the match activity and continue matching without the invoice line details.

3.7 Matching stores coding details it has created to the invoice history

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

Now the user is able to see the changes in the invoice coding that took place when the invoice was matched with a purchase order.

3.8 Create budget-based plan with net sums

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

Now it is possible to create budget-based payment plan with net sums. Earlier, it was possible to create budget-based payment plans only with gross sums.

3.9 Next approver fetched after failed payment plan matching

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

Now the system fetches a next approver from the advanced user rights table to the invoice coding rows if an automatic payment plan matching has failed and therefore the invoice has been automatically sent to workflow. The invoice process needs to contain a row approval activity in this case. Earlier, the system did not fetch a next approver to the invoice coding rows.

4.1 Alusta cookie note

Module(s): Platform
Feature ID: ALUSTA-24728
Release: P2P 17.8
Feature Implementation: Basware consultant work is needed

A cookie note with a link to a page describing cookie usage has been added. Users can now see that cookies are used and get more detailed information of the usage if they wish. The cookie note is shown once, it is a non-interrupting message and it is mandatory for certain regions when all used cookies are not on exceptions lists.