QUESTION: We are trying to understand the overnight update process in relation to GL accounts. Specifically, the sub-ledger balancing to the Control accounts in the GL.
We are wondering if there is a tool to know in advance when a control account and subledger will not balance before they discover it at the end of the month. A sort of exception list that would print or raise a flag.
Are you able to share some documentation in regards to the process and explain how to track if these updates are “out of balance” on any given overnight process.
RESPONSE: The Quality Assurance routine that is included with overnight processes currently deals with rounding issues, which may occur during tasks like AR write-offs, and has little impact with balancing control GL accounts and corresponding reports.
Currently there aren’t any processes available to automatically flag for imbalances between transactions and related Control GL Accounts.
This issue is in review by the Architecture and Design group for future consideration.