Onventis 2025.6

The new Onventis 2025.6 release contains various enhancements, improvements, and bug fixes. Check out the complete list below!

Onventis Platform

Platform

Multi-Factor Authentication

We have implemented Multi-Factor Authentication (MFA) for Onventis Buyer to enhance account security. MFA can be activated on a per-organization basis. When enabled, users will receive a six-digit verification code via email after entering their password. This code must be entered for validation to confirm that they have access to the mailbox associated with the account.

Key Features

• Email verification: Six-digit codes valid for current session only

• Smart input: Paste codes directly from email with auto-submit

• Retry logic: Three attempts per code, 60-second cooldown for resends

• Admin control: Enable/disable via organisation settings

Procure-to-pay

Enhancements to Amazon Integrated Search

Language Personalization in Search Results

• Product search results now use your preferred language from your user profile.

• Product descriptions are shown in your own language instead of the marketplace default.

• This ensures a consistent and user-friendly experience for international users.

• If a user’s selected language is not supported by the Amazon marketplace, the system automatically falls back to English, using the correct variant as defined below:

Filter Amazon Business Integrated Search by Delivery Address

To make your purchasing process more reliable, you can now filter Amazon Business search results based on your preferred delivery address.

• A “Delivery Address” dropdown is now available in the product search sidebar.

• View only products that are eligible for delivery to the selected address.

• If only one delivery address is available, it is selected automatically.

• The filter shows only addresses assigned to your organizational unit.

• You can clear the filter anytime to view all products as before.

• Prevents placing orders for products that cannot be delivered to your location.

• Note: If some product does not display a price, it means it cannot be delivered to your selected address as shown in the example below.

Improved Approval Check for Service Notes with Order Changes

In service-based workflows, approval checks are now more accurate when handling line items added through order changes.

• In workflow configuration, you can now choose between comparing service note values against the original order value or the current order value.

• Workflow settings → Service Note Approval → Miscellaneous section → New option: "Check the difference to the current order value"

• Previously, new line items added via order changes were incorrectly compared to 0 EUR during approval checks, triggering unnecessary approvals.

• A new radio button group under the “Miscellaneous” section lets you define which baseline to use:

  • Original Order Value – uses previous behavior (fallback to 0 EUR for new items)

  • Current Order Value – uses the actual value from the latest version of the order

• Example scenario:

  • Original order: 25,000 EUR

  • Order change adds a new item worth 4,000 EUR

  • Service note includes that item

  • Now, the system compares 4,000 → 4,000 (not 0), preventing false triggers

Extended Character Limit for Cost Category Titles

• The Title field in Cost Categories now supports up to 5,000 characters (previously 1,000).

• Enables smooth import of multilingual cost category data with 10+ translations.

• Prevents import errors like “String or binary data would be truncated.”

• Ensures better support for international users beyond German defaults

PunchOut: Expected Delivery Date Now Captured

You can now transfer expected delivery dates from PunchOut shops back into Onventis for improved order accuracy.

• Expected delivery date entered in the PunchOut shop is now supported via:

<Extrinsic name="ExpectedDeliveryDate">YYYY-MM-DD</Extrinsic>

• The date is captured per item (position) when the cart is returned to:

  • Shopping cart → stored as deliverydate

  • Order → written directly to the order position

  • The date is included in the outgoing OrderRequest as requestedDeliveryDate.

• Format must be YYYY-MM-DD; invalid formats are ignored.

• Fully compliant with cXML 1.2.014, no schema changes required.

• When returning to Favorites, the date is ignored.

Surcharges/Reductions” Now Hidden When Prices Are Suppressed

To respect price visibility restrictions, surcharge and reduction details in purchase orders are now hidden when the relevant user setting is enabled. When the setting “Hide prices in catalog navigation and order handling process” in User → Extended Tab is enabled:

• The “Surcharges/Reductions” section is hidden in the line item conditions.

• The “Total discount/surcharge” is hidden in the line item summary.

• When the setting is disabled, all price-related details remain visible as usual.

Order Export: Now Includes Position Type and ERP Source

To enhance transparency in order reporting, the Excel export of purchase orders now includes two additional fields, this column appears only if the organization setting “Marking” is enabled under Organization setting → Purchase Order-> Marking

• OP_PositionType: Indicates whether a line item is from a catalog or entered as free text.

• OP_IsERP: Marks if the item was created via an ERP integration (1 for ERP, 0 for non-ERP).

Order Search Extended with Custom Accounting Fields & Supplier Comment

• The Purchase Order Search is extended to support filters for Custom Accounting 1, Custom Accounting 2 and Supplier Comment (external comment from supplier's sales order)

• Supports both exact and partial text matching.

• These fields are now also searchable via the "All Fields" global search.

Improved Display Format in Inheritance Model Window in Shopping Cart & Purchase Order

We’ve enhanced the clarity of data shown in the Inheritance model window to help users better identify referenced values across documents.

• All relevant fields now follow the "Number – Title" format for easier recognition.

• Applies to both Shopping Cart and Purchase Order pages.

• Regular views (outside the Inheritance window) remain unchanged.

• Affected fields include:

  • Sales Order (SalesOrderNr)

  • Project (ProjectNr)

  • CAPEX No. (CapexNr)

  • PSP Element (WpsElementNr)

  • Network Plan (NetworkID)

  • Attachment (AssetID)

  • Customs Tariff Numbers (CustomsTariffNr)

The “Task” Field Can Now Be Renamed System-Wide

• The “Task” field is now fully renamable using multi-language support, just like Custom Accounting Fields and Business Area.

• The custom label will appear consistently across the system, including:

  • Catalog items

  • Order positions

  • Demand positions

  • Shopcart

  • Service note positions

  • Auto-finding configuration

  • Account allocation settings

  • PDF order documents

• This allows to adapt the field label to match their internal terminology (for example: rename "Task" to "Cost Unit" or "Work Package").

Account Allocation: Auto-Finding Now Supports Project, Asset, and Task

• The account allocation auto-finding logic has been extended to include Project, Asset, and Task as valid criteria and result fields.

• These fields can now be configured as well in:

  • Organization Setting → Purchase Order

  • Cost Allocation->Account assignment determination criteria

• Excel import/export of the auto-finding rules now supports these new objects, including both AssetNr and SubNr for Asset.

Interfaces Related Key-Update

• New “Final Invoiced” Flag in Order Changes: A new parameter allows purchase order items to be marked as fully invoiced when sending order changes to SAP. When enabled, the system adds <FinalInv>X</FinalInv> in the export XML for each item that is considered financially completed.

• openTRANS Export: Optional Transfer of Payment Term Codes: A new parameter, Export_PaymentTermsAsNrIntern, enables the export of payment terms as internal codes (NrIntern) instead of plain text descriptions in openTRANS Order and openTRANS OrderChange messages. When activated, and if the organization uses predefined payment terms (i.e., selection from a list), the system will insert the internal code into the <REMARK type="Onv-PaymentTerms"> node.

Supplier Management

History Log to track file changes in File Storage

With the Central File Storage, the supplier can create, maintain, and share files with multiple buyer connections. The buyers receive notification regarding file updates, expiration and can view all the files received for all their suppliers centrally. During its lifecycle, the file undergoes several actions such as addition of new version, sharing with buyer, editing of file details by different users.

We have added a ‘History Log’ in the file detail view for both buyers and suppliers to track all the changes made to the file to maintain transparency for audit purpose. Along with the event, timestamp and user details are also captured. The ‘History log’ is displayed in a table format with columns: Timestamp, Event, Details, Username. The table can be sorted by Timestamp. By default, the latest events are displayed on top.

The format of the ‘History Log’ with the list of events covered and their details:

Supplier View:

Buyer View: