NetSuite Employee From iPaaS.com Mapping Documentation

An iPaaS.com employee can be created and updated in NetSuite. The integration maps the employee's name, email, phone, currency, and subsidiary, and through a child collection the employee's address. Employees transfer on demand from the iPaaS.com Manual Sync page or automatically when outbound employee triggers are enabled.

ID Format

Manual Sync ID Format

Enter the iPaaS.com record ID of the employee on the Manual Sync page.

External ID Format

On a successful transfer, the iPaaS.com employee ID is written to the NetSuite employee's External ID, and the NetSuite internal ID is recorded as the external-ID link on the iPaaS.com employee. On update, the integration resolves the existing NetSuite employee by that external-ID link, so subsequent transfers update the existing employee rather than creating a duplicate.

Deleted Record Support

Outbound delete is not provided for employees — there is no Employee delete collection, so a deletion in iPaaS.com does not remove the NetSuite employee. Deactivate or remove the employee in NetSuite using your normal process.

Custom Field Support

The integration carries an example employee custom value to the NetSuite custom field custentity1. Any NetSuite custom field used by the integration must be created in NetSuite (Customization → Lists, Records & Fields) with a matching iPaaS.com custom field of the same Field ID.

Mapping Collection Status

Status: Enabled. Separate Add and Update collections (each with an Address child).
Trigger Events: Create and Update. Automatic transfers fire on the iPaaS.com employee outbound triggers subscribed in Outbound Data Flows; the collection is also available on demand from the Manual Sync page.

Duplicate or Conflicting Mappings

The Add and Update collections write the same NetSuite employee; the Update collection resolves the existing NetSuite record by external ID first. Matching depends on the external-ID link — keep it intact so updates do not create duplicates.

Supported Child Collections

NetSuite Employee Address FROM iPaaS.com (Add and Update) — the employee's address.

System Caveats

NetSuite Caveats

First name, last name, and subsidiary are required. NetSuite requires a name and, on OneWorld accounts, a subsidiary on an employee record.
Subsidiary is resolved by name. The subsidiary is looked up by name and the transfer fails with an error if the name does not exist in NetSuite (the shipped name is a placeholder — see Setup Requirements).
Currency is required. The employee currency is set from a static value (the base currency); confirm it matches your account.

iPaaS.com Caveats

Employee data type. This collection writes from the iPaaS.com Employee entity; the Address child writes from Employee Address.

Setup Requirements

Control Fields and Required Configuration

These mappings gate specific behavior and must be configured before going live; replace every shipped placeholder.

Mapping	Enables	Action	Required?
SubsidiaryId	Employee subsidiary	Resolves a subsidiary by name. Placeholder — replace: ships as `HEADQUARTERS`; set your subsidiary name, or the transfer fails.	Control — required (OneWorld)
CurrencyId	Employee currency	Static value (ships as `1`, the base currency). Confirm it matches your account's base currency.	Control — required

Subscription settings: enable the iPaaS.com employee create/update triggers in Outbound Data Flows (in the iPaaS.com subscription configuration) for automatic transfers; until then, only Manual Sync transfers run.

Authentication

The integration authenticates to NetSuite using the connection configured for the integration (see NetSuite Connections and Settings).

Integration Flow

An iPaaS.com employee transfers — on demand from the Manual Sync page (enter the employee record ID), or automatically when the employee outbound triggers are enabled in Outbound Data Flows.
For an update, the integration resolves the existing NetSuite employee by external ID; for an add, it creates a new employee.
The integration sets the name, email, phone, currency, and the subsidiary (resolved by name), writes the iPaaS.com id to the NetSuite External ID, and transfers the address child.

Mappings

The Add and Update collections share the same field mappings; the Update collection adds an Id resolution to target the existing NetSuite record. Fields marked Control gate a feature; fields with a Placeholder value ship with an example that must be replaced (see Setup Requirements).

Add / Update NetSuite Employee FROM iPaaS.com

iPaaS.com data type: Employee

Mapping Type	Source Field (iPaaS.com)	Destination Field (NetSuite)	Description
Field	FirstName	FirstName	Required. The employee's first name.
Field	LastName	LastName	Required. The employee's last name.
Field	EmailAddress	Email	Recommended. The employee's email address.
Dynamic Formula	`var phone = Addresses?.FirstOrDefault()?.PhoneNumber; if(!string.IsNullOrWhiteSpace(phone)) { return phone; }`	Phone	Optional. The phone number from the employee's first address, when present.
Static	`1`	CurrencyId	Control — required. The employee currency (base currency). Placeholder — confirm it matches your account.
Dynamic Formula	`(resolve subsidiary by name "HEADQUARTERS")`	SubsidiaryId	Control — required (OneWorld). Resolves the subsidiary by name; fails if the name is invalid. Placeholder value — replace during implementation: ships as `HEADQUARTERS`.
Dynamic Formula	`return Id;`	ExternalId	Recommended. Writes the iPaaS.com employee id to the NetSuite External ID for matching.
Field	Netsuite_Employe_CUST	custentity1	Optional. An example employee custom value written to the NetSuite custom field `custentity1`.
Dynamic Formula	`(resolve existing NetSuite id by external id — Update only)`	Id	Required (Update). Resolves the existing NetSuite employee by external ID so the update targets the right record.

Add / Update NetSuite Employee Address FROM iPaaS.com

iPaaS.com data type: Employee Address

Writes the employee's address. The Update address collection additionally sets Override to true so the existing address is replaced.

Mapping Type	Source Field (iPaaS.com)	Destination Field (NetSuite)	Description
Field	Address1	Addr1	Recommended. Address line 1.
Field	City	City	Recommended. City.
Field	Region	State	Recommended. State / region.
Field	PostalCode	Zip	Recommended. Postal code.
Field	Country	Country_RefName	Recommended. Country.
Dynamic Formula	`return Id;`	ExternalId	Recommended. Writes the iPaaS.com address id to the NetSuite External ID.
Dynamic Formula	`(resolve existing NetSuite address id by external id)`	Id	Recommended. Targets the existing NetSuite employee-address record.
Dynamic Formula	`return true;`	Override	Control (Update). Replaces the existing address on update.

Error Handling

"Failed to retrieve the subsidiary ID. The specified subsidiary name "…" is invalid or does not exist in the system." — the subsidiary name in the SubsidiaryId mapping does not match a NetSuite subsidiary. Resolution: set the mapping to a valid subsidiary name (replace the HEADQUARTERS placeholder).

Testing & Validation

Test Scenarios

Create an employee. Manually sync an iPaaS.com employee and confirm a NetSuite employee with the name, email, currency, and subsidiary, plus the address.
Update an employee. Change a field and confirm the existing NetSuite employee (matched by external ID) is updated, not duplicated.
Subsidiary validation. Confirm an invalid subsidiary name produces the subsidiary error above; correct it and re-sync.

Validation Checklist

The SubsidiaryId mapping names a real NetSuite subsidiary (not the HEADQUARTERS placeholder).
The CurrencyId static matches your account's base currency.
Outbound Data Flows triggers are enabled for automatic transfers.

Additional Notes

The employee external-ID link is what the TimeBill collection resolves to attach time entries to an employee; see NetSuite TimeBill From iPaaS.com Mapping Documentation.
Known limitations are collected in NetSuite Known Limitations.