1 Introduction
This document contains descriptions of new features in Basware AP Automation and Procurement 25.2 and its maintenance releases.
2 Invoice Automation
2.1 Minimum confidence threshold for SmartCoding
Module(s): Invoice Automation
Feature ID: APAI-34
Release: AP Automation and Procurement 25.2
Basware SmartCoding is a machine learning based service that proposes invoice coding.
In SmartCoding settings a new minimum confidence threshold has been introduced. The default value is 20%. If the confidence level of a SmartCoding proposal does not reach the minimum threshold, the proposed value will not be automatically applied.
2.2 Remove invoice action supports a-sync model
Module(s): Invoice Automation
Feature ID: AP-183
Release: AP Automation and Procurement 25.2
You can now remove invoices from AP Automation asynchronously in the background, ensuring they are successfully removed from the external system, for example ERP, before being deleted from AP Automation. If the removal from the external system fails, the invoice is not removed from AP Automation either. Previously, the remove action immediately set the invoice to “Removed” status, even if the removal from the external system failed. This could lead to discrepancies between Basware and the external system.
Using asynchronous removal is optional. A consultant can activate it for the tenant and selected organizations through the anyERP entry point.
When asynchronous removal is activated, the remove action initiates the external system removal process, and the invoice status changes to “Removal from external system in progress”. The invoice is removed from AP Automation only after a successful response is received from the external system. While waiting for the external system response, the invoice status appears as “Pending removal” in the Notice column on the invoice list. The invoice details display a banner to refresh the invoice and another to cancel the removal in AP Automation.
If the removal fails, the invoice status remains unchanged, but the removal status is changed to “Removal from external system failed”. An error notification is displayed on the invoice to inform the user about failed removal attempt.
Invoices that failed to be removed can be easily found using the status graph, by clicking Removal failed in the Exceptions section. They can also be found using the Advanced search, where all removal statuses are available as additional search criteria.
If the user tries removing the invoice again after failed removal, the removal dialog offers two options:
- Remove from AP automation only - this removes the invoice from AP Automation even if it cannot be removed from the external system.
- Remove from both AP Automation and external system - this attempts to remove the invoice again from both systems, in case the first attempt failed due to a temporary reason.
2.3 SmartCoding transitive mapping
Module(s): Invoice Automation
Feature ID: APAI-276
Release: AP Automation and Procurement 25.2
Basware SmartCoding is a machine learning based service that proposes invoice coding.
An e-invoice can have important information that is not imported into the database, but SmartCoding can use it to find correlations between the invoice and the coding.
For example, a specific street address or person on the invoice may always correspond to a particular cost center or project code. SmartCoding can now identify such mappings and propose the correct value with even greater confidence than before.
3 Marketplace
3.1 Help portal in Marketplace
Module(s): Marketplace
Feature ID: ALUSTA-115554
Release: AP Automation and Procurement 25.2
Marketplace now includes a comprehensive Help portal designed to support users and administrators. This portal provides detailed instructions, helpful guides, and informative resources covering the system features. This enhancement enables users and administrators to understand and utilize the platform, thereby increasing efficiency and reducing reliance on external support. The portal will be regularly updated with new documents.
3.2 Set minimum order value in agreements
Module(s): Marketplace
Feature ID: ALUSTA-115553
Release: AP Automation and Procurement 25.2
Organization and Agent agreements now include a new Minimum order value field in the supplier section. This allows buyer organizations to set minimum spending requirements for orders placed with specific suppliers. This feature helps buyer organizations manage delivery costs by preventing checkout if the basket total for a supplier falls below the set minimum order value.
4 Purchase
4.1 Automatically close blanket orders
Module(s): Purchase
Feature ID: ALUSTA-114823
Release: AP Automation and Procurement 25.2
It is now possible to set a blanket order, with or without release orders, to be automatically closed.
4.2 Blanket order anyERP import
Module(s): Purchase
Feature ID: ALUSTA-115153
Release: AP Automation and Procurement 25.2
It is now possible to import blanket orders with anyERP requisition or order import. All lines in the requisition import must be either standard or blanket. However, within a single requisition, there can be multiple blanket orders grouped by ordering split criteria.
4.3 Budget row link to corresponding document
Module(s): Purchase
Feature ID: ALUSTA-108206
Release: AP Automation and Procurement 25.2
It is now possible to navigate from the dynamic or manual budget’s document row in Data management to the corresponding document (purchase requisition or purchase order) in Professional Tools. This is provided that the user has the view or manage Professional Tools permission for the corresponding document type.
4.4 Enrich purchase requisition for receiver group
Module(s): Purchase
Feature ID: ALUSTA-113588
Release: AP Automation and Procurement 25.2
It is now possible to enrich up to 20 receivers for each purchase order in a purchase requisition, either during the requisition creation or approval process, based on the requisition line data.
4.5 View changes made to budget basic data in budget history
Module(s): Purchase
Feature ID: ALUSTA-113907
Release: AP Automation and Procurement 25.2
With internal budgets, that is budgets created in Data Management, it is now possible to view changes made to the basic data in the budget history. The change table shows both the old and new values.