G/L Chart Check Exceptions Explained

When I run the G/L Integrity option I get an Exception report, what does it mean and how do I fix it?

Solution

This Utility runs through and checks the basis of your General Ledger and provides a report that should not be ignored.

Autogen, AUTOGEN or autogen

These are Codes that do not exist in your system and the system has created the Autogen Codes so the missing side of the transaction can be recorded.  Please see   Auto Created or Autogen Accounts to repair them.

Error: Sub account of ID adds up the chart

All Transaction Account's add into Totaling Accounts. 
But in the example below, we can see that Sub Account 10-3340, is above Security and Unders and Overs. Mathematically this is not going to work.  Use the Move up button so that these two codes are above the Total Administration Expenses in the Chart or if necessary change the Sub Account.

Error: ID has no Sub Account of ID

All Transaction Accounts need a Sub Account to direct the transactions on where to add the contents to, if this is missing the transactions will not add anywhere.  This may be intentional, like the Variance Account or in the case of unused GL Accounts, but in most cases this is necessary. 

The Variance code will display as an exception until your chart is correct.

eg, Fix the first two Exceptions below and the G/L Integrity check will run without any errors.

Warning: Headers should not be a sub account of any other ID

This occurs when a Transaction General Ledger code is changed to a Header Code without deleting the Sub Account of of field first.

Open the GL Code

Change the Function to a Transaction Function

Delete the value in the Sub Account of Field 10-2300 in the above picture.

Change the Function back to the Header Function

Save.

After all changes, run the Financial Integrity check again.