Open Source ERP: accounting, CRM and more

LedgerSMB is an acronym for Ledger Small Medium Business.
 

Goal

The LedgerSMB project brings accounting software integrating invoicing, order processing, quotations and more (ERP) to small and midsize businesses.

Features

  • Sales (Invoices, Orders, Quotations)
  • Receivables & Payables
  • General ledger
  • Inventory management
  • Fixed asset accounting & depreciation
  • Profit 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.

Current versions

Our current version is 1.5 - initially released on Dec 23, 2016. This version builds on 1.4's move to use the Dojo toolkit to offer a much more modern (and faster!) user interface. A lot of development effort also has been spent toward Quality Assurance and automation of the release process. A full summary of the changes since 1.4 can be found in the release announcement.

Pre-release version

Development of 1.6 is on-going and no pre-releases have been made yet. Check the roadmap for general direction of future development and see the Changelog for the 1.6 series about items realised so far during 1.6 development.

Older versions

Version 1.4 has been declared End-Of-Life on 2017, Sep 15th. With 42 patch releases, we consider this version highly stable. Community efforts are spent maintaining the 1.5 release and development of the 1.6 release.

Version 1.3 has been declared End-Of-Life on 2015, Dec 23rd. 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 community policy to provide at least 36 months of community support for every 1.x release series.  As such, there's no community support available for 1.3 or earlier LedgerSMB versions. However, some vendors are willing to provide support or migration services.

Future

Some features currently under development and/or planned for future releases of LedgerSMB:

  • UI improvements (modern design, including mobile browser support)
  • Webservices
  • Revaluation of financial assets and liabilities
  • Easier installation
  • Further code quality improvements

Quality standards

The project holds high quality standards that should be expected from business software regarding these topics in particular:

  • Security
  • Performance
  • Software quality
  • Useability
  • Accessibility

Approach

We achieve this goal by:

  • Stimulating a vibrant, open community centered around:
  • Keeping a strong focus on efficiency and effectiveness through:
    • use of proven technology
    • re-use of existing solutions
    • code and design pattern re-use within the code base
    • real world use cases - introducing real solutions
    • Highly Extensible Comprehensive Automated Unit Testing
    • Highly Extensible Comprehensive Automated BDD Testing (Automated Browser Driven)
    • Active Development Commutity
    • Active Community Review

History

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 largely based on SQL-Ledger's code.
As of 1.3 our codebase is quickly moving away from what we inherited.
As of 1.5 our User Interface has moved to Dojo Javascript libraries providing a more dynamic feel.
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.