This article describes contracts, contract spend visibiility, and how to enable them for your organization. Please note that these functionalities require configuration changes to be enabled. To request enablement for any of these functionalities, please see Instructions for feature enablement.
Contract spend collection allows tracking of how much has been ordered and invoiced against a contract. This enables contract spend visibility, where you can see the monetary usage of contracts and also follow ordering and invoicing that is not contract-based.
In P2P Purchase, it is possible to collect the list of orders and spend plans using that contract and their total sums. Contracts are not used to limit or restrict ordering. To do that, use P2P Budgets instead.
In P2P Invoice Automation, it is possible to collect the list of invoices and the total sum for those invoices, if the contract number is included on a coding row of an invoice. The contract number may be added to coding during order matching or via a coding template.
Contracts must be imported to P2P from an external system by Basware anyERP or Basware API. It is not possible to create contracts manually. To collect contract spend or export contract metadata and spend information, you must use Basware API.
There are many enhancements related to Contracts functionality and visibility in P2P Purchase, Invoice Automation, Order Matching, and Spend Plans.
Please note that these functionalities require configuration changes to be enabled. To request enablement for any of these functionalities, please see Instructions for feature enablement.
Instructions for feature enablement
For more detailed instructions, limitations, and so on, please see this document.