Month End Reconciliations - Control Accounts are Out of Balance

Modified on Thu, 17 Nov, 2016 at 4:54 PM

If your subsidiary modules are out of balance with the GL control accounts, try these steps to troubleshoot the problem:

Check for Error or unposted batches
The easiest option is to untick the Show Posted & Deleted Batches checkbox to show only unposted entries. Don’t delete the error batch! Refer below for assistance in managing error batches to maintain your system integrity.
Check for Post-in-Progress batches
As above, untick the Show Posted & Deleted Batches checkbox to show only unposted entries. Select the batch and try posting again.
Check for GL journal entries
Use the GL Transaction History screen with source code GL-JE.

Managing Error Batches

Where the batch description starts with “Error Batch” make a note of the originating batch number. Scroll up to that batch entry and across to the column titled Number of Errors.

In the classic desktop, double click in that cell to open the GL Posting Journal Errors report, and in the web screens, select the print (pencil) icon to run the same report. The error message will guide you to the problem preventing successful processing.

Once you understand the problem, adjust your system settings or entry details in the Error Batch and post. Sage 300 manages the full and correct audit trail for you.

Typical issues:

Fiscal period is locked. Either unlock the period in Common Services to include the values in that prior period’s results, or change the posting date/period in the error batch.
Document number already exists: adjust the document number (e.g. add an ‘a’ to make a unique number).
Document is over-applied in AR Receipts: adjust the receipt to apply payment against different open documents.
GL account does not exist: create new corresponding GL account or change the entry within the batch to an existing account.