Data Flow
How ServiceTitan and NetSuite exchange data
Journal Entry AR
JE AR + Doc-based AP
Document-based
Setup
Follow these steps to set up and configure your NetSuite integration with ServiceTitan.
Onboarding checklist
NetSuite Onboarding Part 1: Set up ServiceTitan for integration
Configure ServiceTitan settings required before connecting to NetSuite.
NetSuite Onboarding Part 2: Authenticate NetSuite with ServiceTitan
Complete OAuth authentication to securely link both systems.
NetSuite Onboarding Part 3: Install and configure the ServiceTitan SuiteApp
Install the SuiteApp bundle in NetSuite and configure it to match your workflow.
NetSuite Onboarding Part 4: Configure sync settings
Set your sync preferences, transaction rules, and data mapping options.
Required access
Requires an active NetSuite subscription and ServiceTitan account. The ServiceTitan SuiteApp must be installed in your NetSuite environment.
Once setup is complete
ServiceTitan transactions sync automatically to NetSuite. Vendor and customer records stay in sync across both platforms.
Key workflows
Core workflows for managing and operating your NetSuite integration.
Data mapping
Understand how ServiceTitan data maps to NetSuite and how to manage synced records.
Sync options
Different configurations that determine how ServiceTitan posts transactions and how much detail appears in NetSuite.
Sync flows
Vendor and customer record syncing, transaction preparation, and triggering the sync between ServiceTitan and NetSuite.
General sync workflows
Supporting components that operate outside core transaction workflows for accurate data flow and record linkage.
Journal Entry Accounts Receivable option
How ServiceTitan records map to NetSuite in the Journal Entry AR option.
| ServiceTitan | Flow | NetSuite |
|---|---|---|
| Core | ||
| General ledger accounts | Chart of accounts 1 | |
| Customer | Customer 2 | |
| Tenant | config | Subsidiary |
| Business unit | config | Subsidiary or segment |
| Accounts receivable | ||
| Invoice | Journal entry | |
| Payment | Journal entry | |
| Applied payment | Journal entry | |
| Bank deposit | Journal entry | |
Notes
1. Default mappings are by account number. You can set your own mappings if required.
2. Customers are created or updated as journal entry detail records sync. Journal entry detail is optional.
config Mappings are manually configured and maintained by you.
Journal Entry Accounts Receivable and Document-based Accounts Payable
How ServiceTitan records map to NetSuite in the combined JE AR and document-based AP option.
| ServiceTitan | Flow | NetSuite |
|---|---|---|
| Core | ||
| General ledger accounts | Chart of accounts 1 | |
| Customer | Customer 2 | |
| Vendor | Vendor 3 | |
| Inventory location | config | Location |
| Tenant | config | Subsidiary |
| Business unit | config | Subsidiary or segment |
| Job | Project 4 | |
| Accounts receivable | ||
| Invoice | Journal entry | |
| Payment | Journal entry | |
| Applied payment | Journal entry | |
| Bank deposit | Journal entry | |
| Refund | Journal entry | |
| Accounts payable | ||
| Purchase order | Purchase order 5 | |
| Receipt | Item receipt | |
| Vendor bill | Vendor bill 6 | |
| Vendor return | Vendor credit 6 | |
| Inventory adjustment | Journal entry | |
Notes
1. Default mappings are by account number. You can set your own mappings if required.
2. Customers are created or updated as journal entry detail records sync. Journal entry detail is optional.
3. Vendors sync to ServiceTitan based on an assigned ServiceTitan sync category.
4. ServiceTitan jobs that have been dispatched are created as projects in NetSuite.
5. Purchase orders are created as item receipts are received.
6. Posted vendor bills and returns sync with NetSuite and are marked as exported in ServiceTitan.
config Mappings are manually configured and maintained by you.
Document-based option
How ServiceTitan records map to NetSuite in the document-based transaction to transaction option.
| ServiceTitan | Flow | NetSuite |
|---|---|---|
| Core | ||
| General ledger accounts | Chart of accounts 1 | |
| Customer | Customer 2 | |
| Vendor | Vendor 3 | |
| Inventory location | config | Location |
| Tenant | config | Subsidiary |
| Business unit | config | Subsidiary or segment |
| Job | Project 4 | |
| Accounts receivable | ||
| Invoice | Invoice | |
| Invoice (negative) | Credit memo | |
| Payment (unapplied) | Customer deposit | |
| Payment (applied) | Customer deposit 0.23 | |
| Payment (negative) | Journal entry | |
| Bank deposit | Bank deposit 0.23 | |
| Accounts payable | ||
| Purchase order | Purchase order 5 | |
| Receipt | Item receipt | |
| Vendor bill | Vendor bill 6 | |
| Vendor return | Vendor credit 6 | |
| Inventory adjustment | Journal entry | |
Notes
1. Default mappings are by account number. You can set your own mappings if required.
2. Customers are created or updated as journal entry detail records sync. Journal entry detail is optional.
3. Vendors sync to ServiceTitan based on an assigned ServiceTitan sync category.
4. ServiceTitan jobs that have been dispatched are created as projects in NetSuite.
5. Purchase orders are created as item receipts are received.
6. Posted vendor bills and returns sync with NetSuite and are marked as exported in ServiceTitan.
config Mappings are manually configured and maintained by you. 0.23 Applies to SuiteApp version 0.23 and later.
Troubleshooting & FAQ
Quick solutions to common issues and answers to frequently asked questions.
Troubleshooting
Step-by-step guides to resolve the most common issues.
Frequently Asked Questions
Check out some of the most frequently asked questions for the NetSuite integration.