Summary

Syspro customer accounts can be created and updated from iPaaS.com Customers through Manual Sync or through outbound triggers subscribed in iPaaS.com. Each transfer carries the customer number, name, short name, email address and any special handling instructions into Syspro. Keeping customer accounts aligned in Syspro is a prerequisite for order processing, because a Syspro sales order must be attached to an existing customer account.

ID Format

Manual Sync ID Format

Enter the iPaaS.com Customer ID on the iPaaS.com Manual Sync page.

Example: 4471

External ID Format

After a successful transfer, iPaaS.com saves the Syspro customer account number as the external ID on a dedicated external-ID record. That record is the primary match used to route every subsequent update to the same Syspro customer rather than creating a duplicate account.

The Customer mapping additionally writes the account number onto the Syspro customer record itself, which provides visibility on the Syspro side and acts as a fallback match when no external-ID record yet exists. Remapping Customer to a different source is supported, but it disables the fallback match for any customer that was created in Syspro before the first sync.

Deleted Record Support

Outbound delete is not supported for this entity. The integration does not implement a delete operation for customers, delete mappings are not included in the default templates, and deleting a customer in iPaaS.com will not propagate to Syspro. The Syspro customer account remains in place until it is removed there directly.

Mapping Collection Status

Status: Enabled. The collection carries no mapping filter, so every customer routed to it is processed.

Trigger Events: Create and Update. Outbound transfers are dispatched when the subscriber subscribes to the relevant iPaaS.com customer events in the Outbound Data Flows section of the subscription configuration. Until those subscriptions are enabled, no automatic transfers occur.

Duplicate or Conflicting Mappings

Add/Update Syspro Customer TO iPaaS.com operates on the same entity in the opposite direction, capturing Syspro customer accounts into iPaaS.com.

Because the two collections move customer data in opposite directions, subscribers or their MiSP should decide which system is the source of truth for customer records before enabling both, and review each collection's filters and Add/Update settings accordingly. Running both without that decision can cause values to be overwritten in each direction in turn.

Duplicate accounts are prevented by the external-ID link rather than by a configurable conflict-resolution setting. This entity does not support collision handling, so there are no selectable collision methods on this collection.

Supported Child Collections

None. This collection has no child collections — customer addresses and contacts are not written to Syspro.

System Caveats

Syspro Caveats

Customer name and short name are derived, not copied. Both are built by formula from the iPaaS.com company or personal name, converted to upper case, and truncated — the name to 50 characters and the short name to 20. Longer values are shortened silently rather than causing the transfer to fail.
Company takes precedence over personal names. Where an iPaaS.com customer carries both, the company name is used for both derived fields. Subscribers or their MiSP who need personal names to take precedence should edit the formulas in the iPaaS.com mapping editor.
Customer type is not set by this collection. Syspro uses the customer type to determine how new customer account numbers are assigned, and the Syspro default applies.
Credit, terms and classification are not set. Credit limits, terms codes, price codes and customer classes are left at their Syspro defaults for newly created accounts.

iPaaS.com Caveats

Three fields must resolve to a value. Syspro requires a customer account number, a name and an email address. An iPaaS.com customer with no email address cannot be transferred; the transfer fails and the error appears under Dashboard / Integration Monitoring / Error Logs.

Integration-Specific Caveats

Two customers can share a short name. Because the short name truncates to 20 characters, two customers whose names share their first 20 characters produce identical short names in Syspro. This does not affect matching, which uses the customer account number, but it can make the two hard to tell apart in Syspro lookups.

Setup Requirements

iPaaS.com Configuration

Subscribe to the relevant customer events under Outbound Data Flows in the subscription configuration. Until those subscriptions are enabled, customers must be transferred by Manual Sync.

Syspro Configuration

The Syspro REST API must be installed and reachable, and the subscription's API URL and credentials configured. Refer to the Syspro Installation Instructions for the full procedure.

Integration Flow

A customer is created or changed in iPaaS.com, or a subscriber initiates a Manual Sync using the iPaaS.com Customer ID.
For automatic transfers, the subscribed outbound trigger dispatches the transfer. For Manual Sync, the transfer begins directly.
The integration looks for an existing external-ID record linking this iPaaS.com customer to a Syspro account. If one is found, the transfer updates that account.
If no external-ID record exists, the integration falls back to matching a Syspro account whose customer number equals the value supplied, and links it.
If neither match succeeds, a new Syspro customer account is created.
The customer number, derived name and short name, email address and special instructions are written.
The external-ID record is saved so subsequent transfers route to the same Syspro account.

Mappings

Add/Update Syspro Customer FROM iPaaS.com

iPaaS.com data type: Customer

This collection writes the iPaaS.com Customer into Syspro as a customer account. It carries no mapping filter, so every customer routed to it is processed.

Mapping Type	Source Field (iPaaS.com)	Destination Field (Syspro)	Description
Field	`CustomerNumber`	Customer	Required. The Syspro customer account number. It is the key that identifies the account, and the transfer cannot create or update a customer without it.
Dynamic Formula	`Truncate(...ToUpper(), 50)`	Name	Required. Syspro rejects a customer with no name. Prefers the iPaaS.com company name, falling back to first and last name when the company is empty; upper-cased and truncated to 50 characters.
Field	`EmailAddress`	Email	Required. Syspro rejects a customer record with no email address. Also improves duplicate detection, since the Syspro customer lookup can match on email as well as account number.
Dynamic Formula	`Truncate(...ToUpper(), 20)`	ShortName	Recommended. An abbreviated label Syspro shows in lists and lookups. Same derivation as Name but truncated to 20 characters.
Field	`Comment`	SpecialInstrs	Optional. Free-text handling notes shown to Syspro staff on the customer record. Transferred as entered, with no filtering applied.

Dynamic Formula Documentation

The Name and ShortName mappings share one derivation rule and differ only in their truncation length:

Truncate((!string.isNullOrEmpty(Company) ? Company : string.Format("{0} {1}", FirstName, LastName)).ToUpper(), 50);

Truncate((!string.isNullOrEmpty(Company) ? Company : string.Format("{0} {1}", FirstName, LastName)).ToUpper(), 20);

Both prefer the iPaaS.com Company value and fall back to First Name and Last Name joined with a single space only when Company is empty. Both convert the result to upper case. The first truncates to 50 characters for the Syspro customer name; the second to 20 for the short name.

Error Handling

Errors raised by this collection are catalogued in the Syspro Error Messages article, which is the companion reference for the integration's error text and resolutions. The failure modes specific to this collection are an iPaaS.com customer with no email address, and one with no customer number; both are rejected by Syspro and appear under Dashboard / Integration Monitoring / Error Logs.

Testing & Validation

Test Scenarios

Create a new customer in iPaaS.com with a company name, customer number and email address, and verify a Syspro account is created with the name upper-cased.
Create a customer with no company name but with a first and last name, and verify the Syspro name falls back to the personal name.
Create a customer whose company name exceeds 50 characters and verify the Syspro name is truncated rather than the transfer failing.
Update an existing customer's email address and verify the change propagates without creating a duplicate Syspro account.
Attempt a transfer for a customer with no email address and confirm the transfer fails with an error naming the missing field.
Perform a Manual Sync using the documented ID format and confirm the correct customer is transferred.

Validation Checklist

The Syspro account number matches the iPaaS.com customer number.
The Syspro name is upper-cased and no longer than 50 characters.
The Syspro short name is no longer than 20 characters.
The email address matches the iPaaS.com customer.
Repeat transfers update rather than duplicate the Syspro account.
Outbound customer subscriptions are enabled where automatic transfers are expected.

Additional Notes

Customer addresses and contacts are out of scope. Shipping and billing addresses are not written to Syspro by this collection.
Credit terms, pricing and classification are out of scope. Syspro defaults apply to newly created accounts.
Bulk initialization is not supported. An existing customer base cannot be loaded in one operation. Subscribers or their MiSP should use bulk sync using Postman to load customers in volume.

Syspro from iPaaS.com Customer Mapping Documentation