All Collections
Why has my Sage200c Professional expense posting failed?
Why has my Sage200c Professional expense posting failed?

Learn how to troubleshoot and retry your failed expense posting to Sage200c Professional.

Written by Jack
Updated over a week ago

When posting your expenses to Sage 200c Professional 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 have 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 to follow. If you continue to have difficulty successfully posting your expenses to Sage200c Professional, get in touch with our Support Team.

Integration Connection Status

Accountancy package integration often requires periodic re-authentication - we'd recommend initially checking your integration connection status.

If the status is showing as Disconnected:

  1. Navigate to Admin > Integration.

  2. Use the Actions drop-down and select Reconnect.

  3. Once you've reconnected Sage 200c Professional, you can then select Retry Failed Records.

If you've completed the steps above but still get the same error, get in touch with our Support Team.

Supplier Not Found in Sage 200c Professional

ExpenseIn has been unable to find the Supplier code provided for this expense in Sage200c Professional.

To check the supplier code used (e.g. the User reference or a static field), refer to your Sage 200c Professional Integration mapping settings. You'll need to make sure that the User reference/static field used is verbatim to the Supplier code in Sage 200c Professional.

Nominal Account Code, Cost Centre Code or Department Code Not Recognised in Sage 200c Professional

You'll see the above posting error if there's an issue with either the expense's Nominal Account Code, the Cost Centre Code or the Department code. As shown in the screenshot above, your posting error message will display which code is incorrect.

  1. Your Sage 200c Professional setup will have a corresponding Cost-Centre and Department Code for each Nominal Code. Ensure that the expense values used (i.e. Nominal, Cost Centre and Department codes) align with an existing combination within your Sage200c Professional environment.

  2. Check that the expense values used for the Nominal Code, Cost Centre Code and Department Code are exactly the same as the codes stored in your Sage 200c Professional environment.

  3. Confirm your Integration Mapping Settings are correctly using the appropriate Nominal Code, Cost-Centre Code and Department Code.

If you need to edit the expense (to select another category, department or another field), follow our Help Article for editing completed expenses. If you need to adjust your category or department reference, you can do so by heading to your Admin area and selecting Categories or Departments.

Incorrect Tax Rate Reference

Sage 200c Professional will refer to tax rates with different names/codes - check that your Tax Rate References are verbatim to what your tax/VAT rates are called in Sage 200c Professional.

Incorrect Transaction Analysis Code

To utilise the Transaction Analysis Code field mapping option, ensure that your Transactions Analysis codes are initially enabled in Sage before posting. Once you've confirmed the Transaction Analysis Code(s) has been enabled, you can retry your failed posting.

Incorrect Bank Account Code

The ExpenseIn value used to map against your Sage200c Professional Bank Account Code (e.g. usually a static field or a User Custom Field) needs to be typed exactly the same as it is in Sage200c Professional.

Check your Sage200c Professional Integration Mapping settings to see which ExpenseIn field is being used to map against your Bank Account Code field, and then ensure the ExpenseIn field is correctly storing the required Bank Account Code.

Related Articles

Did this answer your question?