Sage Intacct needs several pieces of setup before a sync can move any data: credentials, an Entity ID, and (for General Ledger) a journal, an accounting entity, and a reference number. Some of these live on the connector's own setup screen, and some are entered fresh each time you run the sync. When one of them is missing, blank, or does not match anything Sage Intacct recognizes, the sync either stops immediately or skips the one record that needed it. None of these messages mean your data was wrong, only that a setup value was missing or did not match.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Sage Intacct Provider could not read the configuration setting '[setting name]'. | Connector setup (fires before any read or write) | One of several settings needed to build or authenticate the connector is missing or blank. Which settings can trigger this, and whether each one stops the sync, is listed in the table below. | Varies by setting. See the settings table below. | Open the connector and fill in the named setting, or escalate if it is a platform-level credential. |
| No Root Location with ID "[configured Root Location value]" was found in Sage Intacct. To correct this issue, you must provide a valid Root Location ID in the "[connector name]" connector, then execute the Sync again. | Arcoro to Sage Intacct (write), Location | None of the Locations already read from Sage Intacct has an ID that matches the connector's configured Root Location value. | Sync stopped. This check runs once, before any Location is written, so the whole sync ends. | See When to escalate. A confirmed "Root Location ID" field could not be located on the connector; escalate rather than searching for it. |
| The Sage Intacct Connector's mapping for [Union / Union Local / Union Class] could not be resolved. Verify the value [configured entity value] is correct and execute the Sync again. | Sage Intacct to Arcoro (read), Union, Union Local, or Union Class | The matching Union Entity, Union Local Entity, or Union Class Entity field on the connector is enabled (not blank and not set to "Not Supported") but its value is not one of the three values Sage Intacct supports for this mapping. | Sync stopped. This check runs before that entity reads any records. | Set the field to one of the three supported values, or to "Not Supported" to turn that read off. |
| Multiple Time Type mappings found for the following rate codes: [rate codes]. Each rate code must have only one associated Time Type. | Connector setup only. This never reaches a sync log. | Two or more rows in the connector's Time Type Mapping list share the same rate code. | The connector cannot be saved and the connection test fails. No sync ever runs. | Remove or correct the duplicate rate code in the Time Type Mapping list, then test and save the connector again. |
| The sync parameter "GL Reference Number" was not specified. This parameter is required when syncing General Ledger. Please rerun the sync and ensure this value is specified. | Arcoro to Sage Intacct (write), General Ledger | The GL Reference Number value entered when starting the sync is blank. | Record skipped. This journal entry is not created; nothing else in the run is affected by this check alone. | Rerun the sync from the Run Sync screen and enter a GL Reference Number. |
| The sync parameter 'Sage Intacct Entity' was not specified. This parameter is required when syncing General Ledger. Please rerun the sync and ensure this value is specified. | Arcoro to Sage Intacct (write), General Ledger | The connector's Entity ID field is blank. | Record skipped. This journal entry is not created. | Despite the wording, this value is not re-entered per run. Open the connector and fill in the Entity ID field, then rerun the sync. |
| General Ledger Journal ID is required when syncing General Ledger. Please correct the data in the Sage Intacct connector configuration and run the sync again. | Arcoro to Sage Intacct (write), General Ledger | The connector's General Ledger Journal ID field is blank. | Record skipped. This journal entry is not created. | Open the connector and fill in the General Ledger Journal ID field, then rerun the sync. |
| A Journal with ID '[configured Journal ID]' could not be found in Sage Intacct. | Arcoro to Sage Intacct (write), General Ledger | The connector's General Ledger Journal ID field has a value, but it does not match any journal read from Sage Intacct for this run. | Record skipped. This journal entry is not created. | Correct the General Ledger Journal ID field on the connector to match an existing journal in Sage Intacct. |
| The Entity with ID "[configured Entity ID]" was not found in Sage Intacct. The journal entry will not be processed | Arcoro to Sage Intacct (write), General Ledger | The connector's Entity ID field has a value, but it does not match any entity read from Sage Intacct for this run. | Record skipped. This journal entry is not created. | Correct the Entity ID field on the connector to match an existing entity in Sage Intacct. |
| One or more journal entries found in Sage Intacct with reference number "[GL Reference Number value]". Either delete the journal entry in Sage Intacct or use a different reference number and run the sync again. | Arcoro to Sage Intacct (write), General Ledger | Sage Intacct already has one or more journal entries with the same reference number as the value entered for this run. | Record skipped. This journal entry is not created. | Delete the existing journal entry in Sage Intacct, or rerun the sync with a different GL Reference Number. |
Settings That Can Appear in "Could Not Read the Configuration Setting"
This message repeats for several different settings. The table below lists every setting confirmed in the code, where it lives, and whether a missing value stops the sync or is silently skipped.
| Setting name (as it appears in the message) | What it is for | Where it is set | If missing |
|---|---|---|---|
| Entity ID | The Sage Intacct entity the connector operates against. | Connector configuration (Entity ID field). | Always stops the sync. |
| Arcoro Location | Controls how Locations are populated when Sage Intacct is the source of Location data. | Connector configuration (Arcoro Location field). | Stops the sync only on the connector configuration named "Sage Intacct For Arcoro." On every other configuration, a missing value is not reported anywhere; the Location feature it controls is simply treated as not configured. |
| Union Entity | Tells the connector which Sage Intacct object supplies Union records. | Connector configuration (Union Entity field). | Same as Arcoro Location: only stops the sync on the "Sage Intacct For Arcoro" configuration, otherwise silently skipped. |
| Union Class Entity | Tells the connector which Sage Intacct object supplies Union Class records. | Connector configuration (Union Class Entity field). | Same conditional behavior as Union Entity. |
| Union Local Entity | Tells the connector which Sage Intacct object supplies Union Local records. | Connector configuration (Union Local Entity field). | Same conditional behavior as Union Entity. |
| SageIntacctClientID | The OAuth client ID Arcoro uses to authenticate to Sage Intacct. | Platform level. This is not a field on any user connector. | Always stops the sync. Escalate; the user cannot fix this. |
| SageIntacctSecret | The OAuth client secret Arcoro uses to authenticate to Sage Intacct. | Platform level. This is not a field on any user connector. | Always stops the sync. Escalate; the user cannot fix this. |
| Sage Intacct Web Services Customer ID | The Sage Intacct web services user Arcoro authenticates as. | Connector configuration (Web Services Customer ID field). | Always stops the sync. |
| Sage Intacct Company ID | The Sage Intacct company ID Arcoro authenticates against. | Connector configuration (Company ID field). | Always stops the sync. |
Confirming Error
- Open Sync History and find the sync execution.
- Open the step for this Sage Intacct connector and the direction involved (read or write, per the table above).
- Most of these messages stop the sync before any record finishes. Check the step's Failures count first. A non-zero Failures count with no per-entity Errors is the signature of the "could not read the configuration setting," "No Root Location," and "connector's mapping" messages, since all three throw before any entity row is produced.
- For the General Ledger messages, open the General Ledger entity row instead and check its Errors count. Each blocked journal entry adds one to Errors, and the Added, Updated, and Unchanged counts for that entity will be lower than expected.
- Match the fixed part of the sentence against the table above, ignoring the values inside quotes.
- "Multiple Time Type mappings found" never appears in a sync log at all. If you cannot save the connector or cannot pass a connection test, that is this message; look at the wizard's own error dialog instead of Sync History.
Resolving Error
Could Not Read the Configuration Setting
- Open the affected connector's Add/Edit Connector screen.
- Find the field named in the message (see the settings table above for where each one lives).
- If the setting is SageIntacctClientID or SageIntacctSecret, stop. These are not on the connector; escalate instead of looking for a field.
- Otherwise, fill in the missing value and save the connector.
- Rerun the sync and confirm the entity or step that previously showed a Failure now completes.
No Root Location with ID... /Connector's Mapping for Union...Could Not Be Resolved
- For the Union mapping message: open the connector and set the named field (Union Entity, Union Local Entity, or Union Class Entity) to one of the values Sage Intacct supports for that mapping, or to "Not Supported" if the user does not use it. Save and rerun.
- For the Root Location message: see When to escalate below before spending time searching the connector for a "Root Location ID" field.
Multiple Time Type Mappings
- Open the connector's Time Type Mapping section.
- Find the rate code named in the message and remove or correct the duplicate row so each rate code maps to only one Time Type.
- Test the connection and save again.
General Ledger Messages
- If the message names "GL Reference Number": this value is entered fresh on the Run Sync screen each time, not on the connector. Rerun the sync and supply it there.
- If the message names "Sage Intacct Entity," "Entity ID," or "General Ledger Journal ID" as required: these live on the connector's Add/Edit Connector screen as the Entity ID and General Ledger Journal ID fields. Fill in the missing field, save, and rerun.
- If the message says an Entity or Journal ID "was not found" or "could not be found" in Sage Intacct: the connector field has a value, but it does not match anything Sage Intacct returned during this run. Correct the Entity ID or General Ledger Journal ID field on the connector to a value that exists in Sage Intacct.
- If the message says a journal entry already exists with that reference number: in Sage Intacct, either delete the existing journal entry or rerun the sync from the Run Sync screen with a different GL Reference Number.
- After any fix, rerun the sync and confirm the General Ledger entity's Errors count drops and the journal entry now appears in Added.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The message names SageIntacctClientID or SageIntacctSecret. These are platform-level values, not fields on the user's connector, and the user cannot fix them.
- The message is "No Root Location with ID..." A "Root Location ID" field could not be confirmed to exist on any Sage Intacct connector configuration reviewed for this article. Escalate rather than telling the user to search for a field that may not be present.
- A setting was corrected exactly as described here, and the same message still appears on the next sync.
- The message text does not match anything in the tables above.
- The outcome is "sync stopped," and the fix above does not clear it after one retry.