Avalara confirmed the cause of the variance is due to different values being sent for the taxIncluded flag on the tax call made for the original (INV) vs. the refunding (IIA) transaction. They also said to fix this issue the values for the taxIncluded flag need to be made the same for both INV and IIA transaction types.
Current configuration:
INV taxIncluded = true
IIA taxInclued = false
The business case is clear: the full amount(s) of the INV should be offset by the IIA(s) and leave a no balance.
It would be great if Zuora would fix this issue with the integration to Avalara and make the values of the flags consistent for both transactions. Or, at a minimum, expose the flag in the UI so users can configure this setting themselves.
Link to Avalara Developer Documentation - taxIncluded
API Call:
{
"lines" : [
{
"amount" : 100 ,
"taxIncluded" : "true"
}
],
"type" : "SalesInvoice" ,
"companyCode" : "DEFAULT" ,
"date" : "2017-10-02" ,
"customerCode" : "ABC" ,
"addresses" : {
"singleLocation" : {
"line1" : "2000 Main Street" ,
"city" : "Irvine" ,
"region" : "CA" ,
"country" : "US" ,
"postalCode" : "92614"
}
}
}
Note from Avalara:
... View more
