Contents

• 1 Introduction
• 2 Invoice Automation
  • 2.1 Corrections to translations of invoice and spend plan history entries
  • 2.2 Exception shortcuts
  • 2.3 Resolve transfer
• 3 Marketplace
  • 3.1 Labels renamed
  • 3.2 Lite Content Loader
  • 3.3 Setting default UNSPSC code
• 4 Match Orders
  • 4.1 Automatic matching with an invoice that is already matched
  • 4.2 Enable matching with small difference
• 5 Platform
  • 5.1 Forward pending tasks to backup persons in P2P Admin
• 6 Purchase
  • 6.1 Purchase requisition’s header approval functionality
  • 6.2 View the budget spent status in a chart

2.1 Corrections to translations of invoice and spend plan history entries

Module(s): Invoice Automation
Feature ID: ALUSTA-93529
Release: P2P 24.9

The history entries in invoices and spend plans have been enhanced. Earlier, some entries (for example, entries related to automatic task forwarding and one-action-only setting) were not translated correctly. The entries have now been corrected so that from now on they will be correctly translated in the user’s language.

2.2 Exception shortcuts

Module(s): Invoice Automation
Feature ID: ALUSTA-79400
Release: P2P 24.9

With the new Exceptions status graph, it is easy to find invoice exceptions that are not related to a specific invoice status. User can filter invoices by two exceptions: Disputed and Overdue in last 30 days.

• Disputed displays all disputed invoices, regardless of invoice status.
• Overdue in last 30 days displays all active invoices with due dates that have passed within the past 30 days.

Additionally, the status graphs now offer more customization. User can select which status graphs are visible. To select the status graphs, user can click the pen icon in the top right corner of the status graphs. A dialog opens allowing the user to select one to five graphs to display. This helps the user to remove unnecessary graphs for a layout with more relevant information. All five status graphs are displayed by default. 

2.3 Resolve transfer

Module(s): Invoice Automation
Feature ID: ALUSTA-96104
Release: P2P 24.9

There is a new action, Resolve transfer, that can be used to manually complete or fail an invoice transfer if the invoice is stuck in the “Transfer in progress” status. The status might incorrectly remain unchanged for two reasons:

• The invoice has been transferred to the ERP system, but the transfer response has failed.
• The invoice has not been transferred to the ERP system but it is stuck in the P2P for some reason.

Previously, users had to contact Basware support to complete or fail the invoice transfer in these cases. Now they can resolve the cases themselves. 

There are two options for resolving the situation, depending on whether the invoice is in the ERP system or not:

• If the invoice is in the ERP system, the user can manually mark the transfer as completed and enter the missing data manually. 
• If the invoice has not reached the ERP system, the user can manually mark the transfer as failed and try to transfer it again later. 

The actions Cancel process, Cancel and resend, and Select process are no longer available for invoices in the “Transfer in progress” status, because Resolve transfer can be used instead.

3.1 Labels renamed

Module(s): Marketplace
Feature ID: ALUSTA-113858
Release: P2P 24.9

The option “Open Punchout” under the Punchout filter has been changed to Self-registration punchout in the Directory tab. This option displays all the public punchouts, allowing the Buyer admin to directly subscribe to them, create an agreement, and link it to the supplier’s pricelist.

The other label change is for the “Agent punchout agreement” that has been renamed to Buyer punchout agreements in the Agreement tab.

3.2 Lite Content Loader

Module(s): Marketplace
Feature ID: ALUSTA-113859
Release: P2P 24.9

The Product Manager admin or the suppliers who upload the content can now use the simple version of the content loader to upload standard items (simple items) in the Marketplace. The Lite Content Loader is a simplified version of the content loader Excel file and it does not support complex features such as bundles, matrices, or custom attributes.

For instructions on how to add your content, refer to the Instructions and Detailed User Guide sheets within the Excel workbook. The Detailed User Guide sheet also specifies which data is mandatory.

The Lite Content Loader can be downloaded from the Product Manager > Loader > Content Loading Template page.

3.3 Setting default UNSPSC code

Module(s): Marketplace
Feature ID: ALUSTA-113883
Release: P2P 24.9

The Default toggle column has been added with the Classification field in punchout and buyer punchout agreement. This is to set the UNSPSC code in the field as a default code.

The punchout items (buyer and supplier managed) have a default classification code defined in the punchout setup. The classification code set on the punchout agreement and buyer punchout agreement was overriding the UNSPSC code set in the punchout setup. It was also overriding the codes being passed with the items from the supplier’s website when added back to the Marketplace basket.

With the default option enabled and the classification field having a value, the classification code of the agreement will override only when no code is returned with the item from the supplier’s website. This happens when items are added to the basket.

The classification code will be picked based on the following table.

For item-based delivery, if the option to create separate delivery items is enabled, the delivery item will use “78102203” as the default classification code. Similarly for header-level delivery, the delivery item will use “78102203” as the default classification code.

4.1 Automatic matching with an invoice that is already matched

Module(s): Match Orders
Feature ID: ALUSTA-109888
Release: P2P 24.9

Automatic order matching can now manage also the invoices that have already been partly matched. This is useful, because sometimes only a portion of an invoice can be matched with the referenced purchase order due to missing goods receipts. In such cases, the invoice is sent to a matching discrepancy task, so that the business user can file the necessary goods receipts. After the goods receipts are recorded, the system automatically matches the remaining part of the invoice with the referenced purchase order. This way the possible coding changes done by the business user remain unchanged in the automatic matching. 

If continuous automatic matching is not yet activated for your organization and you would like to enable it, please contact your Basware consultant or Basware Support. 

4.2 Enable matching with small difference

Module(s): Match Orders
Feature ID: ALUSTA-109829
Release: P2P 24.9

It is now possible to match purchase order based invoices that exceed the referenced purchase order in quantity and/or unit price. This ensures that invoices are not pending for an additional goods receipt when no further receipt is expected to fulfill the difference. Quantity difference may occur, for example, when the net weight of an ordered product is reduced due to water evaporation during transportation from the supplier’s premises to the receiving address. 

To enable matching invoices with small quantity or price differences, please contact your Basware consultant or Basware Support. 

5.1 Forward pending tasks to backup persons in P2P Admin

Module(s): Platform
Feature ID: ALUSTA-110459
Release: P2P 24.9

It is now possible to forward a user’s pending tasks to the backup user in P2P Administrator > Users > Backup persons. Earlier, this functionality was only available in the User settings.

6.1 Purchase requisition’s header approval functionality

Module(s): Purchase
Feature ID: ALUSTA-112063
Release: P2P 24.9

The purchase requisition’s approval workflow now supports header approval. There can be one or many header approval activities in combination with row approvals in one process. Header approval can have one approver, many approvers, or a group of approvers. Approvers can be set manually or based on supervisor hierarchy. It is also possible to customize approvers using anyERP. By default, all set approvers must approve, but it is possible also to state that only one of all approvers must approve.

6.2 View the budget spent status in a chart

Module(s): Purchase
Feature ID: ALUSTA-108133
Release: P2P 24.9

In Data management > Budgets, you can now easily visualize budget consumption with a visual bar that includes hover-over details for spending and a % spent indication, all displayed in the budget detail view.