Avalara AvaTax with CertCapture
Certification for Avalara AvaTax with CertCapture requires the delivery of all functional requirements shown below. This checklist assumes that you are using AvaTax in conjunction with CertCapture.
AvaTax Administration & Utilities Integration
The AvaTax Administration section provides the user with configuration, setup and utility functions necessary to administer the AvaTax sales tax calculation.
|R||AvaTax Configuration – dialog window||
The AvaTax Configuration Dialog window must allow the user to specify the configuration/connection information.
|R||AvaTax Test Connection button||Tests the connection to the AvaTax service and verifies the AvaTax credentials. This is an important element to allow for successful troubleshooting of the AvaTax service.|
|R||Tax Calculation – Disable tax calculation option||The user must have an option to turn on or off the AvaTax Calculation service independent of any other Avalara product or service.|
|R||User Implementation Guide||The User Implementation Guide should contain screenshots and information allowing the end user to configure AvaTax, including where the company code is entered, where the credentials are entered and where tax codes can be mapped.|
|R||Enable logging||Enables detailed AvaTax transaction logging within the application including capture of round-trip processing time.|
|N||Request time out definition||Define AvaTax request time out length, AvaTax best practices prescribes default setting of 300 ms.|
|N||AvaTax Admin Console link||Link to AvaTax production Admin Console|
Customer Record integration
|R||Customer Code||Identify customer code (number, ID) to pass to the AvaTax service.|
|R||Exemption number||Customer record field populating exemption number in an AvaTax transaction. This is used for tracking those customers who have tax exempt transactions.|
|R||Entity/Use Code||This is a group of codes that indicate the type of exemption. See the standard codes, but be aware that users are able to create custom codes as well.It is best to manage this value in your application’s Customer record and pass it to AvaTax as CustomerUsageType at either the document or line level, whichever is applicable. Note that either Exemption Number or Entity/Use code is required (not both). Entity/Use Code is preferred.|
|R||Customer Creation||Creation of an exempt customer record triggers the creation of a customer record in CertCapture.|
|R||Customer Updates||When exempt customer records are updated in the application, those same updates are applied to the customer record in CertCapture.|
|R||Certificate Requests||Exemption Certificate requests can be initiated from the customer record.|
|N||Status of Certificate Requests – Retrieved||Status can be retrieved from the customer record.|
|N||Status of Certificate Requests – Modified||Status can be modified (e.g. user can close them).|
|N||Status of Exemption Certificates||Status of Exemption Certificates and details can be retrieved.|
|N||Certificate Images||Exemption Certificate images can be retrieved.|
Server Audit Clarity
Tax calculation should display a clean audit to limit errors and call volume to reasonable levels.
|R||Pass connector identifier information via the TaxSvc.Profile.Client property||Integrations must include information about the connector, such as name, version, and company name, as a signature to each transaction. EXAMPLE: TaxSvc.Profile.Client = “Dynamics AX,9.0,MyApp for AX by ACME INC,1.0”|
|R||Reasonable errors on server-side analysis||There should be no errors except those that would result from normal (but invalid) user input (e.g. invalid address data). Such errors must be logged/displayed appropriately to the application.|