How to use something other than supervisory hierarchy for journal approval workflow

Summary:

We are looking for another method to use in the journal entry workflow other than the supervisory hierarchy.

Content (please ensure you mask any confidential information):

We are looking to use some other method for routing journal entries for approval other than using the supervisory hierarchy. Our thoughts would be to have some sort of user defined (and maintained) table / hierarchy / tree that would include the team members that would submit a journal entry, along with the people who should approve their specific entries. Each area of the business has its own group of submitters / approvers. We thought we could do this by creating a new position tree and pointing the FinGlJournalApproval workflow rule to this new hierarchy, but we