Skip to main content
All CollectionsIntegrations with Accounting SoftwaresSage 100 native integration
2. Connect Spendesk to Sage 100 cloud (SPC) with integrator
2. Connect Spendesk to Sage 100 cloud (SPC) with integrator
Updated this week

⚠️ This login process applies if your Sage 100 solution is hosted in the cloud. If you host Sage 100 on your own servers, please refer to this dedicated article. In any case, it is essential to be accompanied by a Sage 100 integrator to complete these steps.

To connect Spendesk to Sage 100, start by logging into Spendesk and navigating to the tab: Settings > Accounting > Accounting Integration. From there, click the "Change Integration" button and select the "Sage 100 (Native Integration)" option from the dropdown menu.

Read through the different screens that appear and follow the instructions until you reach a form. Connecting Spendesk to Sage 100 requires filling out a form where you are asked for various elements. These elements are used to generate a specific, unique file containing the information necessary to establish the connection between the two tools. Below is a list of these elements and guidance on how to obtain them:

  1. Name of the Sage 100 folder/company: This is simply the company name as it is registered in Sage 100. You can find your company names in Administration > Companies.

  2. Sage 100 FR installation: Choose the Azure (Sage Partner Cloud) option. If you are using the on-premise version, please refer to this article instead of the one you are currently reading.

  3. SQL Azure instance (server) name: Contact your integrator to obtain this information. The format is typically “XXXX.database.windows.net”.
    ⚠️ When filling in the field in the form, make sure to remove the “.database.windows.net”.

  4. SQL Azure database name: Contact your integrator to obtain this information.

  5. Sage 100 user: Contact your integrator to obtain a dedicated user. Alternatively, you can find the information in System Configuration and Sharing.

  6. Sage 100 SQL Server user: Contact your Sage 100 integrator.

  7. Sage 100 SQL Server password: Contact your Sage 100 integrator.

Once you have entered these details, click “Connect.”

You can then choose whether to receive the file to install on your server via email or directly in your browser.

Retrieve the file through one of the available options and open the Sage 100 remote desktop.

Drag and drop the file onto the remote desktop, and double-click to unzip it.

Select the SetupSage100FRservice that corresponds to your version of Sage and double-click it.

Click Yes when asked, "Do you want to allow this app to make changes to your device?"

Then click OK to confirm the language choice.

Keep the “Standard” option checked and click Next.

Click Next again when prompted to select the location of the settings.json file.

Finally, click Install.

If you are performing a new installation because the first attempt failed, you may see a warning message that “Sage100FRService” already exists. Leave the “Automatically close the applications” option selected before clicking Next.

After the installation, you might see a message indicating that a connection already exists. Click “No” if you are attempting a new connection after a failed attempt, but click “Yes” if you are performing multiple installations on the same server for different subsidiaries.

To verify the connection is active, click on the magnifying glass in the lower-left corner and search for “Services” to open the corresponding menu.

Find the service you just installed, namely Sage100FR Service, and ensure its status is “Running.” If it is not, right-click and force it to start.

Once everything is set up, return to Spendesk and click the "Refresh Server Status" button.

Your status will then change to "Active," indicating that you are connected!

You can click "Refresh Accounting Settings" at the bottom of the page to start the synchronization.

After a few minutes, go to the various setup tabs to configure the integration.

More information on this topic can be found in the following article.

Did this answer your question?