Challenge:

Growing portfolio diversity may lead to general ledger integration issues. For example, a new type of transaction or different business segment may cause account masking errors when posting journal entries.

Solution:

After known general ledger masks are set up, create a mask for all unused general ledger codes equal to the index code. For instance, if general ledger index 4055 is not being masked, set the masking to “4055.” This way, new accosting activity will not produce journal posting error messages during the nightly job stream. Rather, balanced “masked” entries will be created in the file to be uploaded to the GL. The GL will reject the entry to due an invalid GL account “4055,” which easily identifies the activity to be masked.

 
Written by

Tamarack

Tamarack Consulting, Inc.

« Back

Contact us

  • Should be Empty: