Release 2026-03-09
1. Change to the display of the Properties column in tables
Previously, the complete content of a properties column in tables was displayed via a tooltip. To improve readability and user-friendliness, this behaviour has been adjusted: the content can now be accessed via the ‘Show More’ icon within the corresponding table field and opens in a modal window. The filter function for properties columns remains unchanged and continues to work as usual.
2. Talone.One Extension
Instellix now supports refundable coupons in the Talon.One integration. If a transaction using a refundable coupon is cancelled or corrected, the coupon redemption is reversed in Talon.One so the coupon can be used again.
3. Payment Notification: Extended Error Information
Payment Intent notifications now include structured error information in the notification properties, such as error codes, messages, and retry recommendations from the payment provider. This enables improved error handling and retry logic in connected systems.
4. New Notification for document attachments
A new notification type documentAttachment.archived is now available. The notification is sent when a document attachment (e.g., VAT ID validation results, XRechnung PDFs, or dunning documents) has been archived and is ready for retrieval.
5. Document Number Configuration Improvements
The configuration of document number prefix and suffix is now available directly on the document-counter configuration.
Previously, prefix and suffix values were configured via document-number-strategy configuration, which could be confusing, as the numbering logic is ultimately driven by the counter.
With this change: • Prefix and suffix can now be configured directly on the counter. • A toggle allows choosing whether the counter configuration or the existing strategy-configuration-based values should be used.
The existing strategy-configuration-based approach remains available for compatibility and to avoid breaking changes. Future updates will further improve the counter-based approach and support migration from the legacy configuration.
6. OPOS-Case decisions added to Audit Trail
All decisions and reversals within OPOS cases are now recorded in the audit trail, ensuring full traceability for auditing and compliance purposes.
7. E-Invoicing improvements
- Tax Exemptions are now also available for XRechnung and ZUGFerd invoices.
- E-Invoicing parameters are now displayed in the invoice overview table and on the invoice detail page in the Web Portal. This allows users to quickly view and filter invoices based on their E-Invoicing configuration.
- E-Invoicing parameters are now available in the Jsonata Default Mapping.
- The eInvoicingParameters are now included in the response of the Query documents API.
8. Dunning behaviour during payment retries
Receivables in an active charging or retry process are now excluded from dunning until the payment attempt has completed, to avoid sending reminders while payment collection is still in progress.
9. Corrections (document item based)
Introduced a new correction mechanism that allows applying a subsequent credit to a specific line item on an already issued document (e.g., an invoice). This reduces the item amount by a fixed value without cancelling the entire document or issuing a replacement document.
10. Late Usage handling: "carry over" mode
Late metered usages whose end date falls into a previous billing period can now be carried over and billed with the current billing period (next invoice). This helps avoid many small invoices and improves the customer experience. If the contract has already ended and no active billing period exists, the usage is billed immediately.
11. Tax Exemption Ident in Web Portal
It is now possible to assign a Tax Exemption Ident to line items of orders and contracts in the web portal when manually entering tax values. This ensures that invoices with 0% tax are correctly generated for e-invoicing scenarios.
12. Bug fixes
- Fixed a bug where the OPOS decision API incorrectly required an amount field even though the full OPOS balance should be used when no amount is provided.
- Fixed a bug in the API Reference where the example for querying documents used an incorrect parameter (documentType). The example now correctly uses the RSQL query search=type==INVOICE.
13. Password policy configuration available in the web portal
Users with Admin or SuperUser rights can customise the password policy for the respective tenant via the global tenant configuration. Security requirements such as the minimum password length, maximum validity period and optional activation of 2-factor authentication (2FA) can be set individually. The configuration can be done under Configuration → Global → Tenant Configuration → Security Settings.