Sage Intacct Access for Data Foundation
Data Foundation brings data from every ERP system and instance you connect into one Common Finance Model, and Sage Intacct is one of the ERPs it reads directly. The connection uses Intacct Web Services: a sender authorization for PlaidCloud and a read-only Web Services user. This page is for the Sage Intacct administrator who sets that up, and for the PlaidCloud user who asks them to.
PlaidCloud only reads data. Nobody sends a password by email.
Send the Access Request
Section titled “Send the Access Request”On the project’s Foundation tab, choose Create a new connection under Sage Intacct connection. The form shows the full request. Click Copy request to paste it into your own message, or Email request to open it in your mail program with the subject “Read-only Sage Intacct access for PlaidCloud (Web Services).”
What the Sage Intacct Administrator Sets Up
Section titled “What the Sage Intacct Administrator Sets Up”-
Authorize PlaidCloud as a Web Services sender. Under Company > Admin > Web Services authorizations, add the Sender ID PlaidCloud gave you. Send back the Sender ID and the Sender password Sage issued for it.
-
Create a Web Services user. Under Company > Admin > Users, create a user of type “Business” with the “Web services only” option, and a role with View permission on:
Area Objects General Ledger Accounts, Journal entries (all journals, including adjustment journals), Account balances, Reporting periods, Exchange rates, Budgets Company Entities (locations), Departments, Classes, Projects Accounts Receivable Customers Inventory Control Items Order Entry Transactions (sales invoices, and the credit memos and returns that take them back), if you want sales Give the user access to the top level of the company and to every entity PlaidCloud reports on. If your credit memo and return transaction definitions aren’t named Sales Credit Memo and Sales Return, tell the PlaidCloud user their names.
-
Allow the user’s IP address if your company restricts Web Services by IP.
What to Send Back
Section titled “What to Send Back”| The administrator sends | Entered in PlaidCloud as |
|---|---|
| The company ID | Company ID |
| The Web Services user ID | Web services user ID |
| The Web Services user’s password | Web services password |
| The Sender ID | Sender ID |
| The Sender password | Sender password |
| The names of your credit memo and return transaction definitions, if not the defaults | The credit_documents system setting (defaults: Sales Credit Memo, Sales Return) |
| The entities PlaidCloud may read | Chosen under Entities in PlaidCloud |
Passwords go through your password manager, never by email. The PlaidCloud user’s team pastes the Web services password and the Sender password into PlaidCloud themselves. Entities that are your company’s own eliminations go under the elimination_entities system setting.
Check the Access
Section titled “Check the Access”Back in PlaidCloud, enter the values and click Test connection. Each dataset shows as Readable, Missing permission or Error:
| Dataset | Permission it needs |
|---|---|
| Entities | Company: Entities (View) |
| Chart of accounts | General Ledger: Accounts and Statistical accounts (View) |
| Departments | Company: Departments (View) |
| Customers | Accounts Receivable: Customers (View) |
| Products | Inventory Control: Items (View) |
| Currency rates | General Ledger: Exchange rates (View) |
| Fiscal calendar | General Ledger: Reporting periods (View) |
| Trial balance | General Ledger: Account balances (View) |
| General ledger | General Ledger: Journal entries (View) |
| Sales lines | Order Entry: Transactions (View) |
| Budget | General Ledger: Budgets (View) |
| Allocation drivers | General Ledger: Account balances (View) |
When a dataset is missing, the test names the permission to add. Ask the administrator to add it to the role and test again. Sales lines, Budget and Allocation drivers are optional: a company that doesn’t use them still loads everything else.