This release was a big bigger - Please click above to see the detailed view of what has changed

• We added contract migration support! If you already have a running subscription business and want NBX to start billing your subscriptions within their life cycle you can now specify a "Billing Start Date" and NBX will take care of all billing periods after that date.
• We introduced a new "Dunning archived" notification you can subscribe to. This will inform you whenever an invoice has surpassed the next dunning level and a pdf has been archived that can be sent to your customer.
• Various webportal improvements:
  • Improved some response messages in our webportal, like user deletion messages.
  • We renamed "amount" to "quantity" where appropriate to clarify which values are about the number of things and not the monetary amount.
  • Improved the "create Usage Option" user experience. You now need fewer steps to correctly create such an Option.

• You can now add additional non-mandatory Options to Plans already in use.
  For example, let's say you have a mobile phone plan with a fixed 9,99€/month base fee with an Option for your customers to book an additional +5GB/month data for 1,99€/month.
  Now you can offer an additional +10GB/month for 2,99€/month for the same plan with your customers being able to pick either one (or none) - previously you would've needed to create a new Plan for this to work.
• It is now also possible to change the payment details of Contracts and Orders, allowing your customers to change payment methods. Do your customers start using your great product so much that paying via CC starts posing a challenge due to fees? Ask them to transfer the money instead via wire transfer.
• Fixed a bug where an overpayment of an invoice didn't correctly display its OPOS status.

• Usages that have not been billed yet can now be deleted from the system so you can comfortably remove wrongly sent Usages.
• We increased Usage Billing Transparency. You can now more easily figure out on which document a given Usage was billed.
• Terminated contracts can now also be canceled! Does a customer of yours want to terminate their contract but is still within the revocation period, and you'd rather cancel the contract? This is easily accomplished now. See also https://docs.nitrobox.io/docs/termination-cancellation-and-revocation
• We've made the payment settlement reports available via webportal, so you can easily browse individual reports and their associated settlements.

• You can now provide a "notice day" when regularly terminating contracts. This allows you to provide a date from which to calculate the actual end date of the contract.
• When setting up your Plan you can now specify a minimum Quantity of two and more for your subscriptions and one-time options. As an example, say your business is about selling subscriptions to lend out bikes to local distributors, but you don't want to specify that each of your customers signs a contract of at least 100 bike subscriptions, you can now enforce that in the billing in Nitrobox as well with this extension.

• Order allowances can now also be updated and deleted.
• Users can now configure a "Contract Expired" notification, that will notify you at the end of a contract. This could be used in your processes, for example, to trigger the deactivation of licenses.
• Contract activation is now available via our Webportal. Users can prepare a Contract ahead of time for a customer even when the contract delivery date is undefined (such as when an installation of hardware might still be required). Users may later "activate" the Contract and thus start its billing.

• Our Contract Quantity feature is officially released! Users can now decide the quantity a given option should be billed for at Contract creation. For example, one Contract handles the subscription for one license, and another contract -based on the same Plan- is used for 50 licenses.
• During Plan creation, users can now determine if an Option should be mandatory when creating a Contract or could be an optional add-on. Users decide at Contract creation if and how many of each Options will be billed.
• We restructured the Order and Contract creation views to provide better guidance when manually handling those entities and make it look quite a bit nicer!
• We reworked how our operational notification feature worked. While previously users had more of an audit log at their disposal which just listed all attempts made to send a notification to their system, users now have a list of actual notification instances. Looking into the details of such a notification users will find the log of attempts for this very notification here, making it easier to gain an overview of any specific issues their integration with our system could have. Users can also easily copy the requests we send to your API or the responses they answer us with, making debugging issues trivial.
• Users can now also "retry all failed notifications" with a single click.
• Addresses can now also contain properties, allowing users to provide additional information about the addresses of said users' customers, such as place of delivery if they wanted to print this on the invoice document, for example.

• Extended visibility of customer data in our Webportal.
• Fixed a bug where leading or trailing spaces weren't correctly shown in our translation service.

• Our revenue recognition feature is now fully configurable via the Webportal. To use it, simply add a "Deferral Account" to the Revenue Account. If a booking entry with a service period spanning at least 2 months is created for this Revenue Account, then the booking is deferred and recognition bookings are automatically created for the upcoming periods.

• The Option Allowance feature is out of beta.
• You can now delete and update Option Allowances.
• Order level allowances can now be viewed in the Webportal. Be aware that they are currently not considered in the Order totals.
• Fixed a bug where the unit price of a usage wasn't correctly displayed after pooling.
• We clarified a warning where a user would try to assign an invoice to a payment that was previously assigned.