Release 2026-03-23

csv Export added for additional tables

The csv Export function has been extended to include further tables. This feature is now also available in the “OPOS Clearing Run” and “Booking Entries” tables.

Changeover for API keys from roles to scopes

Previously, API keys were linked to roles, which were designed for users of the web portal. As API keys are used to access our API and are not necessarily assigned to a specific user with a role, we have revised this concept. From now on, when creating and editing API keys, roles will no longer be assigned. Instead, so-called scopes will be selected directly. For further information have a look at our API keys and Scopes Documentation.

Existing API keys remain unchanged. The roles previously assigned have been automatically converted into corresponding scopes.

Scopes define an API key’s access to specific endpoints of our API, thereby enabling more precise and transparent control of permissions. For security reasons, we recommend activating only the scopes that are actually required.

Introduced rule-based document number strategy

A new rule-based strategy allows document number assignment to be configured flexibly based on attributes such as customer type, country, billing group, or operating site, with rule priority determining which counter is applied.

Improved settlement data formatting for Adyen

Settlement data from Adyen is now formatted more consistently to prevent issues with downstream systems such as accounting tools when processing special characters.

Enabled webhook-based processing for Adyen

Adyen payment intents and settlements can now be processed via webhooks, enabling more timely and reliable data updates when configured in the Payment-Provider settings.

Webportal improvements

• On document detail and OPOS pages, payment details are now explicitly labeled as applying to future charges to avoid confusion with the originally used Customer Payment Account (CPA), which remains available in the Payment Intent.
• Settlement item properties are now displayed in settlement and transaction details in the Webportal, enabling better analysis and decision-making

Maximum quantity cap per usage

A maximum billable quantity can now be configured per pricing group for timebased usage options. If the billed quantity exceeds the configured cap, only the capped amount is charged. Free quotas are applied before the cap is evaluated.

Split invoices by original billing period

A new splitting configuration option (Original Billing Period) can be enabled per billing group. When active, items whose service periods originate from different billing periods are placed on separate invoices — even if processed within the same billing run (e.g. via late usages in carry-over mode). This allows late-rated usages to be clearly separated from the current billing period and simplifies accounting, particularly around period boundaries such as year-end. The option is disabled by default.

Query remaining correctable amount per document item

A new GET endpoint allows querying how much of a document item can still be credited. The response includes the total correctable amount (totalCorrectableAmount, i.e. the original item amount after allowances) and the remaining correctable amount (remainingCorrectableAmount) after any partial corrections already applied. This enables informed decisions on further partial credit notes.