Release 2025-04-22
- 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. - 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. - 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. - Improved document caching
We've improved the availability of all documents stored in Nitrobox, reducing the chances of technical delays. - 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. - 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. - Webportal
- Added rated usage aggregation details page, which is accessible from the rated usage aggregations tab on Contract details page.
- Bug Fixes
- 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
- 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! - 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. - 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. - Bugfixes
- Fixed an issue where sometimes the wrong customer payment account was displayed in orders if the customer had several accounts.
- Fixed an issue where the filter for Credit Notes did not work correctly.
- Fixed a bug where tax calculations of gross values were rarely off by one cent.
Release 2025-03-24
- 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. - 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. - 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.
- Webportal improvements
- 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.
- Customer or company name in addition to customer ident
- Plan name in addition to plan ident.
- Payment Category: You can now add and delete your payment categories.
- On the "month's closing dashboard" you will find additional reconciliation information to assist you in your tasks:
- Summary of settlement reports.
- Summary of GL account balance.
- On the GL account detail pages, you will now also find the correct total balances.
- 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.
- BugFixes
- Fixed a bug in the webportal where the option catalogs' ordering and pagination information wasn't correct.
- Fixed a bug in the webportal where filtering document dates didn't work correctly.
Release 2025-03-10
- 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. - 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. - Bugfixes
- Fixed a bug where assigning a payment did not refresh the Payment Status or the Assigned Amount section on the payment transaction page.
- 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.
- Fixed a bug where after a small rework the customer vat-id and tax number fields were no longer available to be edited
- Changes to our Customer API
- We have revised the API documentation of our Customer API to make it clearer and more precise. The following changes are included:
- 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.
- Improved schema names: Some OAS schema names have been adjusted to better indicate their usage in API requests or responses.
- General fixes: Minor inaccuracies in the documentation have been corrected.
- 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.
- We have revised the API documentation of our Customer API to make it clearer and more precise. The following changes are included:
Release 2025-02-24
- Opos Decision reversal bookings
Our flexible booking rules are also available for "Opos Case Decisions Reversals". Contact our support to enable them for you. - Payment Category
You can now configure your own payment categories, which are automatically considered in existing assignment rules. - Webportal
- We fixed a small bug that prevented setting a quantity with sub-units when creating Line Items
- Bugfixes
- We fixed a bug where a completed assigned payment might get assigned a second time.
- Fixed a bug where a payment intent response was not accepted when a settlement was already present.
Release 2025-02-10
- 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. - 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 - 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. - 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. - 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. - Customer UI/UX rework
We've improved the UI of our Customer pages to help you find information more quickly. - Bugfixes
- We fixed a bug where prebooked items had a wrong deactivation reason
- 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
-
Debtor account number on document
The debtor account number can now be displayed on the documents. -
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. -
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. -
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. -
Webportal
- Voucher application is now considered in the shown document totals in the document details view.
- We've improved on the Customer Details view, to give a more structured view on the Customers data and their adresses.
-
Bugfixes
- Fixed a bug where the document status of self-billing invoices was closed when it should still have been open.
- Fixed a bug where invoiced usages could have a rounding error, leading to quantity*unit price =! row total price
Release 2025-01-13
- 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 - 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. - 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. - Bugfixes
- Fixed a Bug where repeatedly correcting the same line item could lead to credit notes being issued with wrong values.
- 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.
- Fixed a bug in the deprecated v1 API, where credit notes couldn't be created temporarily.
Release 2024-12-16 - Merry Christmas!
-
E-Invoicing formats ZUGFeRD and X-Rechnung are now available
With E-Invoicing in Germany taking a step forward in 2025 we are happy to announce those new E-Invoicing formats being available using Nitrobox!
Under Global -> Config -> Document Provision in the webportal you can configure which format should be available in which situation (Note: This webportal config is currently only available for "Beta Preview" users, this flag will be removed in the following release). ZUGFeRD will be embedded in the pdf you know and love, while for an X-Rechnung an XML file is created as an attachment on the document. Those files can then be provided to your customers are usual.
Click here if you are interested in learning more about how Nitrobox can help you with your E-Invoicing needs. -
New Dashboards
We've added a few additional dashboards to give our users a faster overview of potential issues.- Failed Billable Items
Was there an Error when billing an item? - Failed Notifications
Were all Notifications successfully sent to an integrated system? - Failed Payment Intents
Were all payment intents successfully executed? - Unassigned Payments
Any payments that couldn't be automatically assigned? If you configure this to be a table, you can quickly assign payments directly from the dashboard. - Uncategorized Payments
Were any payments received where we couldn't assign a category? If you configure this to be a table, you can quickly categorize payments directly from the dashboard. - Failed Basware Workflows
Were there any issues transferring e-invoices to Basware? - Overdue Documents
How many of your issues documents are overdue? - Contracts expiring within (time)
Any contracts that will soon expire?
- Failed Billable Items
-
Default Dashboard
To get users started with our Dashboard we now provide a couple of interesting widgets that should help our users gain an overview of potential issues requiring attention in our system. Here is what it looks like: -
Operating site country in Tax Rules
If you run a cross-border business with different operating sites, then taxation is not just dependent on where the service was provided, but also from where it was provided. This can now be modeled using our Tax Rules by setting different rules depending on the operating site. -
Location extension
We've extended our location objects from Line Items, Allowances, and Usages by street, postal code, city, and state. They can then be printed on your document pdfs if you want to emphasize the exact location where a service was provided (for example for e-charging stations). Down the line, those values can also be used for tax purposes if your tax jurisdiction requires taxation by exact location such as in the US. -
Further Webportal enhancements
- We added an ident quick search to our webportal header. Entering any search term will suggest Customers, Plans, Contracts, Orders, and Documents that contain the term in its ident. This will allow users to navigate through our system faster.
- We extended the Order list view with aggregated agreed and actual deposit sums, and open deposits so you can more quickly see Orders where your customers have not yet paid their deposits.
-
PDF templating enhancement
- Customer Payment Account information is available to be printed on your document pdfs.
-
Bugfixes
- Resolved an issue where payment transactions displayed an incorrect status after a payment reversal followed by reassignment to another order.
- Fixed a bug where self-billing address invoices could only be corrected once.
- Fixed a bug where self-billing invoice address correction documents used the new address instead of the old.
- Fixed a bug where canceling a contract nanoseconds after creation could lead to an invoice but no cancellation credit note being issued.
-
API Updates related to operation names
We have updated our APIs to resolve issues caused by non-unique operation names (referred to as "operationId" in our OAS specification files, available here). Previously, non-unique names led to ambiguous references in our API documentation, such as links likehttps://docs.nitrobox.io/reference/get_1
, which were sequentially numbered but not guaranteed to be consistently over time.
These naming conflicts also impacted client-side code generation and resulting method names. We now provide unambiguous and self-descriptive operation names to address this for easier use and improved clarity.
Affected API versions- Payment API v2-1.68.0
- Payment Assignment API v2-0.200.0
Release 2024-12-05
- Reissue Self-Billing Invoices with Updated Address Information
You can now reissue self-billing invoices if the address information needs to be updated. This ensures that the invoice reflects accurate and up-to-date customer details without requiring manual intervention. - Enhanced Payment Intent Overview
We've added the latest payment intent response to the overview page. This allows users to quickly identify potential payment issues without needing to open the detailed view, saving time and improving troubleshooting efficiency. - View Booking Entry Properties in the Web Portal
Booking entry properties are now accessible directly in the web portal, providing greater transparency and detail about financial transactions at a glance. - Pageable API Endpoints for Key Resources
The API now includes pageable query endpoints for Customers, Orders, and Contracts. This makes it easier to handle large data sets by enabling pagination, improving performance and usability for developers. Note: The non-pageable endpoints are now deprecated and will be removed within a year. Update your integrations accordingly. - Bugfix - Allowances for Inactive Options in Contracts
Fixed an issue where users could attempt to add allowances to options that weren’t active within a contract. The system now correctly restricts this action, ensuring data integrity. - Bugfix - Dunning Aggregation Versioning
Resolved a problem where the versioning for dunning aggregation was being calculated incorrectly. This ensures accurate version tracking and consistent functionality in the dunning process. - Bugfix - Corrected Reporting Overview Pagination
Fixed a bug where the reporting overview displayed incorrect page information. Users will now see accurate pagination, improving navigation and usability.