Aggregator

How do I migrate my existing books to LedgerSMB?

1 week 4 days 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

I want to switch to LedgerSMB, but I have unpaid invoices. What to do?

1 week 4 days ago
I want to switch to LedgerSMB, but I have unpaid invoices. What to do?

The general approach is to migrate invoices first, creating them as they exist in the current accounting solution. Then, differences with the intended balance can be calculated and the remainder posted at-once. For more comprehensive explanation see How do I migrate my existing books to LedgerSMB?

ehu Mon, 06/29/2020 - 11:33 Release All Versions FAQ Category Installation Topic Installation setup Administration
ehu

1.7.17 Released

1 week 4 days ago
1.7.17 Released Security release No LedgerSMB_Team Mon, 06/29/2020 - 11:01 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.17/

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.17

  • Fix reversals of purchases failing to post due to COGS error (#4771)
  • Fix assemblies failing to save after 'Update' (#4755)

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

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

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

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

These are the sha256 checksums of the uploaded files:

64b0cb0fd7c8df1047df633eedab9d135c2df34e71c6569fda2f4fea262fa98a ledgersmb-1.7.17.tar.gz
ec858fa508b1faa890c32b027f1cb06bee30d73519aac48450bb9f1a9ab55122 ledgersmb-1.7.17.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.23 Released

1 week 5 days ago
1.6.23 Released Security release No LedgerSMB_Team Mon, 06/29/2020 - 02:10 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.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.6.23

  • Fix reversals of purchases failing to post due to COGS error (Erik H)

Erik H is Erik Huelsmann

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

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

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

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

These are the sha256 checksums of the uploaded files:

8d6a956967d8ee4e31f1d10c42357c9f1217281ed2435797cbfd0eda0a9c41b2 ledgersmb-1.6.23.tar.gz
48f701467022aaa3261c91825c95fd0ae1f5778476cc36bf5c5904912a42e9bc ledgersmb-1.6.23.tar.gz.asc

Release 1.6
LedgerSMB_Team

1.7.16 Released

2 weeks 5 days ago
1.7.16 Released Security release No LedgerSMB_Team Sun, 06/21/2020 - 14:18 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.16/

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.16

  • Fix migration including NULL and zero exchange rate defaults (#4673)
  • Fix AR Outstanding report showing negative taxes (#4688)
  • Remove dev-mode server-killing /stop URL (#4705)
  • Fix GL journal creation silently inserting 2 'gl' records (#4719)
  • Fix sorting hierarchical balance sheet and income statement sections (#4740)
  • Update Dojo dependency to 1.15.4
  • Add SameSite policy on session cookie to prevent being ignored (#4748)

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

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

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

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

These are the sha256 checksums of the uploaded files:

cb07f541d7dcf9783617702ede423e6ae563b21d6b713357e9ba59208a73a577 ledgersmb-1.7.16.tar.gz
1c83342bac95b86bbb4826f4de881573c12e3dace8f3efd9cd8e7b1458aff68d ledgersmb-1.7.16.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.6.22 Released

2 weeks 5 days ago
1.6.22 Released Security release No LedgerSMB_Team Sun, 06/21/2020 - 14:03 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.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.6.22

  • Update Dojo toolkit dependency to 1.13.8 (Erik H)
  • Fix sorting of hierarchical income statement and balance sheet (Erik H)
  • Fix columns not being populated in AR/AP Outstanding report (Erik H)
  • Add SameSite policy on session cookie to prevent being ignored (Erik H)

Erik H is Erik Huelsmann

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

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

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

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

These are the sha256 checksums of the uploaded files:

8a32c183432cdf655c536d521c6951e8e0e0265d0c1ec92d77c161061e354a9e ledgersmb-1.6.22.tar.gz
ce8fa58f30a8fed180ffb41740fc6c33ec02214b06e70d31410c9206d8b62fc2 ledgersmb-1.6.22.tar.gz.asc

Release 1.6
LedgerSMB_Team

Installing latest LedgerSMB using Docker Compose

3 weeks ago
Installing latest LedgerSMB using Docker Compose

By far the fastest procedure for installing LedgerSMB is by using the published Docker images: Being an ERP, there are many dependencies to be installed and all of them are included in the images, with the exception of the required PostgreSQL database. There are two ways to provide the PostgreSQL functionality: by setting up a separate PostgreSQL server or by using a PostgreSQL-providing Docker container.

This article describes the latter option to use a second Docker container to provide the PostgreSQL server. The instructions below assume installed Docker and Docker Compose. Many tutorials to install them float around on the web; e.g. these instructions from DigitalOcean to install docker-compose.

  1. git clone https://github.com/ledgersmb/ledgersmb-docker.git
    This checks out the docker-compose file which will install the latest production version; if you want to use an older version, e.g. 1.6, add the -b option:
    git clone -b 1.6 https://github.com/ledgersmb/ledgersmb-docker.git
  2. cd ledgersmb-docker
  3. docker-compose pull
  4. docker-compose up -d
    Note that the "-d" is important: it starts the containers in the background; without it, the containers' logs will be shown in the terminal. They can be terminated with Ctrl-C, but that also terminates the containers

    After the steps above, LedgerSMB should be available on http://127.0.0.1:5762/
  5. apt-get install apache2 certbot python-certbot-apache
  6. certbot certonly  --apache -d example.com -d www.example.com
  7. grab the .conf from the LedgerSMB code repository and edit it:
    1. curl https://raw.githubusercontent.com/ledgersmb/LedgerSMB/master/doc/conf/apache-vhost.conf -o /etc/apache2/sites-available/ledgersmb.conf
    2. nano /etc/apache2/sites-available/ledgersmb.conf:
      1. Replace YOUR_SERVER_NAME with your server name; e.g. "example.com"
      2. Replace SSL_CERT_FILE, SSL_KEY_FILE, and SSL_CHAIN_FILE with the corresponding files in /etc/letsencrypt/live
      3. Replace http://localhost:5762 with http://127.0.0.1:5762
        When your server has IPv6 enabled, the former will resolve to ::1, on which the container created above, isn't available
      4. Finally, remove the DocumentRoot line with WORKING_DIR
  8. a2ensite ledgersmb
  9. a2enmod ssl rewrite proxy proxy_http
  10. systemctl restart apache2

 

 

ehu Sat, 06/20/2020 - 04:48 Topic Installation Release 1.6 1.7 1.8
ehu

Preparing LedgerSMB 1.8 for first use

1 month 1 week ago
Preparing LedgerSMB 1.8 for first use

This page explains how to set up LedgerSMB's first company after having completed installation, e.g. through the docker-compose.yml file. Please note that your full URL may differ depending on your installation method.

In case you just completed the quick-start instructions, the base URL at which LedgerSMB is accessible is http://localhost:5762 (If you have a full production setup, you shouldn't need the port indicator [the ":5762" part]). There are two URLs (entry-points) you can use to access the application:

  • /setup.pl [full URL: http://localhost:5762/setup.pl ]
  • /login.pl [full URL: http://localhost:5762/login.pl ]

The two entry points each serve their own purpose: setup.pl is the main tool for the database admin (lsmb_dbadmin); it serves to create new companies, create copies of companies, add users to companies and reset user's passwords. login.pl provides access to all other types of users.

Creating the first company

After browsing to setup.pl, the browser should show:

In case the screen only shows the "Database" field, this indicates problems with JavaScript not having loaded correctly. Fill out the fields as follows:

  • Super-user login: lsmb_dbadmin
  • Password:
  • Database: testcompany

Confirm the screen by clicking "Create". When the server is done creating the database for the company, a new screen will be returned. This can take up to 20 seconds.

The resulting screen shows:

Click "Skip" in order to skip loading a pre-defined Chart of Accounts. Select a country code and click Next to list the pre-defined charts of accounts.

The resulting screen then shows a list of available Charts of Accounts:

The screen above isn't shown when "Skip" was selected in the step before. Clicking "Skip" in this screen skips loading a pre-defined chart of accounts.

Regardless of whether CoA loading was skipped or performed, the following screen will be presented:

Select 'demo' templates for use with LaTeX; select 'xedemo' templates for use with XeLaTeX (which has better support for UTF-8 / accented characters and non-latin character sets). The exact choice made in this step is not highly important: templates can later be changed by loading new ones into the database. After confirming the selection by clicking "Load Templates", the following screen shows:

With this screen, the first user for this company gets created. There are two modes:

  • Import (Yes): Assumes the username already exists in the database (e.g. because it is already used for another company; re-uses the existing username+password)
  • Create (No): Assumes the username does not already exist; will create a new username

The "Assign Permissions" selection determines the rights assigned to the user:

  • "Full Permissions": The user may perform any task in the application
  • "Manage Users": The user has just enough rights to create new users who have appropriate rights

For the purpose of this quick-start guide, enter the following details:

  • Username: first_user
  • Password: first_user
  • Import: No
  • Salutation: Mr
  • First Name: First
  • Last Name: User
  • Employee Number: 1
  • Date of Birth: (today's date)
  • Tax ID/SSN: 1
  • Country: (your country)
  • Assign Permissions: Full Permissions

After confirming these data by clicking the "Create User" button, the following screen shows:

First user login

The "Start Using LedgerSMB" link opens the main application login screen, which can be used to log in using the initial user created above:

Confirming login results in the following page*:

* Note that the picture shows company name "test10", but when succinctly following the instructions, it should show "testcompany".

Database administration of first company

Once the testcompany has been created, it can be logged into through setup.pl as well as through login.pl. When logging in through setup.pl, the following screen with database administration functions shows:

What's next?

The system is now set up for evaluation and testing. The project has multiple channels to contact other users or the developers. Read all about that on the community project resources page.

Any comments as to this specific article? Please sign up to the site and leave your comments below!

ehu Mon, 06/01/2020 - 00:46 Topic Draft
ehu

1.8.0-beta1 Released

1 month 1 week ago
1.8.0-beta1 Released Security release No ehu Sun, 05/31/2020 - 13:58 Release candidate Yes Download https://download.ledgersmb.org/f/Beta%20Releases/1.8.0-beta1/

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-beta1.

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-beta1/) 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-beta1 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
ehu

1.7.15 Released

1 month 1 week ago
1.7.15 Released Security release No ehu Sun, 05/31/2020 - 13:55 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.15/

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.15
* Fix tax on invoice differs from search results (#4651)
* Fix COGS for purchased-in-arrears parts (#4658)
* Update Dojo to 1.15.3

IMPORTANT

The COGS fix addresses a bug which results in incorrect accounting
in case inventory is used and parts are sold before they are
purchased. This problem doesn't impact services or GL-only accounting.

While this fix addresses the core problem, it doesn't fix any data
that may have been recorded incorrectly! If you use inventory and
have sold parts before buying them (such that inventory ended up
being negative), LedgerSMB may have debited income and credited
expenses instead of crediting inventory and debiting expenses.
This leads to too high inventory, too low income and too low expenses.
The LedgerSMB team recommends consulting an accountant if this bug
affects your books or contact a LedgerSMB consultant to identify if
your books are affected (e.g. from
https://ledgersmb.org/content/commercial-support).

Downloads

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

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

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

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

These are the sha256 checksums of the uploaded files:

868cfb31edfb62a404d5f264327c84e5ea5999aeb56a4adac5c7ac532c156f8d ledgersmb-1.7.15.tar.gz
f28a92326f99a4440f1be9ba74187ae4e61101a28262b8287ac8fca08e3e6d11 ledgersmb-1.7.15.tar.gz.asc

Release 1.7
ehu

1.6.21 Released

1 month 1 week ago
1.6.21 Released Security release No ehu Sun, 05/31/2020 - 13:54 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.6.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.6.21

  • Fix COGS for purchased-in-arrears parts (Erik H)
  • Update Dojo toolkit dependency to 1.13.7 (Erik H)

Erik H is Erik Huelsmann

IMPORTANT

The COGS fix addresses a bug which results in incorrect accounting
in case inventory is used and parts are sold before they are
purchased. This problem doesn't impact services or GL-only accounting.

While this fix addresses the core problem, it doesn't fix any data
that may have been recorded incorrectly! If you use inventory and
have sold parts before buying them (such that inventory ended up
being negative), LedgerSMB may have debited income and credited
expenses instead of crediting inventory and debiting expenses.
This leads to too high inventory, too low income and too low expenses.
The LedgerSMB team recommends consulting an accountant if this bug
affects your books or contact a LedgerSMB consultant to identify if
your books are affected (e.g. from
https://ledgersmb.org/content/commercial-support).

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

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

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

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

These are the sha256 checksums of the uploaded files:

d64ae4d5a457a8bc6096982b0fde6d8002df29b59831a0940136519b915ed482 ledgersmb-1.6.21.tar.gz
2cca4d598c02e701c0e80e562ce7c23f83ce40f8aadc1ea27b40273311b0ddc0 ledgersmb-1.6.21.tar.gz.asc

Release 1.6
ehu

1.7.14 Released

1 month 1 week ago
1.7.14 Released Security release No ehu Sun, 05/31/2020 - 13:53 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.14/

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.14

  • Fix AR/AP account being reset to default on transaction Update-s (#4599)
  • Fix CSV, ODS or TXT reports being downloaded without extensions (#4613)
  • Fix 'To pay' amount resetting on second updates in single payments (#4633)
  • Fix 'Paid' amount incorrect when 'Apply discount' unchecked (#4514)
  • Fix income statement failing to filter on invoice reporting units (#4615)
  • Fix payment discount not being posted (#4616)
  • Fix tax base and amount doubled on printed invoice (#4645)

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

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

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

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

These are the sha256 checksums of the uploaded files:

3d66daeaf62e6c236d168619d8ebf2f5f7e2adf4505c36f334ec507445614d48 ledgersmb-1.7.14.tar.gz
5969e1e883cc8339d501f74ed91da1479519237f18fd2f1fdca2874b1c338710 ledgersmb-1.7.14.tar.gz.asc

Release 1.7
ehu

1.7.13 Released

1 month 1 week ago
1.7.13 Released Security release No ehu Sun, 05/31/2020 - 13:50 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.13/

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.13

  • Fix listing asset classes throwing an error (#4569)
  • Solve failure to create initial user by requiring input (#4525)
  • Fix links at the bottom of the CoA screen (#4568)
  • Fix CoA export (ODS, XLS or XLSX) throwing malformed XML error (#4580)
  • Fix downloaded reports missing extension (e.g. '.pdf') (#4584)
  • Improve performance of deleting batches (#4449)
  • Fix error thrown when opening reporting unit 'edit' screen (#4592)
  • Fix transdate being NULL in journal lines from bulk payments (#4587)

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

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

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

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

These are the sha256 checksums of the uploaded files:

2378fa5870bad1d6a2f3098f27e3842e7d77c6062b8b77fd19396ae455386be5 ledgersmb-1.7.13.tar.gz
ab8871c030f8fc458997e967591c65539fe9b46ddab1179b3de1d28327245ce2 ledgersmb-1.7.13.tar.gz.asc

Release 1.7
ehu

Preparing LedgerSMB 1.7 for first use

1 month 1 week ago
Preparing LedgerSMB 1.7 for first use

This page explains how to set up LedgerSMB's first company after having completed installation, e.g. through the docker-compose.yml file. Please note that your full URL may differ depending on your installation method.

In case you just completed the quick-start instructions, the base URL at which LedgerSMB is accessible is http://localhost:5762 (If you have a full production setup, you shouldn't need the port indicator [the ":5762" part]). There are two URLs (entry-points) you can use to access the application:

  • /setup.pl [full URL: http://localhost:5762/setup.pl ]
  • /login.pl [full URL: http://localhost:5762/login.pl ]

The two entry points each serve their own purpose: setup.pl is the main tool for the database admin (lsmb_dbadmin); it serves to create new companies, create copies of companies, add users to companies and reset user's passwords. login.pl provides access to all other types of users.

Creating the first company

After browsing to setup.pl, the browser should show:

In case the screen only shows the "Database" field, this indicates problems with JavaScript not having loaded correctly. Fill out the fields as follows:

  • Super-user login: lsmb_dbadmin
  • Password:
  • Database: testcompany

Confirm the screen by clicking "Create". When the server is done creating the database for the company, a new screen will be returned. This can take up to 20 seconds.

The resulting screen shows:

Click "Skip" in order to skip loading a pre-defined Chart of Accounts. Select a country code and click Next to list the pre-defined charts of accounts.

The resulting screen then shows a list of available Charts of Accounts:

The screen above isn't shown when "Skip" was selected in the step before. Clicking "Skip" in this screen skips loading a pre-defined chart of accounts.

Regardless of whether CoA loading was skipped or performed, the following screen will be presented:

Select 'demo' templates for use with LaTeX; select 'xedemo' templates for use with XeLaTeX (which has better support for UTF-8 / accented characters and non-latin character sets). The exact choice made in this step is not highly important: templates can later be changed by loading new ones into the database. After confirming the selection by clicking "Load Templates", the following screen shows:

With this screen, the first user for this company gets created. There are two modes:

  • Import (Yes): Assumes the username already exists in the database (e.g. because it is already used for another company; re-uses the existing username+password)
  • Create (No): Assumes the username does not already exist; will create a new username

The "Assign Permissions" selection determines the rights assigned to the user:

  • "Full Permissions": The user may perform any task in the application
  • "Manage Users": The user has just enough rights to create new users who have appropriate rights

For the purpose of this quick-start guide, enter the following details:

  • Username: first_user
  • Password: first_user
  • Import: No
  • Salutation: Mr
  • First Name: First
  • Last Name: User
  • Employee Number: 1
  • Date of Birth: (today's date)
  • Tax ID/SSN: 1
  • Country: (your country)
  • Assign Permissions: Full Permissions

After confirming these data by clicking the "Create User" button, the following screen shows:

First user login

The "Start Using LedgerSMB" link opens the main application login screen, which can be used to log in using the initial user created above:

Confirming login results in the following page*:

* Note that the picture shows company name "test10", but when succinctly following the instructions, it should show "testcompany".

Database administration of first company

Once the testcompany has been created, it can be logged into through setup.pl as well as through login.pl. When logging in through setup.pl, the following screen with database administration functions shows:

What's next?

The system is now set up for evaluation and testing. The project has multiple channels to contact other users or the developers. Read all about that on the community project resources page.

Any comments as to this specific article? Please sign up to the site and leave your comments below!

ehu Sun, 05/31/2020 - 02:00 Release 1.7
ehu

Year overview 2019

1 month 2 weeks ago
Year overview 2019

Here's my continuing the tradition to write about the state of the project on each year end.

== Community interest ==   The hits on our web site show a stable line month-on-month, although lower than last year. Consensus has it that traditional websites get lower numbers of hits than several years ago because of mobile and other (social) media. Hits seem to be pretty stable now.   During the year, we've seen the number of Watchers, Stars and Forks on GitHub slowly but steadily increase. Traffic seems to be slightly up on our mailing lists, the users mailing list especially, with questions from new users installing and configuring LedgerSMB.   The number of active developers is a bit lower, than last year; some hang around in our chat channel to help evaluate changes submitted by active members, though.   All in all, the community seems to be on-boarding potential and new users and experiencing its regular in- and outflux of developers.   == Releases ==   Last year we hoped to release 1.7 in the first half of the year. With the release of 1.6.0  on June 10 2018, we hoped to be able to start doing yearly releases. We also expressed the hope to land the MC branch on master. We ended up releasing 1.7 on October 4 2019, a little less than 16 months after 1.6.0. We did reduce the release cycle, but not by as much as we'd hoped. In part, the longer-than-hoped-for release cycle was caused by the fact that the MC branch did land on master, which warranted additional test effort, especially of the database migration scripts against real-world data.   All in all we released around the same number of times as we did in 2018:  
  • 10 stable releases:
    • 1.7.0 - 1.7.6
    • 1.6.10 - 1.6.12
  • 11 old-stable releases:
    • 1.6.13 - 1.6.17
    • 1.5.25 -1.5.30
== Packaging and installation ==   In preparation for the 1.7 release, some work was done on the Docker images to run on Debian Buster. However, we found that Buster deprecated the ssmtp package which we depended on and it was too late in our own release cycle to do any fundamental changes to our e-mail functionality. We ended up going back to Stretch to run 1.7 on. Further work will be required to make sure 1.8 offers similar functionality without depending on ssmtp.   The Debian ledgersmb package for 1.6 transitioned to Buster. Which is great as Debian Stable now has a non-deprecated version in its package repository. Last week we found that the package unfortunately misses a few files. We hope to fix that really soon.   == Development progress ==   Over the course of 2019, 40 issues were created, 19 of which remain open at this point. All 19 issues were created by the development team, many in the process of doing code reviews or development work. A total of 73 issues were closed in 2019, including issues created in prior years. From these numbers, we can see that now that the MC branch has been merged, there's time or room to work on issues not directly related to MC or the creation of infrastructure to support MC development.   The development work spun off 304 pull requests on the LedgerSMB repository. The number of pull requests is a lot lower than in 2018 when the number was around 480. The 304 PRs triggered nearly 1000 builds on Travis CI. During the first half of the year, we developed large numbers of new tests, push coverage up from 34% in last year's report to 41% now. Although 41% still is by far not enough, we started to run into the limits of what Travis CI was able to provide us (which is: maximum of 50 minutes of run-time on each test job). We evaluated a number of other CI providers, including the option to run our own. We ended up going for CircleCI; to their service we moved our longest running test job (we left the others at TravisCI), because they account the total time to be spent by a project differently.   Areas that we're currently spending time on, include:  
  • Selection of a new translation engine which supports more than 2 plural forms
  • Building on last year's separation between printed-document templates and UI templates,
    moving more printed documents into the framework
  • Gradual polishing of 1.7 through regular fixes of issues left to be polished after 1.7.0 release
  • Polishing of the technical implementation and user experience of payments and receipts
  The 334 issues that are open today summarize into these statistics:  
  • 71 are marked bite-sized; this means they should be good places to start for new-comers
  • 188 are marked as desirable enhancements
  • 43 are marked as being in our queue of design work
  (Note that an issue may fall into more than one category.) == New functionality and improvements ==   A long-standing desire was to remove code duplication in templates to generate output tables. This year, we managed to move all code using the old report table infrastructure to the new code base. While doing so, we also cleaned up fixed assets code.   Another topic that we spent time on, is research on how other PostgreSQL based projects structure their authentication. One project that drew our attention was Graphile (https://www.graphile.org/). From their approach, we've come up with an approach that may help us simplify setting up the database connections and managing / reporting password expiry on login.   == Looking forward to 2020 ==   In 2020, we'll likely release 1.8 in the second half of the year. I personally hope that we can shorten the release cycle to get to yearly releases around the middle of the year. With that schedule it'll leave a number of patch releases until the end of the year, allowing users to migrate to a stable release after closing their books at the end of the year (if they didn't migrate earlier already).   For 2020, I'm also hoping that the idea to work concentrate on specific topics, moving from topic to topic to improve the software, leads to an attractive 1.8 release. The various topics have been grouped into GitHub "projects" (https://github.com/ledgersmb/LedgerSMB/projects). Topics that have my personal priority are "Payment/payment_link support for all parts of the code base" and "Polish cash and payments". The first is rather technical in nature and a prerequisite to address the issues collected into the second. For 2020, I'm hoping to complete at least one, but hopefully both projects.   For 2020, I'm hoping for 1 or 2 new contributors (not necessarily developers; translators, testers, documenters or UI artists are all greatly appreciated!). If you want to contribute, but don't know where to start, please contact me.     Leaves me only to wish everybody in our community - and their loved ones - a very good, healthy and prosperous 2020! ehu Mon, 05/25/2020 - 13:24
ehu

1.7.12 Released

2 months 1 week ago
1.7.12 Released Security release No LedgerSMB_Team Mon, 04/27/2020 - 09:49 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.12/

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.12

  • Reconciliation reports list now shows usernames rather than user ids (#4388)
  • Single payment interface throws error without open invoices (#4529)
  • Fix CSV data imports discading the first row (#4567)
  • Improve Chart of Accounts import no longer discards heading (#4567)

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

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

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

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

These are the sha256 checksums of the uploaded files:

9f25e4a4ff7ac15d4cef7f9d615548b9866fc41fe40d5891c34b1d802157e532 ledgersmb-1.7.12.tar.gz
6537bd20015615a9f10e42e72bc9e1bb8d8a8d039152c2bf41a280100e97d50d ledgersmb-1.7.12.tar.gz.asc

Release 1.7
LedgerSMB_Team

1.7.11 Released

2 months 4 weeks ago
1.7.11 Released Security release No LedgerSMB_Team Sat, 04/11/2020 - 12:21 Release candidate No Download https://download.ledgersmb.org/f/Releases/1.7.11/

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.11

  • Fix inventory adjustments failing to update balances (#4467)
  • Fix inability to delete individual vouchers from a batch (#4448)

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

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

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

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

These are the sha256 checksums of the uploaded files:

8df5172a1360e30ae8513766d3c42a2b0612c07f8e2810d0c55c59a9fe67dde2 ledgersmb-1.7.11.tar.gz
94417b9baedee37f76f5578e15e4fd8ce0a3a4870b174008d4c6bc987c1ce4ad ledgersmb-1.7.11.tar.gz.asc

Release 1.7
LedgerSMB_Team