Overview Legend 🧭
Overview Legend 🧭
Introduction
Sage Intacct is a cloud accounting and financial management platform for mid-sized and growing organizations. It covers core financials, planning, and reporting.Activate Sage Intacct
Partner keys
You’ll need your own OAuth2 app, registered with Sage Intacct. Registering an app requires a Sage Intacct Web Services license. To be listed on the Sage Intacct marketplace, you also need a partnership with Sage. Discuss this with your Chift account manager. Approval from Sage is required before the app can be used.1
Create your organization
Go to the Sage Developer Portal, click View Console, and create your organization.
2
Enrol your sender ID in the Developer Programme
Go to Applications > New Application > Sage Intacct, choose Enrol under Sage Intacct Developer Programme, and enter your Web Services sender ID as the Intacct Web Services License Key.
3
Register the application
Go to Applications > New Application and select Sage Intacct again.
4
Name the app and set the redirect URI
Enter an application name. The name is informational, so any value works. Then set the redirect URI to:
5
Add your Web Services credentials and set the scope
Enter your Web Services sender ID as the Intacct Web Services License Key, and your sender password as the Intacct Web Services License Password. Select Production as the client scope, then create the application. Use Non-production instead for a test company. You cannot change the scope after creation.
6
Copy the client ID and secret
Wait for Sage’s approval email, then copy the client ID and client secret from the application. You need them to activate the connection.
Connector settings
No connector-specific settings.Test Sage Intacct
Vendor fees
Software editor (you)
Registering your app requires a Sage Intacct Web Services license (a sender ID and password), sold through your Sage Intacct account manager or partner representative. Prices are not published.
End user
Each end customer needs their own Sage Intacct Web Services developer license, bought through their Sage Intacct account manager.
Connect Sage Intacct
Sage Intacct setup guide for end users
The full step-by-step, with screenshots.
- their own Sage Intacct Web Services developer license (paid, bought through their Sage Intacct account manager), with a sender ID and password
- the Web Services subscription enabled on their Sage Intacct company, with that sender ID authorized under Company > Configuration > Company > Security > Web Services Authorizations, or approved by a Sage Intacct admin during sign-in
- name the connection and choose whether to sync analytic data
- enter the client ID and client secret from the registered OAuth2 app, and their sender ID and password
- sign in and authorize the connection
- select the entity to work with, and, if you enabled analytic accounting, a default dimension
Rate limits
Sage Intacct caps concurrent API requests per application and per company, according to the company’s performance tier (Tier 1: 6 requests per application, 8 per company). Each tier also sets a monthly API transaction entitlement (Tier 1: 100,000). Sage does not block transactions over that entitlement, but bills them as an overage. When a limit is exceeded, Sage Intacct returns an HTTP429 Too Many Requests error. Chift automatically manages these limits to optimize performance and prevent interruptions. However, once the API rate limit is reached, Chift cannot bypass these limitations.
See Sage Intacct’s transaction volume, concurrency and scaling documentation.
Limitations & specificities
Analytics
Analytics
Sage Intacct can make some dimensions mandatory, depending on the company’s setup. Entries sent without them are rejected.
Multi-folder
Multi-folder
One connection reaches several Sage Intacct entities only if no entity is selected during connection. Once an entity is chosen, the connection is limited to it.