New here? This page is a configuration reference for teams implementing the Avalara AvaTax integration in iPaaS.com. It documents scope, design decisions, and settings to confirm before go-live. These are not product defects, and most items are handled during implementation by iPaaS.com or your Managed Integration Service Provider (MiSP). See Understanding Integration Scope & Known Limitations for how we document this for every integration.
Introduction
These are the known limitations of the Avalara AvaTax integration. They are inherent to the current design of the integration and the capabilities of the Avalara AvaTax API, and they apply to all subscribers at the time this documentation was written.
Platform Scope and Tested Versions
This integration was built for Avalara AvaTax and its exemption-certificate management capabilities. It calls the Avalara AvaTax REST API v2 at https://rest.avatax.com (production) and https://sandbox-rest.avatax.com (sandbox), and was validated against the Avalara AvaTax REST API v2 production endpoints as of July 2026.
Not built for: other Avalara product lines or APIs (for example, Avalara for Communications or other Avalara services). If Avalara launches a separate product line or a materially different API version in the future, this integration will not automatically support it.
1. No bulk historical sync
The integration does not provide a bulk initial-load of existing companies or customers. Records are synchronized as they are created or updated, or on demand from the Manual Sync page.
What this means for you: To load a large existing data set into Avalara AvaTax, use the bulk sync using Postman workflow. For ongoing changes, no bulk load is needed — records flow as they change.
2. Deletions are not propagated
Deleting a company or customer in one system does not delete the corresponding record in the other. Delete mappings are not included in the default templates.
What this means for you: Manage record removal directly in each system. If your workflow needs deletions to propagate, submit a feature request through your iPaaS.com partner channel describing the requirement.
3. Certificate updates are captured on a sync, not in real time
Avalara AvaTax does not send change notifications (webhooks) to iPaaS.com. Certificate details captured back into iPaaS.com are retrieved by Manual Sync or on the integration's scheduled polling.
What this means for you: After a certificate changes in Avalara AvaTax, allow for the next Manual Sync or scheduled poll for the change to appear on the iPaaS.com customer. This is the appropriate shape for Avalara AvaTax, which does not offer outbound webhooks.
4. One certificate per company transfer
Each company transfer creates or updates a single exemption certificate for that company.
What this means for you: If a company needs more than one certificate managed, coordinate that with your implementation team or MiSP; a single company transfer handles one certificate.
5. Certificate creation requires a complete set of certificate fields
A certificate is created only when all required certificate fields are supplied (signed date, file name, expiration date, exemption reason, and exposure zone). A customer is attached to the certificate only when all certificate-customer fields are supplied. If required certificate fields are missing, the company still saves but the certificate is skipped.
What this means for you: Provide the full set of certificate fields to have a certificate created. Review the Avalara AvaTax Company From iPaaS.com Mapping Documentation for the exact fields.
6. Exposure zones and exemption reasons must match Avalara AvaTax values
The exposure zone and exemption reason on a certificate are resolved against the values configured in your Avalara AvaTax account, matched by name. If a supplied value does not match, it is left unset and the dependent certificate portion is skipped while the company still saves.
What this means for you: Confirm that the exposure zone and exemption reason values you send match those configured in Avalara AvaTax. Subscribers or their MiSP can adjust the mapping formulas so an unmatched value rejects the whole record instead, if that is preferred.
Summary
This document describes six known limitations of the Avalara AvaTax integration at the time of writing. For detailed field-level behavior, see the integration's Mapping Documentation articles.