Loading page
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
All-in-one HR platform · v2.0
14-day free trial · No credit cardhello@HrMagix.com
Recording when a change takes effect rather than only that it happened, so a past period can be read as it stood at the time. A salary revision, a policy change and a reporting-line move should all carry a date the change applies from.
Not the same as an edit history. Effective dating changes what the system calculates for a period; an audit log only records who typed what.
Effective dating comes up every time HR records a change that does not start today. A promotion approved on 20 May but applying from 1 May, a transfer scheduled for next month, or a new leave policy from 1 January are all entered once with their start date and left for the system to apply.
Example: a salary change is entered on 10 June with an effective date of 1 April. When June payroll runs, the system knows April and May were paid on the old figure and calculates arrears, while a report run for April still shows the April salary.
The mistake teams make is overwriting the current value and adding a note. That loses the history needed for arrears, back-dated PF corrections and audits, and it makes headcount or cost reports for a past month change each time they are rerun. Future-dated entries also need a check that they actually took effect.
Recording when a change takes effect, not just that it happened, so a past period can be read as it stood at the time.
Salary revisions, policy changes and reporting-line moves should all carry the date they apply from.
No. Effective dating changes what the system calculates for a period; an audit log only records who typed what.
It lets payroll compute each period under the terms in force then, for example when an increment is backdated and arrears are due.
A transfer becomes a dated change on the existing record, which keeps continuous service intact.
Yes. That is its purpose: reading a past period as it stood at the time.
The system only knows the current value, so past periods can't be reconstructed or recomputed correctly.
No. It records when changes apply; the history of who made edits is a separate audit record.
14-day free trial · Full access to all 12 modules · Zero implementation fee · Cancel anytime