Leila Fielding
Why I picked it
It stops changes to absences after payroll has run, which saves painful reconciliation.
Where it helps
Once an absence has been paid, it's locked, so accruals and payroll stay in step.
From Oracle's note
One from 25C that's still flying under the radar for some Oracle HCM clients. Retroactive absence edits after payroll closes create reconciliation work that's genuinely painful, off accruals, inconsistent payroll integrations, reprocessing requests. This stops it at the configuration level rather than relying on process reminders or good intentions.
- After a defined number of calendar days
- Once the absence has been paid
Sits at absence type level, so different leave types can have different rules. Redwood pages only. If this isn't configured on your environment yet, it's a quick win worth picking up.
Last reviewed November 2026