When posting your expenses to Sage 50 via the integration, ExpenseIn will always prompt you to review the posting status in the Posting History page under the Imports and Exports section of the Finance area.

Note: You'll also receive an email if one or more of your expenses has failed to post.

The Posting History is particularly important for troubleshooting any failed posting attempts. By clicking on your failed posting, you'll be able to expand your Purchase Invoice or Bank Payment and subsequently view the reason for any posting failures.

Throughout the remainder of this Help Article, you'll find some common troubleshooting steps for resolving any full or partial failed postings. If you continue to have difficulty successfully posting your expenses to Sage 50, get in touch with our Support team.

Your Sage login credentials can only be used for one active session. Consequently, ensure you're logged out of Sage before clicking 'Post Expenses' in the Sage 50 integration connector.

Once you've logged out of Sage 50, you can return to ExpenseIn and select Retry Failed Records before clicking 'Post Expenses' in the Sage 50 integration connector.

When first setting up the Sage 50 integration connector, you're prompted to enter your Sage 50 user credentials - this facilitates the posting of expenses. To correct your Sage 50 integration connector login credentials, open the Sage 50 connector, select the 'Options' heading, then click 'Configure'.

Once updated, you can return to ExpenseIn and select Retry Failed Records before clicking 'Post Expenses' in the Sage 50 integration connector.

ExpenseIn requires your Sage 50 Company name to be stored in your Sage 50 Integration Mapping area using a static field, this is to ensure your expenses are posted to the correct company in Sage.

Ensure the value in your static field exactly matches your Company name in Sage 50. We recommend using the company name displayed on the company selection window, shown when you first open the Sage application.

Once you've checked the static field value, return to the Posting History page in the Imports and Exports section of the Finance area, and select Retry Failed Records before clicking 'Post Expenses' in the Sage 50 integration connector.

Sage 50 has been unable to find the Supplier reference provided for this expense in Sage.

To check the Supplier reference used (E.g. User reference or static field), refer to your Sage 50 Integration mapping settings. You'll need to make sure that the User reference/static field used is verbatim to the Supplier reference in Sage 50 before retrying the failed posting.

Sage 50 has been unable to find the Bank account reference provided for this expense in Sage.

To check the Bank account reference used (usually a static field), refer to your Sage 50 Integration mapping settings. You'll need to make sure that the value mapped to the Bank account reference field is verbatim to the Bank account reference in Sage before retrying the failed posting.

Your Category references will need to be verbatim to the nominal codes you have set up in Sage 50. In this example, you'll need to check that the Category reference used for the failed expense is exactly the same as the Sage 50 nominal code.

If you need to edit the expense (to select another category), you'll need to edit the completed expense(s). If you need to adjust your category reference, you can do so by heading to your Admin area and selecting Categories in the Account Setup section.

Sage 50 will refer to Tax Rates with different names (usually T codes, E.g. T1). Check that your Tax Rate references are verbatim to what your tax/VAT rates are named in Sage 50 before retrying the failed posting.

To post expenses to Sage 50 with either a Project or a Cost Code assigned, you'll need to ensure that both fields are present on the expense and mapped accordingly.

Check your Sage 50 Integration Mapping settings and ensure that both Projects and Cost Codes have been mapped against ExpenseIn fields. You may wish to create and use custom fields to capture your Cost Codes.

To ensure ExpenseIn is operational with new releases of Sage, you'll need to reinstall the latest version of the Sage 50 Connector.