NetSuite Setup: Step 3

Objective: This guide explains how to ensure accurate syncing from Duro to NetSuite for many critical field (Subsidiary, Tax Schedule, GL Accounts), and set how fields map and update during creation and subsequent updates in NetSuite.

Difficulty: Easy 

In this article:

1. Video Tutorial
2. Enabling Internal IDs in NetSuite
3. Subsidiary Mapping
4. Tax Schedule Mapping
5. GL Account Mapping
6. Basic & Sourcing Mapping

To ensure accurate syncing from Duro to NetSuite, you must enable visibility of Internal IDs in NetSuite, collect the correct values (Subsidiary, Tax Schedule, GL Accounts), and set how fields map and update during creation and subsequent updates in NetSuite.

Video Tutorial: Duro to NetSuite Properties Mapping (Step 3)

---

Before you get started, there is 1 critical item that will need to first be resolved.

Enabling Internal IDs in NetSuite

This allows you to see internal IDs throughout NetSuite, including the UoM list.

• In NetSuite, go to the top menu and hover over:
  Home → Set Preferences.
  • Click “Set Preferences”.
• Stay in the General tab.
• Under Defaults, check the box labeled SHOW INTERNAL IDS.
• Click “Save”

---

1. Locate Subsidiary ID & Use Include Children

   1. In NetSuite, go to Setup → Company → Subsidiaries.
   2. Identify the Internal ID of your target subsidiary and enter it in the Duro integration wizard. (Example in the demo: “Honeycomb Manufacturing” = ID 1.)
      
      

2. The Include Children toggle in the wizard

   1. When enabled, Duro pushes items to the selected subsidiary and all child subsidiaries.
   2. In NetSuite, this corresponds to Include Children on Inventory Items, Assembly Items, and BOMs.

⚠️ Important: If items already exist in NetSuite with Include Children previously off, enabling it in the wizard does not retroactively update those items. Manually enable Include Children on each existing Inventory Item, Assembly, and BOM inside NetSuite if needed.

3. Map Tax Schedule Internal ID

   1. In NetSuite, go to Setup → Accounting → Tax Schedules.
   2. Click the relevant tax schedule (e.g., Taxable).
   3. Get the Internal ID from the browser URL (e.g., id=1) and enter it in the wizard
      
      

4. Map GL Account Internal IDs

 Note: Not all integrations use GL account mapping. Some use none or only a subset.

1. In NetSuite, go to Lists → Accounting → Accounts.
2. Locate the Internal IDs for the accounts you want to map.
3. In the wizard, map the required accounts. By default the wizard accepts Asset and COGS accounts; you may add or remove others as needed.
4. For each mapped account, choose when Duro should populate it:
   1. Neither
   2. Push on Create
   3. Push on Update
   4. Both

Tip: You may choose Push on Create only to avoid overwriting changes made later in NetSuite by procurement/admin teams, as shown in the demo.

5. Configure Duro Property Mapping

   1. The Display Name and Description fields must always be mapped for the integration to function. You may modify where in Duro they map from.
      1. In the wizard, adjust the Duro property mapping (e.g., set Display Name to come from Description instead of Name).
         
         
   2. For remaining fields (from Purchase Description through Lead Time), you may make these changes:
      1. Leave as default, alter the mapping, or set when they map (Never, On Create, On Update, Always).

Note: Fields are truncated to NetSuite’s character limits when necessary.

---

Property Type: Map from Specs / Custom Specs

Use the Property Type dropdown in the wizard. Options include:

1. 1. ‘None’, which are the default component properties; 
   2. values from the Specs tile; 
   3. or, if your environment has a Custom Specs tile, values from there as well. 

6. ✅ Click “Next”.

• Now your NetSuite integration is ready to map over basic item details and sourcing information from Duro!
• Click “Next” in Prismatic.