What's new in LedgerSMB 1.11

This release features a new, fresh logo! Next to that, there are:

Barcode reader support added (back) to invoices
Reclassification of negative (current) assets to liabilities
Tracking of the relationship between reversed and reversing transactions

New features

Barcode reader support added (back) to invoices

Before LedgerSMB 1.5, partnumber input fields would pick the correct part when filled with the barcode associated with that part. This functionality was lost in 1.5. A replacement has now been added to 1.11: if a database contains barcode numbers, a barcode entry field is shown on the invoice entry screen as per the screenshot below:

Invoice barcode entry

Here's where to configure the barcodes for use:

Barcodes on the parts configuration screen

Note for upgrades: There is no impact on upgrades. Users who want to use this feature need to configure barcodes and make/models in the parts configuration screen.

Reclassification of negative (current) assets to liabilities (and vice versa)

In it's common practice to present negative current assets as positive current liabilities. An example where this regularly happens is when a bank current account goes into overdraft: instead of the bank owing money to the company (an asset), the company owes money to the bank (a liability). This release adds a new configuration on the account settings screen: "Negative balance heading". This setting applies to asset and liability accounts. See the screenshot below to find where to set the configuration.

When the "Negative balance heading" is set, when an asset account has a credit balance, it will be reported as a liability under the heading indicated in this option.

Negative balance heading configuration

Note for upgrades: Users wanting to use this option need to explicitly set it on affected accounts after migration of the database completes.

Tracking of relationship between reversed and reversing transactions

To enhance clarity of what happened between transactions, tracking of transaction reversal has been added, tracking which transactions have been reversed and by which transactions. Related transactions are shown at the top of the transactions and invoice entry screens; see the screenshot of the GL transaction entry screen below.

Transaction reversal tracking on the GL screen

Note for upgrades: The relationship is only tracked for new reversals. Existing reversals can't be retroactively detected and tracked.

Webservice for Countries

A webservice has been created to manage configuration of:

Countries (/erp/api/v0/countries)

This was created in support of moving the front-end to Vue3 components. For more information on how to use these services, see LedgerSMB Webservices.

Note for upgrades: There is no impact on upgrades.

Notable changes

Transaction state shown in transaction and invoice headers

Transactions and invoices show their state (e.g. Saved, Posted, Reversed) in the top part of the data entry screen. An example for a GL transaction is shown in the screenshot below.

GL entry screen showing transaction state