About LedgerSMB

LedgerSMB is a fork of a popular general ledger software package called SQL-Ledger largely written and maintained by Dieter Simader. If you are considering joining our community please take a look at our Code of Conduct.

SMB is an acronym for Small Medium Business.

LedgerSMB 1.2.13 released

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.13 which is available from the SourceForge download page.
This release corrects all known issues with running LedgerSMB 1.2.x on PostgreSQL 8.3 and although other issues may surface, we will fix those as they are brought to our attention.

Please click 'Read more' to view the change log for 1.2.13.

LedgerSMB 1.2.11 released

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.11 which is available from the SourceForge download page. Some of these fixes are important for Canadian users, as it fixes some tax issues that are affected by the GST change.

Please click 'Read more' to view the change log for 1.2.11.

LedgerSMB 1.2.10 released

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.10 which is available from the SourceForge download page.

The changelog for this release is quite long, please click 'Read more' for all the details.

LedgerSMB 1.2.8 Released

This release corrects a number of SQL injection issues as well as a number of other bugs. The changelog is:

Changelog for 1.2.8

  • Fix SQL errors saving customer price lists (Chris T, 1754172)
  • Fixed AR/AP reversal issues (Victor S, 1752439, 1753358)
  • Fixed various scoping errors (Chris T, 1703347, 1753360)
  • Fixed: Timecards ignore price matrix (Chris T, 1754099)
  • Fixed scoping issues in IS.pm (Chris T, 1754576, 1754579, 1768678)
  • Fixed bugs with reversing invoices (Victor S, 1756387, 1755928, 1755355)

Happy Birthday LedgerSMB!

Today is the first anniversery of LedgerSMB's first public release.

In the past year, we have released three major releases:

1.0.0: Major security enhancements

1.1.0 Moderate security enhancements, new features

1.2.0 Major security enhancements, new features.

In addition, each of these releases has had several revisions which have
corrected various bugs and security issues. All in all, we have had nearly
25 releases in a year. We have gone from 300-500 downloads in our first few
months to 800-1200 most months currently. While this is still only half of

LedgerSMB 1.2.7 Released

LedgerSMB 1.2.7 has been released which contains a number of critical
updates affecting users of LedgerSMB 1.2.x. These include a fix for a
severe security issue. All users who are currently running LedgerSMB
1.2.x are urged to upgrade at once. A security advisory is currently
under development and will be released through these channels once it
is completed.

LedgerSMB 1.2.7 also includes a number of other bug fixes of varying
severity. The full changelog is:

Changelog for 1.2.7

  • Fixed user@company logins (Chris T)

Writing content on LedgerSMB.org (or How I learned to stop searching and wrote it myself)

Contributing to the LedgerSMB project with documentation and articles is easy. This short document will get you going in no time...

LedgerSMB 1.3.0 Milestone 1 released

(From Chris Travers' post to LedgerSMB-devel list)

We have opted to release a milestone release on sourceforge with the changes towards 1.3.0 to-date. Please note that this release is largely aimed as a community update and is not suited well to either active development (due to rapid changes of the codebase) or for production use.

Highlights include:

  • a new template system (Seneca)
  • RESTful web services interface code (Jason)
  • Normalized Contact Management schema to be basis for other CRM functionality (Josh D)

LedgerSMB 1.2.6 released

The LedgerSMB team is pleased to announce that version 1.2.6 was released on June 28th

The following issues have been corrected:

  • customer_id field error in AP transactions
  • invalid HTML in ca.pl
  • Error searching for customer by address
  • Error saving orders, projects, etc. with custom fields.
  • Error saving project with NULL customer id.
  • .po header information showing up on balance sheet.

Additionally, the following preventative measures were included:

  • Meta tags were added to force the use of utf-8 by default
Syndicate content