We have been using this for awhile and the tax caluculation was correct… today we went in and used items that we have used in past invoices that had at the time generated correct invoices. We have made no changes to the tax table in over a year. All we did was update ERPNext… this is very troubling as this is what we see:
We update after we review GitHub and monitor the forums there are really are too many surprises with ERPNext they should keep stuff on development and only migrate to production when its tested and proven we are talking about accounting, sales tax not working and rounding incorrectly is a problem a huge one…
It is about credibility read the forums they are public its easy right now to draw the wrong conclusion about the quality of the product I after a year should not have to dig so deep for a fix that should not have happened in the first place…
ERPNext: v10.1.18 (master)
Frappe Framework: v10.1.16 (master)
tax should be 11.13 not 10.24 and the total cost to customer should be 140.13 not just 129.00 @ushashmi even if I select the tax and charges though we should not have to because we are using using item taxes:
all of the calculation errors that many are experiencing in master are making the product unusable for production I beg the foundation to stop pushing code that has not been vetted and fully tested in dev to master maybe a third beta fork is necessary.
For many of us this is not a hobby this is how we make a living and these mistakes are costly and have legal implications if they are not caught and corrected in a timely manner… lastly we have an app we want to develop to interact with ERPNext but are spending way too much time fixing core functionality like taxes, and email which was at least workable until the introduction of inbox… we joined the telegram group with hopes of seeing progress on email but that seem to have ground to a halt in activity…we have for the last month been looking at other products because of the inconsistency in the product, we would prefer to stay with ERPNext because of its flexibility but not if the method of implementation in master is going to remain the same. its just too risky.