Summary
iPaaS.com Customer records can be captured from Acumatica using an Add/Update sync method. This mapping reads the Acumatica Customer's main and primary contact data — customer number, name, email, and company — and builds an iPaaS.com Customer record, carrying the customer's addresses through a child collection. Capture is polling-based, with an on-demand Manual Sync; writing customers back into Acumatica is handled by a separate article.
ID Format
Manual Sync ID Format
When manually transferring a customer, supply the exact Acumatica CustomerID. For example, entering 10 captures the customer whose Acumatica CustomerID is 10. The integration resolves the value to the underlying record.
External ID Format
Each captured customer and address is linked back to its Acumatica source so that later transfers resolve to the same iPaaS.com record rather than creating a duplicate.
Deleted Record Support
Removal of a Customer in Acumatica is not propagated as a delete in iPaaS.com through this collection, and delete mappings are not included in the default templates.
Custom Field Support
The child address collection captures one custom field, Acumatica Primary Contact, which records whether the captured address is the Acumatica main (primary) contact. The corresponding custom field must be configured in iPaaS.com for the value to be retained; it is what lets a later outbound transfer route the address back to the Acumatica main contact slot.
Mapping Collection Status
Status: Enabled
Trigger Events: The integration periodically polls Acumatica for Customers that have changed since the last successful poll and captures them on a recurring cadence. A subscriber can also run a Manual Sync to capture a specific customer on demand. There are no external webhooks for this collection — Acumatica does not push customer changes to the integration.
Duplicate or Conflicting Mappings
This collection captures Customers from Acumatica into iPaaS.com. The following collection operates on the same entity in the opposite direction:
Add/Update Acumatica Customer FROM iPaaS.com: Writes Customer records from iPaaS.com into Acumatica.
Before enabling this inbound collection alongside the outbound "From iPaaS.com" customer collection, review and customize your mapping collection filters to prevent circular updates between the two systems, where a capture into iPaaS.com triggers a write back into Acumatica that re-triggers the capture.
Collision handling is not supported for the Acumatica Customer entity; customers are linked by their Acumatica identifier.
Supported Child Collections
Parent Collection: Add/Update Acumatica Customer TO iPaaS.com — builds the iPaaS.com Customer record from the Acumatica main and primary contact data.
Child Collection: Add/Update Acumatica Customer Address TO iPaaS.com — captures the customer's addresses from Acumatica into iPaaS.com as part of the parent transfer. It runs automatically with the parent Customer capture and is not invoked independently.
System Caveats
Acumatica Caveats
API access must be enabled for the Acumatica Customer and Contact endpoints so the integration can expand the main and primary contacts during capture.
Acumatica enforces length and format constraints on fields such as the customer name (50 characters by default). Values that exceed Acumatica's limits are stored truncated and are captured as stored.
An Acumatica contact address is captured only when its core fields (line 1, city, state, postal code, country) are populated together; a partial contact address may not be captured as a complete record.
iPaaS.com Caveats
iPaaS.com expects a valid email format for the captured email address; malformed values are rejected and logged.
The Acumatica address State maps to the iPaaS.com Region field; both represent the state, province, or region of the address.
The Acumatica Primary Contact value is captured into a custom field on the iPaaS.com address; the corresponding custom field must be configured in iPaaS.com for the value to be retained.
Dynamic formula field references use the Acumatica response field names exactly as they appear on the expanded Customer record, and these references are case-sensitive.
Integration-Specific Caveats
Main contact precedence with fallback. Name and email are read from the Acumatica main contact first. Email falls back to the primary contact email, and first name falls back to the customer name, when the main contact value is empty. The last name has no fallback — when the main contact has no last name, the captured value is empty.
Per-contact capture. Addresses are captured from each populated Acumatica contact slot (main, billing, shipping) and carried into iPaaS.com with the matching primary flags so each address keeps its role.
Read-back linkage. Each captured customer and address is linked to its Acumatica source so repeated transfers update the existing iPaaS.com record rather than creating duplicates.
Setup Requirements
Acumatica Configuration
API access must be enabled for the Acumatica Customer and Contact endpoints.
iPaaS.com Configuration
An active iPaaS.com Customer mapping collection must exist.
Polling must be configured so that changed Acumatica Customers are captured on a recurring cadence; until polling is set up, customers are captured only by a Manual Sync.
The Acumatica Primary Contact custom field must be configured for that designation to be retained.
The child collection Add/Update Acumatica Customer Address TO iPaaS.com must be active for addresses to be captured with the customer.
Authentication & Security
The integration authenticates to the Acumatica instance with OAuth 2.0, and every request carries the company header. The full authentication walkthrough is covered in the Acumatica Connections and Settings and Acumatica Installation Instructions articles; this document does not repeat it.
Integration Flow
The integration polls Acumatica for changed Customers, or a subscriber runs a Manual Sync with the Acumatica CustomerID.
The Customer is retrieved from Acumatica and its main, primary, billing, and shipping contacts and addresses are expanded.
An iPaaS.com Customer record is built from the mapped fields. Name and email are sourced primarily from the main contact, with fallbacks where the main contact value is absent.
If a Customer with the same external link already exists in iPaaS.com, the existing record is updated; otherwise a new Customer is created.
Each captured customer and address is linked back to its Acumatica source so later transfers resolve to the same iPaaS.com record.
Mappings
Add/Update Acumatica Customer TO iPaaS.com
This collection has no mapping filter; every Customer that the integration polls or that is manually transferred is captured. Subscribers who want to capture only a subset of customers can add a mapping filter to restrict which Customers are processed.
Description: Captures the parent Customer record from Acumatica's main and primary contact data into iPaaS.com.
Mapping Type | Source Field (Acumatica) | Destination Field (iPaaS.com) | Description |
Field | CustomerID | CustomerNumber | Recommended. The key field that links the captured customer back to its Acumatica source. Validate in a staging environment that every Customer produces a non-empty CustomerID, since an empty value prevents reliable matching. |
Dynamic Formula |
| FirstName | Recommended. Captures the main contact first name; when it is absent, falls back to the customer name so a usable value is still captured. |
Dynamic Formula |
| LastName | Recommended. Captures the main contact last name. The live formula has no fallback — when the main contact has no last name, the captured value is empty. Ensure the Acumatica main contact carries a last name, or validate the empty-value behavior in a staging environment before relying on it in production. |
Dynamic Formula |
| EmailAddress | Recommended. Captures the main contact email; when it is absent, falls back to the primary contact email. iPaaS.com expects a valid email format; malformed values are rejected and logged. When both are absent, the captured value is empty. |
Dynamic Formula |
| Company | Recommended. Captures the main contact company name. There is no fallback; when the main contact has no company name, the captured value is empty. |
Add/Update Acumatica Customer Address TO iPaaS.com
This child collection has no mapping filter; every address found on the parent customer's contacts is captured. It runs as part of the parent Customer capture and is never invoked standalone.
Description: Captures each populated Acumatica contact address (main, billing, shipping) into an iPaaS.com address, carrying its primary flags so the address keeps its role.
Mapping Type | Source Field (Acumatica) | Destination Field (iPaaS.com) | Description |
Field | AddressLine1 | Address1 | Recommended. The primary street line of the captured address. |
Field | AddressLine2 | Address2 | Optional. Suite, unit, or additional street detail. |
Field | City | City | Recommended. Part of a complete captured address. |
Field | State | Region | Recommended. The Acumatica field is named State but it represents the state, province, or region, which iPaaS.com stores as Region. |
Field | PostalCode | PostalCode | Recommended. Part of a complete captured address. |
Field | Country | Country | Recommended. The captured value is in the country format Acumatica stores (for example, |
Dynamic Formula |
| FirstName | Recommended. Captures the contact first name; when it is absent, falls back to the contact display name so a usable name value is captured. |
Field | LastName | LastName | Recommended. Contact identity on the captured address. |
Field | CompanyName | Company | Recommended. The business name associated with the address, most relevant for the main contact. |
Field | Phone1 | PhoneNumber | Optional. A contact phone on the captured address. |
Field | IsPrimaryBilling | IsPrimaryBilling | Recommended. Marks the address captured from the Acumatica billing contact as the primary billing address, preserving the role for a later outbound transfer. |
Field | IsPrimaryShipping | IsPrimaryShipping | Recommended. Marks the address captured from the Acumatica shipping contact as the primary shipping address, preserving the role for a later outbound transfer. |
Field | IsPrimaryContact | Acumatica Primary Contact | Recommended. Captures whether the address is the Acumatica main (primary) contact into a custom field. This designation lets a later outbound transfer route the address back to the Acumatica main contact slot. The custom field must be configured in iPaaS.com for the value to be retained. |
Error Handling
Missing CustomerID: The capture fails because the Acumatica Customer has no CustomerID, so iPaaS.com cannot identify the record. Resolution: ensure every Customer in Acumatica has a unique CustomerID before transferring.
Invalid email format: The captured email does not follow a standard format. Resolution: correct the email in Acumatica. The integration rejects invalid emails and logs an error.
String length exceeded: The customer name is longer than the default 50-character limit. Resolution: shorten the name or extend the field length in Acumatica via customization. The captured value reflects what Acumatica stores.
Null contact data: The main contact has no first or last name and no usable fallback is available. Resolution: populate the Acumatica main contact, or rely on the customer-name fallback for the first name.
If the Acumatica web services endpoint is temporarily unavailable during a transfer, the capture fails and an error appears in Dashboard / Integration Monitoring / Error Logs; the customer is re-captured on the next poll or manual sync.
Testing & Validation
Test Scenarios
Capture a new Acumatica Customer with main, billing, and shipping addresses and verify all fields and address roles in iPaaS.com.
Update a contact field on an existing Acumatica Customer and verify the change is captured on the next poll.
Capture a Customer whose main contact has no last name and confirm the captured LastName is empty (no fallback).
Run a Manual Sync using the exact Acumatica CustomerID and confirm the customer is captured.
Capture a Customer with addresses on multiple contact slots and verify each is captured with its primary flags.
Validation Checklist
Every Acumatica Customer produces a non-empty CustomerID.
The first-name and email fallbacks behave as expected.
The last-name field is empty only when the main contact has no last name.
Captured emails are in a valid format.
The Acumatica Primary Contact custom field is configured so the designation is retained.
Additional Notes
This collection is capture-only. Changes made to a Customer in iPaaS.com are not written back to Acumatica through this collection.
Because capture is polling-based, a change in Acumatica is reflected in iPaaS.com on the next poll rather than instantly. Subscribers who need an immediate capture can run a Manual Sync.
The child address collection runs with the parent; it cannot be captured on its own.