We need two kinds of accounts:
Intacct User account: used mainly in the test environment to view and create test data
Web Services User: used by the integration to read and write data
In addition, we need the client to get a Sender ID from Sage. This is purchased from Intacct and is called a Web Services developer license.
We use the APIs provided by Sage described here: https://developer.intacct.com/api/
Intacct User Account
In the Test environment please invite our developer(s) as a user. We use this account for testing, so it should have the accesses needed to create any test data needed for the integrations. In production this can be a read-only account.
Intacct Sender ID
The Sender ID is specific to the client company and can be used in all environments.
Intacct will send to the client the Sender ID and an email where the client can set the password. Please do this and make sure you have a copy of that password as that password can only be reset by Intacct going forward.
After you have done this, go to Company->Setup->Company -> Security to the section "Web Services authorizations" and make sure the provided Sender ID is entered into the list.
Field | Value | Note |
Sender ID | Company name | Provided by Intacct |
Sender Password | TBD | Intacct sends a temporary password to the client who can then set a permanent password |
Web Services User
For a given environment, usually starting with Implementation, we need to have a web services user added.
These credentials are also required but are specific to each environment.
The web services account should be granted access to the needed data in Intacct.
Variable | Value | Notes |
Company ID | TBD | Please provide this to Calance |
User ID | calance |
|
Username | calance |
|
Primary/Account Email Address | <company>@calance.us | This is the email calance provides to your company, from the domain |
Password | TBD | When the user is created, a password is sent to the connected email |
*Note: while the Sender ID is not environment specific, the Web Services User is. Once the switch to production begins, another Web Services User will need to be created in the clients Production environment with all the necessary permissions. You are welcome to use the same values as the ones set for Implementation.