Demo
Below is a listing of demos available from different hosting companies:
Efficito.com
- Read more about Demo
- 2 comments
- Log in or register to post comments
Below is a listing of demos available from different hosting companies:
Versions 1.10 and higher are under active development and are supported by the community. Planned end-of-life dates for current releases are:
If you're looking for help on how to use EOL-ed versions, please try mailing the users mailing list.
If you're looking for someone to create bugfixes, please check with one of the parties providing commercial support or for less urgent fixes LedgerSMB Issues
Version 1.10 has been declared end-of-life on 2024-10-08. The last release in the series is 1.10.38. No futher releases will be made by the community.
Version 1.9 has been declared end-of-life on 2023-09-24. The last release in the series is 1.9.30. No futher releases will be made by the community.
Version 1.8 has been declared end-of-life on 2022-09-04. The last release in the series is 1.8.31. No futher releases will be made by the community.
Version 1.7 has been declared end-of-life on 2022-10-04. The last release in the series is 1.7.41. No further releases will be made by the community.
Version 1.6 has been declared end-of-life on 2021-06-10. The last release in the series is 1.6.33. No further releases will be made by the community.
Version 1.5 has been declared end-of-life on 2019-12-23. The last release in the series is 1.5.30. No further releases will be made by the community.
Version 1.4 has been declared end-fo-life on 2017-09-16. The last release in the series is 1.4.42. No further releases will be made by the community.
Version 1.3 has been declared end-of-life on 2015-12-23. The last release in the series is 1.3.47. No further releases will be made by the community.
LedgerSMB versions 1.0, 1.1 and 1.2 won't be maintained any further due to the fact that there are some known security issues which can't be fixed.
Perl on CPAN
Requires: Perl 5.004, Carp, Exporter, GD (optional)
http://search.cpan.org/~wrw/Barcode-Code128-2.21/lib/Barcode/Code128.pm…
Example:
use Barcode::Code128 'FNC1';
$code = new Barcode::Code128;
$code->text(FNC1.'00000123455555555558');
In general: neither. The advice is to have the full source tree in /opt/ledgersmb/<version>.
The default configuration limits access to the /ledgersmb/login.pl page to connections from localhost (127.0.0.1) only for maximum security.
If you want to allow connections from other locations, it's highly advisable to use encrypted (VPN) connections to access your ledger in order to maintain good security.
The simple one:
Sales order: Customer wants to buy something.
Sales invoice: Customer owes for goods and services delivered.
Business-flow-wise, typically you take an order before everything is done necessary for the transaction to hit the books, and convert it to an invoice when everything that has been done for the income to be realized has happened. This typically means:
1) Goods or services are delivered
2) Any approval/error checking the business requires has happened
To give folks an idea of where the next release is coming, I figure it is worth posting this and updating it from time to time.
Changelog for 1.4 Series
Forthcoming
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.
A lot of people are wondering how to manage their migration to LedgerSMB from SQL-Ledger. While there is no one simple answer that will suit everyone's situation, there is some general advice.
First thing to know is - you are among friends. LedgerSMB is built on a community of people who want to see the software and it's users succeed. Information is freely shared, and as long as you are prepared to have a go at helping yourself, we are happy to jump right in and help you do that!
We now have a mailing list, whether you are actively working on migrating to LedgerSMB or even if you are staying with SQL-Ledger for now and want some friendly community support, join up the User List to get SQL-Ledger to LedgerSMB migration help
The best course of action depends on your situation: