> For the complete documentation index, see [llms.txt](https://prohelp.assetpanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prohelp.assetpanda.com/integrations-store/record-management/netsuite-integration.md).

# NetSuite Integration

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

This integration supports one-way data synchronization, pulling data from NetSuite into Asset Panda Pro. Changes made in Asset Panda will not reflect in NetSuite

{% hint style="warning" %}
NetSuite is a third-party application, and Asset Panda Pro does not control updates made within NetSuite. For more information, refer to NetSuite resources.
{% endhint %}

***

## Prerequisites <a href="#prerequisites" id="prerequisites"></a>

* Active NetSuite account with administrative permissions
* Active Asset Panda Pro subscription with administrative permissions&#x20;
* Token-Based Authentication (TBA) enabled in NetSuite

***

## NetSuite tasks <a href="#netsuite-tasks" id="netsuite-tasks"></a>

### **Enable required features**

1. Log into NetSuite as an administrator.
2. Select **Setup > Company > Enable Features**.
3. Select the **SuiteCloud** tab.
4. Enable the following settings:
   * **Token-Based Authentication**
   * **REST Web Services**
5. Click **Save**.

### **Create an integration record**

1. Select **Setup > Integrations > Manage Integrations > New**.
2. Enter a name (for example, `Asset Panda Integration`).
3. Ensure **Token-Based Authentication** is enabled.
4. Click **Save**. NetSuite generates the **Consumer Key (Client ID)** and **Consumer Secret (Client Secret)**.
5. Copy and store the **Consumer Key (Client ID)** and **Consumer Secret (Client Secret)** securely.

### **Generate an access token**

1. Select **Setup > Users/Roles > Access Tokens > New**.
2. Select the following details:
   * Application Name (integration record created earlier)
   * User
   * Role
3. Click **Save**. NetSuite generates the **Token ID** and **Token Secret**.

{% hint style="warning" %}
The **Token Secret** is shown only once and must be stored securely.
{% endhint %}

### **Retrieve the Account ID**

1. Select **Setup > Company > Company Information**.
2. Copy the **Account ID**.

***

## Asset Panda tasks <a href="#asset-panda-tasks" id="asset-panda-tasks"></a>

### **Set up the NetSuite integration**

1. Log into Asset Panda Pro with an administrator account
2. Navigate to <img src="/files/dLHka5YWbUR3zisHLua6" alt="Settings icon" data-size="line"> **Settings** > **Account Management**.
3. Expand the appropriate account and module.
4. Click **Manage** in the **Integrations** card.
5. Select **Integrations Store**.
6. In the **NetSuite** tile, click **Add**. The **Integrations in this module** tab is displayed.
7. In the **NetSuite** tile, click **Configure**.
8. Enter the following details to authenticate Asset Panda Pro with NetSuite:
   * **Account ID**
   * **Consumer Key / Client ID**
   * **Consumer Secret / Client Secret**
   * **Token ID**
   * **Token Secret**
9. Click **Test and save connection**.
10. If the test is successful, click **Continue with mapping**.
11. Click **Add mapping option**.
12. Enter a **Mapping Name** for your configuration.
13. Select the **External Entity** for which you want to map data fields:
    * Purchase Orders
    * Departments
    * Items
    * Subsidiaries
    * Item Receipts
    * Vendors
14. If **Items** was selected in the previous step, click **Filter** <i class="fa-filter">:filter:</i> to filter the sync based on one or more selected **Item Types**:
    * Inventory Item
    * Non-Inventory Item
    * Service Item
    * Assembly Item
    * Kit/Package Item
    * Item Group
    * Matrix Item
15. Select the Asset Panda Pro **Collection** where the NetSuite data should be stored.
16. In the **Mapping & Sync Direction** section, map the Asset Panda field from NetSuite to the relevant column in your Asset Panda Pro collection. See [Configure data mapping](#configure-data-mapping-and-filtering).
17. Click **Save**.

***

### Configure data mapping <a href="#configure-data-mapping-and-filtering" id="configure-data-mapping-and-filtering"></a>

{% hint style="info" %}
Proper field mapping is critical to avoid duplication or mismatched records
{% endhint %}

1. Under **Oracle NetSuite**, select the NetSuite fields to map.
2. Under **Asset Panda Pro**, select the corresponding Asset Panda Pro fields. See [NetSuite field mapping](#netsuite-fields-and-mapping-guidance).
3. To map additional fields, click **Add more** and then repeat steps 1-2.
4. Click **Save.**

{% hint style="info" %}

* You can schedule the sync to run on a configured schedule or choose **Run now** for the automation to trigger the sync manually.&#x20;
* You can view Automation Logs to review the sync status and any errors or failures. See [Activity Stream](/tools/activity-stream.md).
  {% endhint %}

***

## NetSuite field mapping <a href="#netsuite-fields-and-mapping-guidance" id="netsuite-fields-and-mapping-guidance"></a>

### Purchase Order fields&#x20;

| 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 <a href="#vendor-fields-and-mapping-guidance" id="vendor-fields-and-mapping-guidance"></a>

| Field name     | Description                    | Mapping Guidan          |
| -------------- | ------------------------------ | ----------------------- |
| 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 <a href="#vendor-fields-and-mapping-guidance" id="vendor-fields-and-mapping-guidance"></a>

| Field name                | Description              | Mapping 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              | Averate 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 <a href="#vendor-fields-and-mapping-guidance" id="vendor-fields-and-mapping-guidance"></a>

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

***

### Item Receipt fields

| 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                 |
| Quanitity 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

| 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
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.