Summary
Customer records from iPaaS.com can be synchronized into Acumatica using a manual sync method. This mapping supports the synchronization of customer data from iPaaS into Acumatica via the Customer API.
Mapping Collection Status
Mapping Status: Enabled.
Trigger Events: The sync is triggered manually or when a customer record is updated in iPaaS.
ID Format: When manually syncing, the correct iPaaS CustomerID must be entered (e.g., Customer John Doe with ID 10 must be entered as 10).
Conflicting Mappings: This mapping applies only to Customer records. Ensure no other mappings target the same Acumatica entity to prevent data from being overwritten.
Supported Child Collections
The integration supports the synchronization of the parent customer and its related child collections:
Acumatica Customer Address From iPaaS: Maps primary, billing, and shipping addresses.
System Caveats
iPaaS Caveats
In Acumatica, addresses are configured in three different locations, and you can only designate one address for each type. When mapping fields, the system will use the address from the specified collection.
IsPrimaryContact- set to true to upload as the primary contact.
IsPrimaryBilling – set to true to upload as the billing address.
IsPrimaryShipping – set to true to upload as the shipping address.
NOTE: When using the "send statements by email" flag in template mappings, you must provide a primary billing contact. This is because only one address can be defined as the primary billing address. If this is not done, the system cannot maintain a 1:1 data relationship for addresses, and debug logs will show an error. Email address must be specified if any of the following options is activated:
|
Acumatica Caveats
Customer addresses are stored as primary and shipping address types. Therefore, mapping requires correct tagging.
Setup Requirements
iPaaS Configuration
Customer ID: Unique identifier in iPaaS.
FirstName / LastName: Must be populated for CustomerName formula.
Acumatica Configuration
CustomerID: Map to iPaaS Id.
BillingAddressOverride/ShippingAddressOverride: Set to true to use imported addresses.
Authentication & Security
API Key/Token: Used to access iPaaS API for fetching customer and address data.
Integration Flow
Retrieve Data: Get customer data from iPaaS.
Map Fields: For each customer record, map the required and recommended fields to the corresponding Acumatica Customer entity.
Map Addresses: If there are address records, map them to the Acumatica Customer Address From iPaaS child collection.
Apply Values: Apply any necessary static values or dynamic formulas during the mapping process.
Mappings
Customer (Parent)
Mapping Type | Source Field (iPaaS) | Destination Field (Acumatica) | Description |
Field | Id | CustomerID | Required: iPaaS Customer ID |
Static | EOM | StatementCycleID | Billing cycle |
Field | EmailAddress | Customer email | |
Static | DEFAULT | CustomerClass | The Customer Class must be configured with a value that exists within the end user's Acumatica installation. Available classes can be referenced in Acumatica form ID AR201000. The specific class used should align with the user's business needs and Acumatica. For procedures and more information, see your Acumatica documentation. |
Static | true | BillingAddressOverride | Billing Address Override must be statically set toTRUE for this integration. |
Static | true | BillingContactOverride | Billing Contact Override must be statically set to TRUE for this integration. |
Static | false | SendStatementsbyEmail | Send Statements By Email must be statically set to TRUE for this integration. |
Static | true | ShippingAddressOverride | Shipping Address Override must be statically set to TRUE for this integration. |
Static | true | ShippingContactOverride | ShippingContactOverride must be statically set to TRUE for this integration |
Static | EOM | StatementCycleID | The Statement Cycle ID must be configured with a value that exists within the end user's Acumatica installation. Available cycle IDs can be referenced in Acumatica form ID AR2028PL. The specific cycle ID should be selected based on the user's configuration and business requirements, rather than being statically set to EOM. For procedures and more information, see your Acumatica documentation. |
Dynamic Formula |
| CustomerName | Combines the first and last names to create a full name for the customer. It merges the first name and last name, separated by a space, to display the customer’s complete name in a single field in iPaaS.com and assigns it to the CustomerName field in Acumatica. |
Acumatica Customer Address From iPaaS (Child)
NOTE: When using the "send statements by email" flag in template mappings, you must provide a primary billing contact. This is because only one address can be defined as the primary billing address. If this is not done, the system cannot maintain a 1:1 data relationship for addresses, and debug logs will show an error. Email address must be specified if any of the following options is activated:
|
Mapping Type | Source Field (iPaaS) | Destination Field (Acumatica) | Description |
Field | Address1 | AddressLine1 | Required |
Field | Address2 | AddressLine2 |
|
Field | City | City | Required |
Static | US | Country | The country must be provided in accordance with Acumatica's country format requirements to ensure compatibility with the integration. For example, US – United States of America. For procedures and more information, see your Acumatica documentation. |
Field | PostalCode | PostalCode | Required |
Field | Region | State | Required |
Field | PhoneNumber | Phone1 | Primary phone |
Field | Company | CompanyName | Company name |
Field | FirstName | FirstName | Required |
Field | LastName | LastName | Required |
Field | IsPrimaryBilling | IsPrimaryBilling | Set to TRUE to upload as the billing address Note: Template mappings include a flag to send statements by email, which requires a primary billing contact to be provided. As noted above, only one address may be defined as the primary billing address to maintain a 1: 1 data relationship with addresses. If this is not performed, then debug logs may contain the following error: Email address must be specified if any of the following options is activated: Send Statements by Email, Send Invoices by Email, Send Dunning Letters by Email |
Field | IsPrimaryShipping | IsPrimaryShipping | Set to TRUE to upload as the shipping address Note: Template mappings include a flag to send statements by email, which requires a primary billing contact to be provided. As noted above, only one address may be defined as the primary billing address to maintain a 1: 1 data relationship with addresses. If this is not performed, then debug logs may contain the following error: Email address must be specified if any of the following options is activated: Send Statements by Email, Send Invoices by Email, Send Dunning Letters by Email |
Field | Acumatica Primary Contact | IsPrimaryContact | Set to TRUE to upload as the primary contact. Note: Template mappings include a flag to send statements by email, which requires a primary billing contact to be provided. As noted above, only one address may be defined as the primary billing address to maintain a 1: 1 data relationship with addresses. If this is not performed, then debug logs may contain the following error: Email address must be specified if any of the following options is activated: Send Statements by Email, Send Invoices by Email, Send Dunning Letters by Email |
Dynamic Formula |
| Id | Retrieves Acumatica Customer Address Id if it exists as external Id for an iPaaS.com Customer Address for the system. It is recommended to use only in Update mapping collection if separate mapping collection are being used. |
Error Handling
Collection: Customer (Parent)
Missing CustomerID
Description: ID not provided
Resolution: Populate iPaaS Id
Invalid Email
Description: Email format invalid
Resolution: Provide valid email
Collection: Customer Address
Missing Required Fields
Description: Address1, City, First/Last name required
Resolution: Validate input before sync
Testing & Validation
Validation Checklist
CustomerID correctly mapped.
Dynamic name formula working.
Addresses correctly assigned to billing/shipping.
Email validation passed.
Test Scenarios
Sync a new customer with primary billing and shipping addresses → Verify all fields.
Update existing customer address → Ensure override fields work correctly.
Additional Notes
The child collection must be synced after the parent.
Ensure the primary billing contact exists for statement sending.