Intacct integration error messagesLast updated on 03/22/2022
Accountants
Account configuration is required. To update your account, please contact Technical Support for details.
You can troubleshoot common errors that you might experience when exporting from ServiceTitan to Intacct. If you continue to experience your Intacct exporting error, please contact ServiceTitan support.
Find exporting errors
Export errors from Intacct show up on the ServiceTitan Sync Sessions Report under Reports 2.0. You can specify a date range and select whether or not you want to see only errors. Each line represents a portion of the batch export. You can select a line and click the number under Pair Count to see more information about each object error.
Fix common Intacct errors
The errors below have been generalized. For example, the pound sign (#) indicates where a number or name would appear in the error.
Error | Cause | Fix |
---|---|---|
Location ID is required for the multi-entity shared warehouse with ID: ######### | The warehouse does not have a location or entity assigned in ServiceTitan. | Ensure the warehouse has been mapped to an Intacct entity. To learn more, see Set up inventory with Intacct. |
Use of empty Location is invalid. A valid Multi-Entity Location must be specified. | The business unit does not have a location or entity assigned in ServiceTitan. | Ensure the business unit has a designated Intacct location. To learn more, see Add or edit business units. |
Smart Rule ######### Violated | A custom smart rule has been broken in Intacct. | Contact your Intacct support specialist, as a script revision may be required. |
Bill to Contact is configured as non-editable in Transaction Definition. You cannot change the Bill to Contact. | Users can enable or disable editing for the Bill to Contact field in Intacct. | Ensure the Bill to is checked in Intacct:
|
Ship to Contact is configured as non-editable in Transaction Definition.You cannot change the Ship to Contact. | Users can enable and/or disable editing for the Ship to Contact field in Intacct. | Ensure the Ship to is checked in Intacct:
|
Illegal format for Contactversion : Primary Email Address no. | The customer’s email address was entered incorrectly. | Ensure the email address is in an appropriate format, i.e. xxxxxxx@xxxxx.xxx. To learn more, see Edit or add to a customer and location record. |
Create/update operations are restricted for departments. Please ensure you have a department with exact name '#######' in Intacct. | The business unit on the transaction you are attempting to export does not exist as a department in Intacct. | Choose a business unit that exists as a department in Intacct for the invoice. Alternately, if applicable, add the business unit as a Department in Intacct:
|
The undeposited funds account selected is invalid. Please provide a payment batch key. | The summary frequency is set incorrectly. | Set the summary frequency to Daily:
|
Your ######## transaction definition is configured to affect AR. However, no GL Accounts were found in the AR GL Information tab for itemid ‘#######’ and warehouse ‘#######’. Could not create Document record! | The transaction definition does not have the Item GL Group specified on its posting configuration from the item on the Invoice you are attempting to export. | Add the Item GL Group to the transactions definition’s posting configuration:
|
Your ######## transaction definition is configured to affect AP. However, no GL Accounts were found in the AP GL Information tab for itemid ‘#######’ and warehouse ‘#######’. Could not create Document record! | The transaction definition does not have the Item GL Group specified on its posting configuration from the item on the Invoice you are attempting to export. | Add the Item GL Group to the transactions definition’s posting configuration:
|
This sodocument cannot be created. Leading/Trailing/Consecutive hyphens are not allowed. Could not create sodocument record! Could not create Document record! | The transaction you are trying to export has a number with a hyphen in the incorrect format. | Intacct does not allow numbers to begin or end with a hyphen or for hyphens to be consecutive. To learn how to change the invoice number, see Edit an invoice. |
Dependent entity of type LocationContact (ID = ######) is not synced. contactversion: Required field 'Print As' is missing. Validate contactversion record failed! Could not create contactversion record! | The service location used on the invoice does not have a name. This typically should be the name of the customer. | Add a name to the service location. To learn more, see Edit or add to a customer and location record. |
Unable to get Journal for transaction type: ####### Please specify a journal for ####### in Activities > Setup. | There is no journal specified for this type of transaction. | Add a Journal to the transaction definition specified in the error:
|
Payment dates must be greater than their invoice dates. | A configuration in Intacct prevents having a payment date before the invoice date. | Turn off this configuration:
|
Project customer ST_###### does not match document customer. Could not create Document record! | The service location on the invoice you are attempting to export does not belong to the Bill To customer. | Update the project on Intacct to be the Bill To customer:
|
The record requires the field Vendor Document Number. Error preparing values. Could not create document record! | The receipt you are trying to export requires the Vendor Document Number in Intacct. | Add the Vendor Document Number to the receipt in ServiceTitan:
|
For Sub total 'Sales tax', GL Account '####' is configured as requiring a Location. |
| |
##########: You cannot update a root level customer from an entity/restricted user with one entity | Typically occurs when master data (vendors, customers, items) are loaded at the top-level, but your ServiceTitan environment is set to create and update entity-level master data in Intacct. Note: This error occurs only when data is preloaded for go-live or during UAT. New records created via the API should not trigger this response. | Reload master data to the entity level, rather than to the top level. Prior to doing this, make sure to contact your Intacct VAR/Specialist. |
##########: Invalid Project '############' specified..##########: Could not create podocument record!.##########: Could not create Document record! | PO was tied to a different job in a previous export/load or prior to open posting period in Intacct. | For UAT Testing: Make sure to create new jobs for every test within current posting period (for the job and the PO). |
Want to learn more?
Watch Intacct Essentials
Go back to Basic Intacct Workflows for more on this topic
Important note: Some features may not be currently included in your account and additional configuration may be required. Please contact technical support for details.