NEW! Release notes Business Engine February 2026
This release introduces improvements across Orders, Marketplace checkout, Admin UI translations, Provisioning transparency, and API capabilities, including better separation of system vs provider-controlled cancellation reasons, legally required terms acceptance for Addons, and clearer provisioning error messaging.
Administration Portal
Orders: System cancellation reasons split from provider reasons
System-set cancellation reasons have been moved out of the provider-controlled cancellation reason field into a new field (Move, Change, SP change, Cancelled). The new field is available through the API and Reporting DB, and historical data has been migrated. Replacement orders created due to a Change are now linked, and the new order shows the replaced order number in the Parent order field.
Rename “Active from” to “Planned activation” on Objects
The Object field previously called “Active from” has been renamed to “Planned activation” to better reflect that it represents the planned activation/installation date rather than the actual activation date. The updated name is shown across the UI and has also been applied to the Object import column naming.
Deployment Portal
Deployment Portal: Object number in overview + filter
The Deployment Portal overview list has been enhanced to show the Object number and to support filtering by Object number for easier navigation and identification.
End Customer Billing
Auto-suspension for non-paying customers
Support has been added for auto-suspension of non-paying customers, with the ability to enable or disable automation, configure the number of days after due date before auto-pause, and exclude individual customers. The suspension flow continues to use the existing mechanism (removing NC and L2), and auto-paused customers are also auto-activated through the current flow (when due balance reaches 0).
Provisioning
Provisioning: Separate ONT missing vs uplink missing messaging
Provisioning translations have been updated to better differentiate between ONT missing and uplink missing scenarios. This replaces the previous generic messaging and provides clearer information when the workflow status is Connection required and provisioning state is Error.
Provisioning: Show what configuration is missing
The provisioning configuration missing banner has been improved to provide clearer guidance by specifying whether mapping is missing, the service type is not configured, or the speed is not available. This reduces ambiguity for internal troubleshooting.
Marketplace
Marketplace: Passwordless authentication (optional)
Marketplace login can now be configured to use passwordless authentication. When this setting is enabled, users log in via an email containing a secure login link instead of entering a password. If the setting is disabled, Marketplace continues to use password-based login as before.
Marketplace: Service Terms for Addons
Marketplace checkout now supports a mandatory Service Terms acceptance checkbox when a selected add-on is marked as requiring terms (including VoIP). Customers cannot proceed unless the checkbox is checked, and it is only shown when applicable.
API
API: Wholesale Invoice line items
The API has been extended to support wholesale invoicing, including listing wholesale invoices, retrieving detailed information for a specific wholesale invoice, and creating invoice rows on existing wholesale invoices. This enables downstream integrations to access wholesale invoice data and allows operators and automated systems to add invoice rows and bill additional charges to service providers without manual handling in the UI.
API: Prices in Order create + Next billing date
Order creation via the API now supports submitting detailed pricing and billing information, including date ranges, price type, price, add-on references, billing information, descriptions, as well as next billing date and activation date. This provides full pricing and billing transparency already at order creation and enables external systems to work with accurate pricing data immediately.
API: Order Contract pricing via Order API
Order Contract pricing information is now exposed through the Order API to support use cases such as sending SMS notifications when new orders are created. This enables retrieval of both the service price and the promotion-adjusted price before any invoice exists.
Integrations
Pingen Integration: Optional customer letter
A new integration with Pingen has been introduced to enable sending physical letters to customers. Letters are sent only when explicitly triggered, for example via a Send letter action, allowing more flexible handling of customer communications. This supports scenarios that require formal written communication, such as sending installation preparation instructions.