LedgerSMB 1.2.13 released

Submitted by Chris Travers on

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.

Happy Birthday LedgerSMB!

Submitted by Chris Travers on

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.

LedgerSMB 1.2.6 released

Submitted by Chris Travers on

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:

Why is LedgerSMB PostgreSQL-only?

Submitted by Chris Travers on

Adding support for other database management systems would require that the database logic be coded to the least common denominator. We have decided that we want to eventually allow add-ons in different languages, and thus the database becomes the only point where we can enforce accounting logic consistantly across all parts of the application. Porting and maintaining such logic across database systems is not feasible for this project.

Additionally PostgreSQL is an outstanding RDBMS and we have no desire to move from it.

LedgerSMB 1.2.5 released

Submitted by Chris Travers on

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

This release includes major bugfixes for users of 1.000,00 and 1000,00
number formats. Users with these number formats are urged to upgrade
as soon as possible.

The release also includes a number of UTF-related fixes. Users who
require umlauts, multibyte charaters, and accents should also upgrade.

How do I account for Depreciation in LedgerSMB?

Submitted by Chris Travers on

This content is outdated and kept here for reference only!

NOTE: LedgerSMB has a Fixed assets module as of 1.3. The FAQ below is out-dated.

LedgerSMB does not have a built-in assett tracking / depreciation feature. Depreciation can be managed manually using General Ledger Transactions. You should probably confirm this with your accountant, but the basic procedure (kindly suggested by Tony Fraser) is, assuming a computer asset over 5 years: