Release 2026-07-13

1. nextDunningLevelDate is now nullable

nextDunningLevelDate may now be null on document API responses. This provides support for a new dunning variant (not yet released), in which the next dunning date is not always available at document creation and may be set later. Clients should handle null as “no next dunning date scheduled yet.”

2. Improved UI of the Billing Group details page
The Billing Group details page has been restructured into editable sections, allowing individual configuration areas to be updated independently. This provides a clearer overview and simplifies editing by opening dedicated dialogs for each section.

3. Partner logos on documents

It will be possible to upload partner logos in the webportal and assign them when creating or updating a contract. Documents created for such contracts will then display the assigned partner logo. This feature is currently in development and not yet released — details will be announced here once it becomes available.

4. Audit trail for OPOS Cases

Changes to OPOS Cases (dunning block updates, payment collection enablement, and status changes) are now tracked in the Audit Trail, supporting compliance and full traceability of Data Report operations.

5. Audit trail for Opos Case Clearing Runs

Opos Case Clearing Run actions (creating and reversing) are now tracked in the Audit Trail, supporting compliance and full traceability of Data Report operations.

6. Payment Intent Status Visibility on Pre-Booked Items

In the OPOS Case view, pre-booked items now show the current status of a payment intent. This makes payment issues visible directly in the open-item context without checking Payment Intent details separately. Note: Existing pre-booked items are not migrated; the status is shown for newly processed items only.

7. Webportal Improvements

  • For OPOS case decisions, the Opos-Case-Decision-Type is now displayed
  • Within Transactions and Settlements, the Settlement Received Date is now displayed alongside the Settlement Creation Date.

8. Canceling coupon applications on contracts

Coupons can now be removed from a contract via API and webportal. Removing a coupon cancels its associated discount effective from the next billing cycle — already invoiced periods remain unaffected. Note that the redemption count is not decremented upon removal; the coupon is considered redeemed. The coupon status changes to CANCELLED once removed.

9. Coupon cancellation now available in the webportal

Coupons assigned to a contract can now be removed directly from the webportal UI (contract details → coupons section). A confirmation dialog prevents accidental removal. This complements the API-based cancellation introduced earlier.

10. Update or remove imageIdent on existing contracts

The contract update endpoint (PATCH /v2/contracts/{id}) now supports adding, changing, or removing the imageIdent field. Setting it to a valid identifier associates a previously uploaded image with the contract; setting it to null removes the association. Documents generated for the contract will use the image assigned at the time of billing.

11. Option updates allowed during recalculation

Updating an option is now permitted even when related billable items are in RECALCULATION_PENDING or RECALCULATION_ERROR status.

12. Bug Fixes

  • Fixed a bug where the transaction page was not automatically refreshed after a payment reversal
  • Fixed a bug where the Regex Target Ident Pattern in the payment assignment strategy was not displayed in the edit modal.
  • Fixed a bug where the cancellation modal was not closing after cancelling a payment intent.

13. SSO configuration for automatic user creation

Added a automatic user creation via SSO option to SSO configurations. When disabled, users must already exist in instellix before they can sign in via SSO. New users are no longer created automatically during their first SSO login.