Sage Intacct· Configuration
Step 5 of 11 · Implementation · Updated October 26, 2026

Sage Intacct configuration

Configuration builds the signed design in Sage Intacct: features, setup records, numbering, roles and workflows. Done by hand, it is hours of screens that are hard to review and hard to repeat in production. superglue's agent applies the setup through the Sage Intacct API, in the sandbox first, and records each change it makes.

How this step works

What the agent does

  • Turns the signed design into a configuration plan for your review.
  • Applies the setup through the API in the sandbox.
  • Records each change, so the configuration can be reviewed and repeated.
  • Repeats the tested configuration in production.

What you decide and approve

  • The setup values that only the client can decide.
  • Every write. Each one pauses for your approval.
  • When the sandbox configuration moves to production.

What the client gets

  • A configured sandbox and production account.
  • A configuration workbook that lists every setting.

What to get right in Sage Intacct configuration

  1. 01

    Keep a log of every setting

    A sandbox is a copy of production, and changes in it do not move to production by themselves. Record each setting, and move custom fields, Smart Rules and Smart Events as customization packages.

  2. 02

    Require dimensions on the accounts that need them

    Set required dimensions on each GL account, such as department on expense accounts. Users then cannot post an entry that breaks reporting.

  3. 03

    Set up document sequencing before the first transaction

    Assign a sequence to each transaction type, and set the next number to continue legacy numbering where the client needs it.

  4. 04

    Use role-based permissions

    Set the permission type to role-based in the company configuration. Build one role per job and assign roles to user groups, so new users get access in one step.

From Sage Intacct partners
80%
fewer migration hours per project
<1 hr
to migrate 185 accounts into a Sage Intacct sandbox
40
active fixed-fee implementations
“We do 40+ Sage Intacct implementations a year, and data migration used to take half our budget on every project. superglue turned our biggest cost center into something we can scope in hours, not weeks.”
Sage Intacct implementation lead, certified Sage Intacct partner
Read the case study

Frequently asked questions

What should you get right when configuring Sage Intacct?

Keep a log of every setting; Require dimensions on the accounts that need them; Set up document sequencing before the first transaction; Use role-based permissions. The agent applies the setup in the sandbox first.

Does superglue change Sage Intacct without approval?

No. The agent shows each change before it writes and waits for your approval. Production repeats the configuration you tested in the sandbox.

How does superglue work with our consultants?

superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.

Can we use our own implementation method?

Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.

Which systems can we migrate from into Sage Intacct?

Common sources are QuickBooks, Sage 50, Sage 100 and Sage 200, Microsoft Dynamics GP, Xero and spreadsheets. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.

Is client data safe?

superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.

How do we start?

Start with one live Sage Intacct project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.