Partner help

Sage Intacct setup

The Sage Intacct group on the customer's page connects to the customer's Sage Intacct company through Sage's REST API: Connection, Compare, Since the last load, Configuration and Load log. Ledger Doctor only adds accounts and dimension values that are missing; it never changes or deletes one that's there. Configuration changes are sent only after you confirm them, and each can be put back.

About 40 seconds, narrated, with captions. Sample company, made-up data.
Did you find this video helpful?

Implementation and production

Partners usually load a test migration into an implementation company Sage provides, then set up production. Each customer has both: switch between Implementation and Production at the top of the customer's page. Each keeps its own company, web services user, client application, dimension mapping, checklist and load log. The customer's data and the plan are shared.

Your client applications

An admin enters your default client applications from the Sage Developer Console once, in Settings (the gear at the top of every page), each with its Client ID (the long ID ending in app.sage.com, not the application's name) and Client secret. There are two:

  • Implementation: an application with Sage's non-production client scope, for sandbox and implementation companies. The one you entered before there were two is this one.
  • Production: an application with the production scope, for the customer's production company.

The Implementation environment uses the Implementation default, or the Production one when the Implementation one is blank (a production-scope application works with every company type). The Production environment uses only the Production default. When a customer has its own sender ID and client application, enter that on the customer's Connection instead. Secrets are stored encrypted and never shown.

Connection

  1. Enter the company ID, the web services user (case-sensitive) and, if you need one entity rather than the top level, the entity.
  2. Under Client application, Use my default client application names the default this environment uses (Implementation or Production) and says whether it's entered. Untick it to enter one just for this customer. When the default it needs isn't entered, the page and the sign-in say which one to enter in Settings. A non-production application can't sign in to a production company: the sign-in then says to use a production client application for this environment.
  3. Choose Test REST sign-in. It reads the company's dimensions (with the names the company uses, such as Fund for Location), the entities and the chart's size, and checks each permission the steps need. A missing one says what to give the web services user's role.
  4. Choose which of the company's dimensions each plan dimension goes to, and the Retained earnings account (it can be one the plan creates; it's created first). Choose Save.

Compare, then create

  1. On Compare, pick a frozen plan version and choose Compare. For the chart and every mapped dimension it shows what matches, names that differ slightly, numbers the company already uses for something different, what's to add, and what's only in Sage Intacct.
  2. Decide each number the company uses for something different: Use Sage Intacct's record, or Renumber it in the plan and freeze a new version. Create waits until they're decided.
  3. Choose Create, or tick a few records and choose Create only the ticked for a small test. Before it runs it says how many API calls it takes and how many were made this month.
  4. Check the opening balance entry reads the company and lists what would stop the entry loading: accounts or values missing or inactive, a dimension an account requires left blank, entities missing.

The opening balance entry

On Opening balance, Check against the company lists what would stop the entry loading, and Create as drafts sends one entry per entity, in the journal you choose, as a draft: each goes whole or not at all, and is read back and tied to the plan to the penny. Review and post the drafts in Sage Intacct. Delete the draft removes one Ledger Doctor created that's still a draft; a posted entry is never touched.

API calls

Sage counts each record created and each read as a transaction against the customer's monthly allowance (100,000 on Tier 1; enter the company's on Connection if it's higher). The counter at the top of the page shows Ledger Doctor's calls this month. The customer's other integrations count too, and calls over the allowance are charged, not blocked.

Since the last load, Configuration and Load log

Since the last load shows what GP has that the latest frozen version doesn't, and what's frozen but not in the company yet, so a GL detail load never points at something missing. Configuration reads the company's preference objects, grouped by application; a change is read back and logged. Its Module settings read General Ledger, Accounts Payable, Accounts Receivable, Cash Management and other applications' settings through Sage's XML API, which its REST API doesn't cover yet. They're read only: change them in Sage Intacct, then read them again. They need your XML sender ID and password (Settings, the gear at the top) and the web services user's password (Connection), all kept encrypted. Test XML sign-in on Connection checks just that sign-in, apart from Test REST sign-in. Compare with your defaults puts each configuration setting from your partner defaults beside the company; an admin links a setting to its Sage Intacct field once, and Set it changes the company to your default. Load log lists everything created, refused or changed, with Put it back for configuration changes. The steps done by hand in Sage Intacct are on the Checklist.

Did you find this article helpful?