NetSuite Connector - Fields Mapping

effective field mapping is a critical component of the netsuite integration, ensuring accurate data synchronization between nue and netsuite properly configured mappings enable seamless communication between the two systems, preserving data integrity and reducing manual errors in financial records, invoicing, and accounting statuses this article outlines the standard field mappings between nue and netsuite and explores how custom field mappings can be used to meet unique business requirements standard fields mapping this section provides the details of the standard fields mapping between nue and netsuite customer in nue, customers are represented as the customer object, while in salesforce, they are represented as the account object these are synchronized to the customer object in netsuite field name nue field netsuite field description name name companyname customer name from nue id id externalid netsuite generates the internal id customer email email email standard email field customer since customersince startdate customer since date from nue description description comments truncated to 999 chars phone phone phone standard phone field subsidiary default customer subsidiary subsidiary set within integration for default subsidiary currency currencyisocode currency defaults to base currency for subsidiary, however, if multi currency is enabled, it looks up the ns currency record by iso symbol payment terms paymentterm terms billing address billingstreet, city, state, postalcode, countrycode addressbook address 1 product in nue/salesforce, customers are represented as the product object these are synchronized to the item object in netsuite at a high level, nue products are configured as netsuite items subscription products map to noninventorysaleitem entitlement products map to servicesaleitem asset products map to inventoryitem product sync field nue field netsuite field description id product id externalid sku sku itemid name name displayname description description salesdescription subsidiary netsuite subsidiary defaultid subsidiary populated within the integration to a default netsuite internal id tax schedule netsuite itemtaxschedule defaultid taxschedule populated within the integration to a default netsuite tax schedule internal id income account nue inventoryitem income account nue noninventoryitem income account nue serviceitem income account incomeaccount populated within the integration and based on item type deferred revenue account nue inventoryitem revenue account nue noninventoryitem revenue account nue serviceitem revenue account deferredrevenueaccount populated within the integration and based on item type order in nue/salesforce, orders are represented as the order object these are synchronized to the transaction object in netsuite with transaction type salesorder order sync field nue field netsuite field description order fields → transaction fields customer billingaccountid entity start date subscriptionstartdate startdate end date subscriptionenddate enddate billing address billingaddess billingaddress shipping address shippingaddress shippingaddress payment terms paymentterm terms currency currencyisocode currency subsidiary netsuite subsidiary defaultid inherited from customer subsidiary populated within the integration to a default netsuite internal id order number ordernumber custbody nue transactionnumber order product fields → transaction line fields id id custcol nue transactionlineid currency currency custcol nue transaction line currency product id productid item id net sales price netsalesprice rate quantity quantity quantity total amount totalamountwithouttax amount subscription term subscriptionterm custcol nue term start date subscriptionstartdate custcol nue start date end date subscriptionenddate custcol nue end date invoice / credit memo in nue, invoices and credit memos are represented as the invoice and credit memo object respectively these are synchronized to the transaction object in netsuite with transaction type invoice and creditmemo respectively each invoice and credit memo synchronizes their corresponding invoice item detail and credit memo item detail records to netsuite, where they are represented as transaction lines within the respective invoice and credit memo transactions sync field nue field netsuite field invoice / creditmemofields → transaction fields billing address customer billingaddress billingaddress start date orderstartdate startdate end date enddate enddate due date duedate duedate invoice date invoicedate trandate payment term paymentterm terms currency currencyisocode currency invoiceitemdetail / creditmemoitemfields → transaction line fields transaction quantity transactionquantity quantity transaction amount transactionamountwithouttax amount start date startdate custcol nue start date end date enddate custcol nue end date product id orderproduct productid item id orderproductid orderline invoice line id id custcol nue transactionlineid tax amount taxamount custcol nue tax bundle fields across all objects, we populate the nue connector bundle with the following custom fields sync field netsuite custom field value created from nue custentity nue createdfromnue true nue sync status custitem nue sync status item created/sales order created/invoice created sync timestamp custentity nue sync last current utc timestamp transaction id custbody nue transactionid salesforce account id url to salesforce custbody nue url salesforce url custom fields mapping the netsuite connector supports the custom field mapping between nue and netsuite for the following objects nue object netsuite object customer customer product item order and order line transaction with transaction type salesorder invoice transaction with transaction type invoice credit memo transaction with transaction type creditmemo the following nue field types are supported text checkbox number picklist date date time email id phone currency configure custom field mapping users can set up custom field mappings for all supported objects directly through the netsuite connector in the nue app by following the steps below login to https //app nue io navigate to settings → netsuite integration click 'launch' to launch the configuration wizard in the configuration wizard, after setting up the credentials, click next to navigate to the customers configuration screen in the fields mappings section, click "add property to 1st value" and follow the steps to map netsuite fields with nue fields click 'next' to save the fields mapping of customers, and navigate to the products / items configuration screen repeat the same steps in the products / items configuration screen to configure custom fields mapping for products / items click "next" to save the fields mapping of products / items, and navigate to the transactions configuration screen repeat the same steps in the transactions configuration screen to configure custom fields mapping for sales orders, invoices and credit memos note the mapping schema follows a key/value pair format, where the netsuite field serves as the key and the nue field as the value note that the field setup must use the field name, not the field label multiple netsuite fields can be mapped to a single nue field if multiple netsuite fields are mapped to the same nue field, the value of the nue field will be synchronized to all the mapped netsuite fields during the synchronization process before executing a live sync job from nue to netsuite, it is essential to first sync all field metadata from salesforce to nue for more information about synchornizing custom fields from salesforce to nue, please refer to docid\ tguor j2gqmocfcc bu3m configure field mapping for netsuite's item object because the netsuite connector accesses netsuite items via the soap api due to legacy tax considerations, the item field mapping differs from other objects to address this, the netsuite field type must be included as a suffix in the field mapping example for a netsuite field named ns field 001 with a field type of “list/record,” you would map it to a picklist type nue field (e g , nue field 001 ) using the following format "ns field 001\ list" "nue field 001" the following table shows the configure type names supported for item object custom field type configure type name check box checkbox list/record document list free form text text area phone number e mail address hyperlink rich text string date time of day or date/time (both in one field) date integer number decimal number decimal multiple select multilist configure field mapping for picklist / list type fields for list type records, map the api name of each list option to the corresponding list/record internal id in netsuite example the department in netsuite is a record type and a field on the customer object called department to map it create a picklist field on the salesforce account object, e g , ns department set the api name of ns department to match the internal id of the corresponding department in netsuite example salesforce picklist option → netsuite department internal id configure the field mapping in the configuration wizard this process ensures seamless synchronization between salesforce and netsuite for list type records supporting custom payment term fields in certain use cases, payment terms between nue and netsuite can be different in order to ensure your integration is supported, we support 2 use cases use case 1 standard payment terms with different naming conventions scenario your organization uses netsuite's default payment terms but has customized the names (e g , "30 days" instead of "net 30") why this matters the nue connector performs a case insensitive name lookup against the netsuite term table to find the correct internal id if your netsuite payment term is named "30 days" but nue has "net 30," the sync will fail because the names don't match how to set up identify your active payment term names in netsuite (setup → accounting → accounting lists → type term) create matching payment terms in nue with identical names to your netsuite terms use the new nue payment term when creating customers and orders use case 2 custom payment terms for specific business requirements scenario your organization needs custom payment terms like "net 7," "net 20," or "net 90" that aren't part of the standard set why this matters many businesses have unique payment term requirements based on customer agreements, regional practices, or industry standards these custom terms must exist in both nue and netsuite with matching names for successful synchronization how to set up create the custom payment term in netsuite first (setup → accounting → accounting lists → new term) create matching picklist values in salesforce for both the global picklist and the quote object sync the custom payment terms to nue via settings → payment term → refresh verify the new terms appear in nue's payment term list before using them how to step by step setup step 1 verify payment terms in netsuite navigate to setup → accounting → accounting lists set type filter to term to view all payment terms note the exact name of each active payment term (e g , "net 30," "30 days," "due upon receipt") record the internal id for reference (enable via home → set preferences → show internal ids) step 2 create or update payment terms in salesforce for global picklist (account and order objects) navigate to salesforce setup → picklist value sets locate the payment term picklist add custom values matching your netsuite term names exactly critical change the api name to a number reflecting the payment term days (e g , api name "30" for "net 30") for quote object navigate to object manager → quote → fields & relationships → payment term add the same custom picklist values with matching names step 3 sync payment terms to nue log in to the nue app ( https //app nue io) navigate to settings → payment term click the refresh icon to sync values from salesforce verify all expected payment terms appear in the list step 4 test the integration create and activate an order for that customer wait for netsuite sync (typically within 5 minutes) verify the sales order in netsuite shows the correct payment term create and activate an invoice, then verify sync