HomeDocumentationRecipesAPI ReferenceChangelog
Platform OverviewDemoContactImprintLog In
Changelog
Platform OverviewDemoContactImprint
Back to All

Release 2026-09-21

September 22nd, 2026

  1. Capture-only payments with external authorization

    From now on, you can capture an authorization that was created in your own checkout: store the Adyen pspReference as a Payment Authorization for the Order or Contract, and set the authorization mode of the Adyen configuration to Pre-authorized. instellix then captures against that reference instead of authorizing again. Payment Authorizations are listed in the web portal under Payments → Payment Authorizations and can be queried through the API. See Capture-only Payments with External Authorization.

  2. Multiple PSP configurations per tenant

    Previously, a tenant could connect only one payment service provider (PSP), which forced separate tenants for separate business cases. From now on, you can create several PSP configurations in one tenant (for Stripe and Adyen), each with its own name, credentials, webhook, and Merchant Payment Account. This also covers multi-currency setups that require a dedicated merchant account per currency.

  3. OPOS/Payment-Intent: Deletion of PreBooked Item, after final Retry

    When a Payment Intent fails, and no further automatic retry is scheduled, the related PreBooked Item will be deactivated. The OPOS Case Amount Due is recalculated without that pending collection, so it shows the actual outstanding receivable. Also, dunning will start, depending on the configuration

  4. Clearer column names in the OPOS case view

    With dunning and chargeback fees, the previous column labels in the OPOS case no longer described what is shown. We renamed the columns to Source, Source Type, Applied to, Applied to type, Debit, Credit and Balance. The balance is now color-coded — green when balanced, red for underpayment, blue for overpayment — empty in rows with a zero balance, and shown in bold in the totals row.

  5. Usage Records for Rated Usage Invoices

    Previously, Usage Record configurations covered Metered Usages only. When creating a Usage Record configuration, a configuration type can now be selected:

    • Metered (Metered Usages only)
    • Rated (Rated Usages only)
    • Combined (both in one CSV).

    The configuration is assigned in Document Provisioning so that the matching usage detail file is attached to invoices. For further Information see Usage Records.

  6. New Login Behavior: SSO Only

    A new login behavior "SSO Only" is now available for tenants that wants to exclusively use Single Sign-On.
    When enabled, users are automatically redirected to the configured default Identity Provider. Local authentication with username and password is completely disabled. As a result, related functions such as Forgot Password, password reset emails, welcome emails, and settings for local authentication are no longer available.
    Existing users remain active and can continue to access the tenant through the configured SSO provider. For further Information see SSO Configuration.

  7. Configurable Session Settings

    Session settings can now be configured individually for each tenant. The Idle Session Timeout, Maximum Session Timeout, and Access Token Lifespan can be adjusted to meet individual security requirements.
    The settings apply to both local login and SSO sessions, providing greater control over how long user sessions and access tokens remain valid. For further Information see Session Settings.

  8. Document Provisioning: enable/disable rules

    You can now turn a Document Provisioning rule on or off with a toggle in the web portal — without editing the JSONata expression by hand. Off sets the condition to false (rule does not match); on sets it to true. In Expert mode the JSONata field stays visible and stays in sync with the toggle.

  9. Audit Trail: Billing Group and Avalara ELR

    Changes to the following entities are now recorded in the Audit Trail:

    • Billing Group (including related tax and document preparation settings such as VAT-ID check and zero-value documents)
    • Electronic Invoicing Workflows
    • Avalara ELR Tenant Configuration
    • Avalara ELR Mandate Mapping
    • Avalara ELR credential configuration
    • Avalara ELR Tenant configuration support

    That makes configuration changes in these areas traceable for compliance.

  10. Document Tax Code Mappings for Document API e-invoicing

Document API invoices can now be enriched with electronic invoicing tax parameters (tax category code, exemption reason code, and optional reason text) from a tenant-configurable tax code mapping — without changing amounts or calculated tax values. You maintain the mappings in the web portal under Configuration → Billing → Document Tax Code Mappings, or via API. See Document Tax Code Mappings.

  1. Bug fixes

    1. Creating a settlement item without an exchangeRate returned null in the response, even though the field is required there. Generated API clients failed to deserialize the 201 response as a result. We fixed it, the response returns 1 when base amount and original amount share the same currency, so the OpenAPI specification and the runtime behavior match.
    2. Errors in the text for the ‘Forgotten password’ function and following the updating of an account have been corrected and the relevant messages are now displayed correctly.

  2. Webportal Improvements

    1. The loading indicator on the webportal has been optimised. When loading large amounts of data, misleading values such as ‘10,000’ are no longer displayed. Instead, a neutral placeholder is shown during the loading process until the actual number of records is determined.