Sage Intacct Troubleshooting: Preload or Lookup Data Setup Failure

David N

September 02, 2026 22:54

Before a Sage Intacct sync reads or writes a single record, it loads reference data it will need along the way, things like Locations, Departments, Labor Classifications, Employee Types, and Projects. This step is called preload, and it runs once at the start of the step, before any employee, contractor, time record, or journal entry is touched. If Sage Intacct is missing something the sync absolutely requires, or if the group of lookup queries in preload does not all finish cleanly, the whole run stops immediately. Because this happens before processing starts, nothing at all synced for that entity in that run, not even the records that would otherwise have gone through cleanly.

Error Messages

The five "One or more errors occurred in ... PreLoad" messages below are summary messages, not the specific cause. They fire only when one of the individual lookup queries inside that preload signals a failure. In the current code, the only lookup query in this whole family that actually signals a failure this way, with its own specific message logged first, is the Contractor Employee Type lookup (see PreloadEmployeeTypeContractorMissingError below). For every other summary message, treat it as a sign to check the sync log rows recorded during that same preload step for any more specific Error entry; if there is not one, escalate rather than assuming the summary text alone is the full story.

Message text	Direction	Occurs when	Outcome	Fix
One or more errors occurred in Employee PreLoad for the Sage Intacct Provider. Review the logs, correct the data issue and run the Sync again.	Read and Write	The batch of lookup queries at the start of the Employee read step (Employees, Locations, Earning Types, and, if those scopes are on, Positions and Labor Classifications) or the Employee write step (Employees, Contacts, and, if those scopes are on, Departments, Labor Classifications, and Locations) does not all finish successfully. This exact text also fires from the Contractor write preload; see the note on the Contractor row below.	Sync stopped.	This is a summary. Find the specific Error logged in the same preload step and resolve that instead. Escalate if there is none.
One or more errors occurred in Contractor PreLoad for the Sage Intacct Provider. Review the logs, correct the data issue and run the Sync again.	Read	The batch of lookup queries at the start of the Contractor read step (Contractors, Locations, Labor Classifications) does not all finish successfully. Note: the Contractor write step runs an equivalent batch, but a code defect makes it raise the Employee message above instead of this one. If a user reports this exact text on a Contractor sync, expect it on the read side only; on the write side look for the Employee message instead.	Sync stopped.	This is a summary. Find the specific Error logged in the same preload step and resolve that instead. Escalate if there is none.
One or more errors occurred in Location PreLoad for the Sage Intacct Provider. Review the logs, correct the data issue and run the Sync again.	Read	The Location read step's Contacts lookup does not finish successfully. This lookup only runs at all when the connector's Location source is configured to build Locations from Project Contact records instead of the Location dimension; otherwise this step is skipped and cannot cause this message.	Sync stopped.	This is a summary. Find the specific Error logged in the same preload step and resolve that instead. Also confirm which Location source the connector is configured to use; if it is not the Project Contact source, this specific lookup was not even running.
One or more errors occurred in Time Record PreLoad for the Sage Intacct Provider. Review the logs, correct the data issue and run the Sync again.	Write	The batch of lookup queries at the start of the Time Record write step (Projects, Tasks, Locations, Employees) does not all finish successfully.	Sync stopped.	This is a summary. Find the specific Error logged in the same preload step and resolve that instead. Escalate if there is none.
One or more errors occurred in General Ledger PreLoad for the Sage Intacct Provider. Review the logs, correct the data issue and run the Sync again.	Write	The batch of lookup queries at the start of the General Ledger payroll write step (Journals, Employees, Departments, Locations, Projects, Entities, Cost Types, Tasks, Accounts) does not all finish successfully.	Sync stopped.	This is a summary. Find the specific Error logged in the same preload step and resolve that instead. Escalate if there is none.
No Locations were read from Sage Intacct. Since Employee's must have a work location this Sync will be unable to continue. Correct the issue by adding Locations to Sage Intacct and attempt the Sync again.	Write	Fires from both the Contractor write preload and the General Ledger payroll write preload, immediately after each one's own lookup batch already succeeded. It fires when Sage Intacct returns zero Location records to the connector. No active/inactive filter is applied, so this means literally no Locations at all are visible, not just none that are active.	Sync stopped.	In Sage Intacct, add at least one Location and confirm the web services user the connector authenticates as can see it.
Unable to find an Employee Type with an identifier of "Contractor". This value is required to sync Contractor data to Sage Intacct. Create a new Employee Type for Contractors and execute the Sync again.	Write	Fires only from the Contractor write preload's Employee Type lookup, under either of two conditions: (1) Sage Intacct returns no Employee Type records at all, or (2) Employee Type records exist but none of them has an ID that is an exact, case-sensitive match for "Contractor". Either condition logs this message as an Error, and the lookup then fails, which in turn triggers the Employee PreLoad summary message above (mislabeled as Employee) right after it in the same log.	Sync stopped. This line itself is only the specific Error entry; the actual stop is the mislabeled Employee PreLoad summary that follows it.	In Sage Intacct, create an Employee Type whose identifier is exactly "Contractor".
Unable to validate that the Construction Module is enabled for this company in Sage Intacct. The Construction Module is required to execute any Syncs. Please verify and correct your company data in Sage Intacct, then try again. Reason: [one of three specific reasons]	Read and Write	Runs at the very start of setup for every Sage Intacct read service and every write service, before preload even begins, and also during the connector's Test Connection check. It fires on any of three conditions: no General Ledger dimensions are returned for the company at all; a Cost Type dimension is not found among them; or a Cost Type dimension is found but is not enabled for General Ledger. The bracketed reason above carries whichever of those three applies.	Sync stopped (or, on Test Connection, the connection test fails). Because this is raised as a general code error rather than the clean terminal message the rest of this family uses, the sync log shows a generic connection/data failure sentence with this message's full text appended after it, not this text by itself.	In Sage Intacct, enable the Cost Type dimension for General Ledger for this company. This capability is only available with Sage Intacct's Construction offering.
Missing required custom field "[Arcoro Identifier]" for [Timesheets or Timesheet Entry] in Sage Intacct. Field details: Label: "[Arcoro Identifier]", Length: "[30 or 70]", Data Type: "[Text]", Field ID: "[ARCORO_IDENTIFIER]". Please add this field in Platform Services > Custom Fields and try again.	Write	Runs right after the Construction Module check, at the start of setup for every Sage Intacct write service, and also during Test Connection for connectors using the "Sage Intacct For Arcoro" or "Sage Intacct For Time Configuration" configuration only. It fires when the "Arcoro Identifier" custom field is missing, or is not a Text field, on the Timesheets object (must allow 30 characters) or the Timesheet Entry object (must allow 70 characters).	Sync stopped (or Test Connection fails, for the two configurations named above), wrapped the same generic way as the Construction Module message.	In Sage Intacct, add the named custom field to the named object with the exact Text type and length shown, then try again.

Confirming the Error

Check whether this error occurred on the connector's Test Connection check (on the connector edit page, before any sync ran) or during an actual sync run. The Construction Module and custom field messages can appear in either place; the rest of this family only appears during a sync.
For a sync run, open the sync execution.
Find the step for the Sage Intacct connector and entity involved (Employee, Contractor, Location, Time Record, or General Ledger).
On that entity's row, check the Errors, Warnings, Information, Failures, Added, Updated, and Unchanged counts. A non-zero Failures count with zero Added and zero Updated is the signature of this family: nothing was processed at all.
Open the Failure detail for that row. If it reads exactly one of the "One or more errors occurred in ... PreLoad" sentences, do not act on that sentence alone. Scan the log entries recorded just before it in the same step for a more specific Error, most likely the Contractor Employee Type message if the step is a Contractor write.
If the detail instead reads the No Locations, Construction Module, or custom field text directly, that is the actual cause; there is nothing earlier to look for.
Note whether the step is a read or a write, and which entity it is for. That determines which fix section below applies, and which system needs the correction.

Resolving the Error

A Preload Summary Message With No Other Error Nearby

Confirm there really is no other, more specific Error logged in the same preload step. Check both just before and just after the summary line.
If the step is a Contractor write and the summary reads the Employee PreLoad text, look specifically for the "Unable to find an Employee Type with an identifier of 'Contractor'" text; it is very likely the real cause even though the summary that follows it names the wrong entity.
If nothing more specific is found anywhere in the step, this cannot be resolved from the summary text alone. Escalate with the sync execution ID, the step and entity, and the full list of log entries recorded for that step.

Missing Contractor Employee Type

Confirm the step is a Contractor write.
In Sage Intacct, open Employee Types and confirm one exists with an identifier of exactly "Contractor" (exact spelling and case).
If none exists, create it. If similarly named types exist but none matches exactly, rename or add one so the exact identifier "Contractor" is present.
Re-run the sync and confirm the Contractor write step now completes past preload.

No Locations in Sage Intacct

Confirm the step is a Contractor write or a General Ledger payroll write.
In Sage Intacct, confirm at least one Location record exists.
If Locations do exist but this still fires, confirm the web services user the connector authenticates with has visibility to at least one of them; a permissions restriction can make the list come back empty even though Locations exist.
Re-run the sync and confirm the step now completes past preload.

Construction Module Not Confirmed as Enabled

In Sage Intacct, open the company's General Ledger dimension setup and locate the Cost Type dimension.
If it does not exist at all, the Construction capability that provides it is not enabled for this company; this needs to be added in Sage Intacct before any Sage Intacct sync can run, not just this one entity.
If the Cost Type dimension exists but is not enabled for General Ledger, enable it there.
Retry the connector's Test Connection check, or re-run the sync, and confirm the failure clears.

Missing “Arcoro Identifier” Custom Field

Confirm whether the step is a write or if encountered on Test Connection with a "Sage Intacct For Arcoro" or "Sage Intacct For Time Configuration" connector.
In Sage Intacct, go to Platform Services, then Custom Fields.
Confirm whether a custom field with Field ID "ARCORO_IDENTIFIER" exists on the object named in the message (Timesheets or Timesheet Entry).
If it does not exist, or is not a Text field, add or correct it: Text type, 30 characters on Timesheets, 70 characters on Timesheet Entry.
Re-run the sync (or retry Test Connection) and confirm the failure clears.

When to Escalate

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

Any "One or more errors occurred in ... PreLoad" summary with no other specific Error logged anywhere in the same step. This is not something Tier 1 can resolve from the summary text alone. Gather the sync execution ID, the step number, the entity, and every log line recorded for that step before escalating.
A Contractor sync that shows the Employee PreLoad summary text. Confirm first whether the Contractor Employee Type Error is present nearby and can be resolved that way; if it is not present, this is unexpected and should be escalated as a possible defect, not treated as a normal Employee-entity failure.
No Locations were read even though you confirms Locations exist in Sage Intacct. This points at a web services user permission restriction on the Locations dimension rather than missing data; escalate with confirmation that at least one Location exists and which connector/web services user is configured.
The Construction Module or custom field message recurs after you made the requested change in Sage Intacct. Escalate with the exact reason text (for the Construction Module message) or the exact object and field details (for the custom field message), since a recheck failing right after a fix can point to caching, a wrong company/entity context, or a permissions gap rather than the field or dimension truly being absent.
A connector passed its Test Connection check but still fails on the custom field message during an actual sync. This is possible today because Test Connection only checks the custom field for two specific configuration names; do not treat a passed test as proof the custom field exists.

Module Navigation