Happy New Year! Here are our first improvements for this year:

• We introduced a new config for Document Date determination on the Billing Group Level. Currently, the document date will always be the date when NBX creates the document. The new config allows you to change that to a Document Date according to the Billing Period.
  This solves the problem that some ERP systems require the document date to be the same as the booking period they want to book it in instead of relying on data on item level.
• You can now create Plans with delayed billing. That is: Contracts for those plans will be billed a (configurable) amount of time after the end of the billing period. This allows some time for all transactions (like usages) from the billing period to be transferred to Nitrobox so they can all be easily billed together with subscription elements.
• Now, Options that aren't being used by a Contract can be updated without creating an Option version.
• Fixed a bug where the country Norway was, at times, wrongly translated as "Nein" in the German translations.
• Information
  The next regular scheduled release will be skipped due to the holidays. The next release will be on 2024-10-15.
  We from Nitrobox wish you all happy holidays and a great new year! 🎄

• Added a simplified view for our contract individualization feature that can be toggled on or off. This view only allows price changes to be made to better guide the most used case.
• We restructured our Order view to better show allowances (reductions) and also provide the sum for the entire order volume in one convenient view

• We've released our contract individualization feature. This allows users to easily create a contract based on an existing plan by changing some of its configurations, such as different prices or different billing terms. This will create an individual plan in the background, which you can now see in the Webportal for which quick filters are available.
• We've added new oposCaseUpdated notifications, allowing you to react in real-time when an OPOS case has been updated.

• A user can now provide the information that a document has been- or will be paid via Worldline or Apple Pay. This can be seen on the order or contract page.
• You can now view Line Item Descriptions in our Webportal. Line item descriptions are additional information about the line item. It existed previously in our API but is now available in the Webportal.

• You can now also provide Customers' "tax number" in addition to their VAT ID. This number is required in some jurisdictions for e-invoicing and CTC processes. Examples are the Italian Codice Fiscale or the German Steuernummer.

• Using our Contract API you can now add a new parameter called "slimResponse" that will return a smaller Response body without Line Items, Allowance, etc. Some Use Cases see many thousands of Line Items as part of an Order or Contract, which leads to long loading times when not slimming down the response.
  This "slimResponse" feature will be slowly rolled out to other entities as well, such as customers with many addresses.

• Fixed a bug where the invoice correction process would duplicate the invoice address as the shipping address for the customer if there was no previous shipping address.

• We added a new Notification for "Settlement Created".
• We created a new Line Item Details view that allows users to find all information about a Line Item in one place. This includes attached discounts, agreed deposits, etc. Some of this information was previously not available in the well-known table view.
• Fixed a Bug where in Firefox you were able to type letters in the UI in form fields that should only allow numbers.

• We added pagination to the Line Items of the Contract and Order Details view. Now you can easily navigate the Items if you have more than 20 on a single Contract or Order.
• Fixed a bug where Orders were sorted the wrong way around.

• We enabled the standard add, edit, and delete functionality for Line Items that have agreed deposits. This allows our users to react and adapt the products or services they aim to provide to their customers who have already paid for it partly via a deposit. Any change can also lead to automated bookings to better reflect the changed Line Item on the Order.
• We added a "payment health status" to our Customer Payment Accounts. That enables you to see at first glance if there have been issues with charging the Customer Payment Account.
• For "payment assignment reversed" notifications we've added a reference to the original assignment that was reverted.

• As stated in our last release we have removed HTTP support and only support HTTPs from here on out.
• You can now configure and use different VAT taxes based on regions within a country. That allows you for example in the case of Spain to configure different tax rates on Spain's Mainland, the autonomous cities of Ceuta and Melilla (IPSI) as well as a different tax for the Canary Islands (IGIC).