You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Has amount, shipping, and salesTax as omitemptyed, but this means that you can't actually update the values to zero.
Use case, is super common; Customer gives us tax exempt information after the order processed, we update a transaction as exempt, and set the sales tax to zero, but the sales tax update never goes through because it's being dropped from the marshalled json. So we have a few transactions that look like we charged tax on orders we shouldn't have, but we really didn't.
My suggestion here would be to make at least those three fields pointers, so we can optionally send a zero if needed, or nothing and still work with the optionalness of the API. PR: #14
Also, weird other issue that's not completely related, but if I try to create a refund transaction to remove the sales tax instead, I get this error
taxjar: 400 Bad Request - exemption_type must be 'non_exempt' or 'marketplace' if any present sales_tax parameter values are non-zero
Seems like it's telling me that I can't have an exemption on the order if the tax amount is "non zero", which is technically true with this request because I'm trying to give it a negative number for the tax (which is non zero), but then I have no way of removing the tax for this transaction? Do I have to remove the exemption, then remove the sales tax, then put the exemption back?
The text was updated successfully, but these errors were encountered:
This type
Has
amount
,shipping
, andsalesTax
asomitempty
ed, but this means that you can't actually update the values to zero.Use case, is super common; Customer gives us tax exempt information after the order processed, we update a transaction as exempt, and set the sales tax to zero, but the sales tax update never goes through because it's being dropped from the marshalled json. So we have a few transactions that look like we charged tax on orders we shouldn't have, but we really didn't.
My suggestion here would be to make at least those three fields pointers, so we can optionally send a zero if needed, or nothing and still work with the optionalness of the API. PR: #14
Also, weird other issue that's not completely related, but if I try to create a refund transaction to remove the sales tax instead, I get this error
This is my request.
Seems like it's telling me that I can't have an exemption on the order if the tax amount is "non zero", which is technically true with this request because I'm trying to give it a negative number for the tax (which is non zero), but then I have no way of removing the tax for this transaction? Do I have to remove the exemption, then remove the sales tax, then put the exemption back?
The text was updated successfully, but these errors were encountered: