Summary
This mapping collection captures customer and exemption-certificate details from Avalara AvaTax and updates the matching customer in iPaaS.com. It records a reference to each of the customer's Avalara AvaTax exemption certificates on the iPaaS.com customer and derives the customer's name fields from the Avalara AvaTax contact name, so certificate status is visible against the customer in iPaaS.com.
ID Format
Manual Sync ID Format
This is a TO iPaaS.com collection, so the value entered on the iPaaS.com Manual Sync page is the Avalara AvaTax-side record id: the Avalara AvaTax customer code. Example: CUST001.
External ID Format
After a successful transfer, iPaaS.com records the external id on a dedicated external-id record so subsequent transfers update the same iPaaS.com customer rather than creating a duplicate.
Deleted Record Support
Delete is not supported for this collection. Removing a customer or certificate in Avalara AvaTax does not delete the corresponding iPaaS.com customer.
Custom Field Support
The captured certificate references are written to the Avatax Certificates custom field on the iPaaS.com customer. That custom field must exist on the customer for the value to be stored.
Mapping Collection Status
Status: Enabled
Trigger Events: Update (the collection updates the matching iPaaS.com customer)
Duplicate or Conflicting Mappings
The following mapping collection operates on the same customer in the opposite direction:
Add/Update Avalara AvaTax Customer FROM iPaaS.com writes iPaaS.com customers out to Avalara AvaTax.
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.
System Caveats
Avalara AvaTax Caveats
No webhooks from Avalara AvaTax: Avalara AvaTax does not push change notifications to iPaaS.com, so this collection relies on Manual Sync or scheduled polling; changes in Avalara AvaTax appear in iPaaS.com after the next sync rather than immediately.
Certificate links point to the Avalara AvaTax exemptions portal: the stored certificate reference links to the Avalara AvaTax exemptions site; the production and sandbox portals have different addresses, so links reflect the environment the subscription is connected to.
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 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.
iPaaS.com Caveats
Matching customer must exist: this collection updates an existing iPaaS.com customer, matched by customer number. The customer must already be present in iPaaS.com.
Avatax Certificates custom field: the certificate references are written to the Avatax Certificates custom field on the iPaaS.com customer, which must exist for the value to be stored.
Setup Requirements
iPaaS.com Configuration
Manual Sync is always available from the iPaaS.com Manual Sync page. The integration can also retrieve customers changed in Avalara AvaTax on a schedule; there is no webhook (event-driven) transfer because Avalara AvaTax does not send webhooks.
Avalara AvaTax Configuration
The connection uses the Avalara AvaTax API Url, API User, API Password, and API Client Id subscription settings.
Integration Flow
The integration retrieves the customer from Avalara AvaTax along with the customer's exemption certificates.
For each certificate, it builds a certificate reference that includes the exposure-zone region and a link to the certificate in the Avalara AvaTax exemptions portal.
It updates the matching iPaaS.com customer, storing the certificate references in the Avatax Certificates custom field and setting the customer's name, company, and email fields.
Mappings
Update Avalara AvaTax Customer Certificate TO iPaaS.com
This mapping collection does not have a mapping filter applied; all records are processed.
Mapping Type | Source Field (Avalara AvaTax) | Destination Field (iPaaS.com) | Description |
Field | customerCode | CustomerNumber | Required. The customer number that identifies the customer in iPaaS.com and matches the certificate data to the correct customer. |
Field | emailAddress | EmailAddress | Required. The customer's email address. |
Dynamic Formula |
| FirstName | Optional. The portion of the Avalara AvaTax contact name before the first space; the whole value when there is no space. |
Dynamic Formula |
| LastName | Optional. The portion of the Avalara AvaTax contact name after the first space; empty when there is no space. |
Dynamic Formula |
| Company | Optional. The company on the iPaaS.com customer; empty when the customer name equals the contact name, otherwise the customer name. |
Field | CertificateURL | Avatax Certificates | Optional. A reference to each of the customer's Avalara AvaTax exemption certificates (exposure-zone region and a link to the certificate in the exemptions portal), stored in the Avatax Certificates custom field. |
Error Handling
Missing customer number or email: iPaaS.com requires a customer number and an email address; a record missing either is rejected. Ensure both are present on the Avalara AvaTax customer.
Customer not found in iPaaS.com: this collection updates an existing iPaaS.com customer; if no matching customer exists, there is nothing to update.
Testing & Validation
Test Scenarios
Manually sync an Avalara AvaTax customer by its customer code and verify the matching iPaaS.com customer is updated with the certificate references in the Avatax Certificates custom field.
Verify a customer with multiple certificates records a reference for each certificate.
Confirm the first and last name are derived correctly from the Avalara AvaTax contact name (with and without a space in the contact name).
Confirm the certificate links resolve to the correct Avalara AvaTax exemptions portal for the connected environment.
Validation Checklist
The matching iPaaS.com customer exists and is identified by customer number.
The Avatax Certificates custom field exists on the iPaaS.com customer.
Customer number and email address are present.
Additional Notes
Because Avalara AvaTax does not send webhooks, certificate changes are reflected in iPaaS.com only after a Manual Sync or the next scheduled poll, not in real time.