Overview
Customer records from iPaaS are synchronized with Avalara Exemption Certificate Management through the API integration. Avalara Exemption Certificate Management supports automatic synchronization of customer records from iPaaS using API-based polling and dynamic field mapping. The purpose of this mapping is to ensure consistent transfer of customer demographic and address information for exemption certificate management.
Field Constraints
Customercode: Must Be Unique, Alphanumeric String.
Emailaddress: Must Be Valid Email Format.
Postalcode: Numeric Or Alphanumeric Depending On Country, Max 10 Characters.
Region: Must be valid 2–3 character state/province code where applicable.
Mapping Collection Status
Status: Enabled
Trigger Events: Customer Add or Update in Avalara ECM
Id Format
When manually transferring data from iPaaS for a Customer, such as CustomerNumber CUST-10001, it is essential to enter the correct CustomerNumber into the iPaaS input field on the manual sync page as the customerCode.
Custom Field Support Description
Avalara Exemption Certificate Management stores supplementary Customerinformation within custom fields. When retrieving Customer through the Avalara ECM API, these fields are exposed via the customfields property.
In iPaaS.com flows, this customfields property can be accessed to retrieve values for specific custom fields that are required for data transfer or mapping.
To transfer custom fields from iPaaS.com, the following formula can be applied to access a custom field value by its name from the customfields property:
return GetValueFromCustomField(AdditionalProperties, "custentitytestcat");
System Caveats
iPaaS Caveats
Missing or malformed email addresses will cause customer rejection.
CustomerNumber must be unique.
Avalara Exemption Certificate Management Caveats
Country and region codes must match Avalara’s validation rules.
Postal codes must follow the format rules per country.
Setup Requirements
iPaaS Configuration
Customer entity with address collections enabled.
Mapping formulas defined for dynamic fields..
Avalara Exemption Certificate Management Configuration
API credentials with Customer write permissions.
Active Exemption Certificate Management account with enabled API access.
Authentication & Security
Credential Type: Integration key/ Integration Password
Stored in iPaaS presets for secure connectivity.
Integration Flow
Customer record is created/updated in iPaaS.
Mapping collection extracts values using static fields and dynamic formulas.
Transformed data is sent via API to Avalara Exemption Certificate Management.
Exemption Certificate Management validates required fields (customerCode, email, name).
Customer record is stored or updated in Exemption Certificate Management.
Mappings
Avalara Exemption Certificate Management Customer From iPaaS (Parent)
Mapping Type | Source Field (iPaaS) | Destination Field (Avalara ECM) | Description |
Field | CustomerNumber | customerCode | Required: Unique customer code |
Field | EmailAddress | emailAddress | Required: Primary customer email |
Dynamic Formula |
| name | Required: Full customer name |
Dynamic Formula |
| line1 | Customer address line 1 |
Dynamic Formula |
| city | Customer city |
Dynamic Formula |
| postalCode | Customer postal code |
Dynamic Formula |
| country | Customer country |
Dynamic Formula |
| region | Customer state/region |
Errors
Validation Rules
Email must be valid format.
CustomerNumber must be unique.
Country/Region codes must follow Avalara schema.
Testing & Validation
Test Scenarios
Valid Custome → Syncs successfully to Exemption Certificate Management.
Missing Email → Error logged, customer rejected.
Duplicate CustomerNumber → Update required instead of create.
Invalid Postal Code → API error returned.
Validation Rules
Email must be valid format.
CustomerNumber must be unique.
Country/Region codes must follow Avalara schema.
Validation Checklist
CustomerNumber is unique
Address fields populated correctly
Email valid format.
Country/Region comply with Avalara standards.
Additional Notes
Customer Code must remain unique and case-sensitive to avoid conflicts. Email address is required for certificate linking and must follow valid format rules. Address fields may be auto-normalized by Avalara, and any validation errors are logged in iPaaS for review and retry. Address child collection must sync successfully after parent company creation to avoid orphaned addresses.