Compliance requirements should block automatic approval for incentives, matching, etc.
Current platform configuration allows for Compliance and auto-approval to be enabled in tandem. This presents contradictory messaging to end users.
If compliance is not met by an NPO, it would be helpful to have requests (matching, incentives, etc) be put 'on hold' or denied via automation. As it stands, the system says they cannot be approved but then approves without pause.
-
Liz Rush-Smyth
- Sep 11 2024
- Reviewed: Voting Open
| Client Name | Medtronic |
| Employee Name | Mandy Iverson |
Related ideas
There appears to be some debate re: how this component should function. As it stands now, messaging (at the very least) is contradictory. Are auto-approved non-compliant rewards actually approved, or do they go into holding? Language around compliance in general would have the end user and admin believe compliance is mandatory, however there are circumstances where one can override. I am proposing an overhaul to both messaging and function.