I have to disagree although we are probably only arguing semantics here.
It doesn’t matter what you call it.
Manager has changed how it deals with tax and initial “amounts”. It was always the case users had to enter the data in a particular fashion now it appears manager is deriving the amount. It should not have changed that.
This is exactly how I have always understood manager should have worked in the past. Why does it not work this way now? How is it the way it worked before was right and acceptable at the time but it’s wrong that we do it that way now?
This exactly leads into my other thread where manager has changed my balance sheet. This is probably why, I have done it this way myself. So this is a third major feature change I have to fix in my data in recent history.
The amount you enter into that column (whether it be debits, credits, amount etc), that flag has always indicated whether the amount entered includes or doesn’t include tax.
Why has that changed?
By whose definition? There are valid use cases for entering them as such. I have suppliers that provide tax exclusive invoices that I pay immediately and enter via payments and receipts.
Users have had to work around poorly implemented manager “features” for years. You shouldn’t say users are doing it wrong because manager has updated how it decides to handle it or how they have had to previously work around such problems.
It’s very wrong of @lubos to make such changes without some form of being able to rectify the affected entries and if it is not determinable at managers end, then it should not be implemented without warning.
Hence my thread about fear of updating. Because unless your brain and Lubos’ brain are in complete sync, something will break.