Overview
This article catalogs the error messages you may see in iPaaS.com when synchronizing data with Avalara AvaTax, grouped by mapping collection flow, along with what causes each error and how to resolve it. Errors appear in Dashboard / Integration Monitoring / Error Logs. Most errors originate from Avalara AvaTax's response to a record that does not meet its requirements.
Supported Flows
Add/Update Avalara AvaTax Company FROM iPaaS.com
Add/Update Avalara AvaTax Customer FROM iPaaS.com
Update Avalara AvaTax Customer Certificate TO iPaaS.com
All Flows (errors that can occur on any flow)
Add/Update Avalara AvaTax Company FROM iPaaS.com
Duplicate company code
The company code '{code}' has already been defined.
Description: Avalara AvaTax returns this when a company with the same company code already exists. It occurs when a company is transferred whose company code matches an existing Avalara AvaTax company.
Resolution: Set the mapping collection's Collision Handling Method to Update and Link so the integration matches and updates the existing company instead of failing. Keep each company's company code stable so the match works consistently.
Missing required company data
Avalara AvaTax rejects the company (a required field is missing or invalid).
Description: Avalara AvaTax requires a company name and a valid two-character country code. A company missing a required value, or a certificate whose exposure zone or exemption reason does not match a value configured in your Avalara AvaTax account, is rejected or partially skipped.
Resolution: Ensure the company name and default country are provided, and that any exposure zone and exemption reason values match valid values in your Avalara AvaTax account.
Add/Update Avalara AvaTax Customer FROM iPaaS.com
Duplicate customer not found
Avalara indicated this customer was a duplicate, but no customer with a matching customer_number was found.
Description: Avalara AvaTax reported the customer as a duplicate, but a follow-up lookup by customer code returned no matching customer. This is an uncommon state where the duplicate and the lookup disagree.
Resolution: Verify the customer code in Avalara AvaTax. If the error persists, contact iPaaS.com Support at support@ipaas.com.
Missing required customer data
Avalara AvaTax rejects the customer (a required field is missing).
Description: Avalara AvaTax requires a name, street address line, city, country, and postal code on every customer (and a region when the country is the United States or Canada). This occurs when the iPaaS.com customer has no primary billing address, so the address fields are empty.
Resolution: Ensure the customer has a complete primary billing address in iPaaS.com before syncing.
Update Avalara AvaTax Customer Certificate TO iPaaS.com
Missing customer number or email
iPaaS.com rejects the customer (customer number or email address is missing).
Description: iPaaS.com requires a customer number and an email address. This occurs when the Avalara AvaTax customer being captured is missing either value.
Resolution: Ensure the Avalara AvaTax customer has a customer code and an email address before syncing.
All Flows
Request limit exceeded
Too many requests from the same IP. Please wait before trying again.
Description: Avalara AvaTax limits how many requests it accepts from the same source in a short period and returns a request-limit error when that is exceeded. See Avalara's RequestLimitExceeded reference.
Resolution: Retry the transfer after a short wait. To avoid the limit, stagger large Manual Sync jobs rather than running them all at once.