Changelog
Platform OverviewDemoContactImprint

Release 2024-12-16 - Merry Christmas!

2 days ago by Daniel Hofmeister

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

  2. New Dashboards
    We've added a few additional dashboards to give our users a faster overview of potential issues.

    1. Failed Billable Items
      Was there an Error when billing an item?
    2. Failed Notifications
      Were all Notifications successfully sent to an integrated system?
    3. Failed Payment Intents
      Were all payment intents successfully executed?
    4. 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.
    5. 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.
    6. Failed Basware Workflows
      Were there any issues transferring e-invoices to Basware?
    7. Overdue Documents
      How many of your issues documents are overdue?
    8. Contracts expiring within (time)
      Any contracts that will soon expire?

  3. 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:

  4. 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.

  5. 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.

  6. Further Webportal enhancements

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

  7. PDF templating enhancement

    1. Customer Payment Account information is available to be printed on your document pdfs.

  8. Bugfixes

    1. Resolved an issue where payment transactions displayed an incorrect status after a payment reversal followed by reassignment to another order.
    2. Fixed a bug where self-billing address invoices could only be corrected once.
    3. Fixed a bug where self-billing invoice address correction documents used the new address instead of the old.
    4. Fixed a bug where canceling a contract nanoseconds after creation could lead to an invoice but no cancellation credit note being issued.

  9. 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 like https://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

    1. Payment API v2-1.68.0
    2. Payment Assignment API v2-0.200.0

Release 2024-12-05

16 days ago by Daniel Hofmeister
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.

Release 2024-10-07

3 months ago by Kathrin Roth
  • We've introduced a user tracking tool on our webportal to optimize our product. See our webportals privacy policy for details https://docs.nitrobox.io/docs/privacy-policy
  • You can now configure our payment matching rules to also automatically assign matching overpayments. While this increases the share of payments that will be automatically assigned, it also slightly raises the risk of wrong assignments. It can be very helpful for certain setup scenarios, so we invite you to evaluate this feature for your use case.
  • We added new Opos Case decision types (cash discount, bank fee, and external closed) to classify and manage various financial adjustments and improve accuracy in financial reporting.
  • You can now also reverse Opos Case decisions via our webportal. Previously, this could only be reversed via the API.
  • You can now jump directly from a document to the related Opos Case in our webportal, saving you a few clicks.
  • We've added endpoints for some entities that didn't have a paged GET view, namely Customers & Addresses as well as Orders and Contracts.
  • If you use Contract price determination by performance location, we no longer validate that the tax location of the contract matches a price as well. You do need to have a tax rule configured however.

Release 2024-09-23

3 months ago by Kathrin Roth
  • We have implemented a new functionality that allows us to print the billing period directly on the invoice document. This provides customers with a clear overview of the period covered by the invoice, enhancing transparency and clarity in the billing process.
  • A new feature that enables the automated clearing of small outstanding amounts through a clearing run has been implemented. This eliminates the need for accountants to manually process open item decisions for minor discrepancies, significantly saving time and streamlining the accounting workflow.
  • If you use Orders deposits as well as Order Allowances then those Allowances will now be considered when distributing the expected deposit on the Line Items. This allows a more accurate representation of the tax situation.
  • Improved Notification overview response times.
  • Fixed a bug where a "default" region would be set on line items on occasion.

Release 2024-09-09

3 months ago by Daniel Hofmeister
  • We've enabled our new rights and roles system that will allow you to provide better matching roles to our users than ever before. You can view the new roles when creating new users or managing existing ones, where you will also find more information on what each role contains.
    Existing users retain their current rights, but we recommend you migrate your users to the new roles. We plan to remove the old roles within a year, so Users not migrated in that time might lose access.
  • Billing Group and Business Segment are now available for considering during deposit created booking rules, allowing for more specialized bookings.
  • Fixed a bug where during Plan creation you couldn't switch between billing timing with delay and without.
  • Fixed a bug where Contracts couldn't be created for Plans with quarterly billing and autorenewal.

Release 2024-08-26

4 months ago by Kathrin Roth
  • We've enabled a new feature that validates the VAT-ID of your B2B customers. This can be necessary if you engage in cross-border business and use the reverse-charge system. As reverse-charge is only valid for business customers that are VAT registered in their own country, their VAT-ID being valid is very important and now our system can ensure this validity.
    • If you want this feature enabled on our tenant please speak to your professional services contact.
    • When enabled, you can see the result of the VAT-ID validation in our webportal.
    • We also archive the validation result with our certified archiving provider together with each document created.
  • You can now configure our payment matching rules to also automatically assign matching underpayments. While this increases the share of payments that will be automatically assigned, it also slightly raises the risk of wrong assignments. It can be very helpful for certain setup scenarios, so we invite you to evaluate this feature for your use case. Feel free to reach out to our support team to help you decide if you should enable this feature or not.
  • Using our webportal, you can now update the payment terms of Orders and Contracts in case you have renegotiated those with our customer.

Release 2024-08-12

5 months ago by Daniel Hofmeister
  • We have finally published our v2 document API, you can view it here: https://docs.nitrobox.io/reference/createinvoice_1
    • This is helpful for integrations that provide entire documents to our system instead of interacting with our Orders and Contracts. This can be the case if you generate for example invoices (with or without the pdfs) in your system and need to generate invoice numbers in your system, but are still looking to use our products' payment and accounts receivable management capabilities.
    • Note: You can define for each billing group if you want to handle the billing externally (using the document API) or internally (using our Orders and Contracts). See more in our documentation about Billing Groups: https://docs.nitrobox.io/docs/billing-groups
  • You can now open Booking Periods manually. While they are created automatically as well when a new financial transaction takes place in a new Booking Period, especially when setting up a new tenant creating a BookingPeriod manually to define an accounting baseline can be helpful.
  • Fixed a bug where in the webportal, filtering with equals sometimes returned wrong results.

Release 2024-07-29

5 months ago by Daniel Hofmeister
  • We've adapted the billing behavior of line items added during contract creation. For contracts billed at interval start, line Items provided during contract creation will now be billed with the first invoice. Any Line Item added later will still be billed with the following invoice. This behavior change allows you to invoice your customer's Line Items even earlier without producing additional documents.
  • If you are using our API to close OPOS cases, you don't have to send the amount anymore. If left empty, the amount will be automatically the leftover amount of the OPOS case. This should make any integration a lot easier if you are just looking to close the opos case to prevent for example dunning.
  • Dunning can now be set up in a way that doesn't create any dunning letters on our end. This can be helpful if you already have a dunning letter creation functionality in our ERP for example. In this case, you can just listen to dunning status changes from us and then create and distribute the dunning letters yourself.
  • You can now manage payment assignment rules via our Webportal, for detailed documentation feel free to check out https://docs.nitrobox.io/docs/matching-rules.
  • Fixed a bug where trying to change the business segment while copying a plan didn't work.
  • Deprecation and Sunsetting
    • Most of our endpoints marked as deprecated now provide the official deprecation and sunset date. They will be removed by 2025-07-30 at the latest.

Release 2024-07-03

6 months ago by Daniel Hofmeister
  • Features
    • Contracts can now receive Usage Add-ons. So if you have new Usage based products you can enable them on existing contracts as well. Previously this would've required a new contract.
    • Fixed a bug where multiple contract-expired events were sent out when the contract was updated after it expired.
    • Our reports have been extended to also contain an ident. This makes it easier to know which reports you have already fetched.
    • To have a better overview of the health status per contract, the dunning status of a contract can now be requested via our API (soon also available via our Webportal). You can also be informed via notification if this status changes, named "Dunning status aggregation updated".
    • Fixed a bug where manual opos clearing during payment assignment sometimes did not work.
  • API Deprecation and Sunsetting
    • We have updated and made more transparent our API deprecation and sunsetting policy, you can read up on it here: https://docs.nitrobox.io/reference/api-lifecycle-versioning
    • We are extending all of our already deprecated API endpoints with the information specified in our policy, one example can be viewed for Purchase Items here. Note: The sunsetting date for this specific endpoint is in the past already which is an exceptional case. The purchase item endpoints were officially deprecated over a year ago (see our migration guide), but it wasn't as transparent in our API documentation as we wished. While updating our policy and making this much more visible in our API documentation, we want to finally ensure this endpoint is not used anymore before actually removing it. For new deprecations, such care will not be taken and deprecated endpoints will be available until the sunset date communicated at most.

Release 2024-06-17

6 months ago by Daniel Hofmeister
  • OAuth security definition is now part of every OpenAPI specification file, see also https://docs.nitrobox.io/reference/authentication
  • Contract locations can now be updated with our webportal. This comes in handy when a customer moves to a different country and should thus be billed different amounts or be taxed differently.
  • A new notification has been added: "Report created". You can subscribe to this event with your application and fetch the report immediately.
  • Fixed a bug where assigning a debit transaction was not possible.