Skip to main content
Stuut connects to Sage Intacct with OAuth 2.0. A Sage Intacct administrator registers Stuut as an authorized client application and creates a Web Services user for Stuut, and then you sign in to Sage Intacct from Stuut with that user. There are no keys or certificates to copy. Once connected, Stuut imports your customers, invoices, credit memos, and payments, and then checks Sage Intacct for changes every hour. Estimated time: 20–30 minutes

Before you begin

You will need:
  • A Sage Intacct administrator who can edit Company information, roles, and Web Services users
  • A Web Services subscription in Sage Intacct (Company → Admin → Subscriptions). Contact your Sage account manager if it isn’t listed.
  • A Stuut administrator account
  • Pop-ups allowed for your Stuut dashboard. Sage Intacct’s sign-in opens in a pop-up window.
Stuut’s sender ID is stuutMPP and its client ID is 714f94ad79c8059eb934.app.sage.com. You enter both in Sage Intacct below. If your company enforces IP address filters in Sage Intacct, ask your Stuut team for Stuut’s IP addresses before you start.

What Stuut syncs

Stuut only reads from Sage Intacct. It never creates, updates, or deletes anything in your company, and it does not post payments, notes, or contacts back to Sage Intacct. A few things to know:
  • Stuut pulls Accounts Receivable records only. Bills, purchase orders, and other Accounts Payable or Order Entry transactions are never imported.
  • Sage Intacct invoice states map to Stuut as follows: Draft stays draft; Posted, Open, Partially paid, and similar states are open; Paid is paid; Voided, Reversed, and Canceled are void. An open invoice with nothing left to pay shows as paid.
  • Contacts are imported from the customer record. Stuut creates a contact only when Sage Intacct provides an email address for it. The bill-to contact becomes the customer’s billing contact in Stuut.
  • Stuut reads across all entities in a multi-entity company. You connect once at the top level.

Current limits

  • Credit memo line items are not imported. Stuut imports the credit memo’s header and amounts only.
  • Positive AR adjustments (debit memos) are not imported.
  • A small number of accounts sync invoices in a lighter query-only mode that skips the per-invoice detail read. In that mode, invoice line items are not imported. Your Stuut team will tell you if this applies to your account.
  • Invoice tax and discount amounts are not broken out; Stuut stores the invoice total.

How often Stuut syncs

  • First import: starts as soon as the connection is validated. It brings in all customers and GL accounts, every open invoice plus any invoice dated in the last 180 days, and credit memos and payments from the last 12 months.
  • Ongoing: every hour, Stuut fetches records that changed since the last sync.
  • Deleted invoices: after each sync, Stuut checks a batch of its invoices against Sage Intacct and marks any that no longer exist as deleted.
Sage Intacct does not notify Stuut when a record changes, so a change can take up to an hour to appear. You can start a sync at any time with the Sync button on the connection.

Set up the connection

Steps 1 to 6 are done in Sage Intacct by an administrator. Steps 7 to 10 are done in Stuut.

1. Confirm the Web Services subscription

In Sage Intacct, go to Company → Admin → Subscriptions and make sure Web Services is subscribed. Sage Intacct may show a zero-dollar charge warning for it; that’s expected.

2. Authorize Stuut’s sender ID

  1. Go to Applications → Company, open the Setup tab, and click Company under Configuration.
Sage Intacct Applications menu with Company selected under the Setup tab

Applications → Company → Setup → Company

  1. Click Edit.
Edit button in Sage Intacct Company information
  1. Open the Security tab.
Security tab in Sage Intacct Company information

Company information → Security tab

  1. Scroll to Web Services authorizations and click Add.
Web Services authorizations section with Add button
  1. Enter the following and click Save:
    • Sender ID: stuutMPP
    • Description: any label, for example “Stuut”
    • Status: Active
Web Services sender information form with Sender ID stuutMPP, description For Stuut AI Agents, and status Active

Web Services sender information

Sender IDs are case-sensitive, so enter it exactly as shown. The sender ID is what lets Stuut generate invoice PDFs; the client application in the next step is what lets Stuut sign in.

3. Authorize Stuut’s client application

Still on the Security tab:
  1. Scroll to Authorized client applications and click Add.
Authorized client applications section with Add button
  1. Enter the following and click Save:
    • Client ID: 714f94ad79c8059eb934.app.sage.com
    • Description: any label, for example “Stuut”
    • Status: Active
Authorized client applications form with the Stuut Client ID and status Active

Authorized client applications form

  1. If Enforce IP address filters is turned on for your company, add the Stuut IP addresses your Stuut team gave you. Keep your existing entries in place.
  2. Click Save, then Done, to leave Company information. You’ll come back to this tab in step 6.

4. Create the Stuut role

  1. Go to Company → Admin and, under Users, roles, and groups, click Roles.
Sage Intacct Admin tab with Roles highlighted under Users, roles, and groups

Company → Admin → Roles

  1. Click Add, name the role stuut, give it a description such as “Read-only role for the Stuut integration”, and click Save.
Role form with name stuut and description Role for Stuut AI Agent
  1. In the role’s subscriptions, check these three modules:
    • Accounts Receivable
    • Order Entry
    • General Ledger
  2. For each module, click Permissions, grant the rights below, and click Save.
Stuut only ever reads, so List and View are all it needs. Without Customers the connection fails its health check; without Invoices, Adjustments, or AR Payment the invoice, credit memo, or payment sync fails.
If your company uses user-based rather than role-based security, there is no Roles page. Create the Web Services user in step 5 and grant the same module permissions directly on the user’s Subscriptions page instead.

5. Create a Web Services user for Stuut

  1. Go to Company → Admin and, under Users, roles, and groups, click Web Services users.
Sage Intacct Admin tab showing Web Services users under Users, roles, and groups

Company → Admin → Web Services users

  1. Click Add and fill in:
    • User ID: a dedicated ID such as stuut-user (lowercase, no spaces)
    • Account email address: the address of the person responsible for the integration. Sage Intacct emails this user’s password here.
    • Contact name: a contact for the user, for example “Stuut Integration”
    • User type: Business
    • Status: Active
  2. In the role table, assign the stuut role from step 4. Some Sage Intacct versions show this table on a Roles information tab.
  3. Click Save. You can ignore the warning about billable users.
Web Services user form with the stuut role assigned

Web Services user information

Keep the password email handy: you’ll sign in with this user in step 8. Don’t use an individual administrator’s everyday account.
  1. Go back to Company → Setup → Company → Edit and open the Security tab.
  2. Under Authorized client applications, open the Stuut entry.
  3. Enter the User ID from step 5 in Web Services user ID and click Save, then Done.
That completes the Sage Intacct side.

7. Open the Sage Intacct connector in Stuut

In Stuut, go to Settings → Connectors → All connectors, search for Sage Intacct, and click Add.

8. Sign in to Sage Intacct and allow access

Stuut shows Ready to connect Sage Intacct? Click Connect. A pop-up opens on Sage Intacct’s sign-in page, and the Stuut dialog shows Waiting for authorization until you finish. Stuut closes the pop-up after three minutes. If that happens, click the back arrow in the Stuut dialog and then Connect again.
  1. Enter your Company ID, the Web Services User ID from step 5, and that user’s password.
  2. Approve access for the Stuut client application when Sage Intacct asks.
Sage Intacct login window requesting Company ID, User ID, and Password

Sage Intacct sign-in

The pop-up closes on its own and Stuut shows Validating credentials while it confirms it can read your customers.

9. Add sender credentials for invoice PDFs (optional)

Stuut then shows Configure XML API Credentials (Optional) with two fields, Sender ID and Sender Password. These are Stuut’s own Web Services sender credentials, the ones behind the stuutMPP sender ID you authorized in step 2, and Stuut uses them to ask Sage Intacct to generate invoice PDFs. Your Stuut team provides these values. If you have them, enter them and click Save. If not, leave both fields empty and click Save: the connection still works, and your Stuut team adds the credentials later on the connection’s Settings tab. Stuut attaches invoice PDFs once they’re in place.

10. Done

The connection appears under Settings → Connectors → Connected apps with a Linked badge, and the first import starts right away. Open the connection: the Overview tab lists the Customers, Invoices, Credit Memos, Payments, and Ledger Accounts models with their sync status, which shows Done once the first import has finished.

Manage the connection

Open Settings → Connectors → Connected apps and select Sage Intacct.
  • Check health confirms Stuut can still read your customers and shows Sage Intacct’s error message if not.
  • Sync starts a sync now instead of waiting for the next hourly one.
  • Re-auth appears when the connection is unhealthy. It reopens the Sage Intacct sign-in so you can authorize Stuut again without deleting the connection.
  • Settings holds the Sender ID and Sender Password fields, and Delete integration, which disconnects Sage Intacct and deletes the customers, invoices, credit memos, and payments Stuut imported from it.

Troubleshooting

Your browser blocked the pop-up, so Stuut stays on Waiting for authorization. Allow pop-ups for your Stuut dashboard, click the back arrow, and click Connect again.
Check that the client ID in step 3 is exactly 714f94ad79c8059eb934.app.sage.com with status Active, that the Web Services user is added to that entry (step 6), and that you’re signing in with the Web Services user, not your own login.
The message is usually “Sage Intacct connection health check failed” or “Failed to connect the integration”. Stuut signed in but could not read customers. The stuut role is usually missing the Accounts Receivable → Customers permission, or the Web Services user doesn’t have the role. Fix the permissions in Sage Intacct, then click Connect again.
Sage Intacct stopped accepting Stuut’s access, most often because the Web Services user or the authorized client application was deactivated, or the user’s password changed. Confirm both are Active in Sage Intacct, then open the connection in Stuut and click Re-auth, followed by Check health. Data already synced is kept.
Stuut generates PDFs through Sage Intacct’s Web Services, which needs Stuut’s Sender ID and Sender Password on the connection’s Settings tab and the stuutMPP sender authorization from step 2 set to Active. Ask your Stuut team to check the sender credentials; once both are in place, PDFs are fetched for invoices on the next sync.
Credit memo line items are not imported today. Invoice line items are imported unless your account syncs invoices in query-only mode (see Current limits); ask your Stuut team if you’re not sure.
The first import brings in every open invoice but only closed invoices dated in the last 180 days, and payments and credit memos from the last 12 months. Contact your Stuut team if you need more history.

Security

  • Stuut connects to Sage Intacct over HTTPS.
  • Sage Intacct never shares the Web Services user’s password with Stuut. You sign in on Sage Intacct’s own page.
  • To revoke Stuut’s access at any time, set the Stuut authorized client application or the Web Services user to Inactive in Sage Intacct.
For security questions, contact security@stuut.co.