Avalara Statement of Work for Professional Services
Effective as of May 15, 2020
Services governed by this Statement of Work:
- Nexus Services
- Name or Address Change Services
- Tax De-Registration
- Standard Backfiling Services
- Voluntary Disclosure Agreement
- Tax Exposure Analysis
- Data Transformation Services
- Avalara Implementation Services
- CertCapture Single Sign-On Implementation
- Customer Data File Exchange Implementation
- Exemption Data File Exchange Implementation
- CertCapture REST API for Import Implementation
- CertCapture REST API for Export Implementation
- CertCapture for Retail Implementation
- CertCapture for eCommerce Implementation
- CertCapture Document Automated Upload
- Avalara CertCapture Validation
- CertCapture Campaigns
- CertCapture Tax ID Verification
- CertCapture Validation for CertExpress
This Statement of Work (“SOW”) describes the Professional Services provided to Customer by Avalara. This SOW is in addition to and incorporates by reference the Avalara Professional Terms and Conditions located at www.avalara.com/ps-terms(“Terms”). Any capitalized terms used in this SOW and not defined have the meanings given in the Terms.
I. The Services.
- Nexus Services. Avalara offers nexus analysis services on a one-time, quarterly, and annual basis (“Standard Nexus Study,” “Quarterly Nexus Monitoring Service,” and “Annual Nexus Monitoring Service” respectively, and collectively the “Nexus Services”).
- Name or Address Change Services. For Customers who have purchased “Name or Address Change Services,” Avalara shall assist Customer in notifying sales and use tax jurisdictions of the name or address change up to the number of jurisdictions set forth in the Order Document.
- Tax De-Registration. For Customers who have purchased “Tax De-Registration” services, Avalara shall provide the following tax de-registration services for the number of sales and use tax jurisdictions set forth in the Order Document.
- Standard Backfiling Services. For Customers who have purchased “Backfiling Services” Avalara shall prepare up to the number of sales and use tax returns set forth in the Order Document for the prior reporting periods and taxing jurisdictions identified by Customer. Avalara shall prepare these returns based on the transaction data available in Customer’s AvaTax production account only. Customer must be live on Avalara Returns.
- Voluntary Disclosure Agreement. For Customers who have purchased the “Voluntary Disclosure Agreement” Service, Avalara will assist Customer with compliance options for non-filers, including formal and informal voluntary disclosure programs, offered by the applicable taxing jurisdictions for the number of jurisdictions set forth in the Order Document.
- Tax Exposure Analysis. For Customers who have purchased “Tax Exposure Analysis” Services, Avalara will perform an overall high-level assessment of the potential sales and use tax exposure created by Customer in various taxing jurisdictions.
- Data Transformation Services. For Customers who have purchased “Data Transformation Services” Avalara will provide assistance in uploading historical transactions into Customer’s AvaTax account. Avalara will convert Customer’s source data files into a format useable by AvaTax.
- Avalara Implementation Services. Avalara provides implementation support services for Customers who have purchased AvaTax, CertCapture, or Avalara Returns (collectively, the “Implementation Services”).
a. The Services. For Customers who have purchased a Nexus Monitoring Service, Avalara will work with Customer or Customer’s designated representatives to gather information to conduct a review and analysis of Customer’s nexus status for the number of states set forth in the sales order. Avalara will provide access to Avalara’s online survey requesting specific information about Customer’s activities, business operations, relationships with third parties and other business activities within each of Customer’s selected states over the past twelve months. Avalara may also request that Customer provides additional material about Customer’s products and services to supplement this information.
b. Timing. Avalara will provide Customer with a designated point of contact, an overview of the nexus review process, and login credentials to Avalara’s online survey. Avalara generally delivers the completed nexus study within four weeks after receiving Customer’s completed survey and any additional required information. For Customers who have purchased the Quarterly Nexus Monitoring Service, Avalara will provide this service each quarter and review Customer’s business activities during the prior calendar quarter. For Customers who have purchased the Annual Nexus Monitory Service, Avalara will provide this service annually.
c. Deliverables. Based on the information and supplemental materials provided by Customer, Avalara shall prepare reporting of the findings and analysis for each of Customer’s selected states. If Avalara’s analysis indicates Customer has or may have created sufficient nexus for sales and use tax purposes, Avalara will recommend options for compliance.
a. Avalara Obligations. Avalara shall prepare a name or address change package for submission to each taxing jurisdiction. Depending on the jurisdiction requirements, this package may include a written request to update account information, forms specific to account update requests with Customer’s digital signature affixed to each, and supporting documentation for the change.
b. Customer Obligations.
i. Customer shall complete Avalara’s questionnaire requesting pertinent information related to the account update process including the new information, applicable supporting documentation, and a digital signature.
ii. Customer shall update their AvaTax account with the new information including the organization section and filing calendars, if applicable.
iii. Customer shall respond to additional requests from the jurisdictions after the packages have been submitted.
iv. Customer shall notify all other relevant state and local authorities of the change.
a. Avalara Obligations.
i. Avalara will prepare a de-registration package for submission to each taxing jurisdiction. Depending on the jurisdiction requirements, this package may include a written request to de-register sales and use tax account, forms specific to account closure with Customer’s digital signature affixed to each; and supporting documentation for reason of closure.
ii. Avalara will send the package to Customer for review and approval. Upon Customer approval, Avalara will submit the package directly to each taxing jurisdiction, including any forms and supporting documentation, via online submission or certified mail.
b. Customer Obligations.
i. Customer shall complete Avalara’s questionnaire requesting pertinent information related to the de-registration process, including business/nexus close date, reason for closure, applicable supporting documentation, and a digital signature.
ii. Customer shall file all final returns or notify Avalara to file final returns on Customer’s behalf and cancel Returns service, if applicable. Customer shall disable tax collection within AvaTax and end-date filing calendars, if applicable
iii. Customer shall respond to additional requests from the jurisdictions after the de-registration packages have been submitted. Customer shall resolve any open liabilities or credits on Customer’s account with each taxing jurisdiction. Customer shall work with jurisdictions that require a close-out audit of Customer’s account before authorizing the de-registration.
iv. Customer shall notify all other relevant state and local authorities of the change.
a. Avalara Obligations. Avalara will (a) file period tax returns upon Customer review and approval of liability, and (b) facilitate funding for the tax liability related to the prior period tax returns, if necessary.
b. Customer Obligations.
i. Customer shall ensure transaction data is entered accurately into AvaTax; reprocessing fees will apply if Avalara prepares a tax return more than once due to inaccurate transaction data within AvaTax.
ii. Customer shall approve reporting figures and providing funding for remittance amounts.
iii. Customer shall address any correspondence or communications from the taxing jurisdiction related to the tax returns and payments.
a. Avalara Obligations. Based on the information and materials provided by Customer, Avalara will provide the following:
i. Avalara will review Customer’s business activities and tax policies as they relate to the self-audit process, including tax categorization for products and services, tax type assignment, and customer exemption status;
ii. Avalara will work with Customer to complete the formal or informal voluntary disclosure program application(s), with the preparation of self-audits as required including:
1) Process up to 100,000 of Customer’s historical transactions in Avalara’s internal AvaTax account to calculate the correct amount of tax due (if Customer’s data exceeds 100,000 transactions, Customer will purchase Data Transformation Services with respect to the excess). Avalara will segregate the amounts due to each taxing jurisdiction (excluding local taxing authorities). These amounts will be used for tax reporting under the voluntary disclosure agreement;
2) Prepare a penalty abatement request for Customer’s review and approval.
iii. Avalara will submit any voluntary disclosure program applications to the taxing jurisdiction on Customer’s behalf;
iv. Avalara will coordinate any additional information requests from the taxing authority;
b. Customer Obligations.
i. Customer shall answer Avalara’s questionnaire requesting pertinent information related to the voluntary disclosure program registration process, including ownership information, historical or anticipated start date, and estimated taxable sales. Customer will provide any additional information Avalara may request.
ii. Customer shall provide any historical transaction source data requested and Customer’s tax policies regarding taxation of relevant transactions. Customer will identify any Customer-related exemptions that Customer chooses to apply.
c. Exclusions Updates to the Customer’s filing calendar in Returns to activate tax reporting. Upon receipt of Customer’s approved tax registration application, the taxing authority will issue a license or permit with Customer’s tax registration number, initial filing frequency, and prepayment requirements (if any). Customer shall update the filing calendar in Returns.
a. Avalara will work with Customer to obtain historical transaction data and relevant tax exemption information and create a “Tax Exposure Report” to assist Customer with decisions regarding sales and use tax compliance.
b. The Tax Exposure Report will detail findings and recommendations for each state. The Tax Exposure Report may also identify some key characteristics of each state, including the existence of a formal voluntary disclosure or amnesty program and expected limited-lookback periods. These factors will assist Customer in deciding the order and manner in which to approach each taxing authority. The Tax Exposure Report will use the current average tax rate for each state, include state-specific penalty rates, and will include up to one hour of tax code mapping services from Avalara. The Tax Exposure Report will include analysis for only one business entity. Customer will make the final decisions regarding if and how to register and report any historical transactions to each taxing authority.
a. AvaTax Import Process.
i. Prior to importing any historical transaction data, Avalara will work with Customer to understand Customer’s tax policy and assist Customer is applying that policy to Customers’ AvaTax account.
ii. Importation into AvaTax may result in tax recalculation, reallocation, and redetermination of tax sourcing, which may change the nature of posted transactions. A posted transaction may have a different tax or situs applied than that of the original, native transaction. These results could impact Customer’s tax liability in the applicable tax jurisdictions.
iii. Some historical transactions may fail the import process, either in full or in part, due to incomplete or inconsistent data; for example, address components that are inconsistent with one another (city not belonging to an associated postal code), incomplete (missing state), or inaccurate (invalid postal code). Transactions that fail the import process will be provided to Customer in a separate data file for Customer to remediate.
b. Customer Obligations. Customer must have an existing current AvaTax subscription at the time of transaction import. Customer is solely responsible for the content and accuracy of the transaction data. Avalara is authorized to import Customer’s historical transactions for purposes of Data Transformation Services.
a. Implementation Services Generally. Customer shall have overall responsibility for implementation, including project management, testing, and the technical aspects of installation, configuration, and code modifications and merges. Avalara shall assist Customer and provide consulting expertise during the implementation process, including the following project elements:
i. Planning and Design.
1) Solution Design and Project Planning. Avalara will confirm the solution design and project logistics with Customer’s project team, including resources, roles and responsibilities, timing, and deployment process. Avalara will propose a plan for Customer to incorporate into its overall project plan.
2) Environment Validation. Avalara will collaborate with Customer’s project team on the solution to be used (test and production), including relevant configurations and functionality, system architecture, and patch levels.
ii. Solution Testing. Customer will create test scripts and Avalara will provide feedback. Avalara will provide support during Customer testing and support issue resolution and troubleshooting related to the Avalara solutions. Customer is responsible for ensuring the scenarios tested are complete, the tests are executed to the level required, and the results are accepted at the end of the testing cycle.
iii. Solution Deployment.
1) Production Deployment. Avalara will participate in solution deployment activities, including data migrations and cutover planning.
2) Post-Production Support. Basic customer support is included in most purchases. Additional support may be separately purchased.
1) Avalara will begin work within 30 days of receipt of a signed order authorizing this work. The length of time necessary to complete the project depends largely on Customer’s internal resources.
2) For an Expedited Project Start Date Fee, Avalara will begin the Professional Services within ten business days of Customer’s signed order form being processed by Avalara.
i. Platform Connector Installation. Avalara charges for the AvaTax Implementation Services for each connector.
1) Avalara-Built Platform Connector. Avalara will provide the current installation package for the connector. Customer will install the connector and incorporate the Avalara solution into Customer’s processes or engage with a partner to do so. Avalara will provide technical support in troubleshooting installation issues. For customers implementing a Microsoft D365 connector, the fee set forth in the Order Document assumes that Customer is using the latest version of Microsoft D365; use of prior versions may require a change in project duration and scope and an increase in fees.
2) Partner-Built Connector. Customer will install the connector and incorporate the Avalara solution into Customer’s processes or engage with a partner to do so.
3) Avalara AvaTax API. Avalara will provide guidance for the best practices of developing the AvaTax integration to Customer’s custom system.
ii. Tax Logic Matrix and Tax Code Mapping. Avalara will conduct a workshop with Customer’s tax department to develop a tax logic matrix that defines the business rules for tax exemption (“Tax Logic Matrix”) and assist with identifying and mapping to the appropriate Avalara AvaTax system tax codes for tax exemption processing.
iii. AvaTax Configurations. AvaTax configuration will be completed by Customer’s tax team with guidance and support from Avalara, including the following:
1) AvaTax Entities. Avalara will guide Customer in the configuration of Avalara AvaTax with the appropriate reporting entities.
2) AvaTax Nexus. Avalara will guide Customer through the configurations in Avalara AvaTax to enable tax collection in the various state and local taxing jurisdictions in which Customer has identified a reporting requirement.
3) AvaTax Product Tax Categories. Avalara will guide Customer in the configurations to map Customer’s product tax categories to the appropriate Avalara tax categories based on the Tax Logic Matrix.
4) AvaTax Exemptions. Avalara will guide Customer on best practices for handling of Customer’s customer exemptions within AvaTax and assist Customer in configuration.
iv. AvaTax Training. Avalara will provide key user training on the use and maintenance of the AvaTax solution (two sessions: an initial introductory session to familiarize the key business users and project team members with the Avalara functionality and an advanced session on the use and maintenance of the tax-related functionality before solution deployment).
v. This SOW applies to U.S. and Canadian implementation only and does not include implementation for other countries, configuration for Cross-Border Transactions, Customs Transactions, or Estimated Customs Transactions.
vi. This SOW applies to sales tax only and does not include implementation of use tax functionality.
vi. Support for the use of Avalara AvaTax APIs to support offline transactions specifically the AvaTax POS Content API and the Transaction Import API are out of the scope of this project.
i. CertCapture Training. Avalara will provide user training on the use and maintenance of CertCapture (two sessions: an initial introductory session to familiarize Customer's key business users and project team with the functionality of CertCapture and a follow-up advanced session on customer data maintenance, Certificate requests, managing Certificates, and business process flow).
ii. CertCapture Configurations. CertCapture configuration will be completed by Customer’s tax team with guidance and support from Avalara, including the following:
1) CertCapture Entities. Avalara will provision CertCapture with the entities in which Customer has identified a need for exemption management.
2) CertCapture Settings. Avalara will guide Customer on the configurations and Company Content within the CertCapture application.
3) CertCapture Customers. Avalara will guide Customer on the import/entry of Customer’s customers in the appropriate format for Customer’s business requirements.
i. Returns Training. Avalara will provide key user training on the returns monthly process to include assistance with the appropriate documentation for implementation and then follow up training on the monthly Tax Liability Worksheet review and approval processes.
ii. Returns Configuration. Avalara will guide Customer on the filing calendar setup process for up to five reporting jurisdictions.
9. CertCapture Single Sign-On Implementation. For Customers who have purchased “CertCapture Single Sign-On” Avalara will enable their Authorized Users to access the Service using a web-based single sign-on service, eliminating the need for application-specific passwords. CertCapture SSO uses SAML 2.0 technology. Avalara will provide the following:
a. Technical Requirements. Avalara and Customer will work together to define technical requirements, including Customer’s identity provider, required SAML 2.0 attributes from the identity provider, and rules for user provisioning, role assignment, and sub-entity assignment.
b. Avalara Obligations. Avalara will set up a test company in the Account, and the Parties will jointly test the CertCapture SSO service. Avalara will make no more than one revision to the SAML mapping during testing. Upon Customer’s approval, Avalara will enable CertCapture SSO in Customer’s Account.
c. Customer Obligations. Customer will provide the following:
i. User and user role mapping based on Avalara’s template; and
ii. Customer’s identity provider SSL certificate.
iii. Provisioning within Customer’s identity provider.
a. Avalara will provide Customer with formatting requirements for importing tab delimited files, and the Parties will agree on a final file format. Customer may use up to 10 custom data fields.
b. Avalara will set up a test company in the Account, and the Parties will jointly test the Data File Exchange service. Avalara will set up a SFTP site to enable Customer to automatically upload new data files daily.
c. Customer shall upload the file to the SFTP site in the agreed file format and ensure proper formatting.
d. Avalara will review the upload for accuracy, and Customer will make any necessary corrections. Avalara may provide a second review to verify that any errors have been corrected.
e. Changes to the Avalara file format and data formatting services are outside the scope of this SOW.
11. Exemption Data File Exchange Implementation. For Customers who have purchased “Exemption Data File Exchange Implementation” Avalara will support Customer in setting up Exemption Data File Exchange as follows:
a. Exemption data will be made available in standard file format for retrieval from the SFTP site.
b. Avalara will provide a sample file for Customer to test the integration. Avalara may provide a second sample file to verify that the errors have been corrected.
c. Customer will develop the logic to read and import the data.
d. Any enhancement to the standard file format is outside the scope of this SOW.
12. CertCapture REST API for Import Implementation. For Customers who have purchased “CertCapture REST API for Import Implementation” Avalara will support Customer in setting up access to the CertCapture REST API as follows:
a. Avalara will provide guidance and best practices related to development using the CertCapture REST API. CertCapture REST API specifications are located at http://docs.certcapture6xrest.apiary.io/.
b. Customer shall develop and test the CertCapture REST API in accordance with these specifications.
c. Avalara will support Customer in troubleshooting issues during Customer testing.
d. Any enhancement to the CertCapture REST API for Import is outside the scope of this SOW.
13. CertCapture REST API for Export Implementation. For Customers who have purchased “CertCapture REST API for Export Implementation” Avalara will support Customer in setting up access to the CertCapture REST API for Export as follows:
a. Avalara will provide guidance and best practices related to development using the CertCapture REST API for Export. CertCapture REST API for Export specifications are located at http://docs.certcapture6xrest.apiary.io/.
b. Customer shall develop and test the CertCapture REST API for Export in accordance with these specifications.
c. Avalara will support Customer in troubleshooting issues during Customer testing.
d. Any enhancement to the CertCapture REST API for Export is outside the scope of this SOW.
14. CertCapture for Retail Implementation. For Customers who have purchased “CertCapture for Retail Implementation” Avalara will assist with the setup and configuration of CertCapture for Retail in Customer’s Account.
15. CertCapture for eCommerce Implementation. For Customers who have purchased “CertCapture for eCommerce Implementation” Avalara will support Customer in setting up CertCapture for eCommerce in their web environment by providing guidance and best practices related to the use of the Service.
a. Avalara Obligations. Avalara will support Customer in troubleshooting issues, such as CertCapture for eCommerce not returning the expected result.
b. Customer Obligations. In order to implement CertCapture for eCommerce, Customer will do the following:
i. Define business requirements regarding the collection of exemption Certificates and determination of exemption.
ii. Program CertCapture for eCommerce into Customer’s web environment.
iii. Perform end-to-end systems integration testing using data passed to, and created by, CertCapture for eCommerce.
iv. Maintain the implementation as non-Avalara changes made to the installation’s environment.
a. Avalara Obligations. Avalara will import the historical certificates and link them to the matching customer records in CertCapture as a one-time electronic import.
b. Customer Obligations.
i. Set up Customer’s customers or import them into the Account.
ii. Provide historical certificates to Avalara as individual PDF files.
iii. Provide historical certificate metadata (including jurisdiction, exempt reason, signed date, and expiration date) and sufficient information to map Customer’s customers to the appropriate Certificate images.
a. Avalara will receive legacy certificates, convert hard copies to PDF files, and upload the PDF files into Customer’s Account. Images will not be visible in Customer’s Account until validated.
b. Customer will identify Customer’s customer account numbers associated with the Certificates and add these numbers to the Certificates.
c. Avalara will review the Certificates and assess contents for inclusion of Customer’s customer name, Customer name, exemption reason, tax identification number (Avalara verifies that a tax identification number has been included on the Certificate but does not verify the format or accuracy of this number), signature, and signature date.
d. Avalara will make standard reports available so that Customer can review the validations that have been performed and their results.
e. Multijurisdictional Certificates will be separated by jurisdiction into unique Certificates and assigned individual Certificate identification numbers to ensure proper treatment for each jurisdiction (e.g., jurisdictions may have different expiration rules, reporting rules, and so forth). Avalara will validate multijurisdictional Certificates for each jurisdiction. Each jurisdiction counts as a unique validation. Customer can opt to limit validation of multijurisdictional Certificates to those jurisdictions contained in its nexus table or Customer data.
f. Disclaimer. Customer understands and agrees that Certificate Validation Services do not guarantee the validity of Certificates.
18. CertCapture Campaigns. For Customers who have any of the following “CertCapture Campaigns,” Avalara will conduct a campaign to Customer’s customers to request updated Certificates using Avalara forms.
a. CertCapture Fax. For Customers who have purchased “Avalara CertCapture Fax,” Avalara will conduct a campaign to Customer’s customers to request updated Certificates by preparing and sending up to the number of faxes set forth in the Order Document. Avalara may send subsequent rounds of faxes to those who do not return Certificates up to the total number of faxes set forth in the Order Document.
b. CertCapture Mail (postage). For Customers who have purchased “CertCapture Mail (postage),” Avalara will conduct a campaign to Customer’s customers to request updated Certificates by preparing and sending the number of letters set forth in the Order Document. The letters will be sent by U.S. Mail. This Service includes printing envelopes and contents, stuffing envelopes, and applying postage. Avalara may provide subsequent rounds of letters to those who do not return Certificates up to the total number of letters set forth in the Order Document.
c. CertCapture Email. For Customers who have purchased “Avalara CertCapture Email” Avalara will prepare and send up to the number of emails set forth in the Order Document. Avalara may send subsequent rounds of emails to those who do not return Certificates up to the total number of emails set forth in the Order Document.
d. Disclaimer. Customer understands and agrees that CertCapture Campaigns do not guarantee a response rate to the campaign nor that the Certificates generated by the campaign will be valid.
19. CertCapture Tax ID Verification. For Customers who have purchased “CertCapture Tax ID Verification” Avalara will verify state tax identification numbers for those states that make this information available on their websites up to the number set forth in the Order Document.
20. CertCapture Validation for CertExpress. For Customers who have purchased “CertCapture Validation for CertExpress,” Avalara will review the Certificates virtually created and attached to a Customer’s customer by CertCapture, and verify it contains the following: Customer’s customer name, Customer name, exemption reason, tax identification number (Avalara verifies that a tax identification number has been included on the Certificate, but does not verify the format or accuracy of this number), signature, and signature date. This service does not apply to Certificates uploaded by Customer (e.g., PDF files). Avalara will make standard reports available so that Customer can review the validations that have been performed and their results.
II. Extension of Scope. This SOW applies only to the specific purchases made in the Order Document. Any change in the scope of this SOW or undue delay by Customer in meeting its obligations under this SOW may require an extension in the schedule, an adjustment in the fees and expenses, or an adjustment in the work Avalara is to perform, which will be enumerated in an additional Order Document signed by the Customer.
III. Professional Fees. Customer will pay all fees specified in the Order Document. Payment obligations are non-cancellable, and fees paid are nonrefundable. Unless otherwise stated in a Services Schedule, Avalara charges a fixed fee for the Professional Services set forth in this SOW.
- Customer represents and warrants that all information and documentation provided to Avalara is true and accurate.
- Customer is responsible for all sales and use tax decisions, any Certificate management decisions, and tax positions taken.
- The scope of this Service does not include local jurisdictions unless stated in the Order Document.
- The scope of this engagement does not include any specific tax research or determination of the taxability of your company’s products or services.
- Customer should consult third party tax advisors regarding other tax concerns, such as state income or franchise tax reporting requirements. Registering for sales and use tax collection and reporting can impact federal, state, and other tax reporting requirements, all of which are outside the scope of this Service.
- If Customer engages a third party to provide services, Customer will be responsible for all third-party contracts, costs, and projects including management of all third-party personnel and delivery issues.
- Avalara will use commercially reasonable efforts to provide consistent personnel for the duration of this SOW. However, Avalara may reassign personnel at its sole discretion.
- All work will be performed remotely during Avalara business hours; Avalara will not travel to Customer’s premises under this Service.
- Customer is responsible for the payment of any additional tax, interest and/or penalties due related to the effort in this SOW.
- Avalara will begin performing the Professional Services within 30 days of Services Effective Date.
- If Customer terminates this Service without cause before the Professional Services are completed, Customer shall pay the full cost of the Professional Services set forth in the Order Document.
- This SOW will expire one year after Services Effective Date. Any service outlined in this SOW and not used by Customer will expire at that time and no fees will be refunded.
“Order Document” means a Sales Order, SOW, or other document used to purchase Services from Avalara.
“Sales Order” means Avalara’s sales order form that describes the Services, Avalara Professional Services, fees, support plans, Expenses and any special terms for using the Services that Customer has ordered.
“Services” means the Avalara service offerings to which Customer subscribes, as specified in the applicable Order Document.
“Services Effective Date” means the date on which Avalara processes Customer’s signed Order Document.
“Account” means an account enabled by Avalara for Customer to access the Services.
“Authorized User” means any employee, contractor, representative, or other person acting on Customer’s behalf who is authorized by Customer to use the Services and who has been supplied with access to the Services by either Customer or Avalara, at Customer’s written request.
“AvaTax” means Avalara’s AvaTax Service for calculating transactional taxes on the sale of goods and services, including sales, use, and value added taxes.
“CertCapture” means Avalara’s CertCapture Service for exemption certificate storage and management.
“Certificate” means any compliance document image, such as a tax exemption certificate, excise license, or federal withholding form, that is entered, uploaded, or otherwise recorded in the CertCapture Service for use in a single jurisdiction.
“Returns” means Avalara’s Service for compliance, preparation, and management of sales and use tax returns, treasury, remittance, and notice management.