Yes. IBANs are very long, bank account numbers. LedgerSMB has no problems storing, retrieving and using these without any issue.
Yes. SEPA (Single Euro Payments Area) requires support for very long bank account numbers (IBANs or International Bank Account Numbers). LedgerSMB can store and use these numbers without problems.
Assuming you have followed the How Do I Backup My Data instructions, you can restore your database as follows...
1) Restore the roles
$ psql -h [database host] -U [database admin user] < [roles backup file]
$ psql -h localhost -U lsmb_dbadmin < lsmb-roles.sqlc
2) Create a new database to restore into
$ psql -h [database host] -U [database admin user] -c 'CREATE DATABASE [new company name]'
The table below lists the compatibility of LedgerSMB versions with Perl versions. Products for which support has ceased due to End-of-Life date being reached are not listed and should not be used.
The answer to this question depends on what using means to you.
As a user of the web application, yes, there should be absolutely no problem using a recent (as in: no more than 2 or 3 years old) web browser in order to take advantage of all the features available.
Versions 1.7 and higher are under active development and are supported by the community. Planned end-of-life dates for current releases are:
- 1.7: Planned End-of-life date: 2022-10-04 (released: 2019-10-04)
- 1.8: Planned End-of-life date: 2022-09-04 (to be released 2020-09-04)
- 1.9: Planned End-of-life date: TBD (based on release date; to be released)
End of life
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.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.
In general: neither. The advice is to have the full source tree in /opt/ledgersmb/<version>.
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.
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: