Spendesk

You are about to connect your Spendesk account to Sage 100. Before taking the plunge, take a moment to familiarise yourself with the features supported by this integration, as well as those that are not yet included.

Integrating Spendesk and Sage 100 allows you to benefit from exclusive features designed to streamline the day-to-day accounting management of your expenses, including:

Importing into Spendesk: your bank accounts, VAT accounts, expense accounts, suppliers, analytical fields, and journals.

Exporting in one click to Sage 100: your purchase ledger entries along with their supporting documents for card payments, invoices, expense claims, credit notes, and reimbursements on your company cards.

Automatic export of bank ledger entries: for all transactions already prepared and sent to the purchase ledger.

Exporting analytical axes: applied to expense accounts and their allocation.

Detailed tracking of errors: occurring during exports, specifically for purchase ledger entries and bank ledger entries.

- Importing into Spendesk: your bank accounts, VAT accounts, expense accounts, suppliers, analytical fields, and journals.
- Exporting in one click to Sage 100: your purchase ledger entries along with their supporting documents for card payments, invoices, expense claims, credit notes, and reimbursements on your company cards.
- Automatic export of bank ledger entries: for all transactions already prepared and sent to the purchase ledger.
- Exporting analytical axes: applied to expense accounts and their allocation.
- Detailed tracking of errors: occurring during exports, specifically for purchase ledger entries and bank ledger entries.

However, we would like to draw your attention to the fact that this integration does not include:

Management of start and end dates for prepaid expenses, which we are currently working on.

Creation of data in Sage 100 from Spendesk (such as suppliers or analytical data).

Export of analytical axes applied to accounts other than expense accounts, such as supplier accounts and VAT accounts.

Restoration of your export settings via file configuration, which must be re-entered manually if you decide to revert to the previous setup.

Support for analytical plans with open-ended values; the integration only supports fixed-value analytical plans.

- Management of start and end dates for prepaid expenses, which we are currently working on.
- Creation of data in Sage 100 from Spendesk (such as suppliers or analytical data).
- Export of analytical axes applied to accounts other than expense accounts, such as supplier accounts and VAT accounts.
- Restoration of your export settings via file configuration, which must be re-entered manually if you decide to revert to the previous setup.
- Support for analytical plans with open-ended values; the integration only supports fixed-value analytical plans.

This integration involves two distinct phases:

Connecting Sage 100 to Spendesk: Spendesk provides only limited assistance for this stage, relying on the articles available in our help centre. Most of the required steps are performed directly on Sage 100 servers, so assistance from Sage 100 support is essential. Please note that the installation of Sage 100 requires running a <code>.exe</code> file on your servers, as Sage 100 does not offer a public API. If your internal policies prohibit the installation of this <code>.exe</code> file, it will be impossible to proceed with the installation.

Configuring Spendesk once Sage 100 is connected: Again, our help centre is your primary resource, but our account managers are also available to assist if you are unable to find the necessary information.

1. Connecting Sage 100 to Spendesk: Spendesk provides only limited assistance for this stage, relying on the articles available in our help centre. Most of the required steps are performed directly on Sage 100 servers, so assistance from Sage 100 support is essential. Please note that the installation of Sage 100 requires running a <code>.exe</code> file on your servers, as Sage 100 does not offer a public API. If your internal policies prohibit the installation of this <code>.exe</code> file, it will be impossible to proceed with the installation.
2. Configuring Spendesk once Sage 100 is connected: Again, our help centre is your primary resource, but our account managers are also available to assist if you are unable to find the necessary information.