Skip to main content

Why has my Sage 200c Standard expense posting failed?

Learn how to troubleshoot and retry your failed expense posting to Sage 200c Standard.

J
Written by Jack
Updated today

When posting your expenses to Sage 200c Standard 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 have 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 200c Standard, get in touch with our Support team.

Integration connection status

Accounting 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 Account Name > Admin > Integrations > Accounting.

  2. Click the three dots icon and select Reconnect from the drop-down.

  3. Once you've reconnected Sage 200c Standard, you can then select Retry Failed Records on the failed posting.

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 Standard

Sage 200c Standard has been unable to find the Supplier code provided for this expense in Sage.

To check the Supplier code used (e.g. the User reference or a static field), refer to your Sage 200c Standard 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 Standard.

Nominal account code, cost centre code or department code not recognised in Sage 200c Standard

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 Standard 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 Sage 200c Standard 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 Standard 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), you'll need to edit the completed expense(s). If you need to adjust your category or department reference, you can do so by heading to your Admin area and selecting Categories (in the Account Setup section) or Departments (in the User Management section).

Incorrect tax rate reference

Sage 200c Standard 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 Standard before retrying the failed posting.

Incorrect transaction analysis code

To utilise the Transaction Analysis Code field mapping option, ensure that your Transaction 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 Sage 200c Standard Bank Account Code, e.g. usually a static field or a User custom field, needs to match exactly as it is in Sage 200c Standard.

Check your Sage 200c Standard integration mapping 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?