Sage Intacct connection errors

When Summit can't connect to Sage Intacct, it shows Sage's reason in plain words. Find the message below.

"Sage Intacct didn't accept that Web Services user"

Summit Spend is authorized, but Sage wouldn't sign in as that user. Check each of these in Sage Intacct:

• The Web Services subscription is on (Company > Subscriptions). This is the most common cause: Sage lets you set everything else up without it.
• The Web Services user exists and is active.
• That user is set on the Summit Spend entry under Company > Setup > Company > Security > Authorized client applications.
• The username you typed is the user ID, then @, then the Company ID, like summitspend@ACME.

"Summit Spend isn't authorized for that Sage Intacct company yet"

Add Summit Spend's client ID under Company > Setup > Company > Security > Authorized client applications. You can copy it from the connect screen in Summit. Then check that the Company ID after the @ is exactly the one you sign in to Sage with.

"Sage Intacct is unavailable right now"

Sage is down or in maintenance. Try again in a few minutes.

"Sage Intacct refused the connection"

This one is usually on our side. Email support@summitspend.com with the full message.

The connection says "Reconnect required"

Sage stopped accepting the connection. Connect again from Settings > Accounting > ERP connection with the same username. You don't need to disconnect first.

A coding field syncs zero values

Your company may not use that field in Sage, or the Web Services user can't read it. Check the user's permissions in Sage Intacct, then click Sync fields from Sage Intacct.

A charge won't export

That's an export error, not a connection error. See Sync and export errors.

Full setup steps: Connect Sage Intacct.