The "It can't be fixed," attitude is just wrong, since there is a conceptually simple fix.
It may take a while to code, but why not just put a check box or option group into the tax rate setup that defines whether it is a "per item" or "total" rate. On Wed, May 23, 2018 at 8:46 AM Matthew Pounsett <m...@conundrum.com> wrote: > Thanks for all your replies. If just the people who have replied in the > last 12 hours is any indication, then a lot of people are "living with" a > fairly annoying bug. > > In my case, this is on an invoice I'm generating, not a bill, so I don't > feel like I can mess with the data too much. Fortunately (or not) I'm not > using GnuCash to actually generate the invoice that goes to the customer, > since I find them poorly implemented as well... so the invoice is just for > internal records. But that means it needs to match what I actually send > the customer fairly accurately, or things get "off". > > My workaround is to add -$0.01 item that is non-taxable but is posted to my > tax table's liability account. > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
