Sage Intacct Sync Error | Entity access or console setup issue in Sage sync
Error related to entity access or entity configuration between Ramp and Sage Intacct.
- The User ID used for API authentication does not have access to the entity you are attempting to slide into.
- Confirm the client has granted entity access to this user.
- The client may be using a Console ID structure. In Sage Intacct, the hierarchy is:
- Console ID → Company ID → Entity
- Ensure you are using the correct Company ID and Entity in your authentication.
- If your XML includes a Console ID and Company ID, update the credentials when reconnecting Ramp to Sage Intacct.
- The bill may contain items assigned to an incorrect Entity or mapped to the wrong Sage Intacct location.
- Confirm all line items on the bill are associated with the correct entity and location.
To fix this:
- In Sage Intacct, confirm you are using the correct Company ID (not a Console ID) for the integration.
- Ensure Web Services is enabled and the RampFinancialMPP Sender ID is authorized.
- Go to Company → Admin → Subscriptions and confirm Web Services is active.
- Go to Company → Setup → Company → Security and verify RampFinancialMPP is listed and active.
- Verify the Ramp Web Services user.
- Go to Company → Admin → Web Services users.
- Confirm the user is active, has full module permissions, and has access to the operating entity.
- In Ramp, go to Accounting → Settings → Danger zone, click Disconnect Sage Intacct, then reconnect using the same Company ID and credentials.
- Retry syncing one of the failed invoices.
Recommendation (Ramp entity configuration):
- Adjust the entity settings in Ramp so the entity is set at the Top Level instead of the Entity Level. This avoids entity slide-in errors when posting bills.