Overview
This article catalogs the error messages you may encounter in the iPaaS.com NetSuite integration, what causes each one, and how to resolve it. Errors appear in Dashboard > Integration Monitoring > Error Logs in iPaaS.com when a record cannot be transferred. Each error carries a stable code (for example, NETS-NFND-1006) that you can search for on this page with Ctrl+F.
Every error is grouped below by the mapping collection flow that produces it. If your integration is managed for you, your Managed Integration Service Provider (MiSP) — the partner who owns your mappings, connection settings and credentials, and day-to-day reconciliation — is the first point of contact for most of the resolutions below.
Most common cause — incomplete go-live configuration. Many of the errors below ("… not found", "… is required", "… is invalid") occur because a shipped placeholder value was never replaced for your environment, or a required subscription setting was left unconfigured. The integration ships example values — a location, a subsidiary (Parent Company / HEADQUARTERS), a tax code, a discount item, a shipping-refund item, an inventory-adjustment account, and posting periods — that each subscriber must replace before go-live. Before troubleshooting an individual error, confirm your configuration is complete: see the Placeholders and Control Settings to Review Before Go-Live checklist in NetSuite Known Limitations and the field reference in NetSuite Connections and Settings.
Some integration behaviors are intentional and do not produce an error (for example, a record skipped by a collection filter, or an optional attribute left unset because its custom field is empty). Those are documented in the relevant Mapping Documentation and NetSuite Known Limitations, not here.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Sales Order (FROM iPaaS.com)
Cash Sale & Cash Refund (FROM iPaaS.com)
Invoice & Customer Payment
Return Authorization / RMA (FROM iPaaS.com)
Product & Inventory
Customer (FROM iPaaS.com)
Employee & TimeBill (FROM iPaaS.com)
Connection & Queries (all flows)
Error Collection
Sales Order (FROM iPaaS.com)
Customer could not be created
NETS-EXTN-1003 - Unable to create customer. This will prevent the transfer of the order.
Description: The order's customer could not be created in NetSuite, so the order cannot be created. The customer's own error is logged separately.
Resolution: Check the customer data on the source transaction (a customer requires at least a name, and a subsidiary on OneWorld accounts). Resolve the customer error first, then re-transfer the order.
Customer company could not be created
NETS-EXTN-1004 - Unable to create the company customer. This will prevent the transfer of the order.
Description: The order's company customer (B2B account) could not be created in NetSuite, so the order cannot be created.
Resolution: Review the company customer's required fields (name, and subsidiary on OneWorld), resolve its transfer, then re-transfer the order.
Possible duplicate sales order
NETS-BIZL-1001 - Unable to dynamically link to existing NetSuite sales order using {field}. This may result in duplicate sales orders.
Description: The integration could not match the incoming transaction to its existing NetSuite sales order using the configured Sales Order Duplicate Matching Field, so continuing could create a duplicate.
Resolution: Confirm the Sales Order Duplicate Matching Field subscription setting names a NetSuite field that holds your order number (for example
otherRefNum) and that the mapping populating it is stable. See NetSuite Connections and Settings.
Possible duplicate sales order line
NETS-BIZL-1002 - Unable to dynamically link to existing NetSuite sales order line. This may result in duplicate sales order lines in NetSuite.
Description: A line on the order could not be matched to its existing NetSuite line, which could duplicate the line.
Resolution: Re-transfer the order. If it persists, review the line's item and identifiers with your MiSP.
Line item cannot be linked to a NetSuite item
NETS-NFND-1009 - Sku {sku} cannot be linked to a NetSuite item, so the transaction cannot be created using this line item.
Description: A line references a SKU that does not resolve to a NetSuite item, so the transaction cannot be built.
Resolution: Create or correct the item in NetSuite so its SKU matches the source line, then re-transfer.
SKU is not linked to a NetSuite item
NETS-NFND-1010 - Sku {sku} is not linked to a NetSuite item id.
Description: A line (including a gift-certificate line) references a SKU that is not linked to a NetSuite item.
Resolution: Ensure the item — or gift certificate — exists in NetSuite with the matching SKU before transferring.
Gift certificate does not exist
NETS-NFND-1011 - Gift Certificate does not exist in NetSuite.
Description: A gift-certificate redemption references a certificate that does not exist in NetSuite.
Resolution: Confirm the gift certificate exists in NetSuite (matched by its code) before redeeming it on a transaction.
Gift-card payment is missing its identifier
NETS-VALD-1013 - A gift-card payment is missing its gift-card identifier.
Description: A gift-card payment was sent without a valid gift-card identifier.
Resolution: Ensure the source payment includes the gift-card code/identifier.
Gift certificate quantity too high
NETS-BIZL-1016 - Gift card quantity cannot be greater than 1. NetSuite supports only one gift certificate per transaction line.
Description: A gift-certificate line has a quantity greater than 1.
Resolution: Sell multiple gift certificates as separate lines, each with quantity 1.
Matrix option does not exist
NETS-NFND-1012 - {option} matrix option name does not exist in NetSuite. Please create it manually in the NetSuite portal.
Description: A variant option on the item is not defined as a matrix option in NetSuite.
Resolution: Create the matrix option (and its values) on the NetSuite item, then re-transfer.
Transaction date outside the posting period
NETS-BIZL-1013 - The transaction date is not within the date range of the selected posting period.
Description: The transaction's date does not fall in the NetSuite posting period the integration is configured to use.
Resolution: Use an open posting period for the transaction date. This often means a shipped posting-period placeholder was not replaced — see the go-live checklist in NetSuite Known Limitations.
Possible duplicate gift card
NETS-BIZL-1011 - Unable to dynamically link to existing iPaaS.com gift card using number. This may result in duplicate gift card records.
Description: A gift card could not be matched to its existing iPaaS.com record by number, which could create a duplicate.
Resolution: Keep the gift-card number mapping stable once gift cards exist; re-transfer once aligned.
Payment method not found
NETS-NFND-1014 - Payment Method not found or not linked to iPaaS.com.
Description: A sales order deposit references a payment method that is not found or not linked in iPaaS.com.
Resolution: Confirm the payment method exists and is mapped in iPaaS.com before transferring the deposit.
Shipping method could not be created or transferred
NETS-EXTN-1013 - Unable to create or transfer the shipping method. This will prevent the transfer of the order.
Description: The order's shipping method could not be created or transferred, so the order (or its tracking number) cannot proceed.
Resolution: Resolve the shipping-method transfer first, then re-transfer the order.
Sales order could not be created (tracking number)
NETS-EXTN-1014 - Unable to create or transfer the sales order. This will prevent the transfer of the transaction tracking number.
Description: A tracking number could not be applied because its sales order could not be created or transferred.
Resolution: Resolve the sales order transfer first, then re-transfer the tracking number.
Cash Sale & Cash Refund (FROM iPaaS.com)
These flows also raise the line-item, gift-certificate, matrix-option, tax-code, and posting-period errors listed under Sales Order above.
Location not found
NETS-NFND-1006 - Failed to retrieve the location ID. The specified location name "{name}" is invalid or does not exist in NetSuite.
Description: The location name configured on the collection does not match a NetSuite location.
Resolution: This is almost always an unreplaced placeholder — the template ships an example location value. Set the location mapping to a valid NetSuite location name (see the go-live checklist in NetSuite Known Limitations).
Subsidiary not found
NETS-NFND-1007 - Failed to retrieve the subsidiary ID. The specified subsidiary name "{name}" is invalid or does not exist in NetSuite.
Description: The subsidiary name configured on the collection does not match a NetSuite subsidiary.
Resolution: Unreplaced placeholder — the template ships
Parent Company(andHEADQUARTERSfor employees). Set the subsidiary mapping to a valid NetSuite subsidiary name (see the go-live checklist).
Tax code could not be mapped
NETS-NFND-1008 - The tax code could not be mapped to a NetSuite tax code.
Description: The transaction's tax code could not be resolved to a NetSuite tax code.
Resolution: Confirm the source tax code is mapped to a valid NetSuite tax code on the transaction's tax-code mapping.
Transaction date is missing
NETS-VALD-1010 - The transaction date is missing. Please provide the transaction's created date.
Description: The posting-period check could not run because the transaction's created date was not supplied.
Resolution: Ensure the source transaction includes its created date before transferring.
Invoice & Customer Payment
Invoice does not match its originating order
NETS-BIZL-1018 - Invoice validation failed: one or more invoice line items do not match the original sales order quantities. Invoice will not be transferred to iPaaS.com.
Description: Before an invoice is captured, the integration checks that its line quantities match the originating sales order; the check failed.
Resolution: Review the invoice and its originating order in NetSuite; an invoice that legitimately differs from its order will be stopped by this check. Your MiSP can confirm whether the difference is expected.
Order and invoice totals do not match
NETS-BIZL-1019 - Order-Invoice total validation failed: Original order total ({expected}) does not match the invoice total ({total}). Invoice will not be transferred to iPaaS.com.
Description: The originating order total (recorded on a NetSuite custom field when the order was created) does not match the invoice total.
Resolution: Confirm the order and invoice reconcile in NetSuite; investigate the discrepancy with your MiSP.
Payment total exceeds invoice total
NETS-BIZL-1017 - Payment Total must not be greater than the Invoice Total. Unable to create Customer Payment.
Description: The customer payment amount is greater than the invoice it is being applied to.
Resolution: Ensure the payment amount does not exceed the invoice total before transferring.
Payment could not be created
NETS-EXTN-1015 - Payment creation returned null or empty response.
Description: NetSuite did not return a valid response when creating the customer payment.
Resolution: Confirm the invoice exists in NetSuite and the payment does not exceed the invoice total, then re-transfer. If it persists, escalate to your MiSP with the record.
Return Authorization / RMA (FROM iPaaS.com)
Originating order ID is required
NETS-VALD-1004 - CreatedFrom_Id (Sales Order ID) is required for a Return Merchandise Authorization (RMA).
Description: A return is created by transforming its originating sales order; that order's ID was not provided.
Resolution: Ensure the return references its originating sales order (which must already exist and be fulfilled in NetSuite).
At least one line item is required
NETS-VALD-1005 - At least one line item is required to create a Return Merchandise Authorization (RMA).
NETS-VALD-1006 - At least one line item is required to update a Return Merchandise Authorization (RMA).
Description: The return was sent with no line items.
Resolution: Include at least one return line.
Transaction date or posting period is missing
NETS-VALD-1011 - The transaction date or posting period is missing. Please provide both.
Description: The posting-period check requires both a transaction date and a posting period; one or both were empty.
Resolution: Confirm both the transaction date and the posting-period configuration are set (the template ships an example posting period that must be replaced).
Subsidiary not found
NETS-NFND-1007 - Failed to retrieve the subsidiary ID. The specified subsidiary name "{name}" is invalid or does not exist in NetSuite.
Description: The subsidiary name configured on the return does not match a NetSuite subsidiary.
Resolution: Set the subsidiary mapping to a valid NetSuite subsidiary name (see the go-live checklist).
Shipping-refund item is required
NETS-VALD-1007 - ShippingRefundItemId is required when ShippingCost is provided.
Description: A return carries a shipping amount but no shipping-refund item is configured.
Resolution: Configure your shipping-refund item. The template ships a placeholder shipping-refund item id that must be replaced — see the go-live checklist in NetSuite Known Limitations.
Shipping-refund item is the wrong type
NETS-VALD-1008 - ShippingRefundItemId '{id}' is invalid. Item must be of type 'OthCharge' with subtype 'Sale'. Found: Type='{type}', SubType='{subtype}'.
Description: The configured shipping-refund item exists but is not an Other Charge item with subtype For Sale.
Resolution: Use (or create) an Other Charge / For Sale item in NetSuite as the shipping-refund item.
Originating order could not be created
NETS-EXTN-1005 - Unable to create parent sales order. This prevents creating the return transaction.
Description: The originating sales order could not be created in NetSuite, so the return cannot be created.
Resolution: Resolve the originating order's transfer first (it must exist and be fulfilled), then transfer the return.
Originating transaction not found
NETS-NFND-1001 - Parent transaction not found in source system.
Description: The return references an originating transaction that could not be found.
Resolution: Confirm the originating order exists and has transferred, then re-transfer the return.
Return could not be created or updated
NETS-EXTN-1016 - Return Merchandise Authorization (RMA) creation failed because the NetSuite API did not return a valid response.
NETS-EXTN-1017 - Return Merchandise Authorization (RMA) update failed because the NetSuite API did not return a valid response.
Description: NetSuite did not return a valid response when creating or updating the Return Authorization.
Resolution: Re-transfer. If it persists, escalate to your MiSP with the record and the originating order.
Product & Inventory
Item ID is required
NETS-VALD-1001 - Item Id is required.
Description: A product is missing the SKU that becomes the NetSuite Item ID.
Resolution: Provide a SKU on the product before transferring.
Price levels are required
NETS-VALD-1002 - Price levels are required.
Description: The product's pricing could not be resolved because no price level was available.
Resolution: Ensure the product has at least the default price level set.
Inventory SuiteQL table is not configured
NETS-VALD-1003 - Preset (Inventory SuiteQL Table Name) is null or empty. It must be specified in the subscription settings in order to query inventories.
Description: The integration queries inventory through a SuiteQL table whose name is set by a subscription preset that was left empty.
Resolution: Set the Inventory SuiteQL Table Name preset in the NetSuite subscription's Subscription Settings in iPaaS.com.
NetSuite Account Name is empty (inventory adjustment)
NETS-VALD-1012 - The NetSuite Account Name custom field is empty.
Description: An inventory-adjustment transfer reads the account from the NetSuite Account Name custom field, which was empty.
Resolution: Populate the NetSuite Account Name custom field with a valid NetSuite account name. (On the inventory-adjustment children, the account ships as the placeholder Inventory Adjustment — see the go-live checklist.)
Disabled product with variants
NETS-BIZL-1014 - Product transfers are not allowed when the product is disabled and has variants.
Description: A disabled (inactive) matrix product cannot be transferred while it still has variants.
Resolution: Re-activate the product, or remove its variants, before transferring.
Location not found (inventory availability)
NETS-NFND-1002 - No NetSuite location found with the name {name}.
Description: An inventory-availability check could not find a NetSuite location with the configured name.
Resolution: Set the location to a valid NetSuite location name (see the go-live checklist).
Product or variant not found in iPaaS.com
NETS-NFND-1003 - No product or product variant was found in iPaaS.com for SKU {sku}.
Description: An inventory-availability check could not find a product or variant in iPaaS.com for the SKU.
Resolution: Confirm the product/variant exists in iPaaS.com with the matching SKU before the inventory check runs.
NetSuite item external ID not found
NETS-NFND-1004 - No NetSuite item external ID was found for the product with SKU {sku}.
Description: The product was found but has no linked NetSuite item external ID.
Resolution: Transfer the product to NetSuite first so its external ID is linked, then re-run the inventory transfer.
Location not associated with item
NETS-NFND-1005 - The product with Item ID {id} was found, but no location with ID {locationId} is associated with it.
Description: The item exists in NetSuite but the configured location is not associated with it.
Resolution: Associate the location with the item in NetSuite, or set the mapping to a location the item uses.
Inventory not available at location
NETS-BIZL-1015 - The product with Item ID {id} was found and a location with ID {locationId} was matched, but the available quantity at that location is 0.
Description: The item and location matched, but there is no available quantity at that location.
Resolution: This is a data condition, not a configuration error — confirm the expected on-hand quantity in NetSuite for that item and location.
No bins available with Use Bins enabled
NETS-BIZL-1020 - No bins available for item {itemId}, but the Use Bins field is set to True.
Description: Bin-managed inventory is enabled (the USE BINS setting), but the item has no bins.
Resolution: Confirm the item is bin-managed in NetSuite, or disable the USE BINS setting if this item should not use bins.
Matrix option value does not exist
NETS-NFND-1013 - {value} matrix option value does not exist in NetSuite for the matrix option name {option}. Please create it manually in the NetSuite portal.
Description: A variant option value is not defined on the NetSuite matrix option.
Resolution: Create the matrix option value on the NetSuite item's option, then re-transfer.
Possible duplicate product
NETS-BIZL-1005 - Unable to dynamically link to existing NetSuite product using iPaaS SKU {sku}. This may result in duplicate product records.
NETS-BIZL-1006 - Unable to dynamically link to existing NetSuite product using iPaaS id {id}. This may result in duplicate product records.
Description: The integration could not match the incoming product to its existing NetSuite record by SKU or by id, which could create a duplicate.
Resolution: Confirm the SKU / id matches the existing NetSuite item; re-transfer once aligned.
Possible duplicate product variant
NETS-BIZL-1007 - Unable to dynamically link to existing NetSuite product variant using SKU {sku}. This may result in duplicate product variant records.
Description: The integration could not match the incoming variant to its existing NetSuite record, which could create a duplicate.
Resolution: Confirm the variant SKU matches the existing NetSuite item; re-transfer once aligned.
Possible duplicate variant option
NETS-BIZL-1008 - Unable to dynamically link to existing NetSuite product variant option using option {option}. This may result in duplicate product variant option records.
Description: The integration could not match a variant option to its existing NetSuite record, which could create a duplicate.
Resolution: Confirm the option values match the existing NetSuite matrix option; re-transfer once aligned.
Possible duplicate category
NETS-BIZL-1010 - Unable to dynamically link to existing iPaaS.com category using name. This may result in duplicate category records.
Description: The integration could not match a product category to its existing iPaaS.com record by name.
Resolution: Keep the category name mapping stable once categories exist; re-transfer once aligned.
Product could not be created
NETS-EXTN-1006 - Unable to create the product. This will prevent the transfer of the product.
NETS-EXTN-1007 - Unable to create the product for inventory. This will prevent the transfer of the product.
Description: The product could not be created in NetSuite, so dependent transfers (including inventory) cannot proceed.
Resolution: Review the product's required fields (SKU, units type, and subsidiary on OneWorld), resolve the error, and re-transfer.
Product kit component could not be created
NETS-EXTN-1012 - Unable to create the product kit component. This will prevent the transfer of the product.
Description: A kit component could not be created in NetSuite, so the kit product cannot proceed.
Resolution: Resolve the component product's transfer first, then re-transfer the kit.
Customer (FROM iPaaS.com)
Possible duplicate customer
NETS-BIZL-1003 - Unable to dynamically link to existing NetSuite customer using email address. This may result in duplicate customer records.
Description: The integration could not match the incoming customer to an existing NetSuite record by email, so continuing could create a duplicate.
Resolution: Confirm the customer's email is present and consistent; keep the email mapping stable once customers exist (see NetSuite Known Limitations).
Possible duplicate customer company
NETS-BIZL-1004 - Unable to dynamically link to existing NetSuite customer company using email address. This may result in duplicate customer company records.
Description: The integration could not match the incoming company customer to an existing NetSuite record by email, so continuing could create a duplicate.
Resolution: Confirm the company's email is present and consistent; keep the email mapping stable once companies exist.
Possible duplicate customer category
NETS-BIZL-1009 - Unable to dynamically link to existing iPaaS.com customer category using name '{name}'. This may result in duplicate customer category records.
Description: The integration could not match a customer category (pricing level/group) to its existing iPaaS.com record by name.
Resolution: Keep the customer-category name mapping stable once categories exist; re-transfer once aligned.
Customer pricing level could not be created or updated
NETS-EXTN-1010 - Unable to create or update the customer pricing level as a customer category. This will prevent the transfer of the customer.
Description: The customer's pricing level (represented as a customer category) could not be created or updated in NetSuite, so the customer cannot proceed.
Resolution: Resolve the pricing-level / customer-category transfer first, then re-transfer the customer.
Customer pricing group could not be created or updated
NETS-EXTN-1011 - Unable to create or update the customer pricing group as a customer category. This will prevent the transfer of the customer.
Description: The customer's pricing group (represented as a customer category) could not be created or updated in NetSuite, so the customer cannot proceed.
Resolution: Resolve the pricing-group / customer-category transfer first, then re-transfer the customer.
Employee & TimeBill (FROM iPaaS.com)
Employee could not be created or updated
NETS-EXTN-1008 - Unable to create the employee in NetSuite: {detail}
NETS-EXTN-1009 - Unable to update the employee in NetSuite: {detail}
Description: A time bill references an employee that could not be created or updated in NetSuite.
Resolution: Resolve the employee transfer first (name, subsidiary, and currency are required), then transfer the time bill. The subsidiary is resolved by name and ships as the placeholder HEADQUARTERS — see the go-live checklist.
Possible duplicate time bill
NETS-BIZL-1012 - Unable to dynamically link to existing NetSuite timeBill using externalId. This may result in duplicate timebill records.
Description: The time bill could not be matched to its existing NetSuite record, which could create a duplicate.
Resolution: Re-transfer. If it persists, review the time bill's identifiers with your MiSP.
Invalid location name format
NETS-VALD-1009 - Invalid location name. Provide the parent name and the location name separated by ' : ' when the location has a parent.
Description: A hierarchical location requires the
Parent : Locationformat.Resolution: Enter the location as
Parent Name : Location Namewhen the location has a parent.
Connection & Queries (all flows)
These errors are not specific to one mapping flow — they can affect any transfer when a NetSuite API call or query fails.
NetSuite API call failed
NETS-EXTN-1001 - Error calling NetSuite CallWrapper.{action}: {details} (Http Code: {code})
Description: A call to the NetSuite API was rejected or failed, and the integration surfaces NetSuite's own response. This one code covers every NetSuite API rejection; the specific cause is in the
{details}NetSuite returned. Common NetSuite responses seen here, and how to resolve each:"You have entered an Invalid Field Value {id} for the following field: item.": the discount line (or another line) references a NetSuite item that does not exist in your account, usually an unreplaced discount-item placeholder. On the Add and Update NetSuite Sales Order Discount Line FROM iPaaS.com child collections, set the discount line's item to a valid Other Charge / For Sale item for your account (see the go-live checklist).
"Inventory items must have a positive amount.": the discount line's item is an inventory item; the discount line carries a negative amount, which NetSuite does not allow on an inventory item. Use an Other Charge / For Sale item, not an inventory item.
"The total can not be negative.": the order-level discount is greater than the order subtotal, which would drive the total below zero. Ensure the discount does not exceed the subtotal; model a full-value or larger credit as a return/refund instead.
"Please specify a discount item for this customer.": an order update carried a header-level discount value but no discount item. On the Add and Update NetSuite Sales Order FROM iPaaS.com collections, unmap the header discount fields (DiscountItem_Id, DiscountItem_Rate, DiscountAmount, DiscountRate); order-level discounts are represented by the Sales Order Discount Line FROM iPaaS.com child collection (see NetSuite Known Limitations).
"The transaction date is not within the date range of the selected posting period.": the record being posted (an inventory adjustment, cash sale, cash refund, or return) has a transaction date that falls in a closed NetSuite posting period, or no open period covers it. On the inventory-adjustment collections the transaction date is optional and defaults to the current date, so this also occurs when today's posting period is not open in NetSuite. In NetSuite, open the posting period that covers the date (Setup > Accounting > Manage G/L > Manage Accounting Periods), or map the transaction's date field to a date within an open period. The template also ships example posting-period and date placeholders that must be replaced — see the go-live checklist in NetSuite Known Limitations.
"Uniqueness error - there is already an item with that name or name/parent combination.": a record with the same name/SKU already exists in NetSuite. This most often follows an earlier transfer that failed after the NetSuite record had already been created (for example, a product that was created but whose inventory step then failed), leaving an orphaned NetSuite record that the retry cannot re-create. In NetSuite, either delete the orphaned duplicate or link it to the existing record, then re-transfer. Manual duplicate cleanup or linking in NetSuite may be necessary after a failed transfer.
Resolution: Read the
{details}in the error and apply the matching guidance above. Most causes are a NetSuite-side configuration or data issue — a permission, a feature such as Accounts Receivable for cash refunds, an unreplaced placeholder, a posting period that is not open for the transaction date, or a leftover record from a prior failed transfer that now needs manual cleanup. The NetSuite side must be configured (open posting periods) and the relevant fields mapped accordingly before the transfer will succeed. If the response is unclear or does not match a case above, share the full error text with your MiSP.
NetSuite query failed
NETS-EXTN-1002 - SuiteQL API call failed: {details}
Description: A query to NetSuite (SuiteQL) returned an error from the NetSuite API.
Resolution: Review the details in the error; common causes are an authentication/permissions issue or a NetSuite-side limit. Confirm the connection is configured per NetSuite Connections and Settings. If it persists, share the error text with your MiSP.