Limitations for Back dated transactions

Summary:

Is there a way to limit how far in the past an assignment change transaction can occur?

We need to limit HR users from back dating a transaction more then 30 days. We've looked through the documentation and on Customer connect but have not found any configuration.

Content (required):

Our issue is that local Hospital HR make changes to assignment records back dated, sometimes many months. An example is changing an employee's assignment from Full time to Part time, but it's back dated into 2022. If this type of change is made to the employee assignment, there's a impact to payroll, benefits, PTO accruals, etc. Even allowing changes back to the beginning of the current year causes downstream impacts.