# Netsuite Integration

Integrate your Asset Panda account with your NetSuite account to fetch and manage your business data efficiently. This integration ensures that key records from NetSuite are available in Asset Panda, enabling better asset tracking and operational visibility.

The NetSuite and Asset Panda integration supports **uni-directional data synchronization**, pulling data from NetSuite into Asset Panda.

**NOTE:** NetSuite is a third-party application, and Asset Panda does not control updates made within NetSuite. For more information, refer to NetSuite resources.

***

### Overview

The process of integrating the NetSuite account with Asset Panda to fetch data includes:

* Connecting NetSuite
* Setting up and configuring the NetSuite integration in Asset Panda
* Mapping the fields from NetSuite to Asset Panda
* Running and scheduling automations

***

### Prerequisites

* You must have an active NetSuite account
* You need administrative permissions in both NetSuite and Asset Panda
* Token-Based Authentication (TBA) must be enabled in NetSuite

***

### NetSuite Tasks

#### Enable Required Features

1. Log in to NetSuite as an administrator
2. Navigate to **Setup → Company → Enable Features**
3. Open the **SuiteCloud** tab
4. Enable the following:
   * Token-Based Authentication
   * REST Web Services
5. Click **Save**

***

#### Create an Integration Record

1. Navigate to **Setup → Integrations → Manage Integrations → New**
2. Enter a name (e.g., *Asset Panda Integration*)
3. Ensure **Token-Based Authentication** is enabled
4. Click **Save**

After saving, NetSuite generates:

* **Consumer Key (Client ID)**
* **Consumer Secret (Client Secret)**

Copy and store these securely.

***

#### Generate Access Token

1. Navigate to **Setup → Users/Roles → Access Tokens → New**
2. Select:
   * Application Name (Integration Record created earlier)
   * User
   * Role
3. Click **Save**

After saving, NetSuite generates:

* **Token ID**
* **Token Secret**

**Important:** The Token Secret is shown only once and must be stored securely.

***

#### Retrieve Account ID

1. Navigate to **Setup → Company → Company Information**
2. Copy the **Account ID**

***

### Asset Panda Tasks

#### Setup NetSuite Integration

1. Log in to Asset Panda
2. Go to **Settings → Account Management**
3. Click **Manage** for the respective module
4. Open the **Integrations Store**
5. Locate NetSuite and click **Add**
6. Navigate to **Integrations in this module**
7. Click **Configure**

***

#### Authenticate NetSuite

To authenticate Asset Panda with NetSuite, enter the following details:

* **Account ID**
* **Consumer Key / Client ID**
* **Consumer Secret / Client Secret**
* **Token ID**
* **Token Secret**

Click **Test and Save Connection** to verify authentication.

***

### Configure Data Mapping and Filtering

Click **Add Mapping** after successful authentication.

#### Supported External Entities

* Purchase Orders Items
* Departments
* Inventory Items
* Subsidiaries
* Item Receipts
* Vendors

***

#### Inventory Item Filtering

While selecting **Inventory Items**, you can filter by item types such as:

* Inventory Item
* Non-Inventory Item
* Service Item
* Assembly Item
* Kit/Package Item
* Item Group
* Matrix Item

***

#### Selecting Collection

* Select the **Asset Panda collection** where the data should be stored

***

#### Mapping Fields

1. Select the NetSuite entity
2. Map NetSuite fields to corresponding Asset Panda fields
3. Select appropriate fields for record matching
4. Click **Save**

***

### Automation & Sync

* Run sync **manually** or configure **scheduled automation**
* Scheduled sync ensures that data remains up to date

***

### Logs & Monitoring

* Integration logs are available within Asset Panda
* Logs help track:
  * Sync status
  * Errors
  * Failed records

***

### Important Notes

* This integration supports **one-way sync (NetSuite → Asset Panda only)**
* Changes made in Asset Panda will not reflect in NetSuite
* Proper field mapping is critical to avoid duplication or mismatched records

***

## NetSuite Fields and Mapping Guidance

***

### Purchase Order Fields and Mapping Guidance

| Field Name                 | Description                              | Mapping & Filtering Guidance |
| -------------------------- | ---------------------------------------- | ---------------------------- |
| Amount                     | Total amount for the purchase order line | Map to cost or value fields  |
| Currency ID                | Internal currency identifier             | Backend/reference use        |
| Currency Name (Display)    | Currency name                            | Map for readability          |
| Order Date (Tran Date)     | PO creation date                         | Map to order date            |
| Due Date                   | Payment due date                         | Useful for tracking          |
| Ship Date                  | Shipping date                            | Map if required              |
| Status Name (Display)      | PO status                                | Use for filtering            |
| Purchase Order Internal ID | Internal PO identifier                   | Backend/reference use        |
| PO Number (Tran ID)        | PO number                                | Map for display              |
| Vendor ID (Entity ID)      | Vendor identifier                        | Backend/reference use        |
| Vendor Name (Display)      | Vendor name                              | Map to vendor field          |
| Item ID                    | Item identifier                          | Link to inventory            |
| Item Name (Display)        | Item name                                | Map to asset name            |
| Quantity                   | Item quantity                            | Map to quantity              |
| Rate                       | Unit cost                                | Map to cost                  |
| Line Sequence Number       | Line order                               | Optional                     |
| Last Modified Date         | Last updated timestamp                   | Useful for tracking          |

***

### Department Fields and Mapping Guidance

| Field Name     | Description                    | Mapping & Filtering Guidance |
| -------------- | ------------------------------ | ---------------------------- |
| Department ID  | Internal department identifier | Backend/reference use        |
| Name           | Department name                | Map to department field      |
| Subsidiary IDs | Linked subsidiaries            | Useful for hierarchy         |

***

### Inventory Item Fields and Mapping Guidance

| Field Name                | Description              | Mapping & Filtering Guidance |
| ------------------------- | ------------------------ | ---------------------------- |
| Item Internal ID          | Internal item identifier | Backend/reference use        |
| Item Code / Number        | SKU or item code         | Map to asset code            |
| Display Name              | Item name                | Map to asset name            |
| Item Type (Display Name)  | Type of item             | Useful for filtering         |
| Item Type Code            | Internal type code       | Backend/reference use        |
| Is Inactive               | Inactive status          | Filter inactive items        |
| Created Date              | Creation date            | Map if needed                |
| Last Modified Date        | Last updated timestamp   | Useful for tracking          |
| Average Cost              | Average item cost        | Map to cost                  |
| Last Purchase Price       | Latest purchase price    | Reference pricing            |
| Purchase Cost (Base)      | Base purchase cost       | Map to cost                  |
| Total Value (On Hand)     | Inventory value          | Reporting use                |
| Units Type ID             | Unit identifier          | Backend/reference            |
| Units Type Name (Display) | Unit name                | Map to unit field            |

***

### Subsidiary Fields and Mapping Guidance

| Field Name           | Description         | Mapping & Filtering Guidance |
| -------------------- | ------------------- | ---------------------------- |
| Subsidiary ID        | Internal identifier | Backend/reference use        |
| Name                 | Subsidiary name     | Map to organization field    |
| Parent Subsidiary ID | Parent reference    | Maintain hierarchy           |

***

### Item Receipt Fields and Mapping Guidance

| Field Name                | Description            | Mapping & Filtering Guidance |
| ------------------------- | ---------------------- | ---------------------------- |
| Item Receipt Internal ID  | Internal identifier    | Backend/reference            |
| Receipt Number (Tran ID)  | Receipt number         | Display/reference            |
| Receipt Date (Tran Date)  | Date received          | Map to receiving date        |
| Amount                    | Total amount           | Map to value                 |
| Quantity Received         | Quantity received      | Map to quantity              |
| Quantity Billed           | Quantity billed        | Financial tracking           |
| Rate                      | Unit cost              | Map to cost                  |
| Item ID                   | Item identifier        | Link to inventory            |
| Item Name (Display)       | Item name              | Map to asset                 |
| Department ID             | Department identifier  | Backend use                  |
| Department Name           | Department name        | Map to field                 |
| Location ID               | Location identifier    | Backend use                  |
| Location Name             | Location name          | Map to location              |
| Subsidiary ID             | Subsidiary identifier  | Backend use                  |
| Subsidiary Name (Display) | Subsidiary name        | Map to org                   |
| Vendor ID (Entity ID)     | Vendor identifier      | Backend use                  |
| Vendor Name (Display)     | Vendor name            | Map to vendor                |
| Posting Period ID         | Period identifier      | Backend use                  |
| Posting Period Name       | Period name            | Reporting                    |
| Source PO Line ID         | PO line reference      | Traceability                 |
| Source PO Reference       | PO reference           | Link records                 |
| Line Sequence Number      | Line order             | Optional                     |
| Last Modified Date        | Last updated timestamp | Tracking                     |

***

### Vendor Fields and Mapping Guidance

| Field Name                      | Description                | Mapping & Filtering Guidance |
| ------------------------------- | -------------------------- | ---------------------------- |
| Vendor Internal ID              | Internal vendor identifier | Backend/reference            |
| Vendor Name (entityid)          | Vendor name/identifier     | Map to vendor field          |
| Company Name                    | Vendor company name        | Display/reporting            |
| Legal Name                      | Registered name            | Compliance use               |
| Email                           | Email address              | Map to contact               |
| Phone                           | Phone number               | Map to contact               |
| Currency ID                     | Currency identifier        | Backend use                  |
| Currency Name (Display)         | Currency name              | Map to currency              |
| Balance (Vendor Currency)       | Outstanding balance        | Financial tracking           |
| Balance Primary (Base Currency) | Base currency balance      | Reporting                    |
| Credit Limit                    | Vendor credit limit        | Financial use                |
| Unbilled Orders Amount          | Pending billing amount     | Procurement tracking         |
| Subsidiary Edition              | Linked subsidiary          | Org mapping                  |
| Is Inactive                     | Inactive status            | Filter records               |
| Is Job Resource Vendor          | Vendor type flag           | Optional                     |
| Last Modified Date              | Last updated timestamp     | Tracking                     |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://prohelp.assetpanda.com/integrations-store/record-management/netsuite-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.