--- title: "NetSuite Onboarding Part 3: Configure the ServiceTitan SuiteApp" slug: "netsuite-onboarding-part-3-install-and-configure-suiteapp" tags: ["Area - Accounting Integrations", "Focus - Construction", "Focus - Service Replacement", "Role - Accountant", "Role - Admin", "Type - Commercial", "Type - Residential"] updated: 2026-10-15T02:32:09Z published: 2026-10-15T02:32:09Z canonical: "help.servicetitan.com/netsuite-onboarding-part-3-install-and-configure-suiteapp" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.servicetitan.com/llms.txt > Use this file to discover all available pages before exploring further. # NetSuite Onboarding Part 3: Configure the ServiceTitan SuiteApp ## Overview The next step in integrating your NetSuite account with your ServiceTitan tenant is configure the ServiceTitan SuiteApp. This step requires you to perform the following tasks: 1. Add and authenticate a ServiceTitan account in NetSuite. 2. Map business units to NetSuite subsidiaries. 3. Make GL accounts available and enable automatic item creation. 4. Map GL accounts between ServiceTitan and NetSuite. --- ### #### Who uses this feature - Administrators, office employees, managers, accountants, and bookkeepers - Applies to all business types #### Feature configuration - This feature is currently in Private Preview and available for specific accounts. It is subject to change. If you want to enable this feature for your account, join the waitlist here. ## Step 1: Add and authenticate a ServiceTitan account in NetSuite After installing the SuiteApp, the next step is to connect your ServiceTitan environment to NetSuite by adding and authenticating your tenant. This step establishes secure communication between both systems and is required before you can begin syncing data. ### What you'll need To add and authenticate a ServiceTitan account, you'll need the following: - ServiceTitan Client ID and Client Secret - The correct ServiceTitan environment: - Production - Integration - Next - Stage - Administrator access in both ServiceTitan and NetSuite ### Where to find your Client ID and Secret To find your Client ID and Secret in ServiceTitan: 1. Go to **Settings > Integrations > API Application Access**. 2. Locate your integration application. 3. Copy the Client ID and Client Secret. ### Add and authenticate a ServiceTitan tenant 1. In NetSuite, go to the ServiceTitan menu and open the ServiceTitan Dashboard. 2. Click **Add Tenant** to begin setup. 3. Enter the **Client ID**. This is copied from ServiceTitan. 4. Enter the **Client Secret**. This is copied from ServiceTitan. 5. In the **ServiceTitan Environment** dropdown, select: 1. Production 2. Integration 3. Next 4. Stage 6. Click **Connect** to authenticate the tenant. ![](https://cdn.document360.io/961862ab-d0f2-4d91-bb62-a62ee8184eff/Images/Documentation/netsuite-onboarding-part-3-configure-the-servicetitan-suiteapp-image-pqzzsjgx.png?sv=2026-02-06&spr=https&st=2026-10-16T11%3A07%3A19Z&se=2026-10-16T12%3A07%3A19Z&sr=c&sp=r&sig=%2FwiYvJK64MQfQ27GY0QimrgIng1Hd2YyGsKXtmF2xWs%3D) Once successfully connected, the tenant will appear on the dashboard with a green authenticated status. Next, continue to the next step to complete tenant-specific setup. ## Step 2: Map business units to NetSuite subsidiaries After you authenticate your ServiceTitan tenant in NetSuite, the next step is to map each ServiceTitan Business Unit (BU) to the appropriate NetSuite Subsidiary. This mapping ensures financial transactions sync to the correct entity in NetSuite and align with your operational structure in ServiceTitan. The SuiteApp also supports optional mapping of department, class, and location segments from NetSuite for more detailed financial tracking. ### Why this matters - Business Units in ServiceTitan define operational divisions such as Plumbing, HVAC, or Construction. - Subsidiaries in NetSuite define distinct financial entities in a multi-entity setup. - Mapping BUs to subsidiaries enables accurate transaction routing, reporting, and compliance in NetSuite. - Optional segment mapping (department, class, location) ensures transactions are categorized according to your accounting structure. ### Active Business Units From the *Business Unit Mapping* screen, toggle this switch on to display only **active ServiceTitan Business Units**. Business Units marked **inactive** in ServiceTitan will **not** be shown and cannot be mapped. ![](https://cdn.document360.io/961862ab-d0f2-4d91-bb62-a62ee8184eff/Images/Documentation/netsuite-onboarding-part-3-configure-the-servicetitan-suiteapp-image-lyg9wlhf.png?sv=2026-02-06&spr=https&st=2026-10-16T11%3A07%3A19Z&se=2026-10-16T12%3A07%3A19Z&sr=c&sp=r&sig=%2FwiYvJK64MQfQ27GY0QimrgIng1Hd2YyGsKXtmF2xWs%3D) ### Parent/child segments for business unit mapping The Business Unit Mapping screen now shows both parent and child/sub-segments in the segment selector. Entries are displayed in the format **Parent Segment : Child Segment** and both parent segments and individual child segments are selectable for mapping. ### Map custom segments to business units SuiteApp now supports mapping **up to 3 custom NetSuite segments** in the Business Unit Mapping flow. Custom Segments must first be created and enabled in NetSuite (**Customization > Lists, Records, & Fields > Custom Segments** > **New**) and added to the relevant forms so they are available to the tenant. From the **Tenant Configuration** screen in SuiteApp, choose up to three custom segments and save. These selected segments will then appear as additional segment options on the Business Unit Mapping screen and can be mapped to ServiceTitan Business Units. ![](https://cdn.document360.io/961862ab-d0f2-4d91-bb62-a62ee8184eff/Images/Documentation/netsuite-onboarding-part-3-configure-the-servicetitan-suiteapp-image-igvzodf1.png?sv=2026-02-06&spr=https&st=2026-10-16T11%3A07%3A19Z&se=2026-10-16T12%3A07%3A19Z&sr=c&sp=r&sig=%2FwiYvJK64MQfQ27GY0QimrgIng1Hd2YyGsKXtmF2xWs%3D) ![](https://cdn.document360.io/961862ab-d0f2-4d91-bb62-a62ee8184eff/Images/Documentation/netsuite-onboarding-part-3-configure-the-servicetitan-suiteapp-image-a3lojubz.png?sv=2026-02-06&spr=https&st=2026-10-16T11%3A07%3A19Z&se=2026-10-16T12%3A07%3A19Z&sr=c&sp=r&sig=%2FwiYvJK64MQfQ27GY0QimrgIng1Hd2YyGsKXtmF2xWs%3D) ### Map business units 1. In NetSuite, open the **ServiceTitan Dashboard**. 2. Locate your authenticated tenant and click **Business Unit Mapping** from the *Tenant Configuration* screen. 3. For each business unit listed: 1. Select the corresponding **NetSuite Subsidiary**. 2. (Optional) Map **department**, **class**, and **location** if your NetSuite setup uses segmentation. 4. Click **Save** once all mappings are complete. > [!NOTE] > **Note:** Each BU must be mapped before related transactions can sync. Multiple BUs can be mapped to the same subsidiary if needed. Business Units are account-specific and do not carry over between tenants. ![](https://cdn.document360.io/961862ab-d0f2-4d91-bb62-a62ee8184eff/Images/Documentation/netsuite-onboarding-part-3-configure-the-servicetitan-suiteapp-image-ix5j6vb4.png?sv=2026-02-06&spr=https&st=2026-10-16T11%3A07%3A19Z&se=2026-10-16T12%3A07%3A19Z&sr=c&sp=r&sig=%2FwiYvJK64MQfQ27GY0QimrgIng1Hd2YyGsKXtmF2xWs%3D) ### (Optional) Look up trucks or warehouses If your ServiceTitan tenant tracks inventory in trucks or warehouses, you can enable Truck/Warehouse Lookup for each Business Unit. When this setting is enabled: - The SuiteApp uses the truck or warehouse location specified on the purchase order or invoice in ServiceTitan. - This location overrides the default NetSuite location mapped to the business unit. This ensures that item-level inventory transactions reflect actual storage locations rather than default BU locations in NetSuite. When business unit mapping is complete, continue to the next step. ## Step 3: Make GL accounts available and enable automatic item creation To ensure document-based transactions (such as invoices, vendor bills, and credit memos) from ServiceTitan post correctly to your NetSuite general ledger, each referenced account must be represented by a corresponding item in NetSuite. When you mark a GL account as Available to ServiceTitan, the SuiteApp automatically creates a linked non-inventory item in NetSuite. This item acts as a vehicle for syncing line-level transaction data and is essential for accurate GL posting. > [!NOTE] > **Note:** The GL account–to–item mapping follows this structure: ServiceTitan item > NetSuite item > NetSuite account. ### Make a GL account available to ServiceTitan 1. In NetSuite, navigate to the account record you want to sync. 2. Open the record in Edit mode. 3. Select the **Available to ServiceTitan** box. 4. Save the record. Once saved, a non-inventory item will be created automatically and linked back to the GL account. #### **When a GL account is marked available** - A non-inventory item is created in NetSuite using the same name as the GL account - The item is automatically linked to the associated GL account - The item is used to carry line-level transaction data during document syncs #### Why this matters - ServiceTitan syncs transactions at the line-item level, which requires item records in NetSuite - The non-inventory item enables this sync behavior without requiring a full product catalog in NetSuite - This supports accurate financial posting while maintaining a streamlined operational workflow in ServiceTitan When your GL accounts are marked available and the corresponding items are created, continue to the next step. ![](https://cdn.document360.io/961862ab-d0f2-4d91-bb62-a62ee8184eff/Images/Documentation/netsuite-onboarding-part-3-configure-the-servicetitan-suiteapp-image-lkepx4ae.png?sv=2026-02-06&spr=https&st=2026-10-16T11%3A07%3A19Z&se=2026-10-16T12%3A07%3A19Z&sr=c&sp=r&sig=%2FwiYvJK64MQfQ27GY0QimrgIng1Hd2YyGsKXtmF2xWs%3D) #### Understand account item creation and errors When you mark a GL account as Available to ServiceTitan, and the account type supports account item creation, the SuiteApp automatically creates a corresponding NetSuite account item. These account items are used during transaction synchronization and are required for supported document sync workflows. If account item creation is unsuccessful, the SuiteApp records the reason in the Item Creation Error field on the GL account. This field displays the error returned by NetSuite and can help identify the underlying issue. ![Finance Clearing account details with integration error message highlighted for review.](https://cdn.document360.io/961862ab-d0f2-4d91-bb62-a62ee8184eff/Images/Documentation/netsuite-creation-error(1).png?sv=2026-02-06&spr=https&st=2026-10-16T11%3A07%3A19Z&se=2026-10-16T12%3A07%3A19Z&sr=c&sp=r&sig=%2FwiYvJK64MQfQ27GY0QimrgIng1Hd2YyGsKXtmF2xWs%3D) To resolve the issue, correct the underlying problem in NetSuite, edit the GL account, clear the Item Creation Error field, and save the record. The SuiteApp automatically retries account item creation each time the account is saved, provided the error has been cleared. Account items are created for: - All supported account types when marked Available to ServiceTitan, except those listed below. This includes: - Income - Expense - Cost of Goods Sold (COGS) - Deferred Revenue - Other Current Liability - All other supported account types Account items are not created for: - Accounts Payable (AcctPay) - Accounts Receivable (AcctRec) - Equity - Bank ## Step 4: Map GL accounts between ServiceTitan and NetSuite This step links the NetSuite accounts you made available in Step 3 to the corresponding accounts in ServiceTitan. This mapping establishes a validated connection between the two systems, ensuring that transactions are accurately posted in NetSuite. The SuiteApp automatically attempts to match accounts based on account name and number. Suggested mappings are preselected, but you can review and override them as needed. With NetSuite accounts marked as available and the corresponding non-inventory items created, you can now map accounts between the systems. General Ledger (GL) account mapping ensures that ServiceTitan transactions, such as invoices, bills, and payments, post to the correct GL accounts in NetSuite. > [!WARNING] > **Caution:** Completing this step is required before any financial data can successfully sync. ### What this step does - Links NetSuite GL accounts to the ServiceTitan accounts used in transactions - Tells the SuiteApp where to post each synced transaction - Prevents sync errors by validating that every transaction references a mapped account ### Configure GL account mappings 1. In NetSuite, go to the **ServiceTitan Dashboard** 2. Select **GL Account Mapping** for the appropriate tenant 3. Review the list of NetSuite accounts available for mapping 1. Only accounts marked **Available to ServiceTitan** will appear 4. For each NetSuite account: 1. Select an existing ServiceTitan account from the dropdown, **or** 2. Choose **Create New** to generate a new ServiceTitan account with the same number and name 5. If the account number in NetSuite matches one in ServiceTitan, the SuiteApp will preselect that match 6. Review and confirm each suggested mapping 7. Click **Save** when all mappings are complete. > [!WARNING] > **Caution:** If a ServiceTitan transaction references a NetSuite account that is not mapped, the sync will fail. These sync errors will be visible in the Sync Record Manager. To resolve, complete the missing mapping and reset the sync. Once GL account mappings are complete, continue to NetSuite Onboarding Part 4: Configure sync settings. ![](https://cdn.document360.io/961862ab-d0f2-4d91-bb62-a62ee8184eff/Images/Documentation/netsuite-onboarding-part-3-configure-the-servicetitan-suiteapp-image-ogehk609.png?sv=2026-02-06&spr=https&st=2026-10-16T11%3A07%3A19Z&se=2026-10-16T12%3A07%3A19Z&sr=c&sp=r&sig=%2FwiYvJK64MQfQ27GY0QimrgIng1Hd2YyGsKXtmF2xWs%3D) ## Inactivating a tenant connection A ServiceTitan tenant connection can be taken out of service without deleting its configuration or historical sync data. To inactivate a tenant, open the applicable ServiceTitan Tenant record, click Edit, select Inactive, and save the record. Once inactive: - The tenant remains visible on the ServiceTitan Dashboard as **Disconnected (Inactive)**. - **Dry Run** and **Execute** are disabled, and scheduled syncs skip the tenant. - The tenant is excluded from error emails and **Bulk Checks**, while historical errors remain accessible. - All existing configuration, mappings, and sync history are retained. To reconnect the tenant, edit the tenant record and clear **Inactive**. The tenant can then resume syncing using its existing configuration. Only active tenants are considered for multi-tenant naming requirements. If only one active tenant remains, **Disable prefix/suffix naming** can be enabled even if inactive tenant records are still present. ## Want to learn more? - See [Accounting integrations](/v1/docs/accounting-integrations-overview) - See [NetSuite integration](/v1/docs/netsuite-1) - See [NetSuite Onboarding Part 1: Set up ServiceTitan for integration](/v1/docs/netsuite-onboarding-part-1-set-up-servicetitan) - See [NetSuite Onboarding Part 2: Authenticate NetSuite with ServiceTitan](/v1/docs/netsuite-onboarding-part-2-authenticate-netsuite-with-servicetitan) - See [NetSuite Onboarding Part 4: Configure sync settings](/v1/docs/netsuite-onboarding-part-4-configure-sync-settings-1)