After reading the recent addition to the knowledge-base article at
https://help.zoho.com/portal/en/kb/commerce/user-guide/settings/general-settings/articles/types-of-taxes, I feel compelled for the fourth year now to reiterate the glaring omission in Commerce's inability to handle taxes at the city and county level for several home-base jurisdictions in the US. This oversight makes it impossible for me to correctly assess the sales tax for sales made in my home state at the point of sale. This means that I either eat the tax and pay it myself, or find myself in violation of Colorado's tax law.
Furthermore, this becomes a problem for anyone selling from outside of the state (or any other home-rule state) who's sales are more than $100,000 in a single calender year. (It can vary per state, but $100,000 is typically the threshold).
It's recently became more complex in that Colorado now uses it's own real-time ecommerce tax calculation system called SUTS as described here:
https://tax.colorado.gov/SUTS-info. This is all fine and dandy, and the taxes can easily be determined for anywhere in Colorado down to the exact address... except... there's no API that Commerce provides to allow me to update the tax at the point of sale.
Evident by the fact that Avatax is able to modify the tax amount at point of sale, there clearly must exist an unpublished API by which to do so which would allow me the ability to update the tax programmatically by polling the SUTS system so I can charge the correct tax for Colorado transactions.
Why isn't this API (or something equivalent) publicly available to accommodate this?
(Interestingly, Avatax's parent corporation is responsible for creating the SUTS system here in Colorado. I find it a little aggravating that my tax dollars helped pay for this system that I can't take advantage of because there's no API for me to update the transaction programmatically, and the only resolve is to pay Avatax a second time with a monthly fee to do so, which seems a bit absurd.)
Thanks,
Bryan