Summary
This mapping collection creates and updates customers in Avalara AvaTax from iPaaS.com customer data. These customer records are the bill-to records Avalara AvaTax uses for exemption-certificate management. The customer's identifying details are mapped directly, while the address values are taken from the customer's primary billing address in iPaaS.com.
ID Format
Manual Sync ID Format
This is a FROM iPaaS.com collection, so the value entered on the iPaaS.com Manual Sync page is the iPaaS.com-side record id: the numeric customer id shown on the customer's record in iPaaS.com.
External ID Format
After a successful transfer, iPaaS.com records the Avalara AvaTax customer code as the external id on a dedicated external-id record. That external-id record routes subsequent updates to the same Avalara AvaTax customer rather than creating a duplicate.
Deleted Record Support
Outbound delete is not supported. Deleting a customer in iPaaS.com does not remove the corresponding customer in Avalara AvaTax, and delete mappings are not included in the default template.
Custom Field Support
This mapping collection does not use custom fields. All values it sends to Avalara AvaTax come from standard customer and address fields.
Mapping Collection Status
Status: Enabled
Trigger Events: Create, Update
Duplicate or Conflicting Mappings
The following mapping collection operates on the same customer in the opposite direction:
Update Avalara AvaTax Customer Certificate TO iPaaS.com brings Avalara AvaTax certificate details back onto the iPaaS.com customer.
Review your Add/Update settings and the direction of each collection so the two do not overwrite each other's data. Decide which system is the source of truth for customer data before enabling automatic transfers.
Supported Child Collections
None. The customer's address is provisioned inline from the customer's primary billing address in iPaaS.com; there is no separate address mapping collection to configure.
System Caveats
Avalara AvaTax Caveats
Company scope: customers are created under the single Avalara AvaTax company identified by the API Client Id subscription setting.
Unique customer code: the customer code must be unique within that Avalara AvaTax company.
Required address data: Avalara AvaTax requires a name, street address line, city, country, and postal code on every customer; a region is additionally required when the country is the United States or Canada.
Rate limiting: 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. This integration does not automatically reschedule a transfer that hits the limit; the affected transfer fails and appears in Dashboard / Integration Monitoring / Error Logs, and can be retried. Stagger large manual sync jobs to reduce the chance of hitting the limit.
iPaaS.com Caveats
Primary billing address required: the city, region, postal code, country, and street line are read from the customer's primary billing address in iPaaS.com. A customer with no primary billing address will be missing the address fields Avalara AvaTax requires, and the transfer will fail.
Setup Requirements
iPaaS.com Configuration
To transfer customers automatically, enable the iPaaS.com Customer outbound triggers in the subscription's Outbound Data Flows section — subscribe to customer/created and customer/updated. No automatic transfers occur until those triggers are enabled. Manual Sync is always available from the iPaaS.com Manual Sync page.
Avalara AvaTax Configuration
The connection uses the Avalara AvaTax API Url, API User, API Password, and API Client Id subscription settings. The API Client Id identifies the Avalara AvaTax company under which customers are created.
Integration Flow
A customer is created or updated in iPaaS.com.
The mapping collection builds the Avalara AvaTax customer record, taking the address values from the customer's primary billing address.
The integration creates the customer in Avalara AvaTax under the configured company.
If Avalara AvaTax reports the customer already exists, the integration updates the existing customer instead of creating a duplicate.
When a new customer is created, the integration sends that customer a CertExpress invitation email requesting their exemption certificate.
Mappings
Add/Update Avalara AvaTax Customer FROM iPaaS.com
This mapping collection does not have a mapping filter applied; all records are processed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Avalara AvaTax) | Description |
Field | CustomerNumber | customerCode | Required. Unique customer code; must be unique within the Avalara AvaTax company. |
Field | EmailAddress | emailAddress | Recommended. Main customer email address; also used to deliver the CertExpress invitation. |
Dynamic Formula | (Company == null || Company == "") ? (FirstName +" "+ LastName) : Company | name | Required. Friendly customer name: the company name when present, otherwise first and last name combined. |
Dynamic Formula |
| contactName | Optional. Main contact person's name. |
Dynamic Formula |
| line1 | Required. Street address line, from the primary billing address. |
Dynamic Formula |
| city | Required. City, from the primary billing address. |
Dynamic Formula |
| region | Recommended. Region (state/province) as an ISO 3166 code; required when the country is the US or Canada. |
Dynamic Formula |
| postalCode | Required. Postal/zip code, from the primary billing address. |
Dynamic Formula |
| country | Required. Country (ISO 3166 code or name), from the primary billing address. |
Static |
| IsBill | Set to true by design, marking the record as a bill-to customer. |
Error Handling
Missing required address fields: If the customer has no primary billing address, the name, street line, city, country, or postal code will be empty and Avalara AvaTax rejects the record. Ensure the customer has a primary billing address before syncing.
Duplicate customer code: If a customer with the same customer code already exists in Avalara AvaTax, the integration updates the existing customer rather than creating a duplicate.
Testing & Validation
Test Scenarios
Create a new customer in iPaaS.com with a complete primary billing address and verify it is created in Avalara AvaTax, and that a CertExpress invitation email is sent.
Update an existing customer's email or address in iPaaS.com and verify the change propagates to the same Avalara AvaTax customer (no duplicate created).
Attempt to sync a customer with no primary billing address and confirm the transfer fails with a message in Error Logs.
Manually sync a customer by its iPaaS.com customer id from the Manual Sync page and confirm success.
Validation Checklist
Customer code is unique within the Avalara AvaTax company.
Primary billing address is populated (street line, city, region, postal code, country).
Email address is a valid format.
Additional Notes
When a new customer is created, the integration automatically sends that customer a CertExpress invitation email requesting their exemption certificate. This is sent only for newly created customers, not on subsequent updates, so a valid email address should be provided.