|
Auric
|
August 26, 2016 at 7:02 am
Hi There,
An issue has cropped up where EE (Event Espresso 4.9.8.p) is rounding to what seems to be the 3rd decimal place (although it only shows to the 2nd) and adding in 0.01c when it rounds up.
As an example:
Price without Tax (Tax[VAT] is calculated at 14%) is added to an event as:
Subtotal R219.30
VAT R30.70
Total R250.00 ZAR
When you purchase 2x tickets the total price is R500.00, however, when you purchase 3 or more the price suddenly becomes R750.01 etc. The end total price should be R750.00
I have tried entering a more precise number in the event price block but it always rounds my number back to 2 points.
Below is a link to the event i am referencing.
http://geodev.capechamber.auric-consulting.com/events/youth-unemployment-mismatch-labour-supply-demand-south-africa/
Any assistance would be greatly appreciated.
Thanks
Kyle
|
|
Seth Shoultes
|
August 26, 2016 at 1:46 pm
Hello Auric,
Our developers are looking into this. We’ll report back as soon as we here something.
|
|
Auric
|
August 29, 2016 at 5:28 am
Hi Guys, the URL for the event has changed to:
http://capechamber.co.za/events/youth-unemployment-mismatch-labour-supply-demand-south-africa/
Thanks for the assistance.
|
|
Josh
|
August 29, 2016 at 4:26 pm
Hi Kyle,
So taxes are actually calculated on the pretax total, and then rounded.
So the ticket total of 250.00 including tax is more of an estimate.
Would it help if the ticket selector showed ticket prices excluding taxes, then later the final total is shown at checkout?
|
|
Auric
|
August 30, 2016 at 1:38 am
Hey Josh,
The addition of the extra cent due to rounding in some instances is the issue, not how its displayed.
Is it possible to look at rather changing how it rounds amounts? e.g. 219.30*14% = 250.002 (its the 0.002 that throws everything off) However, if we were to enter 219.2982456140351 as a ticket price before Tax, this would round better, but the system doesn’t allow you to enter numbers like that, it rounds them back to 219.30 when you save the event.
Thanks
Kyle
|
|
Josh
|
August 30, 2016 at 4:45 am
Someone actually made an attempt at adding more digits for the price calculation, but the change broke unit tests. The dev team is also looking into this possibility.
|
|
Auric
|
August 30, 2016 at 5:13 am
thanks for the update, i look forward to a resolution 😉
|
|
Auric
|
September 2, 2016 at 1:25 am
Hi Guys,
Has there been any movement on this?
Thanks
Kyle
|
|
Josh
|
September 2, 2016 at 8:45 am
Yes, we’ll update this thread when we have something that’s ready to test.
|
|
Auric
|
September 13, 2016 at 3:01 am
Hi Guys,
Has there been any progress made on this?
Thanks
Kyle
|
|
Josh
|
September 13, 2016 at 3:21 pm
Hi Kyle,
While some progress has been made on this, there isn’t something that’s ready to be tested. We will update this thread when there is a branch on Github that can be tested.
In the meantime, you can use a percent price modifier (or surcharge) to charge the tax (vat) instead of checking the Is taxable checkbox, that should avoid any rounding errors.
|
|
LamLam
|
September 21, 2016 at 7:32 am
Hi, we have the same problem here, our provincial taxe is 9.975%.
Looking forward for a solution.
Josh, if we already have registrations for one event, is it possible to make the changes with the price modifier. Also, does it shows on the invoice as well as a tax calculation?
Thanks
|
|
Josh
|
September 21, 2016 at 11:12 am
What would end up happening is when you change anything related to price to an existing ticket that has a registration, it will automatically archive that ticket and create a new ticket that has your changes. The price modifiers will be itemized on the invoice.
|
|
Auric
|
September 28, 2016 at 7:55 am
Hi Support,
Its been a while since i logged the initial ticket and i have the client asking when there may be resolution to the issue, can you please advise?
Many thanks
Kyle
|
|
Josh
|
September 28, 2016 at 8:07 am
Hi Kyle,
I can advise that you use the Surcharge price modifier instead of the Tax feature. This way you’ll avoid the rounding issue while the developers work on a fix.
|
