This mapping collection brings customers from NCR Counterpoint into iPaaS.com. A customer that iPaaS.com does not yet hold is created; one it already holds is updated. The collection carries the customer's Counterpoint customer number, their name, their email address, the free-text comment recorded against them, and their category assignment.

This family does not itself carry deletions. Where a separate Delete collection exists for this entity it handles removals from Counterpoint to iPaaS.com; otherwise a removal in Counterpoint is not propagated. See NCR Counterpoint Known Limitations.

Mapping Filter

Filter Description.

Only customers flagged in NCR Counterpoint as e-commerce customers are transferred. Counterpoint holds that flag as a single character, permits only Y or N, and defaults it to N — so a customer transfers only once someone has deliberately set the flag to Y. Subscribers or their MiSP who want every customer transferred, rather than only the e-commerce ones, can widen or remove this filter, and should read the Data Requirements above before doing so, because a wider filter admits customers that may not satisfy them.

Source: CUST_NO · Destination: CustomerNumber

This is a required field — iPaaS.com rejects the customer without it. The customer number as assigned in NCR Counterpoint. Counterpoint stores this as text of up to 15 characters and always populates it, so a value always arrives. This is the value subscribers or their MiSP use to identify the customer in both systems. iPaaS.com also saves the Counterpoint customer number as the external ID on the customer record, which is the primary match for subsequent updates to the same customer.

Source: FST_NAM · Destination: FirstName

This is a conditionally required field. iPaaS.com requires at least one of FirstName, LastName, or Company to be supplied and rejects the customer when all three are empty. The customer's first name as recorded in NCR Counterpoint. Counterpoint stores this as text of up to 15 characters and permits it to be empty. Because Company in this collection is populated only for business-type customers, FirstName and LastName are what satisfy the requirement for person-type customers — a person-type customer with no first or last name in Counterpoint has nothing to satisfy the rule and is rejected. Subscribers or their MiSP whose Counterpoint data includes person-type customers with blank names should confirm this before enabling the collection.

Source: LST_NAM · Destination: LastName

This is a conditionally required field. iPaaS.com requires at least one of FirstName, LastName, or Company to be supplied and rejects the customer when all three are empty. The customer's last name as recorded in NCR Counterpoint. Counterpoint stores this as text of up to 25 characters and permits it to be empty. See the FirstName note in this collection for how the three fields interact for person-type customers.

Source: (CUST_NAM_TYP == "B" ? NAM : null) · Destination: Company

This is a conditionally required field. iPaaS.com requires at least one of FirstName, LastName, or Company to be supplied and rejects the customer when all three are empty. NCR Counterpoint records every customer under a single name field together with a name-type flag that marks the customer as either a business or a person. This formula reads that flag: when it is B, the customer is a business and the Counterpoint name is sent as the company name; for any other value the formula produces no company name, because for a person the Counterpoint name is simply the first and last name already carried by the FirstName and LastName mappings. Counterpoint permits only B or P for the name type, defaults it to B, and always requires a name — so business customers always arrive with a company name of up to 40 characters, and person customers always arrive with none.

Source: EMAIL_ADRS_1 · Destination: EmailAddress

This is a required field — iPaaS.com rejects the customer without it, and on a newly created customer the address must be unique. The customer's primary email address in NCR Counterpoint. Counterpoint stores this as text of up to 50 characters and permits it to be empty, so a Counterpoint customer with no email address is rejected. Subscribers or their MiSP should confirm that every customer selected by this collection's filter carries an email address before enabling the collection.

Before a customer that iPaaS.com has not seen before is created, the integration checks iPaaS.com for an existing customer with the same email address, ignoring differences in capitalization. When one is found, the integration links the Counterpoint customer number to that existing iPaaS.com customer rather than creating a second copy, which is what keeps a customer entered separately in each system from becoming a duplicate. If that link cannot be created, the transfer fails with the message "Unable to dynamically link to existing iPaaS customer using email address. This may result in duplicate customer records." rather than proceeding and creating the duplicate.

Source: COMMNT · Destination: Comment

This is an optional field. The free-text comment recorded against the customer in NCR Counterpoint, carried across unchanged for reference. iPaaS.com accepts the customer without it, and customers with no comment in Counterpoint transfer with this field empty.

Source: return await ConvertCustomerCategoriesToiPaaSIdListAsync(CATEG_COD); · Destination: Categories

This is an optional field. Assigns the customer to its category in iPaaS.com. iPaaS.com identifies a category by its own internal id and accepts only ids that already exist, so the Counterpoint category code cannot be sent directly. The formula takes the category code from the customer record and looks up the matching category already transferred into iPaaS.com, returning its id. When no matching category is found — because the category has not been transferred yet, or the customer carries no category code — the formula produces no category and the customer transfers without one. It does not fail the transfer, and it does not transfer the category on its own.

The category is matched on the Counterpoint category code, which is what Add/Update NCR Counterpoint Customer Category TO iPaaS.com writes as the category name and external ID. Subscribers or their MiSP who want customers to arrive categorized MUST run that collection before this one; otherwise customers transfer uncategorized and stay that way until they are transferred again.

Where more than one category is supplied, iPaaS.com requires that the same category not be listed twice.

Parent: Add/Update NCR Counterpoint Customer TO iPaaS.com.

Mapping Filter

Filter Description.

The filter admits only the address derived from the customer record itself — the billing address — and excludes the customer's ship-to records, which are handled by Add/Update NCR Counterpoint Customer Ship-To Address TO iPaaS.com. Every mapping in this collection reads from the parent customer accordingly. Subscribers should leave this filter in place: without it, this collection and the ship-to collection would both process the same records.

Source: Parent.FST_NAM · Destination: FirstName

This is an optional field. The first name from the parent customer record in NCR Counterpoint, reused as the billing contact's first name because Counterpoint does not hold a separate name against the billing address. Counterpoint stores this as text of up to 15 characters and permits it to be empty, in which case the address transfers without a first name.

Source: Parent.LST_NAM · Destination: LastName

This is an optional field. The last name from the parent customer record in NCR Counterpoint, reused as the billing contact's last name for the same reason as FirstName above. Counterpoint stores this as text of up to 25 characters and permits it to be empty.

Source: Parent.ADRS_1 · Destination: Address1

This is a recommended field. iPaaS.com accepts the address without it, but the first address line is what makes the address usable for billing and correspondence, so it should be mapped for any meaningful customer sync. The first line of the billing address held on the customer record in NCR Counterpoint. Counterpoint stores this as text of up to 40 characters and permits it to be empty, so customers entered without an address transfer with an empty address record attached.

Source: Parent.ADRS_2 · Destination: Address2

This is an optional field. The second line of the billing address, used in NCR Counterpoint for suite, unit, or similar detail. Counterpoint stores this as text of up to 40 characters and permits it to be empty, which is the common case.

Source: Parent.ADRS_3 · Destination: Address3

This is an optional field. The third line of the billing address. Counterpoint stores this as text of up to 40 characters and permits it to be empty, which is the common case.

Source: Parent.CITY · Destination: City

This is a recommended field. iPaaS.com accepts the address without it, but a billing address without a city is not deliverable, so it should be mapped for any meaningful customer sync. The city from the billing address on the customer record. Counterpoint stores this as text of up to 20 characters and permits it to be empty.

Source: Parent.STATE · Destination: Region

This is a recommended field. iPaaS.com accepts the address without it, but the region is generally needed for tax and shipping purposes downstream, so it should be mapped for any meaningful customer sync. The state or province from the billing address on the customer record. Counterpoint stores this as text of up to 10 characters and permits it to be empty, and it carries whatever form the subscriber's Counterpoint installation uses — Counterpoint does not enforce a fixed list of state or province codes on this field.

Source: Coalesce(Parent.CNTRY,"United States") · Destination: Country

This is a recommended field. iPaaS.com accepts the address without a country, but many storefronts and shipping systems that read customer data from iPaaS.com require one, which is why this mapping supplies a fallback rather than passing the field through. The country from the billing address on the customer record. Counterpoint stores this as text of up to 20 characters and permits it to be empty; when it is empty, the formula produces United States instead. The fallback applies per address, so customers who do have a country recorded keep their own value.

Subscribers or their MiSP whose customers are predominantly outside the United States should replace the fallback with the country appropriate to their business, because the fallback is applied silently and an address that reaches iPaaS.com with the wrong country carries no indication that it was defaulted.

Source: Parent.ZIP_COD · Destination: PostalCode

This is a recommended field. iPaaS.com accepts the address without it, but the postal code is generally needed for tax and shipping purposes downstream, so it should be mapped for any meaningful customer sync. The postal or ZIP code from the billing address on the customer record. Counterpoint stores this as text of up to 15 characters and permits it to be empty, and it carries whatever form the subscriber's Counterpoint installation uses — Counterpoint does not enforce a postal code format on this field.

Source: true · Destination: IsPrimaryBilling

This is an optional field. Marks the address as the customer's primary billing address in iPaaS.com. The value is fixed rather than read from NCR Counterpoint because the collection's filter already restricts it to the one billing address held on the customer record — Counterpoint has no second billing address to compete with it, so every address this collection produces is the primary one. Subscribers or their MiSP should leave this set; clearing it leaves the customer with no address marked for billing, which downstream systems reading iPaaS.com may rely on.

Parent: Add/Update NCR Counterpoint Customer TO iPaaS.com.

Mapping Filter

Filter Description.

The first half excludes the address derived from the customer record, which is handled by Add/Update NCR Counterpoint Customer Billing Address TO iPaaS.com, leaving only genuine ship-to records. The second half narrows those to the one whose ship-to identifier is (DEFAULT), which is the identifier Counterpoint assigns to a customer's default ship-to address. Subscribers or their MiSP who need every ship-to address to reach iPaaS.com should widen the second half of the filter, and should read Known Limitations below before doing so.

Source: FST_NAM · Destination: FirstName

This is an optional field. The first name of the contact recorded against this ship-to address in NCR Counterpoint. Unlike the billing address, a ship-to row carries its own name, so this is not the customer's name unless someone entered the same value. Counterpoint stores this as text of up to 15 characters and permits it to be empty.

Source: LST_NAM · Destination: LastName

This is an optional field. The last name of the contact recorded against this ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 25 characters and permits it to be empty.

Source: ADRS_1 · Destination: Address1

This is a recommended field. iPaaS.com accepts the address without it, but the first address line is what makes the address usable for shipping, so it should be mapped for any meaningful customer sync. The first line of the ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 40 characters and permits it to be empty.

Source: ADRS_2 · Destination: Address2

This is an optional field. The second line of the ship-to address, used in NCR Counterpoint for suite, unit, or similar detail. Counterpoint stores this as text of up to 40 characters and permits it to be empty, which is the common case.

Source: ADRS_3 · Destination: Address3

This is an optional field. The third line of the ship-to address. Counterpoint stores this as text of up to 40 characters and permits it to be empty, which is the common case.

Source: CITY · Destination: City

This is a recommended field. iPaaS.com accepts the address without it, but a ship-to address without a city is not deliverable, so it should be mapped for any meaningful customer sync. The city from the ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 20 characters and permits it to be empty.

Source: STATE · Destination: Region

This is a recommended field. iPaaS.com accepts the address without it, but the region is generally needed for tax and shipping purposes downstream, so it should be mapped for any meaningful customer sync. The state or province from the ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 10 characters and permits it to be empty, and it carries whatever form the subscriber's Counterpoint installation uses — Counterpoint does not enforce a fixed list of state or province codes on this field.

Source: ZIP_COD · Destination: PostalCode

This is a recommended field. iPaaS.com accepts the address without it, but the postal code is generally needed for shipping and rate calculation downstream, so it should be mapped for any meaningful customer sync. The postal or ZIP code from the ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 15 characters and permits it to be empty, and it carries whatever form the subscriber's Counterpoint installation uses — Counterpoint does not enforce a postal code format on this field.

Source: (SHIP_NAM_TYP == "B" ? NAM : null) · Destination: Company

This is an optional field. NCR Counterpoint records a ship-to address under a single name field together with a name-type flag that marks it as either a business or a person. This formula reads that flag: when it is B, the address belongs to a business and the Counterpoint name is sent as the company name; for any other value the formula produces no company name, because for a person the Counterpoint name is simply the first and last name already carried by the FirstName and LastName mappings. Counterpoint permits only B or P for the name type, defaults it to B, and always requires a name — so business ship-to addresses always arrive with a company name of up to 40 characters, and person ship-to addresses always arrive with none.

Source: (SHIP_ADRS_ID == "(DEFAULT)" ? true : false) · Destination: IsPrimaryShipping

This is an optional field. Marks the address as the customer's primary shipping address in iPaaS.com. The formula sets the flag when the Counterpoint ship-to address id is (DEFAULT), which is the id Counterpoint assigns to a customer's default ship-to address.

As shipped, this collection's filter already admits only the (DEFAULT) row, so the formula's condition is always met and every address this collection produces is flagged as primary. The formula matters only once that filter is widened: subscribers or their MiSP who change the filter to bring across a customer's additional ship-to addresses will find the formula already distinguishing the default address from the rest, so only one address per customer is flagged as primary. Replacing the formula with a fixed value while transferring more than one ship-to address per customer would flag all of them as primary.

Source: Coalesce(CNTRY,"United States") · Destination: Country

This is a recommended field. iPaaS.com accepts the address without a country, but many storefronts and shipping systems that read customer data from iPaaS.com require one, which is why this mapping supplies a fallback rather than passing the field through. The country from the ship-to address in NCR Counterpoint. Counterpoint stores this as text of up to 20 characters and permits it to be empty; when it is empty, the formula produces United States instead. The fallback applies per address, so ship-to addresses that do have a country recorded keep their own value.

Subscribers or their MiSP whose customers are predominantly outside the United States should replace the fallback with the country appropriate to their business, because the fallback is applied silently and an address that reaches iPaaS.com with the wrong country carries no indication that it was defaulted.

Errors raised while transferring these records surface at Dashboard / Integration Monitoring / Error Logs. The specific messages, their causes and their resolutions are documented in NCR Counterpoint Error Messages. A record stopped by an error is not retried automatically; it must be resolved manually.