InvoiceReady: SEPA-Payment Error When Saving Purchase Invoice in InvoiceReady Version 25.06


What is the issue?

An unintended error message is displayed in InvoiceReady version 25.06 under specific conditions when saving a purchase invoice. This issue is related to the Payment Method and Expenses settings on the invoice form.

How is the issue presented to the user?
When attempting to save a new purchase invoice, users may encounter an error message if the Payment Method is set to SEPA-Payment and the Expenses setting is Following Service Level (SLEV).

Error in English

Error in Finnish

What this article helps with:

This article provides a workaround to resolve the error message until a permanent fix is deployed in a future version of InvoiceReady.

If you are experiencing issues saving purchase invoices in InvoiceReady version 25.06 and encountering a SEPA-related error, please follow the steps below to resolve the issue temporarily.

Resolution:

To work around the issue:

1. Open the affected purchase invoice.
2. Navigate to the Payment and Rate Data tab.
3. In the Payment Method dropdown, select any value other than SEPA-Payment.
4. Ensure the Expenses field is not set to "Following Service Level (SLEV)".

Example of valid values:

validsettings.PNG

Alternatively:

If the supplier is a valid SEPA member, you may select SEPA-Payment as the Payment Method, but ensure the Expenses field is also set to a compatible value.

Example of valid SEPA values:

validsettings_SEPA.PNG

Additional Information:

The Payment Method and Expenses settings in InvoiceReady are typically based on the supplier’s saved bank account details.
These fields pass payment instructions to the payment system, although the actual payment method is determined by the payment platform and the bank account setup.
A recent change in InvoiceReady has caused some combinations of these settings to be incorrectly saved, resulting in the error.

Please submit a customer support ticket if you're affected by this issue and include:

  1. How often the issue occurs
  2. Number of impacted invoices
  3. Number of users affected

This helps Basware assess the urgency and scope of the problem.