Each Invoice and Bank Transaction line item is assigned an Account Code and a Tax Code. The majority of the time, these codes should be consistent for a given supplier or customer. It happens to be best of us though – sometimes these records are assigned the wrong codes, or coding evolves over time.
We’ve crunched the numbers to find these potential mis-codings and you’ll see them presented in this insight, with helpful links directly to Xero & QBO allowing you to amend these where needed.
- Selecting the date filters
- Narrowing The Scope
- Setting Exclusions
- Understanding the Colour-Coding
Xero provides a dedicated mechanism for re-coding, and their support documentation on this is here.
The Multi-Coded Contacts insight allows you to specify two different date filters:
Active During: This is the period where you want to find contacts to assess. Dext Precision will find and evaluate contacts that have been active (i.e. they have transactions) during this time period. For example, this could be your reporting period of the previous month.
Check Transactions Since: Once Dext Precision finds the active contacts to evaluate, this date refers to how far back in time Dext precision should look into each Contact’s transaction history to compare account and tax codes and surface any inconsistencies. For example, if you know that you changed your accounts structure at the start of the year, it doesn’t make sense to evaluate transaction history before the change, so set this date to be the 1st of January (or whenever you made the change).
The Multi-Coded Contacts insight allows you to get really targeted with the data cleanup process, and quickly filter out any suggestions that don’t make sense for your situation.
Revenue | Expense | All: Restrict the suggestions list to only transactions relating to Revenue OR Expenses.
Account | Tax | All: Restrict the suggestions list to only transactions Dext Precision has identified with Account Code anomalies, OR Tax Code anomalies.
Typically, transactions with a single contact will only have one associated account code, with a small number of exceptions. However, in some cases, a contact will always have multiple account codes against it, such as a sale to a contact that pays shipping as a separate transaction. Exclusions allow you to specify combinations of account codes that you feel should not be detected as errors for a given client.
Contacts that have the combination of account or tax codes included in the Exclusion list will no longer appear as detected Multi-Coded contacts. If a Contact has multiple codes on other transactions they will appear in the multi-coded contacts view, but only the transactions relating to combinations of codes outside the exclusion list will be displayed
Using the ‘Exclusions’ button at the top of the multi-coded contacts screen, you will be shown a list of current excluded account or tax code combinations.
You can use this list to add, edit or remove a tax or account code combination from the exclusions list.
To add a combination to the exclusions list, click the ‘add’ button under the account or tax code category. From here you can search for and select the combination of codes you would like to exclude. You must select two or more codes to exclude. This combination of codes will apply as an exclusion across all contacts for that client.
Combinations of account or tax codes can be added or removed from the exclusion list at any time from the Multi-Coded contacts tool.
Exclusions only apply at the Client level – any exclusions set for a client will not apply to other clients in the Precision team.
Dext Precision adds colour to the transaction rows to provide a clear indication as to which transactions fall into the “Active During” period and which ones are historical:
If there is good reason for the different coding, then you can dismiss the multi-coded alert and it will not show again. Any dismissed alerts can be viewed by selecting dismissed from the filter at the top of the screen, where you can then review and undo any accidental dismissals. Dismissed items do not contribute to the Health Score.
This dismissal applies to a few levels below the contact, taking into account both direction (Payable/Receivable) and whether they are Tax Code or Account Code differences.
For example, you can dismiss an alert for a contact with differences in receivable account codes, and we won’t raise any more alerts for additional receivable account codes placed against that contact, but you will still get an alert for that client if we detect multiple payable account code differences, or multiple receivable tax codes.