Accounts Receivable Grid Does Not Match Accounts Receivable on Balance Sheet

Overview

If there is a discrepancy between an Anterra Accounts Receivable (A/R) grid and A/R on an Anterra balance sheet, we recommend taking the following steps to attempt to resolve the issue.

Check Unmapped Accounts

Checking for any unmapped accounts in the GL Account Mapping page may highlight accounts that need to be added to your chart of accounts. Unmapped accounts can directly impact financial statements, as Anterra would not be able to classify which groups the account(s) belongs to.

Check Financial Statement Row Mappings

If all accounts are correctly mapped in your chart of accounts, the next step would be to ensure correct financial statement row mapping. If the balance sheet is mapped to bottom-level accounts, ensure that all of the relevant accounts are included in the row mapping. This can be done on the Anterra Statement Builder page.

Reconcile the A/R and GL Modules in Sage

Because the A/R grids use Sage’s A/R module data and financial statements use Sage’s GL module data, a difference between the two could most likely indicate a difference in Sage itself. This could happen when entries are made in a single module but not posted to the other (this could also apply to other modules as well, such as Billing and SM). In addition, it is important to ensure that entries in Sage for A/R are attached to a customer, as there should be a customer in order to show up in the A/R grids in Anterra.

It is recommended to check that those modules do match in Sage. This link takes you directly to Sage’s knowledgebase for steps to perform this reconciliation: Link to Sage 300 CRE knowledgebase article for reconciling Accounts Receivable to General Ledger. Once reconciled, any correcting entries should be reflected during the next sync from Sage to Anterra.

You can also run an A/R aging report in Sage and compare to an aging report in Anterra (using the same end dates), which should match – assuming the criteria of having all customers attached has been met and properly posted in the A/R module.