JustOn 2.123
We regularly deliver updates to bring new features, improvements and fixes to JustOn Billing & Invoice Management. Continuous development is essential to the legally permissible operation of our e-invoicing application and makes sure that it always responds to current legal regulations about data protection or tax-relevant data. This provides for a seamless and safe operation as well as for the best possible support.
JustOn 2.123
2026-10-14
Welcome to JustOn Billing & Invoice Management Release 2.123.
This release integrates manual invoice write-offs with JustOn Cash Management and fixes issues in standard templates and in the status processing of Avalara ELR e-invoices.
This page summarizes new features, notable changes and bug fixes included with this delivery. For detailed information about JustOn's features, refer to the JustOn documentation.
Preliminary information
Generally, JustOn recommends to delete all draft invoices before installing the new JustOn Billing & Invoice Management release in order to allow for a smooth transition to the new features.
If you bundle JustOn permission sets in permission set groups, always make sure their status is Updated. This indicates that the bundled permissions are up-to-date.
Upgrading | Important Info
If you upgrade earlier versions of JustOn Billing & Invoice Management to a recent release, JustOn strongly recommends to follow the JustOn Upgrade Guidelines. This document summarizes breaking changes as well as configuration tasks to complete before upgrading.
Additions
Cash Management Integration: Entry Reductions for Manual Write-Offs
Writing off an invoice manually did not lower the open amount of its entries, so JustOn Cash Management kept requesting money that had been written off. A manual write-off now reduces the invoice's open entries by the written-off amount, and deleting the write-off balance reverts the reduction. For invoices written off before the integration, the new fix invoice task Create Write-Off Reductions produces the missing reductions. For details, see Write-Off in JustOn Cash Management. (PLAN-479)
SEPA Order Export: ISO 20022 2019 Formats and Creditor Bank Account
The SEPA order export now supports the formats XML CDD pain.008.001.08 and XML CCT pain.001.001.09; existing export settings keep their format. In addition, SEPA Direct Debit export settings can specify a creditor IBAN and BIC that replace those of the business entity. For details, see SEPA Order Export and Configuring SEPA Creditor Fields. (PLAN-1843, PLAN-1845)
Fixes
Template Management: PDF of Credits Without Related Invoice
Standard templates failed to render the PDF of a credit that has no related invoice – for example, a credit resulting from a negative amount in a regular billing run. The delivered Liquid file now prints a neutral opening sentence for such credits, read from the new override label key messages.credit. For details, see Override Labels. (PLAN-1878)
Existing templates keep their attached Liquid file and their override labels. To apply the fix, transfer the changed opening message block from the Liquid file of a newly created template, and add the key messages.credit to the Override Labels of your templates – without it, the sentence is printed in English. For details, see Keeping Changes Across Upgrades.
Template Management: Shipping and Handling Fees
Standard templates did not print line items of the type Shipping Fees or Handling Fees, although their amounts were included in the totals – the printed line items did not add up to the grand total. The delivered Liquid file now prints one row per fee, followed by the tax of the fees per tax rate, and lists the tax of the fees in the remaining amount block of final invoices. For details, see Printing Shipping and Handling Fees. (PLAN-1877)
Existing templates keep their attached Liquid file. To apply the fix, add the fee rows to the Liquid file as described in Printing Shipping and Handling Fees.
Avalara ELR: Completion After Distribution Error
If Avalara ELR reported an error for an e-invoice and completed it later after all, the completion was discarded – the invoice stayed in the E-Invoice Status Distribution Error, and sending the e-invoice again did not help. A success reported after an error is now applied to the invoice like any other success. A later error, by contrast, still does not overwrite a recorded success. For details, see Reviewing Status Fields. (PLAN-1873)