SedonaOffice General Ledger Out of Balance Audit
Please find included the stored procedure written by Emeka, which can be used to identify sources of out of balance issues in the SedonaOffice general ledger here..
This stored procedure should only be used after a review has been done of the GL and reporting to confirm the out of balance is a legitimate data concern, and not a misunderstanding of the reporting, or a reset_totals issue.
Important
We cannot assume that every data error identified by this stored procedure should be corrected. Some data errors have already been offset.
Use the gl accounting period variance subtotals to identify periods that may require correction. Net period totals together to identify the last time the overall variance was 0.00. For example, if January has a variance of 10.00 and February has a variance of -10.00, then the items from January and February offset each other, and should be left alone. Once you identify the first period where the variance is not offset, review the data errors within that period to see if any of them offset each other. Only variances with no offset should be addressed. Users may be able to address these through the front end by deleting the item that created the entry, or the items may require data repair.
