Configure Your Sage Intacct Connection in the Roghnu Data Portal

This guide walks you through setting up your Sage Intacct sender ID for the Sage Intacct to Data Vault integration using the Roghnu Data Portal. You can manage your Web Services credentials in one place: add, edit, remove, and test them as needed. For questions or issues, contact support@roghnu.com.

Step 1: Confirm and locate your Sender ID and password

1. Confirm you have an Intacct Web Services Developer License.
   • If you are unsure, check your latest invoice from Sage or your VAR for that SKU, or ask your account representative.
   • If you do not have the sender password, open a ticket with your VAR or Sage to request a reset. A password reset affects every integration that uses that sender ID, not only the Data Portal.

Step 2: Log in to the Data Portal

1. Open your browser and go to https://apps.roghnu.com.
2. Sign in with your Roghnu Data Portal credentials.

Who can update these credentials?

You need either administrator access in the Data Portal or access to the Credentials Setup app on your user role. If you do not see Credentials Setup in the menu, ask your company administrator to make the update. Otherwise, reach out to Roghnu Support for assistance.

Step 3: Open Credentials Setup and choose Sage Intacct

1. In the left menu, open Credentials Setup.
2. On the integration cards screen, select the app shown as Sage Intacct (the label may correspond to your Intacct / Data Vault product).
3. Choose Sage Intacct as the integration. You should see the Sage Intacct configurations table.

Step 4: Add or edit a configuration

First time or new environment

1. Click Add configuration.
2. Enter the following (values come from Sage Intacct):
   • Sender ID — In Sage Intacct: Company → Setup tab → Company → Security tab → Web Services authorizations.
   • Sender password — The password issued for your Web Services developer/sender registration. If you do not have it, work with your VAR or Sage (same caution as in Step 1 if you reset it).
   • Company ID — In Sage Intacct: Company → Setup tab → Company → General Information → Company information.
   • Entity ID — Optional. Use only if your Intacct company uses multi-entity and you have a specific entity to target.
3. Save the dialog.

Change existing credentials

1. In the table, find the configuration row you want to change.
2. Click Edit, update the fields, and save.
3. Save your changes.

Multiple Sage Intacct environments (optional)

Some companies are entitled to more than one Sage Intacct environment in the Data Portal. If your subscription includes that option, you will see Add configuration available after the first environment is saved; use it for each additional environment. If you only need one environment, you will maintain a single row in the table.

If you believe you should have multiple environments but cannot add a second configuration, contact support@roghnu.com.

Step 5: Add Web Services user credentials

Roghnu uses separate Web Services user credentials (in addition to the sender ID) to execute API work on your behalf.

1. In Credentials Setup > Sage Intacct configurations, find the configuration row you just added or updated.
2. Open that row’s Relationships controls.
3. Click + New Web Service to create a Web Services user entry.
4. Enter the following fields:
   • Integration: Intacct
   • User ID: the Sage Intacct Web Services user login
   • User Password: the password for that Web Services user
   • Active: enabled/on
5. Select Create.

Step 6: Test the Sage Intacct connection

1. In the same configuration row, click Test.
2. Wait for the test result.
3. Confirm the success message: The Intacct API connection was successful.
4. If the test fails, use the error guidance below, correct the values, save if needed, and test again.

Common errors and what to do

• Unable to connect (or Unable to connect to server)
  • Credentials may be wrong, the Web Services user may be inactive/unauthorized, entity access may be missing, or there may be a temporary network/service issue.
  • Verify Sender ID, Sender Password, Company ID, optional Entity ID, and Intacct Web Services user credentials; confirm the Web Services user is active and has API permissions in Sage Intacct; then test again.
  • If you are unable to troubleshoot the connection, reach out to Roghnu Support for more help.

Tips

• Double-check Company ID and Sender ID; small mistakes cause auth failures.
• Protect sender and Web Services passwords like any production credential.
• After any change, run Test on the affected configuration.

Conclusion

You can now maintain Sage Intacct sender and related credentials in Credentials Setup. If anything fails or you are unsure which environment row to use, contact support@roghnu.com.