OE Orders detail tax calculation (4 replies)
Steve, the logic has been in IMan forever as we needed to build this for an early eCommerce integration.
When you have Tax Calculation on the order/shipment/invoice disabled/unchecked the tax calculation is based on the price entered.
These fields, toggle the Tax Included flags prior to setting the Unit Price, so the Tax Amount (calculated by Sage) is inclusive vs. exclusive.
Thanks James. I still don't get it, sorry. Are you saying the OE0500.TINCSWBEFOREUNTPRCX value is only used if Tax Calculation is disabled? If so, then how is Sage calculating the tax amount as inclusive vs. exclusive anyway?
Perhaps I'm misunderstanding the scenario or even the way Sage 300 works. Do you have any quick worked example?
Try entering an order with Tax Calcuation unchecked.
- Create an Order with Tax Calculation unchecked
- Enter the price prior to setting the Tax Included, tax will initially be calculated as exclusive.
- Change the Tax Included to Yes. Tax will not recalculate.
What this value does is to swap points 2 & 3. This makes the initial tax calculation inclusive.
Thanks and sorry, still don't get it. At step 2, if tax calculation is unchecked then the tax isn't calculated at all. As such it's not clear how the tax can be "initially calculated as exclusive".
Don't worry, it's me not getting it. I'll do some more investigation rather than bother you.
There is a section in the Sage 300 supported import types under OE Orders. It reads:
DETAIL TAX CALCULATION
OE0500.TINCSWBEFOREUNTPRCX (TAX INCLUDED X B/F UNIT PRICE)
Denotes if the tax included flag should be set for a line prior to setting the unit price. Since Tax Included pricing calculates Tax on top of Unit price after the Tax Inc. Flag is set to true, this backs out the tax so the Unit Price is inclusive of tax.
Does anyone know what this does exactly? It looks extremely useful and I have tried setting to both True and False along combined with setting the associated Tax Included value to True and False. The value of OE0500.TINCSWBEFOREUNTPRCX seems to make no difference to any values I can see.