When posting your expenses to Sage 50 via Integration, ExpenseIn will always prompt you to review the posting status in the Export History section of the Finance area (on the Postings tab). You'll also receive an email if one or more of your expenses has failed to post.
The Postings tab 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.
Sage 50 Integration Connector - Active Sage Session: Username is already in use
Your Sage login credentials can only be used for one active session. Consequently, ensure you are 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 selecting 'Post Expenses' using the Sage 50 integration connector.
Sage 50 Integration Connector - Incorrect User Credentials: Invalid or incorrect username or password
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 selecting 'Post Expenses' using the Sage 50 Integration Connector.
Sage 50 Integration Connector - Incorrect Company Name
ExpenseIn requires your Sage 50 company name to ensure your expenses are posted to the correct company. Your Sage 50 company name is stored in your Sage 50 Integration Mapping area using a static field.
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 Postings tab via Export History and select Retry Failed Records before selecting Post Expenses using the Sage 50 integration connector.
Incorrect Supplier Reference
ExpenseIn has been unable to find the Supplier reference provided for this expense in Sage 50.
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.
Incorrect Bank Account Reference
ExpenseIn has been unable to find the Bank Account Reference provided for this expense in Sage 50.
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.
Category Reference not recognised in Sage 50
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), follow our Help Article for editing completed expenses. If you need to adjust your category reference, you can do so by heading to your Admin area and selecting Categories.
Incorrect Tax Rate Reference
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.
Cost Code or Project not supplied
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.
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.
Invalid Open Mode
To ensure ExpenseIn is operational with new releases of Sage, you'll need to reinstall the latest version of the Sage 50 Connector.