1. Brute Force detection configuration available in the webportal

Users with Admin or SuperUser rights can customise the Brute Force detection configuration for the respective tenant via the global tenant configuration. The configuration can be done under Configuration → Global → Tenant Configuration → Security Settings. Further information on available configurations can be found here.

2. Audit Trail is now available via API

Previously, audit trail data could only be accessed in the web portal. From now on, audit trail entries can also be retrieved via API.

3. Adyen recurring processing model can now be configured

Previously, the recurring processing model for Adyen was predefined. From now on, users can choose the processing model in the Adyen configuration. The available options are Subscription and UnscheduledCardOnFile; the default remains Subscription.

3. E-Invoicing Improvements

• From now on, long error messages in workflow details are displayed in a popover. This makes it easier to review full Avalara error messages directly in the web portal without resizing table columns.
• Workflows in error status can now be marked as ignored in the web portal. This helps users keep the workflow overview focused on items that still require action, especially when an issue has already been resolved through a follow-up correction flow.
• From now on, additional recipient codes are available in the E-Invoicing parameters. This expands support for international E-Invoicing scenarios and allows users to select the required recipient identifiers. And the E-Invoicing parameters are also now visible on the document overview and document detail pages.
• The workflow view now includes the Avalara status alongside the ISX status.

csv Export added for additional tables

The csv Export function has been extended to include further tables. This feature is now also available in the “OPOS Clearing Run” and “Booking Entries” tables.

Changeover for API keys from roles to scopes

Previously, API keys were linked to roles, which were designed for users of the web portal. As API keys are used to access our API and are not necessarily assigned to a specific user with a role, we have revised this concept. From now on, when creating and editing API keys, roles will no longer be assigned. Instead, so-called scopes will be selected directly. For further information have a look at our API keys and Scopes Documentation.

Existing API keys remain unchanged. The roles previously assigned have been automatically converted into corresponding scopes.

Scopes define an API key’s access to specific endpoints of our API, thereby enabling more precise and transparent control of permissions. For security reasons, we recommend activating only the scopes that are actually required.

Introduced rule-based document number strategy

A new rule-based strategy allows document number assignment to be configured flexibly based on attributes such as customer type, country, billing group, or operating site, with rule priority determining which counter is applied.

Improved settlement data formatting for Adyen

Settlement data from Adyen is now formatted more consistently to prevent issues with downstream systems such as accounting tools when processing special characters.

Enabled webhook-based processing for Adyen

Adyen payment intents and settlements can now be processed via webhooks, enabling more timely and reliable data updates when configured in the Payment-Provider settings.

Webportal improvements

• On document detail and OPOS pages, payment details are now explicitly labeled as applying to future charges to avoid confusion with the originally used Customer Payment Account (CPA), which remains available in the Payment Intent.
• Settlement item properties are now displayed in settlement and transaction details in the Webportal, enabling better analysis and decision-making

Maximum quantity cap per usage

A maximum billable quantity can now be configured per pricing group for timebased usage options. If the billed quantity exceeds the configured cap, only the capped amount is charged. Free quotas are applied before the cap is evaluated.

Split invoices by original billing period

A new splitting configuration option (Original Billing Period) can be enabled per billing group. When active, items whose service periods originate from different billing periods are placed on separate invoices — even if processed within the same billing run (e.g. via late usages in carry-over mode). This allows late-rated usages to be clearly separated from the current billing period and simplifies accounting, particularly around period boundaries such as year-end. The option is disabled by default.

Query remaining correctable amount per document item

A new GET endpoint allows querying how much of a document item can still be credited. The response includes the total correctable amount (totalCorrectableAmount, i.e. the original item amount after allowances) and the remaining correctable amount (remainingCorrectableAmount) after any partial corrections already applied. This enables informed decisions on further partial credit notes.

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

1. Tax Exemptions are now also available for XRechnung and ZUGFerd invoices.
2. 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.
3. E-Invoicing parameters are now available in the Jsonata Default Mapping.
4. 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

1. 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.
2. 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.

1. Removal of sunsetted API operations

We have removed several API operations related to Purchase Items that have already reached their sunset date. This primarily affects the endpoint /v2/orders/{orderIdent}/purchaseItems and its sub‑paths:

• Add purchase item
• Retrieve purchase item
• Edit purchase item
• Cancel purchase items
• Cancel purchase items
• Add agreed deposit to purchase item
• Get agreed deposit of purchase item from a specific order
• Prepare document creation for certain items

Please refer to our guide on API Lifecycle Management as well as our earlier migration guide related to Purchase Items (published March 2023).

Additionally, the sunsetted operation "Set items on hold" for contracts has been removed. A replacement is already available: "Hold line items for contract".

These changes also include corrections to existing operation names to ensure unambiguous and self‑descriptive naming. This improves clarity and ease of use for our API consumers without any effects at runtime, but it may impact client‑side code generation and the resulting method names on your side.

2. Changes to detail pages: Introduction of cards instead of the tab overview

To improve clarity and user-friendliness, the existing tabs at the end of the detail pages will gradually be replaced by individual cards. The tab component has become too extensive, meaning that content was often only accessible by scrolling further.

In the coming sprints, the areas previously displayed in the tab overview will therefore be displayed as separate cards arranged one below the other on many detail pages. These can be expanded or collapsed as required to display information in a more targeted manner.

1. Traceability for the Entity-Ident for Entity "Users" in the audit trail

In the audit trail, the Entity-Ident-column for the ’User’ entity now allows to click on the ident to be redirected directly to the corresponding user detail page. The ident is also displayed in the detail view of an audit trail entry for the ‘User’ entity and is clickable, allowing direct navigation to the corresponding user.
In addition, the ident has been added to the ‘User’ navigation area and is displayed both in the table view and on the user detail page.

2. Traceability for the Entity "Options" in the audit trail

All create, update, and delete actions on options are now fully recorded in the Audit Trail, including changes to prices and other relevant attributes. This applies to all option types and option version updates, ensuring end-to-end traceability and compliance requirements are met.

3. Table csv export function (MVP)

An csv export function is now available for a large number of tables in the webportal. The export is started via a button at the top right of the respective table. Before starting the export, an individual file name can be specified and the desired columns for the export can be selected.

As this is an initial MVP version, the following limitations currently apply:

• A maximum of 1,000 records can be exported per export
• Only data that is directly linked to the respective entity is exported. As a result, columns may be displayed in the webportal but not be available for export

4. Deprecated: Data access API

The Data Access API endpoint is now deprecated and should no longer be used for new integrations. For document access, please migrate to the Document API endpoint, which provides the supported and future-proof interface.

5. Go to First Page Button

The pagination in the webportal is expanded to include a ‘Go to first page’ button, which allows to jump directly to the first page from any page starting at page 2

6. Exchange rate in templates

Exchange rates are now available in templates and can be printed on documents if required.

Bug Fixes

• Adjusted the OpenAPI specification to correct nullable definitions and enforce required fields where applicable, improving consistency and correctness of the API contract.

1. Webportal Improvements

The item list on the document details page now displays the quantity type in addition to the quantity value.

2. Extended Document Provisionig Configuration

Document provisioning configurations can now be activated from a defined invoice creation date, allowing more flexible, criteria-based control of document settings.

3. Enhanced API Access Control with Scopes

We’ve introduced improved access control for our APIs using OAuth2 scopes as part of our role-based access control (RBAC) model. API clients now receive tokens aligned with the specific roles and access rights assigned to their account, ensuring clearer and more granular permission handling across all API operations.

For more details, please refer to our documentation:

• https://docs.instellix.io/reference/authentication
• https://docs.instellix.io/docs/rights-and-roles.

Existing API credentials and tokens issued at runtime are not affected by this change and will continue to work as before.

To fully benefit from the improved access control model, we strongly recommend creating new API credentials that reflect the principle of least privilege, ensuring each integration has only the access it requires.

Bug Fixes

• Corrected nullable fields definitions in the OpenAPI specification. The specification now consistently reflects which fields may return null.
• Fixed a bug where the OPOS case section disappeared from the document details page after executing an OPOS case decision.

1. Show VAT ID and Company Name for B2C customers

When creating or editing a B2C customer in the web portal, the fields VAT ID and Company name can now be maintained. This allows more complete and accurate customer data management directly within the portal.

2. Show E-Mail in contract details

On the contract details page, the relevant email address now appears under ‘More information’ for invoice and shipping addresses, together with the postal address. This makes the email easily accessible without opening the contact information page.

3. Extensions Document V2 API

We have extended the Document V2 API to include deposits. If an order or contract includes deposits, these are now also output via the Document V2 API. In addition, we now also display the complete data of a customer payment account in the Document V2 API, which is helpful if this data/these fields are to be displayed in the invoice, for example.

4. Late Rated Usage Handling (Billing Group Configuration)

You can now control how late-rated usages are handled on a per Billing Group basis. You can decide whether usages that arrive after an aggregation has already been billed should trigger a correction of the previous invoice or be carried over to the next billing period instead. This reduces unnecessary credit notes and reissued invoices.

Bug Fixes

• We fixed a bug where the download button for documents in the e-invocing workflow was not working.
• We fixed a bug that caused the breadcrumb to no longer be responsive.

1. Billing Run Control per Customer (Webportal)

You can now enable or disable the billing run for individual customers directly via the web portal or via API. This allows you to perform complex corrections without generating intermediate credit notes, reducing the number of correction documents created during ongoing adjustments. When the billing run is disabled for a customer, no billing documents will be generated until the billing run is reactivated.

2. Tax Classification Update & Invoice Reissue

You can now update or add a customer’s tax classification retrospectively and reissue a corrected invoice. If a tax classification was missing or incorrect at the time of invoicing, the original invoice can be cancelled and a new invoice will be issued with taxes recalculated based on the updated classification. This ensures correct taxation and compliant invoicing without manual workarounds.

3. API Key Roles

You can now assign roles to API keys, similar to user roles. This enables consistent permission management and improved access control for API-based integrations.

4. New Notification for E-Invoicing

A new notification has been added: "E-Invoicing workflow updated". As soon as there is an update to an e-invoice that has been sent to Avalara, a notification about the update will be sent. You can subscribe to this event with your application and fetch the report immediately.

5. Customer-Level Dunning Block

Dunning blocks can now be set directly on customer level to stop all documents of a customer from being dunned, instead of managing this individually per open item. An optional note can be added, and the customer-level dunning block is visible across all OPOS cases.

6. Document Counter Start Value Configuration

The document counter configuration has been extended with a configurable start value, allowing counters and resets to begin from a defined lower limit instead of always starting at zero.

Bug Fixes

• Fixed an issue where metered usage items were missing a price calculation basis on customer invoices
• Fixed duplicate parameters in the Customer (Tax Classification) OpenAPI specification

1. Tax Exemptions
   You can now create Tax Exemptions and assign them to tax rules. This is especially important for e-invoicing, as invoices with a 0% tax rate must include a valid Tax Category Code and a Tax Exemption Reason Code to be considered compliant.

   With this feature, you can define your own Tax Exemptions and link them to existing tax rules to ensure correct tax classification and compliant invoice creation across different countries and regulations.

   This improves validation, reduces rejection rates from tax authorities, and ensures your e-invoices meet mandatory legal requirements. Learn more.

2. Expert Mode for Document Provisioning
   The Webportal now offers an Expert Mode for document provisioning configuration. When enabled, an additional JSONATA field becomes available, allowing advanced routing logic based on custom conditions.

   This enables complex use cases such as: • Routing based on invoice amount thresholds (e.g. only apply rule if amount > 250) • Industry- or region-specific routing logic

   All JSONATA conditions are evaluated within the Document Provisioning Service and are also respected by the e-invoicing workflow, ensuring consistent behavior across all document formats.

   This enhancement increases flexibility and supports advanced compliance requirements.

3. Default Jsonata Mapping for E-Invoicing Configurations
   When creating a new e-invoicing mandate, a default JSONata mapping is provided automatically. This helps you get started faster without having to build the mapping from scratch.

4. Added Business Segments to OPOS-Cases
   We added visibility of business segments in the OPOS cases to support correct account splitting and posting.

5. Billing Run Control per Customer (API only) You can now enable or disable the billing run for individual customers directly via API. This allows you to perform complex corrections without generating intermediate credit notes, reducing the number of correction documents created during ongoing adjustments. When the billing run is disabled for a customer, no billing documents will be generated until the run is reactivated.

6. Bug Fixes

   1. We fixed a bug where some required mappings for a correct ZUGFeRD invoice were missing, such as Payment Instructions (BG-16 / BT-21) and Payment Reference (BT-83).
   2. Fixed an issue where tax rules with a classification were incorrectly applied even when no valid customer tax classification existed.

7. Announcement instellix Rebranding
   As part of the rebranding of our company from Nitrobox to instellix, the webportal will undergo a rebranding in the coming weeks to reflect our new brand identity. This includes adjustments to colours, typography and visual elements to align them with our revised design and vision for the future. Stay tuned.

   1. As part of the instellix rebranding, we are also refining the user interface to make it cleaner and more intuitive. To keep frequently used actions easy to access while reducing visual clutter, we will introduce a consistent “three dots” action menu across the webportal. Actions that go beyond the standard options like viewing, editing, or deleting are no longer shown as separate buttons. Instead, these additional options can be found by clicking the three‑dots icon next to the relevant item, which opens a small menu with all available actions for that context. This helps the interface feel more modern and organized, while ensuring that all familiar actions remain easy to find.

1. Download of E-invoicing Documents within the Workflow
   All e-invoicing documents generated within the workflow can now be downloaded directly. This is especially useful when multiple invoice formats (e.g. XML, PDF) are created in parallel, giving you full visibility of all transmitted documents and formats within each workflow.
2. Advanced JSONata Configuration for E-invoicing
   Within Document Provisioning, the expert mode now supports JSONata expressions for even more granular e-invoicing configurations. This allows you to define complex conditions — for example, ensuring that only invoices with a total amount above €250 are processed as e-invoices, while lower amounts continue to be issued as PDFs. This enhancement offers maximum flexibility for implementing custom e-invoicing strategies.
3. Bug Fixes
   1. Fixed a bug that prevented 0-value rated usages from being aggregated.
   2. Fixed a bug where the recalculation of billable items failed.