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.

📘

Info: The next deployment will occur on 2025-12-04 to comply with our "No deployment within 3 days of months end" policy.

1. Payment Provider Adyen You can now set up and manage your Adyen integration without developer support – including activation, deactivation, and management of payment retry logic directly via the Nitrobox Webportal. This makes it easier to adjust payment behavior for different use cases, such as e-commerce or subscriptions. Webhook configuration will follow shortly.
2. Accessible Documents All documents can now be generated as accessible PDFs. This feature helps businesses comply with digital accessibility regulations (e.g. the EU Accessibility Act / German BFSG). Please get in touch with your Professional Service representative if you are interested in enabling this feature.
3. Customer Tax Classification
   You can now define custom customer tax classifications, assign them to customers, and use them within tax rules. This enables more advanced tax scenarios, such as fiscal unities or reseller relationships. Classifications can also include an end date, enabling time-bound assignments automatically.
4. Webportal
   1. Internationalization Enhancements As part of our ongoing internationalization efforts, we’ve improved translations across multiple areas of the platform — including the DataGrid component to ensure consistent language handling across the interface.
5. Bug Fixes
   1. Refunds now correctly display the original Customer Payment Account, even if it has been overwritten in the meantime. The refund itself was always processed to the original account – this was only a display issue in the web portal.
6. Upcoming API Changes
   We would like to inform you about upcoming changes to deprecated endpoints that will be removed in the upcoming (2025-11-17) deployment in accordance with our sunsetting policy https://docs.nitrobox.io/reference/api-lifecycle-versioning.
   1. We will be removing the deprecated 'Purchase Item' endpoints from our Contract APIs that are part of the Billing API. Line Item endpoints replaced this feature.
   2. We will be hiding the deprecated 'Purchase Item' endpoints from our Orders API spec that are part of the Billing API. We aim to remove them by March 2026. Line Item endpoints replaced this feature.
   3. In the request and responses of both Orders and Contracts, the Purchase Items will be hidden in the API spec from now on.

We deployed a small hotfix to address several API description (OAS) issues that were brought to our attention, preventing some clients from easily generating client code from our API specification.

1. Data Access API We have revised the API documentation of our Data Access API to make it clearer and more precise. The following changes are included:
   1. Correction and extension of payment methods.
2. Changes to our Invoice API General fixes: Minor inaccuracies in the documentation have been corrected.
   1. The property paymentInformation is now documented as nullable

Important: The API functionality remains unchanged. Paths and payloads have not been modified - this update affects the documentation only. Minor adjustments to client side generated code may be necessary. If you have any questions, our support team is available to assist you.

• Batch Payments
  Nitrobox now supports Batch Payments, making it easier to assign a single payment to multiple invoices or credit notes.Batch Payments can be processed manually in the web portal, via API, or automatically by uploading a remittance advice, which is matched to the corresponding invoices. For more information, click here.
• PaymentIntentResult-Notification extended with retry ident The PaymentIntentResult Notification has been extended to include new fields called RetryIdent and Final-Retry-Flag. This field allows you to identify whether a failed payment attempt belongs to a specific retry cycle and whether it represents the final retry for that Payment Intent. With this enhancement, payment owners can now monitor failed payment attempts more accurately and take appropriate actions — for example, automatically canceling affected contracts when all retries have failed.
• Accessible Documents To ensure compliance with legal accessibility requirements, Nitrobox now supports the creation of accessible documents. If you require this functionality, please contact your Professional Services representative for more information and enablement.
• Graphical Contract Lifecycle To provide a clearer overview of contracts, Nitrobox now offers a graphical timeline visualization for contracts with monthly billing. The timeline displays all related documents and payments in chronological order. Different icons and colors indicate the current status of each document and whether it represents a payment or payout. This enhancement allows to understand the entire contract history at a glance — without having to navigate through multiple documents.

1. Payment Category in Settlements The Settlement Report no longer displays the payment category. This field never had a functional purpose, but could lead to confusion.
2. Extension of the Payment-Intent-Result-Notification We have extended the Payment-Intent-Result-Notification to include the retry ident and to indicate whether it's the final retry of a failed payment intent. This helps make follow-up decisions, such as terminating a contract after the last retry attempt.
3. Calculation Basis on Templates The calculation basis of Billable Items for recurring options is now available to be used in your PDF templates as well. Now you could show your customers why they only need to pay a pro-rated amount in the first month, for example.
4. Batch Payment Assignment We have introduced the new Batch Payment Assignment feature, allowing a single payment (e.g. a bank transfer) to be assigned to multiple invoices or credit notes at once. Assignments can be done either manually or via CSV import, providing flexibility for different workflows. All further details can be found at https://docs.nitrobox.io/docs/batch-payment-assignment.
5. Performance Status We've added a new status to our contracts, API only for now. It can show you at a glance and allows for quick filtering to see if a contract hasn't yet started, is in its performance phase is no longer being serviced, without having to create difficult search queries checking against the start and end date.
6. Bug Fixes
   1. We fixed a bug where some applicablePurchaseItemTypes were missing in our API documentation.
   2. We fixed a bug where multi-tax rates were displayed incorrectly in the invoice details. The tax rate is now shown as the cumulative value of all applicable taxes. Previously, only the value of the first multi-tax was displayed.
   3. Fixed a bug where the credit billable item endpoint was shown as deprecated

Due to an internal software update by the third-party provider we use to publicly publish our APIs, the way customers access the Open API specification (OAS) files will change slightly. The URL used to retrieve each of the specification files will be updated — transitioning from a purely technical identifier to a human-readable identifier and file name. The structure and content of the specification files remain unchanged.

The entry point for all OAS files remains unchanged as well at https://docs.nitrobox.io/v2/reference/openapi-specification-oas.

Please ensure that any integrations or tools relying on the previous URLs are updated accordingly for continued access and processing of these files. This change will take effect on Wednesday, 24th of September.

For your convenience, we have listed the mapping of changes for each API below:

Example

https://docs.nitrobox.io/v2/openapi/60b8f92103850600379a144c

will change to

https://docs.nitrobox.io/v2/openapi/customer-api.json

1. E-Invoicing Improvements The Avalara mapping configuration now only displays companies and billing countries activated in the Avalara portal, which prevents accidental selection of unconfigured countries.
2. Extended self-managed payment methods We have significantly expanded support for externally managed payment methods in orders and contracts. Instead of the previous 16 methods, around 80 additional payment methods are now available and can be printed on documents. See the full list of supported self-managed payment methods here.
3. Performance improvements
   1. We improved the performance of our outgoing Notifications.
   2. We improved the performance in retrieving contracts by a significant margin.
4. Bug fixes
   1. We fixed a bug where, after reverting a partial or complete assignment, the status incorrectly remained ‘Partial Assigned’ instead of changing back to ‘Unassigned’.
   2. Fixed a bug where Options in status DRAFT that were no yet being used in any contract couldn't be deleted.
   
   

1. Bug Fixes
   1. Fixed a bug where sometimes a dunning document was not sent to the archive solution.
   2. Fixed a bug where searching and sorting for the new seller entity didn't adhere to our API standards

1. Avalara E-Invoicing
   We have made several improvements to Avalara E-Invoicing integration in Nitrobox, making it easier to manage credentials, configurations, and documents directly in the web portal:
   • You can now enter Avalara ELR credentials directly in the web portal and configure all Avalara settings there.
   • The document workflow has been extended so that PDF or XML files can be downloaded directly from a workflow step – no separate Avalara login is required anymore
   • In addition, we have implemented a validation that immediately checks the JSONata mapping for errors, helping to identify and fix issues faster.
2. Credit Card Type in Customer Payment Account
   You can now specify the credit card type used by your customers in the customer payment account. This can be used, for example, to print more specific information on your documents.
3. Cancellation of Payment Intents
   It is now possible to cancel payment intents before they are processed. This allows you to stop the transaction entirely, rather than charging the customer and then issuing a refund. The change helps avoid unnecessary payment processing steps, improves the overall customer experience, and reduces PSP costs.
4. API
   • You can now provide a sellerOperatingSiteIdent in the document v2 API. This allows you to specify a different seller on a document than your tenant, allowing for a basic marketplace setup.
   • We've added a new endpoint where invoiced recurring and one-time option items can be corrected. This should help handle support cases more easily. You can find the endpoint here: https://docs.nitrobox.io/reference/correctbillableitem
     We aim to soon enable this feature in the web portal as well.
   • Our notifications have been extended to include the timestamp when an API call to your system is being made. This can help you order and process the notifications in the correct order.
5. Bug Fixes
   • Fixed an issue in the voucher process via TalonOne where the character “/” in the documentIdent was not handled correctly. The system now fully supports this character, ensuring smoother voucher creation and redemption.
   • Fixed a bug where optional usage options were sometimes not displayed in the contract details page.
   • Fixed a bug where picking a different language during order creation didn't work correctly.
   • Fixed a bug where 0-value rated usages could not be sent via API.
6. Webportal
   • You can now change the correction mode (item-based vs document-based) on billing group level in the UI.
   • When adding new usage options to plans you can decide if you want to enable them automatically for all existing contracts or if you want to enable them later on a per contract basis.