Changelog
Platform OverviewDemoContactImprint

Release 2025-05-19

  1. Price Calculation Basis
    We now provide additional information on how the billed values were calculated. For example, for recurring elements, you can now view the base values for pro rata calculations in the Billable Item overview. Additionally, via API, you can also find more details for Usage calculation, which will be added to the webportal as well in the coming weeks.
  2. Billable Item Recalculation Error
    Should billable item recalculation occur (for example, if the tax or performance location was changed that might impact pricing or taxation), but encounter an error, the billable item will now have a separate error status and new actions to retry the recalculation. A billable item where the recalculation failed will not be invoiced.
  3. Webportal improvements:
    1. Price adaptation values applicable from a date can now be deleted, for example, if the value changed on the index or in case you misconfigured.
    2. The option selection in the "add usages modal" is now sorted alphabetically, with the first option being automatically selected for easier and quicker adding of usages manually.
    3. On the payment intent details page, the status and the message of the latest payment intent response are now directly visible.
    4. Ther payment intents and payment intent task pages have been merged to provide a more holistic view on each attempted payment intent.
    5. You will find two new widgets on the new payment intents page: planned and failed payment intents which provide more information on the processing. Additional detail pages are available.
    6. The email of your customers is now also available as a column in the contracts overview table.
    7. Additional small UI improvements were made about the size of information cards on several pages.
  4. Bug Fixes
    1. Fixed a bug where monetary amounts of 100 million and larger couldn't be processed completely.
  5. Removal of deprecated APIs
    We've removed several of our depcreated APIs that had reached their sunset date. We ensured those APIs haven't been used for the last few months.
    Namely
    1. /v2/orders/{orderIdent}/depositInvoice/purchaseItem
    2. /v2/orders/{orderIdent}/prepareInvoice
    3. /v2/contracts/{contractId}/prepareInvoice
    4. /v2/invoices/{invoiceIdent}/actions/reissue
    5. /v2/orders/{orderIdent}/cancel
    6. /v2/contracts/{contractId}/cancel
    7. /v2/contracts/{contractIdent}/terminateContract
    8. /v2/contracts/{contractId}/terminateContractId

Release 2025-05-06

  1. Rated Usage Aggregations
    We've added detailed views for Rated Usage Aggregations in the Webportal. With this release, it's now easier to identify aggregations that require manual action—for example, those that need to be closed again after late usage data has arrived. This closing action can now also be performed directly via the Webportal.
  2. Multi-Phase Plan Option Update
    We've removed a constraint preventing the update of Options belonging to Multi-Phase Plans.
  3. Bugfixes
    1. Fixed an issue where certain properties in our API schema were unintentionally no longer marked as required, due to a problem introduced by a third-party library update.
    2. Fixed a Bug where the auto-renewal date wasn't recalculated after a renewal if the contract's underlying plan didn't have any recurring options.
  4. Changes to our Billing API
    1. We have removed several unused operations from our Billing API specification as part of a planned deprecation. While these operations are no longer included in the published API schema, they remain available at runtime for a limited time before being fully sunsetted. For more details and migration guidance, please refer to our API Migration Guide.
  5. Webportal improvements:
    1. CreatedAt and lastModifiedAt information can now be found at the bottom right of all details page that support this information.
    2. Order views have been redesigned to enhance the user experience.
    3. "Add Usage" window was restructured to improve the layout.
    4. Payment has received a small overhaul to improve UI/UX
    5. Improved the Plan creation flow to offer a tailored experience based on whether you're creating a single-phase or multi-phase plan.
    6. The plan column in the contract can now be filtered.
    7. Added informative tooltips to the Order and Contract update actions to help users better understand how these actions behave.
    8. The Billable Item detail page for recurring elements now includes a "Price Calculation Basis" section, providing additional insight into how the price was determined. Particularly useful in scenarios like pro rata calculations.
    9. Fixed a bug
      1. where Users were sometimes not shown
      2. where document numbers with a slash "/" in them didn't work properly.
      3. where tilde (~) character in idents caused problems in certain entities.

Release 2025-04-22

  1. Tax-Provider determination
    The tax providers can now be additionally configured based on the billing group. This enables more flexible tax handling for multi-country, multi-billing-groups, and multi-provider setups.
  2. Payment Intent Task now only created for document-based OPOS cases
    If an OPOS case is reopened by external factors, such as a direct refund with your PSP, then we won't create new payment intents for the now again open position. This helps to avoid unintended payment retries and ensures better control over automated collections.
  3. Improved visibility for Not-Assignable payment transactions
    Transactions that cannot be assigned (e.g., cash pool transactions) now appear in a different status color to visually distinguish them from actual unassigned payments. This reduces confusion and helps finance teams identify real unassigned transactions faster.
  4. Improved document caching
    We've improved the availability of all documents stored in Nitrobox, reducing the chances of technical delays.
  5. Adding Rated Usage Options for running contracts now also available on earlier periods
    Previously, when adding new Rated Usages Options to existing contracts, the option could only be for later billing periods and not for the past. This is now improve,d so the new options can also be used for past rated usages.
  6. Configurable Debtor Account Number
    You can now easily increase the debtor account number range start, which will help to ensure separate GL/Debtor Account number ranges.
  7. Webportal
    1. Added rated usage aggregation details page, which is accessible from the rated usage aggregations tab on Contract details page.
  8. Bug Fixes
    1. Fixed a bug where the credit item after the termination of a contract, followed by a complete cancellation, could have the wrong service period (while its value still being correctly calculated).

Release 2025-04-07

  1. Multi-Party Billing
    We've released our Multi-Party Billing MVP! This will allow you to automatically share end customer revenue with your partners or your parent company.
    Find out more about it here.
    Or join our upcoming webinar!
  2. Retry function for suspended payments
    You can now reactivate suspended payments (e.g., chargebacks) directly within an OPOS case.
    Use the new “Enable Automatic Payment Collection” button to retry payment using the same or a different customer payment account. You can also define a new due date.
    The payment collection status is now visible in OPOS case details and can be used as a search filter in the Webportal.
  3. Update Payment Intent Task
    It’s now possible to change the customer payment account and due date for orders or contracts where the document is already created but the charge hasn’t been processed yet.
    You can edit or cancel Payment Intent Tasks via the overview or detail page, as long as they haven’t been executed.
    To simplify navigation, a new “Payment Intent Tasks” tab has been added to the document and OPOS case detail views, giving you direct access without having to search manually.
  4. Bugfixes
    1. Fixed an issue where sometimes the wrong customer payment account was displayed in orders if the customer had several accounts.
    2. Fixed an issue where the filter for Credit Notes did not work correctly.
    3. Fixed a bug where tax calculations of gross values were rarely off by one cent.

Release 2025-03-24

  1. Contract modification
    You can now modify prices on your contracts. Previously, if you wanted to offer an existing product with different prices to one specific customer, you would've needed to create new options and new plans, creating an unnecessary overhead. Now you can specify a different price during contract creation and keep them updated separately!
    This is especially handy in a B2B environment, where your salespeople negotiate the prices individually and don't want to be constrained by one-size-fits-all pricing.
    You can find more about it here.
  2. Added automatic price adaptation for contracts
    You can now link contract prices to inflation or other indexes, ensuring they automatically adjust over time. This helps protect your long-term contracts against value loss from inflation and reduces the need for manual price updates. Especially in times of volatile inflation, this feature helps keep your pricing aligned with market conditions.
    You can find out more about it here.
  3. Avalara AvaTax Improvements
    We’ve made several enhancements to our Avalara integration to improve transparency, flexibility, and usability:
    • New Avalara Integration Guide: A comprehensive step-by-step guide is now available to help with setup and configuration.
    • User Interface: A dedicated UI has been added to view Avalara-related data directly within the platform.
    • Flexible Configuration Options: We’ve introduced more granular configuration options to match your tax calculation needs.
    • Logging of Requests and Responses: All Avalara requests and responses are now logged to support easier debugging and traceability.
    • Tax Exemption Code Handling: Avalara exemption codes can now be added for a line item and passed along in tax requests.
  4. Webportal improvements
    1. On the Contracts overview, you will now find more helpful information to identify the contracts instead of the various idents. We plan to roll out this enhancement on more and more tables in the coming weeks, so you will have to work less with the more technical idents.
      1. Customer or company name in addition to customer ident
      2. Plan name in addition to plan ident.
    2. Payment Category: You can now add and delete your payment categories.
    3. On the "month's closing dashboard" you will find additional reconciliation information to assist you in your tasks:
      1. Summary of settlement reports.
      2. Summary of GL account balance.
    4. On the GL account detail pages, you will now also find the correct total balances.
  5. BugFixes
    1. Fixed a bug in the webportal where the option catalogs' ordering and pagination information wasn't correct.
    2. Fixed a bug in the webportal where filtering document dates didn't work correctly.

Release 2025-03-10

  1. Dunning block
    The dunning block feature allows users to pause any dunning for a specific document or an opos case. This can come in handy when you've reached out to the customer and are in clarification, without wanting to issue reminders.
    When adding a Dunning Block, you can also add a note to remind you why it was set.
  2. Type restriction for file upload
    We've limited the type of files you can upload using for example our Contracts or Orders attachment feature. This aims to reduce the chance that malicious files can be uploaded and later downloaded by your users. See File type whitelisting for more informations.
  3. Bugfixes
    1. Fixed a bug where assigning a payment did not refresh the Payment Status or the Assigned Amount section on the payment transaction page.
    2. Fixed a bug where the incorrect customer payment account was displayed on the orders and invoices if a customer had more than two payment accounts.
    3. Fixed a bug where after a small rework the customer vat-id and tax number fields were no longer available to be edited
  4. Changes to our Customer API
    1. We have revised the API documentation of our Customer API to make it clearer and more precise. The following changes are included:
      1. Correction and refinement of schema definitions: Specifications have been added or refined including the classification of required and optional fields to accurately reflect the API's actual behavior.
      2. Improved schema names: Some OAS schema names have been adjusted to better indicate their usage in API requests or responses.
      3. General fixes: Minor inaccuracies in the documentation have been corrected.
    2. 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.

Release 2025-02-24

  1. Opos Decision reversal bookings
    Our flexible booking rules are also available for "Opos Case Decisions Reversals". Contact our support to enable them for you.
  2. Payment Category
    You can now configure your own payment categories, which are automatically considered in existing assignment rules.
  3. Webportal
    1. We fixed a small bug that prevented setting a quantity with sub-units when creating Line Items
  4. Bugfixes
    1. We fixed a bug where a completed assigned payment might get assigned a second time.
    2. Fixed a bug where a payment intent response was not accepted when a settlement was already present.

Release 2025-02-10

  1. Currency rounding option
    We've enabled flexible currency rounding strategies that allow you to configure to which significant digits our system will round values of items. This can be handy if you have business in countries where best practices deviate from the official ISO 4217 standard, which we usually use as basis for any rounding questions.
    A practical example would be the Hungarian HUF, which officially supports 2 decimal values (fillér). However, the practical use has mostly discontinued in 1999 and payment providers such as PayPal don't support using fillér at all.
    Note: Unit Prices are not affected by this rounding.
  2. Opos Case decision search enabled
    You can now search for Opos Decisions in general using our API. This allows for easy retrieval of all Opos Cases of a given period, for example, in order to synchronize the information to your ledger or other systems.
    Find the API here
  3. Tax Rules extension - Invoice address country
    You can now also use the customer's invoice address country to more precisely determine the correct tax for your use case.
  4. Chargeback Handling
    We've removed automatic retries should a payment be charged back. As those cases are often related to fraud or disputes, automatic retries would fail while still incurring additional PSPs costs in some instances.
  5. Codice Destinatario for italian e-Invoicing
    If you are using Nitrobox as e-Invoicing solution in Italy, you can now provide the Codice Destinatario to improve the chance your invoices get routed to the correct customer via the Italian SDI system. While normal addresses are usually sufficient, the Codice Destinatario improves reliability.
  6. Customer UI/UX rework
    We've improved the UI of our Customer pages to help you find information more quickly.
  7. Bugfixes
    1. We fixed a bug where prebooked items had a wrong deactivation reason
  8. Beta preview
    If you are a power user looking for the latest feature, you can get a peek at a "month's closing dashboard" in development that aims to improve your accounts live by providing important monthly KPIs such as document totals or sum of Opos Decisions taken.
    You can find it under Accounting -> Month Closing Dashboard.

Release 2025-01-27

  1. Debtor account number on document
    The debtor account number can now be displayed on the documents.

  2. E-Invoicing parameters
    In preparation for the e-invoicing requirements, we have added e-invoicing parameters for customers. In the first step, the recipient code type and the recipient code can now be provided. This ensures that e.g. Basware can deliver the invoice to the correct invoice recipient.

  3. Automated assignment of overpayments for orders
    From now on, you can configure our payment matching rules to automatically assign matching overpayments to orders as well.

  4. Contract Timeline
    Our Contract detail view now offers a better visual representation of key dates of your customers contract. This should make it easier to see important information at a glimpse.

  5. Webportal

    1. Voucher application is now considered in the shown document totals in the document details view.
    2. We've improved on the Customer Details view, to give a more structured view on the Customers data and their adresses.

  6. Bugfixes

    1. Fixed a bug where the document status of self-billing invoices was closed when it should still have been open.
    2. Fixed a bug where invoiced usages could have a rounding error, leading to quantity*unit price =! row total price

Release 2025-01-13

  1. Integration Voucher Solution with Talon.One
    We have integrated the Promotion Engine from our partner Talon.One. This feature allows you to efficiently run campaigns and helps manage vouchers, directly improving customer loyalty and satisfaction through flexible voucher options. NBX will automatically consider relevant vouchers during the billing cycle, based on the customer or contract. Additionally, voucher amounts will be considered for any credit notes or invoice corrections.
    You can read more about it here
  2. E-Invoicing Config Update
    We've removed the Beta-flag from the E-Invoicing Configuration, so non-beta users can also freely configure our product to their E-Invoicing needs.
  3. Contract termination before reaching the start date
    We now allow the termination of contracts even before they have started. This will now lead to the contract ending at the end of the first period, previously we disallowed this case.
  4. Bugfixes
    1. Fixed a Bug where repeatedly correcting the same line item could lead to credit notes being issued with wrong values.
    2. Fixed a Bug where we allowed multiple option allowances to be created before the start of the contract, leading to unexpected behavior. Currently, we only support one Option allowance per Contract per Option at a time.
    3. Fixed a bug in the deprecated v1 API, where credit notes couldn't be created temporarily.