Votes

10

Improve Trasaction Optional Field Validation

by: Carol L. | over a year ago | General Enhancements
Cast your vote or comment ...
return to idea list

Allow users to create an optional field that is mandatory for a specific GL account - but not all GL accounts. This needs to carry through the subledgers.

For example, my client has specific GL accounts that requires an Optional Field to be filled in in AP, but not for all GL Accounts. If the O.F. is set as required in either the GL or AP Setup, then ALL transaction detail lines must be populated with that optional field.

If the Optional Field is set as required at the GL account screen, it will require it for Journal Entries. However, the AP does not check for this -- and neither does the GL, when the AP subledger batch is being posted.

As it stands, it is up to the AP data entry folks to make sure that they remember to populate the O.F. for the accounts in question. In a large accounting department, this is not realistic and mistakes can and will be made.

by: Carol L. | over a year ago | General Enhancements

Comments