HomeDocumentationRecipesAPI ReferenceChangelog
Platform OverviewDemoContactImprintLog In
Changelog
Platform OverviewDemoContactImprint
Back to All

Release 2026-04-21

April 22nd, 2026

1. Audit Trail – Tenant Billing Run, Plans and Usages

Tenant Billing Run configuration changes (enable/disable), Plan actions (Create, Update, Delete and Cancel) and Usage actions ((Create, Delete and Cancel) are now tracked in the Audit Trail, supporting compliance and full traceability of tenant-level and plan-level operations.

2. Related document date now available in Document API and E-Invoicing

The Document API now includes a new optional field relatedDocumentDate. The value is mapped to BT-26 and forwarded to Avalara and Mustang, ensuring the origination date of a referenced document is correctly reflected in e-invoices.

3. Webportal Improvements

  • The Jsonata field can now be displayed as a column in the Document Provisioning overview table. This makes it easier to distinguish entries that differ only in their Jsonata configuration, such as Tax Category-specific rules.
  • The Debtor-Ident on the document overview page is now a direct link to the corresponding customer record.

Bug Fixes

  • Fixed a bug where Self-Billing Corrections were sent with the wrong CreditNoteTypeCode (381 instead of 261), causing rejections in Avalara ELR and Mustang.

4. Traceability of users for API keys

To improve traceability, a new ‘API Keys’ section has been added to the user details page. This section displays all API keys created by the respective user.
In addition, the following columns have been added to the API keys table view:

  • Creation Date
  • Last Modified
  • Created By

These enhancements are designed to improve transparency and traceability. Find more information here.

Please note that deleting a user does not automatically remove their API keys. Existing processes for creating, editing and deleting users and API keys remain unchanged. It is recommended that API keys be removed manually before deleting a user. A corresponding note has been added to the delete modal.

For existing API keys, it may be the case that not all information is available. In such cases, missing values are represented by “-”. Furthermore, it is possible that existing API keys are not displayed on the details page of the associated user.

5. Error-Message Error message if the username contains invalid characters

When creating a user account, certain special characters, including umlauts, must not be used. If the username contains an invalid character, an error message will appear when saving, explicitly indicating that an invalid character has been used.

6. Plan Change at specific date

Plan changes can now be executed at any custom date (in the next billing period), not just at the end of a billing period. This removes a previous MVP limitation and simplifies two key workflows: mid-month contract transitions no longer require a contract termination and re-subsctiption, and upsell upgrades can be scheduled for any desired date via API and web portal.