The LedgerSMB project provides small and mid-size businesses with open source accounting software: integrating invoicing, order processing, quotations and more (ERP). LedgerSMB aims to provide a strong (multi-currency accounting) basis to build your business on -- without vendor lock-in.
- Sales (Invoices, Orders, Quotations)
- Receivables & Payables
- General ledger
- Inventory management
- Fixed asset accounting & depreciation
- Profit & cost centers, departments, projects
- Output documents in PDF, HTML, CSV, Office formats
- Mail documents (e.g. invoices) from within the application
- Translatable to your language (comes with 45 languages)
- and more
The fact that LedgerSMB is open source - meaning that the source code is freely available - makes it even more customizable and flexible.
While LedgerSMB will generally work in any industry for its basic accounting functionalities, it is known to have been deployed in the following types of businesses:
e.g. VOIP services
i.e. invoicing of others
- (IT) Services
e.g. Website design, IT Support, hourly services
- Financial services
e.g. Investment firms
e.g. Housing rental, IT Hosting
e.g. Sewing necessities
e.g. Trading pet foods
Many of these applications include integration with domain-specific applications to perform specific business functions.
Next to the ones listed above, various manufacturing setups have been deployed, ranging from standard (batch based) mass production, to make-to-order one-time product configurations. The latter being supported by a custom developed product configuration plugin.
Although the nature of open source projects makes it hard to know where our software is being used; however, the project is aware of installations in the US, Canada, EU (Netherlands, Hungary, Estonia, United Kingdom), Indonesia, Myanmar, Philippines, Hong Kong, Malaysia, Australia, Barbados and Colombia.
The software can run in a different language for each user. Also: documents (invoices, orders, etc) can be produced in selectable languages, different from the user's language.
The project welcomes any and all contributions. With lots of areas which would benefit from more attention, we like to invite newcomers to read our community guidelines and start out simple. Good (and helpful!) starting points are translation contributions as well as reviewing our (beginners) documentation.
Our current stable version is 1.9 - initially released on Sep 24, 2021. This release has a wide variety of improvements and code cleanups: it features faster loading of pages, restored ability to mail aging reports regressed from 1.4, e-mailed documents (invoices, orders, etc) being stored in the database and much more... More details about this release can be found in the release notes. This release will see its End-Of-Life for community support at Sep 24, 2023.
Our old stable version is 1.8 - initially released on Sep 04, 2020. This release has a wide variety of improvements and code cleanups: it features faster loading of the menu, fixed migrations from 1.2, the ability to upload a logo into the database and include it in printed documents and much more... More details about this release can be found in the release notes. This release will see its End-Of-Life for community support at Sep 04, 2022.
Our current oldest supported version is 1.7 - initially released on Oct 04, 2019. This release focusses on improved support for foreign currency transactions, lifting the restriction of a single rate per currency per day; UI improved by showing both the functional and foreign currency amounts. Additionally, a lot of work has been spent on increasing the application stability through more rigorous testing and code cleanup. A full summary of the changes since 1.6 can be found in the release announcement. More details on this release can be found in the release notes. This release will see its End-Of-Life for community support at Oct 04, 2022.
Version 1.6 has been declared End-Of-Life on 2021, June 10th (released on June 10 2018). With 33 patch releases, we consider this version highly stable. Although there are more patch releases for 1.6 than thee are for 1.5, their size is on average smaller, attesting to the project's promise of delivering increasing software quality.
Version 1.5 has been declared End-Of-Life on 2019, Dec 23rd (released on 2016-12-23). With 30 patch releases, we consider this version highly stable. We believe that the lower number of patch releases over a similar life-span as 1.4 is an indication of better stability of the initial 1.5.0 release. We conclude that the project is delivering on its promise of increasing stability of minor releases.
Version 1.4 has been declared End-Of-Life on 2017, Sep 15th (released on 2014-09-15). With 42 patch releases, we consider this version highly stable.
Version 1.3 has been declared End-Of-Life on 2015, Dec 23rd (released on 2011-10-11). With a total of 48 patch releases since the initial release in October 2011, we consider this version highly stable.
Although their use is highly discouraged for both security reasons and data stability issues, older versions are still available for download. When using LedgerSMB versions 1.2 or earlier, you should to do so in only in a highly restricted network environment.
It's project policy to provide at least 24 months of community support for every 1.x release series; note that this policy was updated: releases 1.7 and earlier had 36 months community support. As such, there's no community support available for 1.5 or earlier LedgerSMB versions. Vendors may be willing to provide support or migration services.
LedgerSMB began in 2006 as a fork of the popular general ledger software package called SQL-Ledger largely written and maintained by Dieter Simader since 1999. Versions 1.2 and earlier are heavily based on SQL-Ledger's code.
As of 1.3 our codebase is quickly moving away from what we inherited.
Some of the improvements that we've made to the code base so far include:
- Enhanced security
- More reports
- Better data integrity controls
- More code quality control measures
- Major code size reduction while growing functionality
- Unit testing Infrastructure to help ensure once an issue is fixed it stays fixed
- BDD (headless automated browser) Testing infrastructure
- A very large number of tests against both testing frameworks
Travel in our history with Internet Archive and WayBackMachine.
Matrix support request ownership proof: firstname.lastname@example.org