Yes - we are seeing this as well. This causes an additional attempted auth after a capture - which is way confusing for people using the OrderMgr :)

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595


On Jun 22, 2007, at 9:26 AM, Jacopo Cappellato wrote:

Unfortunately, there are still some rounding issues when sales taxes are involved.
After some research, I think I have found where the problem is:
OrderPaymentPreference.maxAmount (the field where the auth/captured amount is stored) has 2 decimal digits; the field OrderAdjustment.amount has 3 decimal digits; the number of digits (set in the arithmetic properties file) for sales taxes is 3. My guess is that somewhere we move a 3 decimal number (without proerly rounding it as we do with the order grand total) to a 2 decimal field (maxAmount) and so the db approximate the number for us (in a different way from the grand total).
The end result is this:

https://demo.hotwaxmedia.com/ordermgr/control/orderview? orderId=WSCO10001

The order total is $18.83 (rounded from 18.825)
The amount auth/captured/invoiced is $18.82

Any hints on how we can fix this?

Jacopo

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to