- users - lists.freelock.com

questions re: inventory and inventory management
by o1bigtenor 19 Jan '22

19 Jan '22

Greetings Looking at the possible use of ledgersmb. Inventory and inventory management get to be quite useful in such is used (not to necessary for consulting firms though - - grin!). I can't find any screenshots or any information in the manual I can find online regarding this area. Anyone have some text/pics so that I can access what ledgersmb does? TIA

1 1

LedgerSMB 1.9.7 released
by Erik Huelsmann 19 Jan '22

19 Jan '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 fix for a dataloss issue that was reported to us two days ago. The issue concerns the deletion of batches, which causes loss of information linking payments to the transactions being paid. This issue is present in all 1.8 releases before 1.8.25 and all 1.9 releases before 1.9.7. Additionally, it contais the following fixes and improvements: Changelog for 1.9.7 * Fix clearing To/Cc/Bcc/... fields which were cleared in the UI (#6168) * Fix invoice amounts for invoices generated from orders (#6125) * Fix saving purchase orders as invoices (#6341) * Require gain/loss account setup to post FX transaction payments #6360) * [DATALOSS] Fix deletion of any batch removing payment information (#6368) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.9.7/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.9.7 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.9.7 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.9.7 These are the sha256 checksums of the uploaded files: f1fc0faf40b5a9f925e35ffc2718cbe1ac9d744db0f0ce8863fa604c93fca375 ledgersmb-1.9.7.tar.gz abf7f430b68cd703a435d317ec49ba4d62ad53af5425ef53d6785d86366002c6 ledgersmb-1.9.7.tar.gz.asc

1 0

LedgerSMB 1.8.25 released
by Erik Huelsmann 19 Jan '22

19 Jan '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 fix for a dataloss issue that was reported to us two days ago. The issue concerns the deletion of batches, which causes loss of information linking payments to the transactions being paid. This issue is present in all 1.8 releases before 1.8.25. Additionally, it contais the following fixes and improvements: Changelog for 1.8.25 * Fix batch details printing throwing a PSGI error (#6325) * Fix saving of AR/AP vouchers throwing errors (#6327) * Fix account initialization in tax calculation module (#6335) * Require gain/loss account setup to post FX transaction payments (#6360) * [DATALOSS] Fix deletion of any batch removing payment information (#6368) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.8.25/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.8.25 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.25 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.8.25 These are the sha256 checksums of the uploaded files: 185d12a8f4e75b8c519042b98e0c7e2142193b2c3c4874fc2eaea193c61f2f24 ledgersmb-1.8.25.tar.gz c5438af7ccddda0aa0d485df6d077624df5b65c2a436df041023b19b19dca76e ledgersmb-1.8.25.tar.gz.asc

1 0

LedgerSMB 1.7.38 released
by Erik Huelsmann 19 Jan '22

19 Jan '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.38 * Fix batch details printing throwing a PSGI error (#6325) * Fix saving of AR/AP vouchers throwing errors (#6327) * Fix account initialization in tax calculation module (#6335) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.7.38/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.7.38 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.38 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.7.38 These are the sha256 checksums of the uploaded files: fcb593db1760ad37f1d428f657fecb4a34361bf62db8e320b271128d666a0969 ledgersmb-1.7.38.tar.gz 91697911649244be9628261914279dd8691de1d3e043904ca50a68388d678c07 ledgersmb-1.7.38.tar.gz.asc

1 0

Fwd: Questions
by Erik Huelsmann 06 Jan '22

06 Jan '22

With permission of Johann, I'm forwarding the mail below to the public mailing list for inclusion in the list archive: There are a number of answers which might benefit other (potential) users. ---------- Forwarded message --------- From: Erik Huelsmann <ehuels(a)gmail.com> Date: Sun, Jan 2, 2022 at 10:37 PM Subject: Re: Questions Hi Johann, Thank you for your patience while you waited for my reply. Christmas and New Year's are traditionally busy times and this year even more so. > I have attempted to configure your program. I include some questions > (some daft ones - but rather safe than sorry) that I would appreciate > some answers on before embarking on a more comprehensive evaluation. No problem. Happy to answer. Before I do, one question though: generally I tend to handle as many replies as possible through public channels so others can benefit from the replies. There are cases where details can't be shared. I do handle those through private communications channels, including private e-mail. These are very often linked to (paid) support requests though. Is there a compelling reason to stay private? Or can we share our conversation with other (potential) users for their benefit? > Which version is the most up to date and stable one for such an > evaluation as I would not like to get bogged down with testing at this > stage? Depending on which features you want to use, I'd advise you to use 1.8: 1.9 has had a few changes where people are currently experiencing problems when converting orders to invoices. Other than that, I'm not aware of any problems with 1.9 which would prevent you from getting your testing done. > Questions: > 1. As no COA for my country is available I had to create a new Chart of > accounts from scratch. > I also had to specify the currency as ZAR > The tax tables were also created with corresponding tax accounts in the > GL. > Are the above sufficient to have a program fully functional for > evaluation or are other country > specific modules also required to be installed? There are no further requirements to use the application for your country. However, other configuration may be required to take advantage of certain functions in the application: In order to track outstanding receivables and payables, you need to create "Contacts" and within them "Accounts" as one example. > 2. Must the user entering transactions be listed as an emplyee? Currently, in order to be able to log in, you need to create an employee for every user. That's correct. (It's something which I want to change, but it's how it is today.) > 3. When creating a part I would assume that the choice exists to enter a > mark up% or a selling price > but not both as these could in some instances contradict each other when > cost prices change? That does sound how it should work, but I just ran some tests and it's not how it actually works: the markup is calculated from the last cost and the sellprice: I entered a sellprice of 12 and then purchased at 8. When I returned to the part definition screen, the markup showed 50%. > Furthermore must the list and selling prices be vat inclusive? That's not how I use the application. There's a checkmark on the customer which indicates "Tax included", but I think it's impractical to use it on customers (on vendors it's a different story), because then sometimes the prices will be regarded as being VAT inclusive and on other customers, they will be regarded as VAT exclusive, because you can only register one sellprice (not one with and one without VAT; nor can you indicate in the part that the price is VAT inclusive). > 4. I was able to generate tax inclusive and exclusive Purchase Orders > depending on how the > Vendors were configured. Is this observation correct or does the program > only allow for tax > inclusive processing. Pardon this dumb question. I really hope it is > permissible! This is a completely correct observation. > 5.When creating GL accounts I also included Heading accounts. Presumably > these will reflect the > totalled balances of the child and other heading accounts of which it is > a parent? That's correct. You will find that both for the PnL and the balance sheet reports the headings will be presented with the totals of the children. > 6. When recording a purchase several workflows seem possible: > 6.1When no warehousing or goods – receive work flow is present an > invoice can be generated from > the PO? That's correct: you can generate an invoice from the order directly for the amount received. Once you post the invoice, items will be added to inventory (without a specific warehouse). The number of items entered in the "Rec'd" column will be taken out of the outstanding order. > 6.2 An invoice for a vendor can be generated from within the AR menu > where a PO number is > required in the input? A specific PO is not required in this case. The goods will simply be added to the inventory when the the invoice posts. To be explicit: when you *do* enter a PO number, this workflow leaves the PO untouched -- it does *not* reduce the number of items outstanding in the PO. > 6.3 When using the goods receive workflow (Goods – Transfer) which is > useful for a picking list > workflow to be included, is it only permissble when a warehouse has been > defined or can it be used > without the existence of any warehouses? (as would be the case for a > small business) The Goods > Transfer workflow is intended to move stock between warehouses. If you want to use picking list type workflows for shipping to customers, I would recommend using orders and the shipping menu (Shipping > Ship for customer shipments ; Shipping > Receive for vendor shipments). > 6.4 When is the Stock account in the GL updated – only once an invoice > for the vendor has been > posted? Yes. And it's decremented when the inovice for the customer has been posted. I've contemplated making a difference between "being in stock" and "being in inventory" where the former would be "available in the warehouse" and the latter "accounted for in the balance sheet". But I think that's too complex for most smaller businesses, although, if you think differently, I'd love to hear your opinion too. Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

LedgerSMB 1.9.6 released
by Erik Huelsmann 05 Jan '22

05 Jan '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.9.6 * Populate more fields in batch approval details report (#6271) * Fix error when posting an invoice created from an order (#6280) * Fix saving invoices and transactions as part of vouchers (#6327) * Fix printing batch details from batch details approval screen (#6324) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.9.6/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.9.6 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.9.6 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.9.6 These are the sha256 checksums of the uploaded files: 8748d005601557a690898758c06a3c7a88c3b3130ca778a53ade630a46e1a342 ledgersmb-1.9.6.tar.gz 97fb3bbfa6ce1cc4a52eab767bf65ec7780935132263db73ab3c45eee45de920 ledgersmb-1.9.6.tar.gz.asc

1 0

modified GIFI codes
by o1bigtenor＠gmail.com 29 Dec '21

29 Dec '21

Greetings I would like to add invoicing to my business system. In my AP I'm using GIFI codes modified to look like xxxx.xx.xx.xx so that I can get the granularity that I want. Does LedgerSMB tolerate AP numeric codes with more than 4 digits (like my 10 (with spacers - - - much easier to read that way!!))?

3 4

LedgerSMB Community overview 2021
by Erik Huelsmann 27 Dec '21

27 Dec '21

As the year-end approaches, it's time to provide an overview of what our community has achieved over the past year. At the end of last year, I wished everybody a healthy and prosperous 2021. The year has turned out to be as challenging as the last and I hope this overview reaches you in a health as good as (or better than) last year's. == Community interest == Although the number of hits on the website has declined steadily over the years, it seems that the decrease is slowing down: ca 1,000 fewer hits than in 2020, but 2020 lost ca 6,000 hits when compared to 2019. Traffic on the mailing lists was - in line with 2020 - very low this year. However, from the fact that during the year, we've also seen the number of Stars and Forks on GitHub slowly but steadily increase (Stars went up from 207 on 22 December 2020 to 260 today), we can conclude that there is still interest in the project, however, the broader community didn't have much time to engage with the project this year -- similar to what other volunteer-driven projects are experiencing this year. == Releases == With the release of 1.9.0 on 25 September 2021, we realized our goal to release 1.9 in the second half of the year, around a year after 1.8. This way, our target of releasing around the middle of the year, in order for the software to mature well before year-end (when most companies close their books). Despite the short release cycle, we were able to include a sizeable list of new functionalities, changes and (code) cleanups through 902 files changed, 306,496 added lines and 271,066 removed lines of code (and comments) between 1.8.0 and 1.9.0. With the number of releases doubled in 2020 over 2019 (44 releases over ~20 before), the question was whether we'd keep it up to release that often. Turns out we were able to meet our prior year standards with 38 releases in 2021: 1.6 (5): 1.6.29 - 1.6.33 1.7 (12): 1.7.26 - 1.7.37 1.8 (15): 1.8.10 - 1.8.24 1.9 (6): 1.9.0 - 1.9.5 Which excludes the alpha, beta and release candidate releases. == Packaging and installation == For the 1.9 Docker images, we moved from Debian Buster to Debian Bullseye as the base operating system. Contrary to prior experience - moving to Buster - there were no notable problems in the move. Significant engineering effort went into automating the mapping of Perl dependencies to their Debian package names during the Docker build process. By having this automation in place, error margin and manual release maintenance has been eliminated. The automation worked so well that it was backported from the initial 1.9 implemenetation to the release processes for 1.8 and 1.7 as well. With some help from the Debian community, we were able to fix the packages that come with Debian Bullseye: the packages that were there before were missing the "old/lib/" subdirectory. Unfortunately, Debian still includes 1.6. == Development progress == This year saw fewer commits than last year. Although this could be an indication that our project is suffering from the same problem many other Open Source projects have during the pandemic: a loss of available time from their contributors. I don't think that's the case for our project as some of it can be explained by the tougher topics being picked up in the second half of the year. Although the sheer number of commits was lower, the number of pull requests (832) is in the same order of magnitude as those from last year. The number of active developers - judging by accepted commits - went up from 47 last year to 9 people contributing commits this year - even though 2 of last year's contributors were one-off contributions. Last year I expressed my desire to close a number of long-standing issues this year and in fact, we have: * #975: Edit/Update on a saved invoice or transaction clobbers changes * #1135: Ability to delete a login account * #816: Ability to install in a schema other than "public" * #835: Performance of the balance sheet report (should use cached balances) All from 2015, just to name a few. Project commits on all branches (excluding merges and bots): 895 Erik Huelsmann* 139 Yves Lavoie* 61 Aung Zaw Win* 11 Neil Tiffin* 4 Richard T. Weeks 3 NoGare 2 lianto.ruyang 2 daOrangePeeler 1 Xin Wang * includes contributions on maintenance branches By comparison, these are the figures for 2020: 1247 Erik Huelsmann* 179 Yves Lavoie* 108 Nick Prater* 37 Aung Zaw Win* 3 Håvard Sørli 1 Bobberty 1 Andreas Karlsson Please note that the number of commits is in no way a measure of time spent on the project. Also note that these numbers don't include the time spent by those taking the effort to report their problems and taking the time to respond to developer questions as well as helping to test solutions when developers think they solved the problem. Similarly, there was a lot of activity with respect to issues: Number of open issues at 2021-01-01: 226 of which remain open today: 137 Issues closed: 173 of which created before 2021-01-01: 89 Issues created: 105 of which still open: 21 Number of open issues today: 158 This amount of development activity triggers many CI/CD jobs. Last year, we had just moved our regular CI loads to GitHub Actions; this year we have run almost 2,000 CI workflows on the main repository alone(!). A high number of jobs was triggered by Dependabot and Renovate Bot, two bots which have helped us to keep our JavaScript dependencies up to date. While Dependabot could run integration checks multiple times a day, we moved to Renovate in order to be able to reduce the number of CI jobs and merges. They're now set to once a week -- we're not releasing multiple times per day from our repository anyway. In the Changelog for 1.10 (https://github.com/ledgersmb/LedgerSMB/blob/master/Changelog#L3) you'll be able to read where we spent our time, for all effort that didn't end up in 1.9 and wasn't listed above. Areas that we're currently spending time on, include: Encapsulating Dojo widgets in "custom elements" in order more easily switch component libraries Putting the requirements in place in order to develop our UI with Vue3 Development of webservice APIs The 158 issues that are open today summarize into these statistics: * 11 bite-sized: a good place to start when looking to make contributions * 69 enhancement: requesting new features added to the application * 4 help wanted: looking for someone to help out on this issue * 10 migration: these issues need help testing and developing migration from SQL Ledger * 6 needs-documentation: there's not enough documentation... (Note that an issue may fall into more than one category or none at all.) == New functionality and improvements == Distributed with 1.10, a very nice although somewhat niche, functionality was added supporting localized handling of taxes: in the US, Washington State (WA) operates a web service which serves the tax rate in the tax district. We have built a module that queries this service based on the billing address on the invoice. The module calculates the applicable tax amount and posts it. The webservice returns a "tax district code" which gets posted with the amount for tracking and auditing by an accountant. This use-case goes to show what customizations are becoming possible after the years LedgerSMB has been in development, with all the code cleanup that has been going on. == Looking forward to 2022 == In 2022, we'll likely release 1.10 around the middle of the year; again in a release cycle a bit shorter than a year. This year two release branches will reach End-Of-Life status: 1.8 on 4 September 2022 and 1.7 on 4 October 2022. By the end of 2022, we'll be back to supporting two active release branches as we were before we switched to yearly release cycles. Experience has shown that given sufficient automation, maintenance of 3 branches is doable, but still challenging; there are simply too many merge conflicts on any non-trivial backport to do the job well. And last but not least, I'm hoping for 1 or 2 new contributors (not necessarily developers; translators, testers, documentation writers or UI artists are all greatly appreciated!). If you want to contribute, but don't know where to start, please contact me. == In closing == Thanks to everybody who contributed to any of the above in any way, especially to Computerisms.ca for hosting our DNS Freelock.com for hosting our website and mailing lists Efficito.com for hosting our mailing list archive, apt repository, release and download server GitHub.com, CircleCI and coveralls.io for hosting our development workflow My special personal thanks go to my GitHub Sponsors for supporting me for time, efforts and (financial) resources dedicated to the project! Leaves me only to wish everybody in our community - and their loved ones - happy holidays and a safe and productive 2022! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 1

Tamilrockers Proxy
by nicomoshe951＠gmail.com 21 Dec '21

21 Dec '21

Tamilrockers Proxy is one of the most prominent free streaming public torrent websites for watching and downloading the latest Tamil, Telugu, Hindi, Kannada, Malayalam movies without any legal rights. https://www.technopublish.com/tamilrockers-proxy/

1 0

LedgerSMB 1.9.5 released
by Erik Huelsmann 08 Dec '21

08 Dec '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.9.5 * Fix correct AR/AP account being selected on Update and when editing (#6191) * On date-entry, add the separator character immediatly when possible (#6121) * Fix the end date on credit accounts being shown correctly (#6235) * Fix calculation of credit limit remaining shown on transactions and invoices * Fix credit limit remaining calculation for foreign currency transactions * Extend AR/AP batch import to support multi currency imports (#6250) * Fix login errors being hidden behind an "insecure response" error (#6251) * Fix deletion of unapproved batches failing (#6252) * Fix GL batch import menu item missing, even with appropriate permissions (#6248) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.9.5/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.9.5 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.9.5 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.9.5 These are the sha256 checksums of the uploaded files: 94d1fe61b5c5c2914c0f02bc57794754ae51cbd52efea115ff4a7bdc16bcee94 ledgersmb-1.9.5.tar.gz fcd0872685e3c112cfe19a915e8bf13189a733630ea67960211e27cebd153a87 ledgersmb-1.9.5.tar.gz.asc

1 0