Skip to main content

Avalara AvaTax Error Messages

Error messages you may encounter when synchronizing companies, customers, and exemption certificates between iPaaS.com and Avalara AvaTax, with causes and resolutions.

Overview

This article catalogs the error messages you may see in iPaaS.com when synchronizing data with Avalara AvaTax. Errors appear in Dashboard / Integration Monitoring / Error Logs. Each error carries a stable code (for example, AVTX-EXTN-1001) that you can search this page for with Ctrl+F. Most errors originate from Avalara AvaTax's response to a record that does not meet its requirements.

Some resolutions refer to your Managed Integration Service Provider (MiSP) — the partner who manages your mappings, configuration, credentials, and reconciliation for this integration.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Supported Flows

  • Add/Update Avalara AvaTax Customer FROM iPaaS.com

  • All Flows (errors that can occur on any flow)

Error Collection

Add/Update Avalara AvaTax Customer FROM iPaaS.com

Duplicate customer not reconciled

AVTX-BIZL-1001 - 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 flag and the lookup disagree.

  • Resolution: Confirm the customer's code exists and is unique in Avalara AvaTax, then re-run the transfer. If the error persists, your MiSP should review the customer record and its mapping; if it cannot be resolved there, the MiSP can escalate to iPaaS.com Support.

Customer address could not be created or linked

AVTX-EXTN-1002 - The customer was created, but an address could not be created or linked: {error}

  • Description: The customer was created in Avalara AvaTax, but creating or linking one of its ship-to / bill-to addresses failed. The specific Avalara AvaTax error is included at the end of the message. The customer's identifiers were saved, so the transfer can resume without duplicating the customer.

  • Resolution: Read the included Avalara AvaTax error to see why the address was rejected, then correct the failing address — typically a missing street, city, country, or postal code (and a region when the country is the United States or Canada) — and re-run the transfer.

All Flows

Avalara AvaTax API call failed

AVTX-EXTN-1001 - Error calling Avalara AvaTax {action}: {message} (Http Code: {code})

  • Description: Avalara AvaTax rejected or failed the request; the message includes Avalara's own response and the HTTP status code. This is the general error for any Avalara AvaTax rejection. Common cases include:

  • A missing or invalid required field — for example, a company name, a valid two-character country code, or a customer's address fields.

  • A duplicate company code — Avalara reports "The company code … has already been defined," which surfaces when the Company mapping collection's Collision Handling Method is set to Error.

  • A request limit exceeded — Avalara returns a "Too many requests" / RequestLimitExceeded response when its rate limit is hit. See Avalara's RequestLimitExceeded reference.

  • A transient Avalara-side failure.

  • Resolution: Read the Avalara message included in the error log and act on what it identifies:

  • For a missing or invalid field, correct that field on the source record and re-run.

  • For a duplicate company code, set the Company mapping collection's Collision Handling Method to Update and Link (or Remap and Link) so the integration matches and updates the existing company instead of failing; keep each company's company code stable.

  • For a request-limit error, retry after a short wait and stagger large Manual Sync jobs rather than running them all at once.

  • If the error persists and the record looks correct, your MiSP should review the record and the Avalara AvaTax account configuration.

Invalid primary key data

AVTX-VALD-1001 - Invalid data passed to {entity}.SetPrimaryKey.{field}: {value}

  • Description: The integration received an identifier value it could not use when linking a record to its Avalara AvaTax counterpart. The value did not match the format expected for that record's key.

  • Resolution: Verify the identifier value on the record being linked. If the value looks correct, your MiSP should review the mapping that supplies the identifier for that collection.

Related Documents

Related Articles
Did this answer your question?