---
title: "Connect Sage Intacct"
slug: "sage-intacct-user-guide-connect"
description: "Connect Sage Intacct to MakersHub: prepare Web Services access and permissions, test the connection, sync records, and choose Direct Entity where applicable."
tags: ["Web Services User", "Connect", "User Guide", "Sage Intacct", "Integration rules", "Troubleshooting", "Integration"]
updated: 2026-11-04T18:49:11Z
published: 2026-11-04T18:49:11Z
canonical: "support.makershub.ai/sage-intacct-user-guide-connect"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.makershub.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](/docs/sage-intacct-user-guide-best-practices) for the recommended configuration. For an existing connection, use [Choose the connection’s Direct Entity](/docs/sage-intacct-user-guide-connect#mh-7-choose-the-connections-direct-entity), [After changing permissions](/docs/sage-intacct-user-guide-connect#mh-after-changing-permissions), or [Disconnect the integration](/docs/sage-intacct-user-guide-connect#mh-disconnect-the-integration) below. For credential changes, follow [Save corrected credentials and test](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-save-corrected-credentials-and-test) in Troubleshooting.

### Setup access

*For a visual companion to these setup steps, see [Setup Walkthroughs](https://support.makershub.ai/docs/integrating-with-sage-intacct#turn-on-web-services).*

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](/docs/sage-intacct-user-guide-best-practices#mh-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](https://support.makershub.ai/docs/contact-us) 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](/docs/sage-intacct-user-guide-vendors-in-a-multi-entity-company#mh-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](/docs/sage-intacct-user-guide-connect#mh-7-choose-the-connections-direct-entity) below to save and verify a selection. [Locations and Direct Entity](/docs/sage-intacct-user-guide-working-with-entities#mh-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.

| **Item** | **What to prepare** |
| --- | --- |
| Web Services subscription | Enable **Web services** under **Company > Admin > Subscriptions**. See [Subscribe to Web Services](https://www.intacct.com/ia/docs/en_US/help_action/More/Customization_and_Platform_Services/Setup/subscribe-to-web-services.htm). *Screenshots: [Turn on Web Services](https://support.makershub.ai/docs/integrating-with-sage-intacct#turn-on-web-services).* |
| Company ID | Copy **Company ID** from **Company > Setup > Company > General information**. See [Company information](https://www.intacct.com/ia/docs/en_US/help_action/Company/Company_setup/Company_Information/company-information.htm). *Screenshots: [Find your Company ID](https://support.makershub.ai/docs/integrating-with-sage-intacct#find-your-company-id).* |
| Sender authorization | Add **MakersHubMPP** under **Web Services authorizations**, with status **Active**. Follow [Web Services authorizations](https://www.intacct.com/ia/docs/en_US/help_action/Company/Company_setup/Company_Information/Security/company-web-services-authorizations.htm). |

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.

**Existing user-based setup**

If your company already uses user-based permissions, create the Web Services user first, then apply full access directly using the short instructions in step 3. Keep your company’s existing permission model.

1. [Copy an available **Admin** role or create a new role](https://www.intacct.com/ia/docs/en_US/help_action/Administration/Roles/manage-roles.htm), 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](https://www.intacct.com/ia/docs/en_US/help_action/Administration/Permissions/permissions-overview.htm#Useshortcutstograntorremovepermissionsquickly).
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.

**Save in both places:** save each edited Permissions window, then the outer Roles subscription page. Saving the windows alone does not complete the role-permission changes.

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

**Individual permissions**

Individual grants are not recommended for standard setup. If your company’s access policy requires them, use [Choose individual Sage Intacct permissions](https://support.makershub.ai/docs/integrating-with-sage-intacct#create-user-permissions) instead of All, and review the grants as supported features change.

### 3. Create the Web Services user

[Create a separate Web Services user](https://www.intacct.com/ia/docs/en_US/help_action/Administration/Users/web-services-only-users.htm#AddaWebServicesuser) for MakersHub, using these setup choices.

| **Setting** | **Value** |
| --- | --- |
| User type | **Business** |
| Admin privileges | **Full** |
| Status | **Active**. Review [Intacct's Web Services user statuses](https://www.intacct.com/ia/docs/en_US/help_action/Administration/Users/web-services-only-users.htm#Status) if the account is locked out or inactive. |
| Role-based permissions | Assign the **MakersHub** role prepared in step 2 to this Web Services user. |

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.

**Existing user-based setup**

Create the Web Services user first.

**Where to assign access:** **Company > Admin > Users, roles, and groups > Web Services users > Subscriptions** for that user. For standard full access, select **All** for **Activities and lists** and, separately, **Reports** where shown in each application’s **Permissions**. If following the individual-grant reference, retain its selections instead. Save each window, then select **Save** on **User Application Subscriptions** if shown. No role is assigned; keep the company’s existing permission model. See [Intacct’s Administration permissions guidance](https://www.intacct.com/ia/docs/en_US/help_action/Administration/Permissions/Application_permissions/administration-permissions.htm).

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](https://www.intacct.com/ia/docs/en_US/help_action/Administration/Passwords/reset-password-admin.htm).

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](https://www.intacct.com/ia/docs/en_US/help_action/Administration/Admins/make-user-an-administrator.htm).

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](https://support.makershub.ai/docs/integrating-with-sage-intacct#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](/docs/sage-intacct-user-guide-connect#mh-understand-direct-entity).

### 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**.

| **Result** | **What to do** |
| --- | --- |
| **Connection successful** | Continue to step 6. |
| **Permission denied: …** or **Permissions denied: …** | Review your configured application permissions, then follow **After changing permissions** below before testing again. |
| **Could not verify permissions: …** | The check did not finish. Run **Test Connection** again; if the message persists, contact [MakersHub support](https://support.makershub.ai/docs/contact-us) with the message. |
| **Failed: select the top-level entity when testing the connection** | This result identifies denied required read access in the selected Direct Entity context. Follow **After changing permissions** below, then retest the restored working context. If that context still fails, keep setup incomplete and contact support with the selected location, its entity, and the exact message. |
| A sign-in or sender-authorization error | Before another attempt, use [Sign-in, lockouts, and connection holds](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-sign-in-lockouts-and-connection-holds) to correct the reported problem, save changed credentials, and verify access. Then return here to finish setup. |

#### After changing permissions

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

**Two Saves are required for role permissions:** save **each edited Permissions window**, then select **Save** on the outer **Roles subscription** page.

**Existing user-based setup**

For an existing user-based setup, save each edited Web Services-user Permissions window, then select **Save** on **User Application Subscriptions** if shown.

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](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-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](/docs/sage-intacct-user-guide-connect#mh-7-choose-the-connections-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](https://support.makershub.ai/docs/contact-us) 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](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-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](/docs/sage-intacct-user-guide-working-with-entities#mh-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](/docs/sage-intacct-user-guide-working-with-entities#mh-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](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-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](/docs/sage-intacct-user-guide-connect#mh-after-changing-permissions) above for permission failures or [Sign-in, lockouts, and connection holds](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-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](/docs/sage-intacct-user-guide-working-with-entities#mh-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](/docs/sage-intacct-user-guide-connect#mh-6-import-and-inspect-your-sage-records) for **Locations** and confirm its company and entity in Intacct. Contact [MakersHub support](https://support.makershub.ai/docs/contact-us) 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](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-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.

**Disconnecting the integration**

*Disconnect cannot be undone, and reconnecting does not restore the existing links between MakersHub records and this integration. It does not cancel MakersHub payments or delete transactions already created in Intacct. Contact [MakersHub support](https://support.makershub.ai/docs/contact-us) about uncertain transactions or record-link problems before disconnecting.*

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](/docs/sage-intacct-user-guide-connect#mh-steps) above. Reconnecting creates a new connection.

## Continue in MakersHub

Continue with [Working with Sage Intacct entities](/docs/sage-intacct-user-guide-working-with-entities) to confirm the operating context and records for your bill, then use [Vendors in a multi-entity company](/docs/sage-intacct-user-guide-vendors-in-a-multi-entity-company) to identify or maintain its vendor. Once the context and vendor are ready, continue with [Bills and payments](/docs/sage-intacct-user-guide-bills-and-payments).

Configure your bill-coding rules using the rule-editor controls in the [Integration Mapping overview](https://support.makershub.ai/docs/integration-mapping). Choose from the Intacct lists you have already verified.

For a transaction sync error, use [Sync errors](/docs/sage-intacct-user-guide-troubleshooting-and-common-questions#mh-sync-errors). That article also routes setup questions and other unexpected results to the relevant checks.

Return to [Overview](/docs/sage-intacct-user-guide-overview).