Blog Product

Why an employee record needs an effective date

6 min read

Every change to an employee record has two dates: the day it took effect and the day someone entered it. A last-modified stamp keeps only the second. Payroll, audit and almost every question asked about the past depend on the first. One invented promotion, entered three weeks late, shows what is lost when a record keeps only its current state.

Maintained by the TriblockHR Compliance Team. Updated 2 October 2026. This page describes how the employee record is structured; it states no statutory figure for any territory.

Two dates

A change to an employee’s record happens in the world before it happens in the system. A promotion is agreed in a meeting and takes effect on a date. A transfer starts on a Monday. Someone then sits down, sometimes the same day and sometimes weeks later, and enters it.

So every change carries two dates:

  • When it took effect: the date from which the new position, pay or status was true.
  • When it was entered: the date someone recorded it.

On a well-run day the two are close. On a busy one, or after a holiday, or when a manager forgets to send the paperwork, they can be weeks apart. A record that keeps only one of them will, sooner or later, give a wrong answer to a question about the past.

What a last-modified stamp answers

Many systems keep a last-modified stamp on each record: a date and, sometimes, a user. It answers a narrow question well. Who touched this record last, and when?

It cannot answer the questions payroll and audit actually ask:

  • What was this person’s job on 14 March?
  • What was their salary in the pay period that ended on 31 March?
  • Were they on probation when that leave was approved?

Each of those is a question about what was true on a day, and a last-modified stamp says nothing about that. It records the moment of editing, and the edit itself has replaced whatever was there before. The record now holds only its current state.

A promotion entered three weeks late

Take an invented employee, Dahlia Ferguson, a team lead in the claims department of a fictional insurer, Harbour Mutual. On 1 March she is promoted to claims supervisor, with a higher salary from that date. Her manager is on leave, and the change is entered on 22 March.

In a record that holds only its current state, the edit on 22 March overwrites her job and salary. Ask the record two different questions and it gives two different wrong answers.

Asked on 15 March, before the edit, “what is Dahlia’s salary?” returns her old salary. That was the system’s state on the day, and it was wrong: she had been a supervisor for two weeks.

Asked in June, after the edit, “what was Dahlia’s salary on 15 March?” returns her new salary, because that is the only value the record now holds. It has forgotten that the old salary ever existed, and it cannot say from when the new one applied.

The last-modified stamp shows 22 March. That date is real, but it is the wrong one for payroll. Her March pay depends on 1 March. A record that holds the change as an event dated 1 March, with the entry made on 22 March, can answer both questions correctly: the new salary applies from 1 March, and it was recorded three weeks later.

What a late entry then means for a pay run already processed is a separate question, covered in recalculating a past period after a correction.

The events that need dating

Salary is the obvious case. It is not the only one. Each of these changes what is true about a person from a particular day, and each is a question someone will ask about later:

  • Promotion: job, grade and pay from a date.
  • Transfer: department, location and manager from a date.
  • Probation: its start, any extension and its end.
  • Suspension: from and to.
  • Termination: the last day, and the offboarding that follows.
  • Rehire: a new start, without erasing the earlier employment.
  • Pay frequency: a move from weekly to monthly changes how every later run is cut.

A pay-frequency change shows why bulk edits need dates too. Moving a whole department from fortnightly to monthly is one action applied to many records, and each of those records needs the date the change takes effect, as well as the day the bulk update ran.

Every one of these, held as a dated event, becomes something the record can be asked about. Held as an overwrite, it becomes something the record has forgotten.

Two halves of one history

A record that answers questions about the past needs both dates, and in TriblockHR they are held in two places that work together.

The effective-dated employment history is the “took effect” half. Promotions, transfers, probation, suspension, termination, offboarding and rehire are held by effective date. A change is a dated event on the record. Ask what was true on any day, and the history answers.

The audit history is the “entered” half. About forty per-entity history tables hold the value before, the value after and the person who made each change, with an audit feed and downloadable reports of user activity. Ask who changed Dahlia’s salary and when it was keyed, and the audit history answers.

Together they cover what a last-modified stamp cannot. The effective date says when something was true. The audit entry says when it was recorded and by whom. A three-week gap between them is visible, and that visibility is often the first sign that a late entry needs a correction.

That is what makes a past period reproducible on the facts that applied to it, which is the subject of recalculating a past period after a correction.

Questions

What is an effective date on an employee record?

The date from which a change was true, such as a promotion or transfer, as distinct from the date someone entered it.

Why is a last-modified stamp not enough?

It records when the record was last edited, and the edit replaces what was there. It cannot say what was true on an earlier day.

Which changes need an effective date?

Promotions, transfers, probation, suspension, termination, rehire and pay-frequency changes, among others.

How does TriblockHR hold both dates?

Employment history is held by effective date, and the audit history records the before and after values and who made each change.

Keep every change as a dated event, so the record can answer what was true on any day.

Book a demo

  • SOC 2 Type II attested
  • AES-256 at rest
  • 99.9% uptime
  • Built in The Bahamas