Collections Dispute Approval: deriving the approver from a customer account attribute (26C)

Summary:

We would like to confirm whether the approver for a Collections dispute can be
derived dynamically from an attribute held on the customer account, using standard
functionality or supported configuration, and if not, what approach Oracle
recommends.

Content (please ensure you mask any confidential information):

- Disputes are raised from Collections > Transactions.
- Dispute approval currently follows an amount-based hierarchy: single-level approval below a defined threshold, two-level approval above it.

What we have checked

We reviewed an earlier discussion on routing dispute approvals to the invoice creator, where it was confirmed that the creator attribute is not present in the