When posting your expenses to AccountsIQ via either the AccountsIQ (V1) or AccountsIQ (V2) integrations, 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 Batch 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 AccountsIQ, get in touch with our Support team.

Accounting package integration often requires periodic re-authentication, or if you've up the credentials used to connect the integration may no longer be valid. If you receive an unexpected error, we'd recommend first checking your integration connection status.

If you've completed the steps above and are still receiving the same error, get in touch with our Support team.

AccountsIQ has been unable to find the supplier code provided for this expense in your AccountsIQ account.

To check the supplier code used (e.g., the user reference or a static field), refer to your AccountsIQ (V1) or AccountsIQ (V2) integration mapping settings. You'll need to ensure that the user reference or static field entered matches the supplier code in AccountsIQ verbatim. This field is case-sensitive, so if the supplier code is in lowercase, you'll receive the error shown below.

Your Category references must match the GL Account Codes you have set up in AccountsIQ verbatim. In this example, you'll need to check that the Category reference used for the failed expense is exactly the same as the AccountsIQ GL Account Code.

If you need to edit the expense (e.g., 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).

Your Tax Rate references must match the Tax Codes you have set up in AccountsIQ verbatim. In this example, you'll need to check that the tax rate reference used for the failed expense is exactly the same as the AccountsIQ Tax Code before retrying the failed posting.

If you need to edit the expense (e.g., to select another tax rate), you'll need to edit the completed expense(s). If you need to adjust your tax rate reference, you can do so by heading to your Admin area and selecting Tax Rates (in the Rates section).

If you haven't mapped the Tax Code in your integration mapping, you will instead receive the 'Tax code was empty' error. To check this, refer to your AccountsIQ (V1) or AccountsIQ (V2) integration mapping settings.

If you're posting expenses or invoices to AccountsIQ as Bank Payments, the ExpenseIn values used to map against your AccountsIQ Bank Account GL Code (e.g., a Static Field or Custom Field) must match exactly as they appear in AccountsIQ.

Check your AccountsIQ (V1) or AccountsIQ (V2) integration mapping settings to see which ExpenseIn fields are being used to map against your Bank Account GL Code, and then ensure the ExpenseIn field is storing the required information correctly.

If you haven't mapped the Bank Account GL Code in your integration mapping, the error will display 'no bank found with code 'EMPTY'. Refer back to your integration mapping settings to ensure the field is mapped correctly.

AccountsIQ was unable to find the BI Code provided for the expense in your AccountsIQ account.

Check your AccountsIQ (V1) or AccountsIQ (V2) integration mapping settings to see which ExpenseIn field is being used to map to your BI Code. Then ensure that this ExpenseIn field is correctly storing the BI Code verbatim as it appears in AccountsIQ.