NetSuite Add Cash Sale FROM iPaaS

When a transaction is created in iPaaS.com that qualifies as a cash sale, meaning it has at least one payment with a description that does not contain "House Account," a non-refunded status, and a non-negative total, it is transferred to NetSuite as a Cash Sale. This mapping collection handles the creation of Cash Sales, including header-level details, address information, gift redemption, line items, and gift card line items.

This mapping works alongside two related collections that handle different transaction types from the same iPaaS.com source: NetSuite Sales Order Add From iPaaS.com (for "House Account" payments) and NetSuite Sales Order Cancel From iPaaS.com (for cancellations). The mapping filter on each collection determines which transactions are routed where.

NetSuite calculates its own tax amounts based on the customer, item, and shipping method configuration. Tax amounts cannot be set directly from iPaaS.com using the API. Template mappings include the iPaaS.com tax amount in the order memo, and the tax amount may also be uploaded to a transaction custom field. Consult with your NetSuite implementation team to implement overrides of the NetSuite-calculated tax amount after the Cash Sale has been created.

Ensure the following prerequisites are in place before configuring this integration.

When manually transferring a Transaction from iPaaS.com, enter the valid iPaaS.com Transaction (internal ID) into the input field on the iPaaS.com manual sync page.

This flow uses two child collections to create the complete Cash Sale record in NetSuite:

Parent: NetSuite Add Cash Sale FROM iPaaS

The following fields are required for successful Cash Sale creation.

Mandatory Header Fields

Recommended Header Fields

Mandatory Line Fields

Mandatory Gift Card Line Fields

Mandatory Gift Redemption Fields

This integration references several NetSuite custom fields for tax override functionality. These fields must be created in NetSuite before they can be populated.

If using order-level tax collection in NetSuite, create the following transaction body custom fields:

If using line-item-level tax collection in NetSuite, create the following transaction column custom fields:

To transfer custom fields from iPaaS.com, create an iPaaS.com subscription custom field with the same name as the NetSuite custom field ID. You may then create a mapping directly to the custom field.

Transaction custom field IDs may be found in the following NetSuite locations:

For the transfer of custom fields from iPaaS.com, create an iPaaS.com subscription custom field having the same name as the NetSuite custom field Id.

Transaction custom field Ids may be found in the following NetSuite locations:

Custom fields will need to be allowed on Sale transactions

NetSuite does not allow the payment method to be set when creating a customer deposit from an iPaaS.com transaction. As an alternative, template mappings provided include a translation collection to map iPaaS.com payment method names to NetSuite account IDs. It is recommended to use a different account for each external payment method. NetSuite account IDs can be found in Setup > Accounting > Chart of Accounts:

If no account is provided, NetSuite will use the undeposited funds account for all deposits from iPaaS.com. By default, all iPaaS.com transaction payments will be transferred. Add filters as needed to limit which payment statuses are transferred.

To transfer location Id from the iPaaS.com transaction to the NetSuite Cash Sale a Location Name must be set in the mapping collection dynamic formula of Cash Sale Add From iPaaS.com.

You can see the locationName to add in the mapping. Replace the locationName where indicated in the Dynamic Formula with the desired location.

To transfer Subsidiary Id from the iPaaS.com transaction to the NetSuite Cash Sale, a Subsidiary Name must be set in the mapping collection dynamic formula of Cash Sale Add From iPaaS.com.

You can see the subsidiaryName to add in the mapping. Replace the subsidiaryName where indicated in the Dynamic Formula with the desired subsidiary.

Cash Sale created by iPaaS.com when you create a Cash Sale, NetSuite needs to know which period the revenue and associated payment should be recognized in. If the period is closed or the transaction date does not fall within an open period, NetSuite will not allow the transaction to be saved unless adjustments are made.

You can see the accountingperiodId to add in the mapping. Replace the accountingperiodIdwhere indicated in the Dynamic Formula with the desired accounting period.

NetSuite uses token-based authentication (TBA) or OAuth 2.0 to authorize API requests during transfer operations. OAuth 2.0 must be configured in NetSuite by creating an Integration Record, enabling Token-Based Authentication / OAuth 2.0, and granting the required permissions to the integration role. The generated Client ID and Client Secret are used by iPaaS.com to obtain an access token and securely authenticate API requests. Ensure credentials are stored securely within the iPaaS.com credential manager.

The integration processes iPaaS.com Transaction records as follows:

This mapping collection creates NetSuite Cash Sales from qualifying iPaaS.com Transactions. It maps header-level information, including customer identification, order status, location, subsidiary, accounting period, memo details, shipping, and tax override fields. The CreateTransactionAs control field ensures the record is created as a Cash Sale rather than a Sales Order. Child collections handle addresses and line items.

This filter ensures that only qualifying transactions are transferred to NetSuite as Cash Sales. It validates that the Payments collection is not null, contains at least one payment, and at least one payment has a non-empty description that does not contain "House Account." It also checks that the status is not "Refunded" or "Partially Refunded" and that the total is non-negative. Transactions where all payment descriptions contain "House Account" are handled by the Sales Order mapping collection instead.

This mapping collection maps iPaaS.com address records to NetSuite Cash Sale addresses. It handles both billing and shipping addresses, using the IsPrimaryBilling and IsPrimaryShipping flags to identify address roles.

This mapping collection creates Cash Sale line items in NetSuite from iPaaS.com transaction lines. It validates that each SKU is linked to a NetSuite item and determines the line item type based on the product type in iPaaS.com.

var netSuiteProductId = await GetNetSuiteProductIdBySku(Sku); if (netSuiteProductId != null) { return true; } else { throw new Exception("Sku " + Sku + " does not exist in NetSuite as an item id"); }

This filter validates that the line item SKU exists in NetSuite. If the SKU is found, the line is processed. If the SKU is not linked to a NetSuite item, the filter throws an exception and the line is not transferred.

This mapping filter ensures that only gift cards with a valid corresponding NetSuite Gift Certificate are processed. It prevents creating orders in NetSuite with invalid or unmapped gift cards, maintaining data integrity between iPaaS.com and NetSuite.

var netsuiteGiftCertificateId = await GetGiftCertificateIdBySkuAsync(Sku);
if(netsuiteGiftCertificateId != null) {
if(Qty > 1) {
throw new Exception("Gift card quantity cannot be greater than 1. NetSuite supports only one gift certificate per transaction line");
return false;
}
else {
return true;
}
}
else {
return false;
}

This mapping filter verifies that a corresponding NetSuite Gift Certificate item exists for the SKU. If the item exists, the line is allowed to transfer; otherwise, it throws an exception to prevent creating a Gift Card line without a matching NetSuite item.

The following code examples are provided as templates in the integration mapping. They are commented out by default and must be customized to match your NetSuite configuration before use.

This example maps iPaaS.com tax information to a NetSuite tax code ID based on the customer's country and region. It applies to both custbody_otg_ipaas_tax_code (header) and custcol_otg_ipaas_tax_code (line) fields.

// This is an example only and must be updated to your configuration! var country = GetCustomFieldValue(CustomFields, "NetSuite Tax Code Country"); var region = GetCustomFieldValue(CustomFields, "NetSuite Tax Code Region"); // Depending on your order source, normalize the country here country = CountryCodeRequired(country); // Map the country and region to a NetSuite tax code ID if (country == "US") { // This function will abbreviate US or Canada regions region = StateAbbreviation(region); switch (region) { case "NJ": return "-11"; // NJ in NetSuite break; case "NY": throw new Exception("Unmapped tax code"); // Throws an error break; default: // Default when no region match is found return "5"; break; } } // Add else if for each country // else if () ... else { // Default when no country match is found return "-7"; // Not taxable in NetSuite }

This example calculates the line-level tax percentage using a three-step fallback: line TaxPercent, estimated tax amount, or order header totals.

// Tax percent is provided if (TaxPercent != null && TaxPercent != 0) { return Math.Round(TaxPercent, 2); } // Estimated tax amount is provided — calculate percentage if (EstimatedTaxAmount != null && EstimatedTaxAmount != 0) { var result1 = (EstimatedTaxAmount / ExtendedPrice) * 100; return Math.Round(result1, 2); } // No line tax information — use order header amounts if (TaxPercent == null || TaxPercent == 0 || EstimatedTaxAmount == null || EstimatedTaxAmount == 0) { var result2 = (Parent.TaxAmount / Parent.Subtotal) * 100; return Math.Round(result2, 2); }

Sync a qualifying transaction from iPaaS.com with standard line items and a non-"House Account" payment. Cash Sale should be created in NetSuite with correct header details, addresses, and line items. Verify the memo contains the payment summary and tax information.

Sync a transaction where the CustomerId external ID does not exist. Verify the system falls back to email address lookup.

Sync a transaction with a line item SKU that does not exist in NetSuite. Verify the line filter throws an exception, and the error is logged.

Update the Location_Id formula with an invalid location name. Sync a transaction and verify the transfer fails with a location not found exception.

Sync a transaction with a date that falls outside the configured accounting period. Verify the transfer fails with an appropriate error.

Sync a transaction and verify that custbody_otg_ipaas_tax_rate is calculated correctly from TaxAmount and Subtotal.

Sync a transaction where all payment descriptions contain "House Account." Verify the Cash Sale filter rejects it (confirming it would be routed to the Sales Order mapping instead).

Sync a transaction where the gift card SKU does not exist in NetSuite. Verify that the line is filtered out and an appropriate error is logged.

Sync a transaction where the gift card SKU does not exist in NetSuite or the gift card line item quantity is greater than 1. Verify that the line is filtered out or the transaction fails with an appropriate error logged, ensuring that only valid NetSuite Gift Certificate items with a quantity of 1 are processed.

Sync a transaction where the MethodInfo object does not contain a GiftCardId or the value is empty/invalid. Verify that the transaction fails with the error “GiftCardId is missing or invalid in MethodInfo” logged, ensuring that no redemption is attempted without a valid GiftCardId.

Sync a transaction where the provided GiftCardId does not correspond to any existing gift certificate in NetSuite. Verify that the transaction fails with the error “Gift Certificate does not exist in NetSuite” logged, ensuring that only valid gift certificates are processed for redemption.