JayTheGeek
MIS
Macola ES 372 release 4.0.0.324
I am seeing a small, inconsistent problem with taxes. I don’t think this is isolated to just the way we Canadians do taxes - we see the same issue in our Seattle branch.
We generally apply two tax levels (Federal and Provincial) to the costs of product. Both taxes are calculated on the sale price and totalled into the price that the customer pays. Both taxes are generally stated on sales transactions.
We use the tax details and tax schedules to represent the different combinations. Generally speaking the structure in Macola does represent the tax structure used in Canada. We use the values posted to the GL to pay our taxes here in Canada.
What we are seeing in very small volumes (3 order lines per week out of 3000) are OE line items with the Tax Schedule field in a NULL value.
Through testing we are unable to create this problem through the data entry screen. The validation fires and prevents an empty field and any combinations of erroneous info that we try.
We see this problem on orders of any status (1, 4, 7, 8 & 9 in our confirm shipping environment) and it does carry through on invoiced orders. So unlike other incorrect tax calculations which are fixed during the invoicing process, these errors are written to history tables. So these errors in OE Taxes do carry through as errors in the GL. Accordingly without any steps to correct these errors, we will incorrectly record Taxes payable.
We have not yet been able to identify any consistency based on product, customer, user etc. So we are stumped.
Any experiences out there that sound familiar?
Anyone with busy OE tables willing to do a quick
SELECT *
FROM oeordlin_sql
WHERE (tax_sched IS NULL)
I am seeing a small, inconsistent problem with taxes. I don’t think this is isolated to just the way we Canadians do taxes - we see the same issue in our Seattle branch.
We generally apply two tax levels (Federal and Provincial) to the costs of product. Both taxes are calculated on the sale price and totalled into the price that the customer pays. Both taxes are generally stated on sales transactions.
We use the tax details and tax schedules to represent the different combinations. Generally speaking the structure in Macola does represent the tax structure used in Canada. We use the values posted to the GL to pay our taxes here in Canada.
What we are seeing in very small volumes (3 order lines per week out of 3000) are OE line items with the Tax Schedule field in a NULL value.
Through testing we are unable to create this problem through the data entry screen. The validation fires and prevents an empty field and any combinations of erroneous info that we try.
We see this problem on orders of any status (1, 4, 7, 8 & 9 in our confirm shipping environment) and it does carry through on invoiced orders. So unlike other incorrect tax calculations which are fixed during the invoicing process, these errors are written to history tables. So these errors in OE Taxes do carry through as errors in the GL. Accordingly without any steps to correct these errors, we will incorrectly record Taxes payable.
We have not yet been able to identify any consistency based on product, customer, user etc. So we are stumped.
Any experiences out there that sound familiar?
Anyone with busy OE tables willing to do a quick
SELECT *
FROM oeordlin_sql
WHERE (tax_sched IS NULL)