Onventis Invoice Processing 2025.4

Release 2025.5 is planned for October 4, 2025 (Beta) and October 18, 2025 (Production).
This release was originally scheduled for 26 July 2025, but has been postponed by one week to ensure system stability and the successful delivery of all planned features.

🚀 Introduction: AI Coding & E-Invoices

This release includes two key updates:

1. AI Coding Proposals: We have enhanced the accuracy of line recognition to ensure that line totals consistently align with header totals, thereby facilitating improved automation.

2. E-invoice data handling: E-invoice data is now stored at the tenant level, enabling customers to fully leverage invoice details for smarter, more automated processing

💎 AI Coding Proposals: Single-Line Amount Adjustment

In specific cases, line recognition isn't always accurate—so we've introduced MatchingScript.AdjustAmountOfOneLine to correct it. When enabled, and only one (grouped) invoice line exists, the system aligns the line amount with the invoice header (if they differ and the header is valid). VAT and price are recalculated automatically.

To utilize this feature, your consultant needs to make specific configuration changes.

💎 AI Coding Proposals: Improved Grouped Line Descriptions

Customers don’t always want the standard “Grouped invoice line #” labels. That’s why we’ve added MatchingScript.GroupedLineDescription: when enabled, it replaces the default label with the supplier’s default transaction description.

To utilize this feature, your consultant needs to make specific configuration changes.

🆕 Extended and smarter E-Invoice Data Handling

We’ve improved how e-invoice data is processed by switching to Storecove’s new connection point called received_document. This update improves reliability, consistency, and prepares us for future e-invoicing requirements.

What’s Changed:

• Future-Ready: The new endpoint supports upcoming e-invoicing regulations, such as those expected in Poland.

• Complete Data Storage: All invoice data is now stored in the customer database. Previously, only key fields were saved, sometimes missing details needed for automation or compliance.

• Controlled Rollout: A feature flag allows Onventis to enable this functionality per customer. By default, it’s turned off and only activated when needed.

This update ensures customers are better equipped for evolving e-invoice standards—without disrupting current processes.

To utilize this feature, your consultant needs to make specific configuration changes.

🛠️ FIX: Rejected Invoices Not Shown After 'Assume'

We’ve resolved an issue where rejected invoices were not shown in the “Rejected to me” worklist after being assumed by a coder. With this fix, assumed transactions are now properly removed from other coders’ worklists, and the “Rejected” counter and filters reflect only relevant items, ensuring accurate visibility in multi-coder workflows.

🛠️ FIX: Stream Records with Matching Errors Now Mark Batch as Failed

We’ve fixed an issue in stream (interface) processing where records with matching errors, such as "Too many matches for record. Try to specify UniqueKey", were incorrectly marked as ‘Success’ at the batch level.

• From now on, if such an error occurs in any record, both the record and the entire stream batch will be marked as ‘Fail’.

• This ensures accurate status reporting and prevents misleading success indicators in interface executions.