This document looks forward from the last stable public release (currently 1.6). The document should be taken as a general indication of direction. As with every open source project, contributors follow their own priorities; as such, features may be implemented earlier or later than indicated or even features entirely not mentioned may be implemented.
LedgerSMB 1.3.19 has been released. This release corrects two
significant issues and makes the application generally easier to use.
The two significant issues it fixes is that voided transactions were
including the original payments again, and that CSV exports had no
data. A large number of more minor problems were fixed including the
fact that some reports were requiring that the date be set in ISO
format, and fixed an encoding issue that caused corruption on
retrieval of some attached files (the files were stored correctly so
We are a US not-for-profit (http://riverbendmath.org/) using SQL-Ledger and LedgerSMB since 2006 (I'm not sure exactly when we made the switch). We are a small organization: ~15 part-time employees; ~$150,000 annual revenues; 2 users of the ledger. We are still using 1.2.x because my trial transition to 1.3.x did not work out as smoothly as I had hoped. Thus, I have put the transition on hold until I can give it a few days attention. As an organization we believe in and use open source software almost entirely.
This release corrects a few bugs that are specific to 1.3 and a few bugs which have been longstanding since before the fork. Additionally pricelists are now exported in ODS format. XLS output which has been broken for some time was removed.
The most important bugfixes are that ODS output now works, and selecting from the year and month dropdowns doesn't result in bogus dates being printed at the top of the report. Additionally an internal server error when running monthly requirements reports was corrected.
I have made a payment to a vendor, but entered an incorrect date, far in
the future. Consequently the payment does not show when I try to reconcile
the relevant bank statement.
How do I back-out the incorrectly entered payment?
Cash/Vouchers/Reverse Payment.
Then when you are done adding the payments you want to reverse,
approve the batch.
Robert James Clay just wrote the -users list to make the following announcement:
The 1.3.15-2 package for LedgerSMB has been accepted into Debian
unstable. I expect that version of the package to migrate to Debian
testing (wheezy) by the end of this month.
LedgerSMB Debian source package page:
This release corrects the internal server error on tax lookup issue, and it also corrects an issue that was found in file uploads. Additionally for those running the latest Math::BigInt and Math::BigFloat packages, one is_zero issue was found and fixed. A number of more minor bugfixes are included as well.
This release corrects a number of issues regarding international support, including an issue with UTF-8
characters not showing up properly in HTML invoices, some corrections in the aging report so that invoices are clustered by currency (with subtotals per currency), new user screen not respecting default country, and some enhancements for local tax rules support.
Please see the changelog below for more details.
Best Wishes,
Chris Travers
Changelog for 1.3.16
This release corrects a few bugs in installation and setup as well as early payment discounts. It also provides a means to print pricelists for a customer as PDF, or exporting as CSV so that they may be imported into a spreadsheet of your choice.
Please see the complete changelog below.
Best Wishes,
Chris Travers
This content is outdated and kept here for reference only!
Check the 1.5 installation instructions up to date instructions.
=============================================================
Update: mai 2012