Platform OverviewDemoContactImprint

Release 2024-07-03

about 1 month 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

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

Release 2024-06-05

about 2 months ago by Daniel Hofmeister
  • Document number ranges can be configured in our Webportal. This means easier setup for new tenants and new number ranges, without support from our NBX professional service colleagues.
  • Rated Usages are now shown under contracts and documents, allowing for better transparency in how they are being billed.
  • We've added the ability to extend your custom reports by our properties as well, increasing the amount of data provided to you.

Release 2024-05-21

2 months ago by Kathrin Roth
  • Our option allowance, with which you can grant running contract discounts, can now be configured to last for multiple billing periods.
  • Using our Webportal, line Items can now be filtered by properties.

Release 2024-05-06

3 months ago by Kathrin Roth
  • We have extended our document aggregation strategies to allow for more flexibility. You can now for example sum up multiple different item groups into one custom subtotal. Those custom subtotals and our previous sub totals are also displayed on the invoice detail page.
  • Fixed a bug where new payment assignments weren't shown on payment transactions.
  • Fixed a bug where customers couldn't be billed if they reached over 5.000 addresses.

Release 2024-04-22

3 months ago by Daniel Hofmeister
  • Added a feature to delay the charging of payments until the invoice's due date. Potentially created partial credits are taken into account, charging only the actual open amount at the time of due date arrival.
  • Payment transactions are now assigned directly to a document before a settlement is posted. A PreBooked Item is created in the Opos overview to provide better payment insight.
  • You can now turn off the creation of "zero-amount documents" in your Billing Groups. This allows for better integration with legacy general ledger systems that can't handle such documents. This option can be enabled within the Billing Groups settings.
  • In our Webportal the account name for any GL account is now displayed next to the account number on all bookings, so you no longer have to remember all of your accounts.
  • Payment Terms for Contracts and Orders can now be updated via API, in case you come to a different payment term agreement with your customers.
  • We enabled the first part of our rated usage feature in our Webportal. While already completely available via API, you can now use our Webportal to configure Rated Usage Options and attach them to Plans. Those Rated Usages will become more visible in the coming weeks and months!
  • Fixed a bug in our Webportal, where the billable items processing date was displayed in the users local time instead of UTC despite being labeled as UTC.

Release 2024-04-08

4 months ago by Daniel Hofmeister
  • Using our Webportal, when manually assigning a payment to a document, you can immediately clear a potential open amount and trigger an Opos Decisions. This should speed up the workflow for any smaller under/overpayment situations.
  • Pending payments are now visible in the Opos Cases as "prebooked item" to prevent double payment charges and to handle refunds correctly when payments are captured but not settled, thus providing a better overview of the OPOS situation for any given document.
  • We are now rounding contract and order line items, allowances, and agreed deposits according to the currency. Previously we only rounded accordingly when the actual document was created. Ensuring line items have the same precision increases consistency.
  • Unpooled (metered) Usages can now be cancelled, leading to a credit note if theywere already billed.
  • Payment terms can now be configured during order and contract creation. This allows users to overwrite the tenant default configuration for payment terms and allows for more flexibility.
  • Billing Groups can now be configured to be split by performance location. While tax location is always mandatory, you might want to split transactions by where they occurred, giving your customers a better overview of invoices.
  • To prevent tenant misconfigurations, you can no longer change the name of a billing group region already being used in options for price determination.
  • Improved connection consistency for external Tax Providers.
  • Improved performance for searches in Opos Cases
  • Improved our API doc, removing some empty tags, ordering some endpoints to their correct groups, and more.
  • Fixed a bug where document creation failed when a customer's post office box had more than 16 characters.
  • Fixed a bug where, during contract creation, adding a new option would reset the quantity of previous options back to 1.
  • Fixed a bug where Contract Expired events were still sent out at the original contract end date, even after the contract had its end date moved up.

Release 2024-03-13

4 months ago by Daniel Hofmeister
  • We enabled our Order Agreed Deposit feature. Instead of only defining agreed deposits on items, you can also specify them on Order level and let NBX handle the decision on which items the deposits are expected. We will then split them off into the items with the highest VAT first.
  • Assigning a Payment to an Order (deposit), where the payment amount is larger than the total order amount, will now work and any overpaid amount will also be assigned to the item with the highest VAT.
  • Our API will now respond with a 308 permanent redirect when being requested with an url that ends in a slash ("/").
  • When creating an Order we will now also check if there is also a fitting Payment present and will assign it automatically. This will increase the automation success rate for automatic assignments and reduce operations for your AR managers.
  • Opos Cases now have explicit debit and credit indicators to avoid confusion by looking at the plus and minus signums (API only).
  • Merchant payment accounts can now be configured to create Payment intents on the due date of a document, thus for example charging your customers at a later date.
  • Fixed a bug where locations weren't sorted correctly.
  • Fixed a bug where "in-between" dates filter did not always appear.
  • Fixed a bug where the color of the "plus" and the background color on the "Add" button were the same on the dashboard page.

Release 2024-02-26

5 months ago by Daniel Hofmeister
  • Deposit refunds will now be automatically assigned to Orders and Deposit Invoices
  • Deposit payments now show up as a single OPOS case entry, instead of one per item. This should make things clearer.
  • Using our API when creating line items for contracts, you can now choose if they should be billed with the current billing period or the billing period according to the functional data, for example, the delivery date or the service period. This gives users more control on when their items will be billed.
  • Users can now search customers by their vat-id.
  • When adding Options to Plans or selecting non-mandatory Options during Contract creation you can now pick multiple Options at once, this should ease operations when handling many Options.
  • We fixed several bugs that impeded the consistency of billing in cases of extraordinary termination. Now your end customer should receive their final invoice right after the contract ends, previously line items or usages might be billed at the end of the regular billing period.

Release 2024-02-06

6 months ago by Daniel Hofmeister
  • We enabled pricing by region, allowing more detailed pricing configurations. This is especially helpful if you want or need to charge more for remote territories within a country.
  • We have added a configuration to turn off automatic clearing in our bookkeeping domain. The intended use is for clients not using NBX as a full sub-ledger, which leads us to be unable to fully clear in any case, leaving an inconsistent state. Document OPOS is unaffected by this change.
  • It is now possible to configure multiple vat-ids per operating site. This eases the setup for companies that operate from one country, but are tax-registered in another without having set up a separate operating site for it.