Yes. LedgerSMB has a mechanism called "Account headings". The headings are the opposite of what Intuit explains about Quickbooks for their subaccount support: Quickbooks splits an account into multiple and aggregates those new accounts into the old one for reporting. To achieve the same in LedgerSMB, you create multiple accounts and one or more headings. LedgerSMB then aggregates the totals of the accounts per heading. The system used by LedgerSMB closely resembles what MYOB describes about their accounts and headers.
Company database upgrades are supported all the way back from 1.4 directly to 1.8, using the 1.8 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.8 structure, while upgrades adjust the existing structure for 1.8.
In preparation of the final release of LedgerSMB 1.8, the release branch has been created for a period of stabilization. In order to release the most stable version released by the project ever released, a preview version was published earlier today: 1.8.0-beta3.
By far the fastest procedure for installing LedgerSMB is by using the published Docker images: Being an ERP, there are many dependencies to be installed and all of them are included in the images, with the exception of the required PostgreSQL database. There are two ways to provide the PostgreSQL functionality: by setting up a separate PostgreSQL server or by using a PostgreSQL-providing Docker container.
In preparation of the final release of LedgerSMB 1.8, the release branch has been created for a period of stabilization. In order to release the most stable version released by the project ever released, a preview version was published earlier today: 1.8.0-beta1.
What's new in LedgerSMB 1.8
- Authentication and session storage using encrypted cookies
- In-database logos and images upload and template support
- Downloadable reports now stored in the database for customization
- New e-mail configuration in ledgersmb.conf
- Reconciliation takes payments as first-order transactions
- Import of OFX bank statement files for reconciliation
Authentication and session storage using encrypted cookies
This release switches to using encrypted cookies instead of HT
Getting all the development dependencies and a working copy for LedgerSMB can be time consuming and complex. However, using our Docker Compose infrastructure reduces this to four simple steps:
The table below lists the compatibility of LedgerSMB versions with Perl versions. Products for which support has ceased due to End-of-Life date being reached are not listed and should not be used.
Versions 1.6 and higher are under active development and are supported by the community. Planned end-of-life dates for current releases are:
- 1.6: Planned End-of-life date: 2021-06-10 (released: 2018-06-10)
- 1.7: Planned End-of-life date: 2022-10-04 (released: 2019-10-04)
- 1.8: Planned End-of-life date: 2023-09 (to be released 2020-09)
End of life
If you're looking for help on how to use EOL-ed versions, please try mailing the users mailing list.
If you're looking for someone to create bugfixes, please check with one of the parties providing commercial support or for less urgent fixes LedgerSMB Issues
Version 1.5 has been declared end-of-life on 2019-12-23. The last release in the series is 1.5.30. No further releases will be made by the community.
Version 1.4 has been declared end-fo-life on 2017-09-16. The last release in the series is 1.4.42. No further releases will be made by the community.
Version 1.3 has been declared end-of-life on 2015-12-23. The last release in the series is 1.3.47. No further releases will be made by the community.
LedgerSMB versions 1.0, 1.1 and 1.2 won't be maintained any further due to the fact that there are some known security issues which can't be fixed.
The table below lists the compatibility of LedgerSMB versions with PostgreSQL versions. Products for which support has ceased due to End-of-Life date being reached are not listed and should not be used.