AvaTax TaxCodes and UI Certification

[aaronjudd]

Additional UI and functionality is needed to have our AvaTax module be "certified".

Some are additional settings, and will need UI in the dashboard settings.

Implementation requirements are here: http://developer.avalara.com/avatax/testing-your-integration/

Integration checklist for Functional Review http://developer.avalara.com/avatax/certification/

Use Case for handling Exemptions http://developer.avalara.com/avatax/handling-tax-exempt-customers/

Using the RESTv2 API, there are two http headers we need to pass:

• X-Avalara-Client : This is a string in the format '(app name); (app version); (library name); (library version); (machine name)'
• X-Avalara-UID: xxxxxxxxxx

Swagger (AvaTax API reference) https://rest.avatax.com/swagger/ui/index.html

These endpoints can be used to retrieve TaxCodes,etc. TaxCodes will need to be stored on product, see #1699 Line Item calculation is required (should already be wired this way).

Testing can be validated here: http://developer.avalara.com/avatax/self-test/

Future - Developer Blog post on Landed Cost using RESTv2 API http://developer.avalara.com/blog/2016/10/13/landedcost-with-rest-v2/

[aaronjudd]

Example certification settings:

[brent-hoover]

For us the Tax codes for Shipping/Handling should probably go in the Avalara tax settings panel

[brent-hoover]

Some Todo items here:

• [x] Add a "Tax Exempt" field/checkbox to the Account record (#1860)
• [x] Add a "Tax Description" field to Products (can be added to what @kieha is doing) (#1699)
• [x] Record a per item tax rate in the cart/order
• [ ] Reflect tax code/tax rate per item in the order management screens (#1857)
• [x] Ensure that Shipping is handled correctly and you can assign a Tax Code to it
• [x] Ensure that discounts are taken into account when recording taxes
• [x] Ensure that both Tax Exempt products and Tax Exempt customers are handled correctly. Related to #1860
• [x] Add try/catch around taxCalc methods so that we aren't throwing uncaught errors (especially for common errors like Authentification)
• [x] Add enable/disable Address validation by country

[brent-hoover]

Current audit self-test results

[brent-hoover]

We had the compliance audit today and here were the issues that came up:

Compliance Issues

1. Biggest Issue Breaking out quantities into individual items is going to cause some issues with Avalara's limits on order sizes. #2102
2. We need to warn but not stop customers from proceeding with an order if the address fails complete address validation. (do we need to record the fact that it didn't validate?) #2104
3. The Order ID displayed in the admin panel and the Order ID being transmitted to Avalara is not the same so it's hard to cross-reference the two. #2103
4. "Customer Usage Type" doesn't allow you to set a custom value. #2101

Not blockers for compliance but things on the horizon:

1. Location code for Retail locations (Evereve?)
2. "Tax Included" for VAT retailers

[brent-hoover]

Ok, so the "biggest issue" wasn't the biggest issue, address validation is. But once #2104 is completed we should be good to go. Moving out to 1.2

[brent-hoover]

We are certified. Closing