Aggregator

1.8.4 Released

3 hours 26 minutes ago
1.8.4 Released Security release No LedgerSMB_Team Sun, 09/27/2020 - 12:38 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.8.4/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.8.4

  • Fix subtotals not showing on AR/AP outstanding report (#4732)
  • Apply default sorting to AR/AP outstanding and transactions reports (#5080)
  • Fix failure saving new reporting unit classes with modules checked (#4614)
  • Fix failure sorting AR > Search results for filter with spaces (#4872)
  • Fix aging detail overview throwing error when generating report (#4018, #3572)
  • Fix various aging report problems (#5091)
    • Duplicate PDF/HTML format selectors
    • 'Date' column in PDF/PS output remaining empty
    • 'Select all' functionality fixed (now handled in the browser)
  • Fix various payment transaction issues (#5094)
    • POST AND PRINT html output on payments screen returned as text (#5077)
    • Payment report not containing payment lines
    • Remove unavailable PDF and PS output options for POST AND PRINT
  • Fix check printing showing random number in amount block (#5078)
  • Fix subtotals not working in GL report (#5098)
  • Add starting and ending balance to GL report filtered on account (#4985)
  • Fix AR/AP transaction applying exchangerate without locale conversion (#4879)
  • Fix parts searches failing to filter by serial number (#5107)
  • Various sales person related fixes (#5115)
    • Fix sales person failing to save on AR/AP Transactions
    • Fix sales person selection retained on Update in sales invoice
    • Fix loading sales person from database on document retrieval
  • Fix upgrades from 1.7 failing on self-created exchange rate types (#5112)
  • Fix 'Manager' drop down not populated in employee page (#5125)
  • Fix parts lookup on invoice not filtered by entered text (#5138)
  • Fix Account contact screen buttons populating customer on invoice/... (#932)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.8.4/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.8.4

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.4

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.8.4

These are the sha256 checksums of the uploaded files:

bc9739622a417d19471fc17aa6b546f2538df5d20d63f815f8552dd270341df3 ledgersmb-1.8.4.tar.gz
5f5adc5788757036257723af9b6039957984b124f4217672de42a360feeed58f ledgersmb-1.8.4.tar.gz.asc

Release 1.8
LedgerSMB_Team

1.7.23 Released

3 hours 57 minutes ago
1.7.23 Released Security release No LedgerSMB_Team Sun, 09/27/2020 - 12:07 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.23/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.7.23

  • Fix subtotals not showing on AR/AP outstanding report (#4732)
  • Apply default sorting to AR/AP outstanding and transactions reports (#5080)
  • Fix failure saving new reporting unit classes with modules checked (#4614)
  • Fix subtotals not working in GL report (#5098)
  • Fix AR/AP transaction applying exchangerate without locale conversion (#4879)
  • Various sales person related fixes (#5115)
    • Fix sales person failing to save on AR/AP Transactions
    • Fix sales person selection retained on Update in sales invoice
    • Fix loading sales person from database on document retrieval
  • Fix 'Manager' drop down not populated in employee page (#5125)
  • Fix Account contact screen buttons populating customer on invoice/... (#932)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.7.23/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.23

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.23

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.23

These are the sha256 checksums of the uploaded files:

de542f0f45aef924503d630c6a87a1ab49c4bdfb5d6ca58cd1ec85f544d9e2c7 ledgersmb-1.7.23.tar.gz
2bbf401076013ee8ce2df18812645e0c138e9729e3c1c3dfb5b75c2cc8915cb8 ledgersmb-1.7.23.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.27 Released

4 hours 9 minutes ago
1.6.27 Released Security release No LedgerSMB_Team Sun, 09/27/2020 - 11:55 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.27/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.6.27

  • Fix sales person failing to save on AR/AP Transactions (Aung ZW, 5115)
  • Fix 'Manager' drop down not populated in employee page (Erik H, #5125)
  • Fix contact screen buttons populating customer on invoice/... (Erik H, #932)

Aung ZW is Aung Zaw Win
Erik H is Erik Huelsmann

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.6.27/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.6.27

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.27

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.6.27

These are the sha256 checksums of the uploaded files:

d164025590499d339f9aafa2e709ac2038031aa4f14be03ab31b27c25fde327a ledgersmb-1.6.27.tar.gz
eae1f1612a1c90a2fd71ce98c982beb62683f845b2a6aab60c2d6af1886e09e9 ledgersmb-1.6.27.tar.gz.asc

Release 1.6
LedgerSMB_Team

1.8.3 Released

1 week 2 days ago
1.8.3 Released Security release No LedgerSMB_Team Fri, 09/18/2020 - 01:36 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.8.3/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application. Please
note that this release fixes mostly long-standing issues and only
a few 1.8 specific ones.
This release contains the following fixes and improvements:

Changelog for 1.8.3

  • Fix broken Bcc e-mail support (#5034)
  • Fix duplicated sales persons list on order entry (#5035)
  • Fix inability to open employee screen under specific circumstances (#5043)
  • Fix creation of assets class without required accounts (#4624)
  • Fix saving part's customer rate without 'Min QTY' (#4849)
  • Fix 'Parent' dropdown empty in Report Unit entry screen (#4625)
  • Explain password reset when importing user on company creation (#3249)
  • Fix inability to delete business unit class (#4597)
  • Fix missing buttons on unsaved invoice in closed period (#4840)
  • Fix lengthy errors showing stack dumps (#5072)
  • Split description and vendor/customer columns in GL and Drafts reports (#4836)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.8.3/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.8.3

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.3

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.8.3

These are the sha256 checksums of the uploaded files:

735e81b48fb08beadc909c5ae707d8a661b59aff38d7988ae2bfe3012063de27 ledgersmb-1.8.3.tar.gz
9079a73e1ed07ec9e11e9d901f7e56e2168f7e8017bf9afcec013440ce750b68 ledgersmb-1.8.3.tar.gz.asc

Release 1.8
LedgerSMB_Team

1.7.22 Released

1 week 2 days ago
1.7.22 Released Security release No LedgerSMB_Team Fri, 09/18/2020 - 01:06 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.22/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.7.22

  • Fix duplicated sales persons list on order entry (#5035)
  • Fix inability to open employee screen under specific circumstances (#5043)
  • Fix creation of assets class without required accounts (#4624)
  • Fix saving part's customer rate without 'Min QTY' (#4849)
  • Fix 'Parent' dropdown empty in Report Unit entry screen (#4625)
  • Explain password reset when importing user on company creation (#3249)
  • Fix inability to delete business unit class (#4597)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.7.22/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.22

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.22

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.22

These are the sha256 checksums of the uploaded files:

d072ef9fe160b4282715f163d52510cd7a305e1b2336a2fab72e74d5aa30142b ledgersmb-1.7.22.tar.gz
ad772745893703be621e852a0438ff4b75c63d01978db9aab1b6755265947f20 ledgersmb-1.7.22.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.26 Released

1 week 2 days ago
1.6.26 Released Security release No LedgerSMB_Team Fri, 09/18/2020 - 00:46 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.26/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.6.26

  • Fix inability to open employee screen (Erik H, #5043)
  • Fix creation of assets class without required accounts (Erik H, #4624)
  • Fix saving part's customer rate without 'Min QTY' (Erik H, #4849)
  • Explain password reset when importing user on company creation (Erik H, #3249)
  • Fix inability to delete business unit class (Erik H, #4597)

Erik H is Erik Huelsmann

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.6.26/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.6.26

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.26

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.6.26

These are the sha256 checksums of the uploaded files:

57b92e62c71a7a323fa6943b134a8689c16793e4d968d3557b15085370fafe8e ledgersmb-1.6.26.tar.gz
39d4f36a3433153e7a11b2f3254aaf5eb7424ee86a0037d23bf4bf7c451fb6ab ledgersmb-1.6.26.tar.gz.asc

Release 1.6
LedgerSMB_Team

1.8.2 Released

2 weeks ago
1.8.2 Released Security release No LedgerSMB_Team Sun, 09/13/2020 - 13:19 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.8.2/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.8.2

  • Fix AR/AP search sales person not limiting selection (#4604)
  • Fix departments dropdown not populated on Receipts/Payments entry (#4636)
  • Fix sales person not shown on existing AR/AP transactions (#5004)
  • Fix failure to post recurring GL transaction (#4946)
  • Resolve conflict between HTML5 and our 'date' INPUT tags (#5016)
  • Fix asset screen dropdowns not populating correctly (#5016)
  • Fix asset classes not in search output when missing accounts (#5020)
  • Fix address-type (Billing, etc) not correctly initialized on edit (#2564)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.8.2/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.8.2

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.2

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.8.2

These are the sha256 checksums of the uploaded files:

d6d10ef1348c12b89410291800757c409d5424efcf85dedcf3058c29b1c91d57 ledgersmb-1.8.2.tar.gz
45ec29b3e3a25c3cce40a264995d096f26b951c4a231cfd59ab3e0f56c41dea8 ledgersmb-1.8.2.tar.gz.asc

Release 1.8
LedgerSMB_Team

1.7.21 Released

2 weeks ago
1.7.21 Released Security release No LedgerSMB_Team Sun, 09/13/2020 - 12:34 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.21/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.7.21

  • Fix AR/AP account dropdown not retained on 'Update' (#4927)
  • Fix AR/AP search Employee filter not limiting the result (#4606)
  • Fix Departments dropdown not populated on Receipts/Payments (#4636)
  • Fix missing sales employee on existing AR/AP transactions (#1015)
  • Fix error when posting recurring GL transactions (#4946)
  • Fix incorrectly populated dropdowns on Asset screen (#5017)
  • Fix conflict between HTML5 and our 'date' INPUT widgets (#5017)
  • Fix asset classes with missing accounts not being in search result (#5021)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.7.21/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.21

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.21

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.21

These are the sha256 checksums of the uploaded files:

a0bc7420b011cc1ff520ca91775c16d50a05e77639586860b811100929d6ce1f ledgersmb-1.7.21.tar.gz
3bc59cfad68031d9f30bc059c639651126535cb4746aaa1c7a51db47e23c02ff ledgersmb-1.7.21.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.25 Released

2 weeks ago
1.6.25 Released Security release No LedgerSMB_Team Sun, 09/13/2020 - 12:18 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.25/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.6.25

  • Fix AR/AP account on transactions retained on 'Update' (Erik H, #4927)
  • Fix AR/AP search not limited by Employee selection (Erik H, #4604)
  • Fix Departments dropdown not populated on Receipts/Payments (Erik H, #4636)
  • Fix showing sales employees on existing AR/AP transactions (Erik H, #1015)
  • Fix populating values in Asset screen dropdowns (Erik H, #5018)
  • Fix conflict between HTML5 and 'date' INPUT widgets (Erik H, #5018)
  • Fix asset class report to include classes missing accounts (Erik H, #5022)

Erik H is Erik Huelsmann

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.6.25/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.6.25

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.25

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.6.25

These are the sha256 checksums of the uploaded files:

a6ace87ff36470954c71bb33f2c3a21c4c65722da3999c5ac062289f3e9a9906 ledgersmb-1.6.25.tar.gz
4d11f7e503b53ba3ecda6b9a1b13a75eccfb310add0bcb5d0f88d5c111e1975b ledgersmb-1.6.25.tar.gz.asc

Release 1.6
LedgerSMB_Team

1.8.1 Released

2 weeks 5 days ago
1.8.1 Released Security release No LedgerSMB_Team Tue, 09/08/2020 - 12:26 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.8.1/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.

This release corrects a rounding bug in the payments code which
causes differences between the payment amount entered by the user and
the amount recorded in the ledger (although the actual amount recorded
is later correctly presented). Due to the high level of inconvenience
of this bug, this release follows quickly on the release of 1.8.0.

Due to a high level of development activity on the master branch and
related backports, a number of additional fixes are also included.
This release contains the following fixes and improvements:

Changelog for 1.8.1

  • Fix incorrect rounding on payments leading to under/overpayment (#4986)
  • Fix AR/AP dropdown on transactions not retained after 'Update' (#4927)
  • Fix sales order generation from timecards (#4984)
  • Better defaults for 'HR > Add Employee' screen (#1672)
  • Fix timecard Save feedback screen showing zero quantities (#4982)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.8.1/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.8.1

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.1

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.8.1

These are the sha256 checksums of the uploaded files:

fe48040bb4fe957b60f10070bb818005ba71a70e9f6fc3ec1da3333c975afa77 ledgersmb-1.8.1.tar.gz
db76ab59b686316c729ee6faf07d8c9cdb906443e927ab0205772e32879f6875 ledgersmb-1.8.1.tar.gz.asc

Release 1.8
LedgerSMB_Team

1.8.0 Released

3 weeks 2 days ago
1.8.0 Released Security release No LedgerSMB_Team Fri, 09/04/2020 - 14:16 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.8.0/

The LedgerSMB development team is happy to announce the first
release of a new release branch: 1.8.0. This series features
a wide variety of new features, improvements, bug fixes and
cleanup. To name a few:

  • Support for in-database logos and images for inclusion in printed
    documents; this improves support for customized document templates
    inside docker containers
  • Authentication now uses encrypted cookies instead of HTTP Basic
    authentication which improves support for logging out and improves
    security
  • Support for OFX bank statement imports for reconciliation
  • Faster loading of the menu and GL account drop-downs
  • Fixed LedgerSMB 1.2 and 1.3 migrations as well as SQL Ledger 2.8 & 3.0
  • Fixed incorrect discount calculations for transaction dates <> 'today'
  • Fixed single-entry timecard support (which was broken since 1.4)

For the full changelog see https://github.com/ledgersmb/LedgerSMB/blob/1.8/Changelog

For a more in-depth coverage of notable changes in this release, please consult the
release notes at https://ledgersmb.org/content/18-release-notes

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.8.0/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.8.0

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.0

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.8.0

These are the sha256 checksums of the uploaded files:

dfa57209df83bd3d63d4e8ed7cba2b6a87ecf42d29568071cfc85ed00c5c64db ledgersmb-1.8.0.tar.gz
05616215e87de640d86457e2538a09d5d7abd7043b07c02a3266c66bd12ae29c ledgersmb-1.8.0.tar.gz.asc

Release 1.8
LedgerSMB_Team

1.7.20 Released

3 weeks 2 days ago
1.7.20 Released Security release No LedgerSMB_Team Fri, 09/04/2020 - 12:58 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.20/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.7.20

  • Fix Arabic being default language on Account creation (#4439)
  • Add Locale::Codes as explicit dependencies after removal from CORE
  • Fix invoices opened from payments screen missing CSS (#4890)
  • Add date-filter to Draft search filter screen
  • Fix amounts filter in Draft search not working (#4929)
  • Fix missing accounts in AR/AP transactions using 'Min Empty Lines (#4930)
  • Add 'select all' column toggle button to Draft search
  • Fix sequences returning 'invnumber' instead of sequence number (#4949)
  • Make AR/AP transaction sequence drop-down follow application style

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.7.20/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.20

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.20

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.20

These are the sha256 checksums of the uploaded files:

7df8195c6f2e2906bb2a8d3fb81e520c874054b4c9b3e130381d6773e69dcc52 ledgersmb-1.7.20.tar.gz
e673cd555e81d9208aecde38676f9c4b76e9768d144281dd5dd75381fce97833 ledgersmb-1.7.20.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.24 Released

3 weeks 2 days ago
1.6.24 Released Security release No LedgerSMB_Team Fri, 09/04/2020 - 12:15 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.24/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.6.24

  • Fix Arabic as standard language selection on Account creation (Erik H, #4439)
  • Add Locale::Codes explicit dependencies, due to removal from CORE (Erik H)
  • Fix invoice opened from payment screen missing CSS (Erik H, #4890)
  • Fix amount filters on Draft search not working (Erik H, #4929)
  • Fix sequences returning 'invnumber' instead of sequence number (Erik H, #4949)
  • Make AR/AP transaction sequence drop-down follow application style (Erik H)

Erik H is Erik Huelsmann

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.6.24/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.6.24

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.24

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.6.24

These are the sha256 checksums of the uploaded files:

ecf860bcfc551ab190f0f83d7559fb9981f1b2a1d48c9027af63153b49d364a3 ledgersmb-1.6.24.tar.gz
b7560670988df2bb80fd6689937595bbae8e9a967307288e3305afc126c9ba4c ledgersmb-1.6.24.tar.gz.asc

Release 1.6
LedgerSMB_Team

Installing LedgerSMB 1.8

3 weeks 2 days ago
Installing LedgerSMB 1.8 Installation from tarballs

This page contains the comprehensive version with the installation instructions for LedgerSMB 1.8 targetting a production installation from release tarballs and deals with these steps:

  • Installing the LedgerSMB Perl module dependencies
  • Configuring the PostgreSQL server
  • Configuring a webserver
  • Configuring LedgerSMB

If you already have all of the above, please proceed to the "Preparing for first use" guide.

These are not the Quick start instructions, but instructions for setting up a full production system. Also, please note that if you're in a position to use LedgerSMB's Docker images, or packages for your Unix/Linux distribution, using those will be far quicker and easier than following the instructions below.

Please note that installation of version 1.5 and up is completely different from the installation of versions 1.4 or earlier: This version uses Plack to handle integration with front-end web servers. This means LedgerSMB can now be run in combination with many web servers, including (but not limited to):

It's no longer possible to run LedgerSMB as set of CGI scripts. This should not be a big concern, since Plack allows plugging LedgerSMB into Apache using mod_fcgid, mod_fastcgi or mod_proxy all of which have been available for versions 2.0 and up.

Feel free to log in and share your experiences in the comments at the end of the article.

System requirements

Requirements are documented on the system requirements page.

Client

There are no specific requirements for LedgerSMB clients (web browsers) other than that they should have JavaScript enabled and be able to run Dojo 1.16.

A broad range of browsers is supported (Chrome, FireFox, Opera, ...), including Microsoft Internet Explorer (10 or newer) and Microsoft Edge.

Browsers explicitly not supported are:

  • Lynx
  • w3m
  • IE9 or earlier
Unpacking the release tarball

According to the Filesystem Hierarchy Standard, both /usr/local/ledgersmb and /opt/ledgersmb could be chosen as install locations. Unpack the tarball by running (as "root" user):

# tar xf ledgersmb-1.8.x.tar.gz --directory /usr/local/ Installing the LedgerSMB Perl module dependencies

Please note that some distributions (e.g. Fedora) do not by default install all core modules, but rather, install a subset. LedgerSMB doesn't list core modules as dependencies as they should be available.

The instructions below assume all dependencies will be installed from CPAN. It is however possible to install most modules from distribution repositories. The Docker image can be consulted for an example.

# Installation of LedgerSMB Perl dependencies from CPAN
cpanm --quiet --notest --with-feature=starman --installdeps /usr/local/ledgersmb/

Then, there are a number of features which need additional modules.
The above command includes the Starman Feature which is required for most installations.
The modules required for each feature can be installed by appending "--with-feature=" to the above command line.

These features are supported:

Feature Description latex-pdf-ps Enable PDF and PostScript output
Note: In order to make use of this functionality, the server must also have 'latex' or 'xelatex' installed. On many distributions, these packages are called 'texlive-latex' and 'texlive-tetex' respectively. latex-pdf-images Image size detection for PDF output starman Starman Perl/PSGI (standalone) web server openoffice OpenOffice.org document output edi (EXPERIMENTAL) X12 EDI support

 

# Installation of LedgerSMB Perl dependencies directly from CPAN
# With Starman and PDF & Postscript output

cpanm --quiet --notest --with-feature=starman --with-feature=latex-pdf-ps \
--installdeps /usr/local/ledgersmb/

Configuring the PostgreSQL server

There are only two requirements for the PostgreSQL database server. This section instructs how to configure an pre-installed PostgreSQL installation to meet those requirements. It's assumed that the LedgerSMB server and PostgreSQL are being run on the same system. The requirements to meet are:

  1. A database administrator user (in PostgreSQL called a 'role') for creation and administration of LedgerSMB company databases
  2. Authorization setup so the database administrator can log into the database through LedgerSMB's 'setup.pl' program
Creating the company database administrator account

The database administrator user account needs to have at the bare minimum:

  • The right to create databases (CREATEDB)
  • The right to create roles (CREATEROLE)
  • The right to log in (LOGIN)
  • A password to authenticate logins

The following command issued as root user, creates a user named "lsmb_dbadmin" (which isn't a super user):

# su - postgres -c 'createuser -S -d -r -l -P lsmb_dbadmin'
Enter password for new role: ************
Enter it again: ************

Configuring database access rights

PostgreSQL takes its access configuration through a file called 'pg_hba.conf'. The location of this file may differ per distribution:

  • Debian derivatives: /etc/postgresql///pg_hba.conf
  • RedHat derivatives: /var/lib/pgsql//data/pg_hba.conf

On most systems, this file has four effective lines:

local   all             postgres                                peer
local   all             all                                     peer
host    all             all             127.0.0.1/32            peer
host    all             all             ::1/128                 peer

These lines mean that each system user can connect to the database system with an equally named database user; the connecting source doesn't make a difference: unix and TCP/IP sockets have the same configuration.

The LedgerSMB software needs to be able to connect to the database system as 'lsmb_dbadmin' or as a LedgerSMB user, not as the user that runs the server process. The new content should look like:

local   all             postgres                         peer
local   all             all                              peer
host    all             postgres         127.0.0.1/32     reject
host    all             postgres        ::1/128      reject
host    postgres,template0,template1   lsmb_dbadmin         127.0.0.1/32     md5
host    postgres,template0,template1   lsmb_dbadmin         ::1/128      md5
host    postgres,template0,template1   all          127.0.0.1/32     reject
host    postgres,template0,template1   all          ::1/128      reject
host    all             all             127.0.0.1/32     md5
host    all             all             ::1/128          md5

This configuration takes advantage of the fact that each connection method (unix sockets vs TCP/IP sockets/addresses) can be separately configured. While the default connection method of the 'psql' tool is to connect over the 'local' (unix socket method), the default connection method for LedgerSMB is to use 'localhost' (127.0.0.1/32 or ::1/128).

The above configuration means that the user 'postgres' can't be used any longer to connect from 'localhost', no user can connect to the 'postgres' database through 'localhost' [reject] and all other combinations of users and database names need password authentication [md5].

Notes:

  1. PostgreSQL matches the lines first to last and uses the first matching line, so the order of the lines is very importance.
  2. For more information about the pg_hba.conf configuration options, see the PostgreSQL pg_hba.conf documentation
  3. The databases 'template1' and 'template0' are system databases available in every cluster; this configuration blocks those for access from LedgerSMB as well.

After reconfiguring pg_hba.conf, the PostgreSQL service needs to be restarted. this works with one of the following commands (depending on your distribution):

# restarting postgresql service (as root)
# service postgresql restart
# - or -:
$ service postgresql- restart

Verifying database access

To verify access for the database admin user 'lsmb_dbadmin', an accessible database - not named 'postgres', 'template0' or 'template1' - is required. On new installs, these are the only databases. So the next example creates one. Here's how to verify the setup:

# Verify access configuration (run as root)
$ su - postgres -c 'createdb lsmb_access_test_db'
$ psql -h localhost -U lsmb_dbadmin -d lsmb_access_test_db -c "select version()"
PostgreSQL 9.6.3 <--- this line indicates success("9.6.3" is just an example version number)
$ su - postgres -c 'dropdb lsmb_access_test_db'

Configuring a web server

Regardless of your web server setup, configuration of an "application server" is required. The application server used with LedgerSMB can be any PSGI compatible server. The default application server is Starman, which is widely considered the fastest available. The Starman server process lives behind a reverse proxy. While Starman deals specifically with those HTTP requests which require "application logic", all other requests (mostly static content, such as images or CSS) are dealt with by the proxy.

Configuring the Starman application server

Depending on the distribution, a startup method must be installed; this can be one of:

  • SysV init script
  • Upstart configuration
  • Systemd configuration

At the time of writing, the only configuration that comes with LedgerSMB's tarball is the systemd configuration. The following common setup is required regardless of the system used to manage services on the target system.

To support priviledge separation, the Starman server should be running as a user which meets these criteria:

  • Not the same user as the web server
  • Does not have write access to the LedgerSMB directories

To that extent, identify an existing (unused) system user, or create one with this command:

# create 'ledgersmb' user for Starman server to run
$ useradd -d /non-existent -r -U -c "LedgerSMB/Starman service system user" ledgersmb

Configuring systemd for Starman

In the directory conf/systemd/ from the tarbal, there is a preconfigured systemd service file, which needs to be copied into place. In case you decided to install dependencies into a local::lib, the service file needs to be edited to set a PERL5LIB environment variable before you can succesfully start the service.

# 'copy' systemd service configuration, enable and start
$ sed -e "s#WORKING_DIR#$PWD#" conf/systemd/ledgersmb_starman.service \
| sudo tee /etc/systemd/system/ledgersmb-starman.service
$ systemctl enable ledgersmb-starman
$ service ledgersmb-starman start

Note that the above assumes that the commands are being run from the root of the unpacked tarball. It also assumes that the tarball has been unpacked at its installation path.

To verify that the service started up correctly, run:

# verify that the Starman/LedgerSMB server started correctly
$ journalctl -u ledgersmb-starman.service --since="today" -l -e

Configuring a reverse proxy

For a quick test-run or demo setup running on localhost only, configuration of a proxy isn't mandatory. However, for a production setup with LedgerSMB being network or even web-exposed, it's ill-advised to run without the reverse proxy for - at least - the following reasons:

  • The proxy can serve static content [much] more efficiently (performance)
  • The proxy can support HTTP/2 which multiplexes requests (performance)
  • The proxy guards Starman against public exposure (security)
  • The proxy adds TLS (security)

With TLS certificates being completely free these days through Let's Encrypt, and only a few dollars for the simplest of certificates from commercial vendors, there's really no reason not to secure traffic to the server. Further documentation below assumes you have such a certificate. As for getting Let's Encrypt certificates, use their Getting Started guide.

For simplicity, only the configuration of nginx as a reverse proxy is documented here.

Configuring nginx

The tarball contains an example virtual host configuration file to set up a reverse proxy with nginx. It needs to be included in the 'http { }' block in your nginx configuration. On Debian derived systems, this is done by copying the file to /etc/nginx/sites-available/ledgersmb.conf. On RedHat/Fedora derivatives, the copying goes to /etc/nginx/conf.d/ledgersmb.conf. After editing the file, replacing the following variables:

  • Same replacement as before
  • SSL_CERT_FILE
    Should be where your certificate file is stored; probably /etc/certs/your_host.example.com.pem
  • SSL_KEY_FILE
    Probably the same as the SSL_CERT_FILE, but with '.key' extension
  • YOUR_SERVER_NAME
    If nothing else, should be replaced by the output of the command 'hostname -f'

NOTE: by default snakeoil certificates will be used by at least our nginx sample config files.
These certificates are locally created and will normally require your browser clients to override something before they can be used.

On Debian derivatives, activate this file after it has been edited, using:

# On Debian/Ubuntu/Mint activate the virtual host
$ ln -s /etc/nginx/sites-available/ledgersmb.conf /etc/nginx/sites-enabled/

On RedHat/Fedora derivatives, no symlinking is necessary: the configuration is active immediately. Now, verify that the configuration is acceptable:

# (Re)start nginx service to make nginx reconfigure itself and validate configuration
$ service nginx restart

Configuring LedgerSMB

The tarball has a default LedgerSMB configuration file conf/ledgersmb.conf.default. Install the configuration file with:

# Install the default ledgersmb.conf configuration file
$ cp conf/ledgersmb.conf.default ledgersmb.conf

That is it.

In case the in-app e-mail feature is going to be used, check the values in the [mail] section and optionally adjust for the mail setup of the target system.

Next steps

Now follow the instructions in the "Prepare LedgerSMB for first use" guide.

ehu Fri, 09/04/2020 - 11:34
ehu

Does LedgerSMB support "sub-accounts"?

1 month 4 weeks ago
Does LedgerSMB support "sub-accounts"?

Yes. LedgerSMB has a mechanism called "Account headings". The headings are the opposite of what Intuit explains about Quickbooks for their subaccount support: Quickbooks splits an account into multiple and aggregates those new accounts into the old one for reporting. To achieve the same in LedgerSMB, you create multiple accounts and one or more headings. LedgerSMB then aggregates the totals of the accounts per heading. The system used by LedgerSMB closely resembles what MYOB describes about their accounts and headers.

ehu Thu, 07/30/2020 - 09:50 Release 1.5 1.6 1.7 1.8 FAQ Category Accounting
ehu

Upgrade to LedgerSMB 1.8

1 month 4 weeks ago
Upgrade to LedgerSMB 1.8 Overview

Company database upgrades are supported all the way back from 1.4 directly to 1.8, using the 1.8 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.8 structure, while upgrades adjust the existing structure for 1.8. When upgrading from versions earlier than 1.7, please read the release notes and upgrade instructions of those versions: those instructions still apply but are not repeated here.

Before starting, please remember:

  • Create a backup
  • Don't do this in a hurry
  • When running into problems, check out the "Support" page
Technical upgrade

Upgrading the software works the same as with prior versions. Please refer to the procedure to upgrade a tarball installation for 1.7 for the 1.8 upgrade. Be sure to install the new Perl module dependencies listed in the Changelog. Also note that the Docker image definition contains a comprehensive list of Debian Buster package dependencies.

Company database upgrade

Technically, this process hasn't changed since 1.7 and the instructions for 1.7 still apply.

Each new LedgerSMB release has tightened the checks on validity of the data stored in the database. 1.8 continues on that path and adds yet more checks - this helps us find bugs and prevents undesirable data entering into the ledger. During the upgrade, existing data is checked against these new quality criteria and optionally offered for correction (or deletion, depending on the type of inconsistency).

Before you begin:

  • Verify that all Reconciliation Reports have been either approved or deleted
    If you forget this step, the migration will offer to delete it for you; approval isn't supported during migration. Note that this does not refer to transactions; unapproved transactions can safely exist during upgrade.
  • Create a backup
  • Tell users not to use your system during upgrade

 

ehu Mon, 07/27/2020 - 23:11 Topic Upgrade Upgrading Release 1.4 1.5 1.6 1.7 1.8
ehu

1.8.0-beta3 Released

2 months ago
1.8.0-beta3 Released Security release No LedgerSMB_Team Sat, 07/25/2020 - 03:06 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.8.0-beta3/

In preparation of the final release of LedgerSMB 1.8, the release branch has been created for a period of stabilization. In order to release the most stable version released by the project ever released, a preview version was published earlier today: 1.8.0-beta3.

Users are encouraged to download the Docker images (tag: ledgersmb/ledgersmb:1.8) or the tarball (https://download.ledgersmb.org/f/Beta%20Releases/1.8.0-beta3/) for evaluation purposes. Bugreports either in response to this mail or as GitHub issues are highly appreciated!

The 1.8 release shifts away from HTTP Basic authentication, using encrypted cookies instead. This eliminates the popup authentication dialog on expired sessions. Additionally, does it provide a broader range of settings for outgoing e-mail and has support been added to upload logos and other files which can be used in downloadable documents.

Please test LedgerSMB 1.8.0-beta3 with your use-cases (but not in production) and report any issues you're experiencing so they can be fixed before the final 1.8.0 release!

Release 1.8
LedgerSMB_Team

1.7.18 Released

2 months ago
1.7.18 Released Security release No LedgerSMB_Team Sat, 07/25/2020 - 02:43 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.18/

The LedgerSMB development team is happy to announce yet another new
version of its open source ERP and accounting application.
This release contains the following fixes and improvements:

Changelog for 1.7.18

  • Fix payment posting due to number formatting errors (#4781)
  • Fix payment posting due to date formatting errors (#4794)
  • Fix posting reversal of sales invoice after assembly reversal (#4791)
  • Fix overpayment reversal failing to post (#4803, #4816)

For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.7.18/README.md

The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.18

The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.18

Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.18

These are the sha256 checksums of the uploaded files:

d01428d034431a4f31cffaebeee26181e678097dbb6b471cde196ac34258ee1e ledgersmb-1.7.18.tar.gz
250fd6cb59571d19de7dd03d40976aee1def063ad6013b74e6a751dca0c4b136 ledgersmb-1.7.18.tar.gz.asc

Release 1.7
LedgerSMB_Team

How do I migrate my existing books to LedgerSMB?

2 months 4 weeks ago
How do I migrate my existing books to LedgerSMB?

There are two strategies in migrating your books to between accounting solutions in general:

  1. Choose a cut-off point and migrate your balance sheet and income statement per that day as an opening balance
  2. Migrate the complete history of the books from the old solution to the new one

These approaches apply even when the source is a spreadsheet (i.e. "manual") and LedgerSMB is the target. The second approach requires a full mapping of data from the source system to the target. This is usually quite involved and a reason not to use it. On the other hand, businesses are generally required to retain their records for a specific amount of time (multiple years, for audit purposes) and the second approach migrates the history-to-be-retained to the target system. With the first approach, a separate solution needs to be found to retain the required history.

Steps to migrate your opening balances into LedgerSMB

The goal of the migration is to "cut-over" accounting as per the chosen date. The general approach to that is to create an opening balance and opening income statement per that date and continue from there. Generally, a natural date to be chosen for such a cut-over is at the year-end when the income statement starts out clean for the year to come and an opening balance is created in the balance sheet.

The above works for relatively simple balance accounts such as a bank account or petty cash. When the account is a summary of underlying items, this approach is more problematic: in order to pay invoices, the system needs to know about them; migrating the total balance doesn't work well. The same applies to inventory where available inventory attributes to Cost Of Goods Sold (COGS) on a FIFO basis.

To construct a beginning balance with sufficient detail to support a complete cut-over, I have followed these steps:

  1. Set up your chart of accounts
  2. Migrate fixed assets
    1. Create the assets at their original value at the acquisition or depreciation start-date using their original depreciation scheme
    2. Run depreciation all at once on the day before migration resulting in the correct fixed asset account balance
  3. Migrate inventory
    1. Identify when remaining stock was acquired (in order to initialize COGS)
    2. Set up "Goods & Services > Parts" for stock to be migrated
    3. Create an import file listing per day which items in stock were acquired and at what price
      • From the file above, exclude any stock from unpaid invoices; it will be added in the next step
      • Note that for assemblies "acquisition date" should be interpreted as "production date" -- the date the assembly was entered into inventory
    4. Import the file into the system (how)
  4. Migrate open invoices
    1. Create customers and vendors at the bare minimum for which there are open invoices
    2. Create open sales and purchase invoices at their original creation dates
    3. Apply payments to the invoices on the original payment dates
  5. Migrate the remaining balance
    1. Subtract the balances in the accounts in the new system from the balances to be migrated
    2. Create a GL transaction on the date before the cut-over with the calculated differences
    3. Post the GL transaction
    4. Verify the migrated numbers by running a balance sheet on the day before cut-over
    5. The numbers should be the same as those in the original balance
  6. Freeze the migration balance to prevent hampering
    1. Go to "General Journal > Year End", tab "Close Period"
    2. Enter the date before the cut-over in "Close As-of"
    3. Click "Close Period"

Lets say that the cut-over date is "2020-01-01"; then the date to close the books at is "2019-12-31". After completing the procedure above, no transaction can be entered or modified before or at "2019-12-31", making this a truely static opening balance.

 

ehu Mon, 06/29/2020 - 13:23 Topic Installation setup Administration Release All Versions
ehu