Connect Sage Intacct

Connect Sage Intacct to your MakersHub bill and approval workflow, then verify the imported records and working context.

Start with Sage Intacct best practices for the recommended configuration. For an existing connection, use Choose the connection’s Direct Entity, After changing permissions, or Disconnect the integration below. For credential changes, follow Save corrected credentials and test in Troubleshooting.

Setup access

For a visual companion to these setup steps, see Setup Walkthroughs.

Use your own Sage Intacct account with Full administrator privileges for Intacct setup and administration. In MakersHub, use an administrator account or one with integration access; if Integrations is unavailable, ask your MakersHub administrator to grant access. Choose an accessible Account email for the separate Web Services user’s information and password recovery.

Establish the intended company structure and entity tracking using Single-entity and multi-entity configuration. Where available, give the Web Services user Top level access for setup and permission checks; a genuine single-entity company without Top level retains its default context. Application grants and entity restrictions are separate. Contact MakersHub support if the required access cannot be established.

Understanding MakersHub’s Direct Entity

Direct Entity is MakersHub’s connection setting for the Intacct location you work from. That location identifies its associated entity and affects which records MakersHub retrieves and which actions are permitted. The bill’s Entity and line coding remain separate.

Find the setting after the first sync:

1. Open user menu > Integrations, then select View for Sage Intacct.
2. Open Edit Web Service Authentication, then select Edit.

The selector appears when the imported Locations list contains records; it is not on the initial credentials form.

• Top-level work: leave Direct Entity empty at Top Level... for shared-vendor creation and work across available entities, subject to your Intacct access and transaction-entry settings.
• Entity-specific work: select a location associated with the intended entity. Use the owning entity’s context to retrieve or maintain a private vendor.
• Single-entity companies without Top level: keep the established default context; the optional selector is not required.

For shared or private vendor creation, follow Create a new vendor in the intended context for the form’s defaults, choices, and result checks. Shared creation requires a Top-level connection; a vendor’s ownership is fixed after creation.

Follow Choose the connection's Direct Entity below to save and verify a selection. Locations and Direct Entity explains its effects; a previously imported record still being listed does not confirm current access.

1. Prepare Web Services access

In Sage Intacct, prepare these three items before creating the connection.

Enter MakersHubMPP with that capitalization; Intacct's Sender IDs are case-sensitive.

2. Set up application permissions

Give MakersHub’s dedicated Web Services user full application access across the applications available in your Intacct company. For role-based permissions, prepare the role before creating that user in step 3.

1. Copy an available Admin role or create a new role, naming it MakersHub.
2. Open the role’s Subscriptions page and select Permissions for an available application.
3. Select All for Activities and lists and, separately, Reports, where shown. See Use shortcuts to grant or remove permissions quickly.
4. Select Save in that Permissions window. Repeat for every available category, including when reviewing a copied Admin role.
5. After completing all categories, select Save on the outer Roles subscription page. Assign the saved role when creating the Web Services user in step 3.

Available categories depend on your Intacct subscriptions. Review every category shown, including any beyond these examples:

• Administration
• Company
• Cash Management
• General Ledger
• Accounts Payable
• Platform Services
• Accounts Receivable
• Projects
• Expenses
• Inventory Control
• Order Entry
• Purchasing
• Consolidation
• Contracts
• Taxes
• Fixed Assets Management
• Time
• User Defined Dimensions

3. Create the Web Services user

Create a separate Web Services user for MakersHub, using these setup choices.

Enter your accessible email address in Intacct's Account email field. Complete the creation confirmation in order:

1. Select Save.
2. Select Create.
3. Verify with your own Intacct password.

Intacct emails the new user's User ID information. Retain the User ID and password for step 4; if the password is unavailable, reset the Web Services user's password.

The Full administrator setting and application permissions are separate. Keep the application access from step 2 assigned to this user. See Assign permissions to an administrator.

Use the Web Services user's credentials in MakersHub. This user cannot sign in to the Sage Intacct interface; manage it from your own Sage Intacct account.

4. Save the connection in MakersHub

1. Open your user menu, then select Integrations.
2. On the Sage Intacct card, select Connect.
3. Select Create a Sage Intacct Connection.
4. Enter Company ID, User ID, and User Password using the Web Services user's credentials.
5. Select Save.

For screenshots of the connection form, testing, and first sync, see Setup in MakersHub in Setup Walkthroughs.

Direct Entity is not in this initial form. After the first sync, step 7 covers the applicable connection context and location choice; see Direct Entity explained.

5. Test the connection

Test Connection checks the connection and required read permissions. It does not exercise every Add, Edit, Post, or Run grant.

Select Test Connection. Continue to the initial sync when the message is Connection successful.

After changing permissions

Update the role or Web Services user already configured for this connection, retaining its application grants.

1. Find Test Connection. Open an existing connection with View, or use the initial setup form. If the control is absent, preserve the context and use If Test Connection is unavailable.
2. Test the initial company context. Where available, use Direct Entity empty at Top Level...; a genuine single-entity company without Top level keeps its established default. Use Choose the connection's Direct Entity below for any change. If already at Top level, test the saved values as they are.
3. Verify the working context. After a successful Top-level test, restore any temporarily changed context using that same procedure, including its test, refresh, and record checks. A Top-level test does not verify another context.

If a permission error remains after saving, wait 15–30 seconds, then test again. Recheck grants and Saves if it persists; contact MakersHub support with the intended context and exact message if unresolved. Treat verification as incomplete.

Update and Refresh Data do not replace Test Connection. For rejected credentials, lockouts, or holds, use Sign-in, lockouts, and connection holds before further attempts.

6. Import and inspect your Intacct records

1. Select Sync Data with Sage Intacct. Wait until Sage Intacct Mapping replaces Sage Intacct Integration Setup. If an error appears instead, correct the reported problem before retrying the sync.
2. Open Integration Data, then review Synced Data List.
3. Review each list shown. Use the searchable dropdowns to find known Suppliers and Chart Of Accounts records, plus the Departments, Accounting Classes, Items, and Customer|Job records you use in Intacct. Lists you do not use need not contain records.
4. For entity records, inspect the row labeled Locations.

To verify the initial sync, find a known Intacct record by name in each list your work needs and read the result of any row you refresh. Use Check the record types your bill needs for ownership and availability checks, then return here to finish setup.

If expected records are absent, or a list has a zero/blank count or date:

1. Select the refresh icon at the right end of that row.
2. Confirm Refresh Data.
3. Read the result beside the icon. Refresh data completed confirms that refresh succeeded; a failure message appears in red. Correct a reported access problem using step 5, then refresh that row again.

A count of 0, or a blank count and Last Updated date, does not by itself mean the sync failed. A successful import with no returned records can leave the row blank; check the row’s refresh result.

7. Choose the connection's Direct Entity

Use this after the first sync or for later changes. Choose Top Level... for shared-vendor creation and permitted work across entities, or a location associated with the intended entity for entity-specific work. See Choose the connection context for your work. Single-entity companies without Top level keep their established context: skip selection and Update, then complete the test and record checks.

1. Prepare. Copy unsaved work and note the current context. Open user menu > Integrations > View for Sage Intacct. If Test Connection is absent, preserve the context and use If Test Connection is unavailable.
2. Select and save. Open Edit Web Service Authentication > Edit. Choose the location, or leave Direct Entity empty at Top Level.... Select Update if changed, then reopen the authentication details to confirm Company ID, User ID, and Direct Entity. Cancel cannot undo an Update; after a save error, inspect the values before retrying and contact support if uncertain.
3. Test. Select Test Connection and confirm Connection successful. Use After changing permissions above for permission failures or Sign-in, lockouts, and connection holds for access errors. A refused location alone is not a reason to reset credentials.
4. Refresh and inspect. In Integration Data > Synced Data List, refresh required lists and confirm Refresh data completed. Find the records using Check the record types your bill needs. Update does not refresh lists; listed options do not prove action permissions.
5. Resume. After temporary vendor maintenance, restore the working context and repeat these checks before bill work.

If a required selector or location is missing, follow the refresh steps above for Locations and confirm its company and entity in Intacct. Contact MakersHub support if it remains unavailable or fails testing; treat the context as unverified. Keep company structure and entity tracking unchanged.

Check it worked

• Test Connection reports Connection successful for your saved connection. If the test is unavailable, complete the support verification route in If Test Connection is unavailable before treating setup as verified.
• In Integration Data, you can find the known suppliers, accounts, and coding records your work needs. For any row you refreshed, confirm Refresh data completed. An unused list need not contain records.
• Your applicable connection context is saved and verified using the available test or the support-verification route; each inspected list has been refreshed after any change to Direct Entity.

Disconnect the integration

Use this removal procedure for an existing connection, including one that cannot currently connect. It requires neither initial setup again nor a successful connection test.

Disconnect removes the active connection and its imported integration lists from this MakersHub company. It is not a sign-in recovery step or a way to obtain a missing Test Connection control.

1. Open the Sage Intacct connection's Integration Data tab.
2. In the connection-removal input, type Disconnect exactly as shown.
3. Select Confirm Disconnect only when you intend to remove this connection.

For a new connection, return to Set up and verify the connection above. Reconnecting creates a new connection.

Continue in MakersHub

Continue with Working with Sage Intacct entities to confirm the operating context and records for your bill, then use Vendors in a multi-entity company to identify or maintain its vendor. Once the context and vendor are ready, continue with Bills and payments.

Configure your bill-coding rules using the rule-editor controls in the Integration Mapping overview. Choose from the Intacct lists you have already verified.

For a transaction sync error, use Sync errors. That article also routes setup questions and other unexpected results to the relevant checks.

Return to Overview.