HomeDocumentationRecipesAPI ReferenceChangelog
Platform OverviewDemoContactImprintLog In
Changelog
Platform OverviewDemoContactImprint
Back to All

Upcoming Release

July 29th, 2026
  1. Removal of merchantPaymentGateway from Customer Payment Account responses

Our Customer Payment Accounts currently respond with an additional entity: The Merchant Payment Gateway. It is both referenced via ident (documented) and provided as an entity (undocumented). We aim to remove the latter, the entity, as we assume that no logic was attached to this undocumented behaviour. Should you generate your client from our OAS this field was not available for you to use.

If for some reason you do require the entity please reach out so we can find a solution.

  1. Peppol recipient identification scheme (ICD)

For e-invoicing parameters in the web portal, you will be able to select the recipient identification scheme from the Peppol ICD list (for example SIRENE), instead of an instellix-specific recipient code type. This feature is currently in development and not yet released — details will be announced here once available.

  1. Service and billing period on documents

Document overviews and document details in the web portal will show the service period and billing period. The same fields will also be available on the Document and Draft Document APIs, including RSQL filters. This feature is currently in development and not yet released — details will be announced here once available.

  1. Audit trail for additional billing entities

The following entities will be added to the Audit Trail: Documents, Aggregation Configurations, and Tax Provider Configurations. Further billing entities will follow. This feature is currently in development and not yet released — details will be announced here once available.

  1. Bulk actions for e-invoicing workflows

In the e-invoicing workflow overview, you will be able to select multiple workflows and resend or ignore them in one step. This feature is currently in development and not yet released — details will be announced here once available.

  1. Configuration Transfer Improvement

Selecting configurations for import and export is now faster and more convenient. The previous dropdown has been replaced with a table that supports multi-selection using checkboxes, including a Select All option. This makes it easy to work with large numbers of configurations without selecting each one individually. Find further information here.

  1. OPOS Case Dunning (Preview)

instellix supports OPOS-case-based dunning as an alternative to (legacy) document dunning soon. Matching rules let you apply different dunning levels and fees depending on criteria such as customer type (e.g. B2B vs. B2C) or Billing Group — so each segment can follow its own escalation path. Dunning plans are created and tracked for overdue open items.
Note: This feature is currently available to users with the Beta Preview role. Important follow-up work is still planned, including Accounting and PDF files.

  1. Order line item service period editable after deposit invoice

After a deposit invoice has been created, the service period (periodStartDate / periodEndDate) of an Order Line Item can now be updated via the existing Edit Line Item API. All other fields (price, name, deposit amount) remain locked. The deposit invoice is not cancelled or corrected. This allows integrators to set the final service period between deposit and final invoice.

  1. Document-item corrections trigger refund-capable reason

Credit notes created via POST /v2/documents/{documentIdent}/corrections (document item corrections) now set the itemReason to CANCELLATION instead of CORRECTION. This ensures that downstream payment services can automatically trigger refunds for corrected items. Address corrections remain unchanged with reason CORRECTION.

  1. Further areas with configuration transfer

Configuration Transfer has been enhanced and is now available for additional configuration areas. In addition to SSO Configuration and Tax Rules, the following configurations can now be transferred between tenants and environments:

  • Payment Categorization Rules
  • Payment Assignment Strategy
  • Payment Assignment Configuration

Existing configurations can be exported as a JSON file and imported into another tenant or environment, making it easier to reuse established setups.
Detailed instructions can be found in the documentation.

  1. Webportal Improvements
    1. Merchant Payment Accounts now show a tooltip on Payment Collection Configuration explaining that dunning is driven by the document due date — not by charging set to “Immediately”.
    2. The OPOS Case view now includes tooltips for Balance, Amount due, Dunning Block, and Dunning Block Origin, clarifying how these values differ and where a dunning block applies.
    3. Audit Trail entity filtering now uses a searchable dropdown instead of free text, making it easier to find the right entity type.
  2. Bugfixes
    1. Fixed a bug where IP addresses were missing from Audit Trail entries.
    2. Fixed a bug where users with the Auditor role could see write actions in Payment Categorization. The action is now hidden for read-only roles as intended.
    3. Fixed an issue where contract line item updates (e.g. triggered by the Rated Usage Service) failed when a technical property was present on the line item.
    4. Fixed a bug where the dashboard widget ‘Customers with disabled billing run’ displayed an error when loading the list.