Our organization utilizes two transaction codes in the Admin section of Financial Edge (database version) (located in table entries).  One is set up to track grant activity, the other is set up to track grant match activity.  We would love to be able to implement an automated control so that certain grant codes cannot be used with certain match codes (i.e., grant #25 should not also be used together with match #25 - it is either a direct grant expense or a match expense).  I view this as something similar to defining invalid segments, but for transaction codes.

Or, like you are able to define account restrictions for project codes, the ability to define account restrictions for transaction codes.