Sage Intacct Troubleshooting: Org Structure (Department, Location, Job, Cost Code)

David N

September 03, 2026 22:50

This family covers the org structure entities in a Sage Intacct sync: Locations, the Business Unit and Primary Work Location fields on Employees and Contractors, the Job (Project) hierarchy, Cost Codes (Tasks), and the location, department, project, task, and cost type dimensions on a General Ledger payroll journal entry.

Most of these messages mean a value on one side does not have a matching record on the other side. On a read, Sage Intacct has data that Arcoro cannot map (an incomplete address, a Location tied to a different Entity). On a write, Arcoro is sending a value that Sage Intacct does not recognize (a Location name that is not 40 characters or fewer, a Department or Project name with no match). A few messages are about uniqueness: the same Location name, or the same Project and Cost Code combination, showing up more than once in the same sync.

Error Messages

Locations and Business Units

Message text	Direction	Occurs when	Outcome	Fix
A Location with an ID/Name of '[location name]' has been sent to Sage Intacct multiple times. Only the first Location with this value will be saved. Employee's associated with duplicate values may not have their Location set correctly. Correct the source data and run the sync again.	Write (Arcoro to Sage Intacct)	Two or more Location records in the same sync have the same Name, ignoring upper/lower case.	Record skipped. Only the first Location with that name is saved; every later one with the same name is rejected.	Give each Location a unique Name in the source system, then re-run the sync.
Location Name is required. Correct the data in the Source System and execute the Sync again.	Write	The Location record being sent has no Name value.	Record skipped.	Enter a Name for the Location in the source system.
Sage Intacct requires that a Location Name has a maximum length of 40 characters. Correct the data in the Source System and execute the Sync again.	Write	The Location Name is longer than 40 characters.	Record skipped.	Shorten the Location Name to 40 characters or fewer in the source system.
A Location Name contains one or more invalid characters. [invalid character] is not a valid character. Correct the data in the Source System and execute the Sync again.	Write	The Location Name contains a character that could not be represented correctly (shown in the log as a single replacement character).	Record skipped.	Remove or replace the invalid character in the Location Name in the source system.
The Location must have a Primary Contact with the location's physical address to be valid for Syncing. Modify the record in Sage Intacct to create a valid Primary Contact with the Location's address and execute the Sync again.	Read (Sage Intacct into Arcoro)	Reading Locations from Sage Intacct Location Dimensions (the default setup). The Location's Primary Contact is missing, or its mailing address is missing address line 1, city, state, or postal code.	Record skipped.	In Sage Intacct, add or complete the Location's Primary Contact address (address line 1, city, state, postal code).
The Project does not have a Ship To contact assigned, or the Ship To contact does not have a valid mailing address. This field is required for syncing locations from projects. Modify the record in Sage Intacct and execute the Sync again.	Read	Only when the connector is set up to build Locations from Project Ship To contacts instead of Location Dimensions. The Project has no Ship To contact, or the Ship To contact's mailing address is missing address line 1, city, state, or postal code.	Record skipped.	In Sage Intacct, assign a Ship To contact to the Project and complete its mailing address.
The Country Code '[country code]' could not be mapped to any valid Arcoro value. The Record will not be sent. Correct the data in source system and run the sync again.	Read	Reading a Location's address (from either the Location's Primary Contact or, in Project Ship To mode, the Project's Ship To contact). The address country cannot be converted to a matching Arcoro country.	Record skipped. The Location's address failed validation, so the whole Location is not read.	In Sage Intacct, correct the country on the address so it maps to a supported Arcoro country.
The Iso Country Code '[ISO country code]' could not be mapped to any valid Arcoro value. The Record will not be sent. Correct the data in source system and run the sync again.	Read	Same address check as above; the country cannot be converted to a matching ISO country code.	Record skipped.	Correct the country on the address in Sage Intacct.
The State '[state]' could not be mapped to any valid Arcoro value. The Record will not be sent. Correct the data in source system and run the sync again.	Read	Same address check; the state/province value cannot be converted to a matching Arcoro value.	Record skipped.	Correct the state/province on the address in Sage Intacct.
Unable to match the Location value from the Employee. It's possible the Location is assigned to a different Entity within Intacct.	Read	The Employee has a Location assigned in Sage Intacct, but that Location was not found among the Locations loaded for this sync.	Field skipped only. The employee's Business Unit is left blank; the rest of the employee record is still read normally.	In Sage Intacct, confirm the Employee's Location belongs to the same Entity this connector is configured to sync.
Unable to match the Location value from the Contractor. It's possible the Location is assigned to a different Entity within Intacct.	Read	Same check as above, for a Contractor.	Field skipped only. The contractor's Business Unit is left blank; the rest of the record is still read normally.	In Sage Intacct, confirm the Contractor's Location belongs to the same Entity this connector is configured to sync.
The Primary Work Location is required. Correct the data in the Source system and execute the Sync again.	Write	The Contractor's Primary Work Location value is blank.	Record skipped.	Set a Primary Work Location on the Contractor in the source system.
The Primary Work Location could not be matched against a Location in Sage Intacct.	Write	The Contractor has a Primary Work Location value, but it does not match the name of any Location in Sage Intacct.	Record skipped.	Correct the Primary Work Location name so it matches an existing Sage Intacct Location name, or create the Location in Sage Intacct first.
Business Unit is required. Correct the data in the Source system and execute the Sync again.	Write	The Employee's Business Unit value is blank.	Record skipped.	Set a Business Unit on the Employee in the source system.
The Business Unit "[business unit]" was not found in Sage Intacct. This record will not be Synced. Verify the Business Unit exists in Sage Intacct and is mapped correctly in the Source system, then execute the Sync again.	Write	The Employee has a Business Unit value, the Business Unit scope is turned on for this sync step, and that value does not match a Location known to Sage Intacct.	Record skipped.	Confirm the Location exists in Sage Intacct and that the source system's Business Unit value matches its name exactly.

Jobs and Cost Codes

Message text	Direction	Occurs when	Outcome	Fix
Sage Intacct projects/jobs exceeded the max job tree depth of [10] and will not be read past this depth.	Read	A Project (Job) hierarchy branch goes more than 10 levels deep below its root.	Collection item skipped. The job at the 10th level is still read normally, but none of its child jobs below that level are read at all.	In Sage Intacct, flatten the Job hierarchy so no branch goes past 10 levels, or accept that jobs deeper than that will not sync.
A [entity] with Project Id: '[project id]' and Cost Code Id(s): '[cost code id]' has already been read. This combination must be unique, and the record will not be Synced. Modify the data to ensure each Project-Cost Code set is unique and execute the Sync again.	Read	More than one Cost Code (Task) record shares the same Project and Cost Code ID combination. Cost Codes with no Project assigned are dropped before this check runs and never appear at all, with no error.	Record skipped.	In Sage Intacct, make each Cost Code (Task) ID unique within its Project.

General Ledger journal dimensions

These fire while building a single payroll General Ledger journal entry, one row at a time, in Sage Intacct. A journal entry sync record represents one payroll journal entry made up of several lines. If any one line fails one of these checks, the whole journal entry is skipped, not just that line.

Message text	Direction	Occurs when	Outcome	Fix
The Project "[job]" was not found in Sage Intacct. The journal entry will not be processed.	Write	A payroll journal line has a Job value that does not match any Project in Sage Intacct.	Record skipped. The whole journal entry, including its other lines, is not created.	Correct the Job name on the payroll line so it matches an existing Sage Intacct Project.
No Task "[cost code]" associated with Project "[job]" was found in Sage Intacct. The journal entry will not be processed.	Write	The line has a Cost Code value, and its Job matched a Project, but no Task with that Cost Code name exists under that Project.	Record skipped (whole journal entry).	Correct the Cost Code name, or confirm the Task exists under that Project in Sage Intacct.
The Cost Type with ID "[cost type]" was not found in Sage Intacct. The journal entry will not be processed.	Write	The line has a Cost Type value that does not match any Cost Type ID in Sage Intacct.	Record skipped (whole journal entry).	Correct the Cost Type ID, or create it in Sage Intacct.
The Cost Type "[cost type]" is not associated with the Task "[task]" in Sage Intacct. The journal entry will not be processed.	Write	The Cost Type matched by ID exists in Sage Intacct, but it is not linked to the Task already matched for this line.	Record skipped (whole journal entry).	In Sage Intacct, associate the Cost Type with the Task, or correct the Cost Type/Cost Code combination on the payroll line.
The Department "[department]" was not found in Sage Intacct or the Department in Sage Intacct is not active. The journal entry will not be processed.	Write	The line's Department, taken from the Job if it has one or otherwise from the Employee, does not match any active Department in Sage Intacct.	Record skipped (whole journal entry).	Correct the Department name so it matches an active Sage Intacct Department.
The employee's department "[department]" matched more than one department in Intacct. Ensure each department has a unique name in Intacct and execute the Sync again.	Write	On a General Ledger payroll journal line, the resolved Department name matches more than one Department in Sage Intacct.	Record skipped (whole journal entry). Note: this exact sentence can also appear as a non-blocking Warning on Employee and Contractor syncs, where it does not stop the write. Only this General Ledger occurrence blocks the record.	In Sage Intacct, rename Departments so each name is unique.
The Location with name "[business unit]" was not found in Sage Intacct. Please correct the data and run the sync again.	Write	The line's Business Unit Name value does not match any Location name in Sage Intacct. This check only runs after confirming the line's Location Name value is not blank (see the row below).	Record skipped (whole journal entry).	Correct the Business Unit Name on the payroll line so it matches an existing Sage Intacct Location name.
Location Name is required. Correct the data in the Source System and execute the Sync again.	Write	On a General Ledger payroll journal line, the Location Name value is blank. This is a separate check from the Location Name check on Location records above; here it guards one payroll line, and the actual Location match is done using the line's Business Unit Name value instead.	Record skipped (whole journal entry).	Confirm the payroll line has a Location Name value set. If it is set and this still occurs, escalate.

Confirming the Error

Open the sync execution for the run.
Find the step for the Sage Intacct connector involved (a read step for Location, Job, or Cost Code; a write step for Location, Employee, Contractor, or General Ledger).
On that step, find the row for the entity in question (Location, Employee, Contractor, Job, Cost Code, or General Ledger) and check its Errors, Warnings, Information, Failures, Added, Updated, and Unchanged counts.
A non-zero Errors count on Location, Employee, Contractor, Job, or Cost Code, or a non-zero Warnings count that includes a General Ledger department match sentence, points to this family.
Open the entity row's errors list and match on the fixed wording of the sentence (for example, "Location Name is required" or "was not found in Sage Intacct"), not on the quoted values, since those vary per record.
Note which entity and which direction (read or write) the error appears under - that tells you which system to fix.
A non-zero Failures count on these entities is not one of the messages in this article. Failures reflect the target system rejecting a write after it was sent; see "Target System Rejected the Write" for those.

Resolving the Error

Location Records Rejected on Write

Confirm the sync step is a Location write (Arcoro to Sage Intacct).
In the source system, open the Location record named in the error.
Set a Name if one is missing, shorten it to 40 characters or fewer if it is too long, or remove any invalid characters reported in the message.
If the error is about a duplicate Name, rename one of the Locations that share the same Name so each is unique.
Re-run the sync and confirm the Location no longer appears in the Errors list for that step.

Location Records Rejected on Read (Address Problems)

Confirm the sync step is a Location read (Sage Intacct into Arcoro).
In Sage Intacct, open the Location (or, if the connector uses Project Ship To mode, the Project) named in the error.
Open its Primary Contact (or Ship To contact) and confirm the mailing address has address line 1, city, state, and postal code filled in.
If the error names a Country Code, ISO Country Code, or State, correct that value on the address so it is a real, standard value.
Re-run the sync and confirm the Location record moves out of the Errors list.

Business Unit Not Set on an Employee or Contractor Read

Confirm the sync step is an Employee or Contractor read.
In Sage Intacct, open the Employee or Contractor record and check which Location is assigned to it.
Confirm that the Location belongs to the same Entity the Sage Intacct connector is configured to sync. If it belongs to a different Entity, either move the Location assignment or reassign the person to a Location under the correct Entity.
Re-run the sync and confirm the Business Unit field is now populated on that Employee or Contractor.

Primary Work Location and Business Unit Failures on Write

Confirm the sync step is an Employee or Contractor write.
In the source system, open the record named in the error.
For a Contractor, set the Primary Work Location if it is blank, or correct its spelling so it matches an existing Sage Intacct Location name.
For an Employee, set the Business Unit if it is blank.
If the Business Unit is set but still fails to match, confirm the corresponding Location exists in Sage Intacct and that the Business Unit scope is turned on for this sync step; correct the Business Unit value to match the Location's name exactly.
Re-run the sync and confirm the record moves out of the Errors list.

Job Hierarchy Depth

Confirm the sync step is a Job read.
In Sage Intacct, open the Project named in the error and trace its parent chain.
If the branch is more than 10 levels deep, either restructure the hierarchy so it fits within 10 levels.
Re-run the sync; jobs within the depth limit will read normally.

Duplicate Cost Code and Project Combination

Confirm the sync step is a Cost Code read.
In Sage Intacct, find the Cost Codes (Tasks) that share the Project and Cost Code ID named in the error.
Rename or renumber one of them so the Project and Cost Code ID combination is unique.
Re-run the sync and confirm both Cost Codes read successfully.

General Ledger Journal Line Dimension Failures

Confirm the sync step is the General Ledger write.
Open the journal entry's errors and read every message on it; because one bad line blocks the entire journal entry, there may be more than one issue to fix before it will post.
For a Project, Task, or Cost Type message, correct the Job, Cost Code, or Cost Type value on the payroll line so it matches an existing, correctly linked record in Sage Intacct.
For a Department message, correct the Department name so it matches one active Department in Sage Intacct (rename Departments in Sage Intacct if more than one shares the same name).
For a Location message, correct the Business Unit Name on the payroll line so it matches an existing Sage Intacct Location name. If the error is that the Location Name is required, confirm the line has a Location Name value set at all; if it does and the error persists, escalate.
Re-run the sync and confirm the journal entry now posts (Added count increases, Errors count for that row clears).

When to Escalate

If any of the following occur, you may need to reach out to Arcoro support for additional assistance.

The Employee's Business Unit or the Contractor's Primary Work Location value matches the Sage Intacct Location by name, but the error still fires. This can mean the Business Unit scope is not enabled as expected, or the preloaded Location list is stale; escalate with the sync execution ID.
A General Ledger journal entry keeps failing on a Location Name message even though you have confirmed the payroll line has a Location value. Since the underlying match actually uses the Business Unit Name value and not the Location Name value, this may need engineering to confirm which field the source data is populating; escalate rather than guessing.
A Location, Employee, or Contractor record is correct in both systems and still does not match, especially if it involves multiple Sage Intacct Entities. This may be a preload or connector Entity scoping issue; escalate. See also "Preload or Lookup Data Setup Failure".
You want Job hierarchies deeper than 10 levels to sync. This is a fixed limit in the connector.
Any of these messages appear alongside a non-zero Failures count for the same record. That combination points to a target-system rejection, not just this validation family; escalate using "Target System Rejected the Write".

Module Navigation