Glossary
What is effective dating?
Effective dating means storing each change to a record with the date it takes effect, so a system can hold past, current and future values.
Effective dating is a way of storing records in which each change has a date from which it applies. HR systems such as UKG and Workday use it widely: a promotion can be entered today but take effect next month, and a correction can be back-dated. The record therefore has a history and sometimes a future, not one current value.
How does it work?
| Change | Entered | Effective |
|---|---|---|
| New hire | 3 March | 1 April |
| Transfer to Sales | 10 May | 1 May (back-dated) |
| Termination | 20 June | 30 June |
A safe pattern is to store the effective date with each change in the target system or in the integration layer, and to schedule actions such as account creation or deactivation for that date.
Where it shows up in integrations
- Future hires An integration must decide whether to create the LMS account now or on the start date.
- Terminations Access should end on the effective date, not when the change was typed in.
- Back-dated transfers Group memberships and reporting may need correcting retroactively.
- Reporting Point-in-time reports need the value that was effective on that date.
Common pitfalls
- Reading only “current” values and missing future-dated changes until they suddenly apply.
- Using the change’s entry date instead of its effective date.
- Overwriting history in the target system, which breaks audits.
- Not re-running sync logic when an effective date arrives.