1. HRMS with Exit Management
  2. Features
  3. Employee records
Feature · Employee records

Employee records

Keep the person, manager, position and employment status together.

OverviewEmployment changes
HRMS with Exit Management · Employee records

Employment changes

Employment history

New
EmployeeEvent typeEffective dateReasonRecorded by
Termination24 OctMerit
Termination20 OctMarket
Termination11 OctPromotion
Termination20 OctVoluntary
Termination11 OctInvoluntary
6 of 6 records
EH-34620Employment history · EH-34620
Termination
Effective date24 Oct
ReasonMerit
Example screen with sample data

What you can do

Begin with the employee record

HR Business Partner keeps each person attached to the correct department, position, manager and payroll calendar. Those links give an exit review its context. When a manager asks whether someone has already left, the employee status and termination date are the starting point; the dated event in employment history explains what changed.

A departing employee may have a current record, a dated employment change, an exit checklist and a payroll statement. Review the links between those records before treating one status as the whole answer. The manager and HR Business Partner should be able to identify the next owner from the assigned task and its due date.

How the work is organized

  • Person. Keep the employee identifier and current manager with the departure record so the work is attached to the right worker.
  • Date. Use the effective event date and task due dates to distinguish future work from overdue work.
  • Result. Record the status and supporting evidence on the record where the work occurred.

What to agree during setup

Agree how the effective termination date is recorded, how a correction is entered and who can change status. Confirm which manager and department should appear for a person who has moved recently. The record also holds pay grade and base salary, so limit edits to the roles already allowed to manage Employees.

For the pilot, choose an employee with a normal departure and one with a change close to the payroll cutoff. Decide who reviews each case and where an exception will be recorded. The team should use the exact same owner for a task in the app and in its operating procedure.

Check the handoff on an actual case

Take a departing employee whose manager changed before notice was given. Check the current manager, then open the dated manager-change and termination entries in employment history. Confirm the departure date matches the checklist start and the payroll period being reviewed. If a position was transferred, retain the prior event instead of replacing history with a new current value.

Ask the next owner to open the record without relying on a separate message. They should see the relevant employee, dates, current status and who completed or still owns the work. If they cannot make the next decision from those records, improve the task description or review rule before expanding use.

What your team sees

  • Former employees — Open the relevant records and review the current result.
  • Employment changes — Open the relevant records and review the current result.

Follow the work through

See employee departure, payroll review and implementation for the handoffs around this module.

What it keeps track of

Data model
Employees
Central person record for every worker; all suite transactions tie back to Employees.
Departments
Organizational departments with parent hierarchy and cost centers.
Positions
Seat-level org entries that an Employee fills.
Employment history
Every lifecycle event: hire, promotion, transfer, comp change, manager change, leave of absence, termination.
Payroll calendars
Named pay schedules per legal entity, country and currency.

Who uses it

Permissions
HR Business Partner
Manages employee and history records.
Payroll Admin
Reads employee context for the last payroll run.
CHRO / VP People
Reviews the overall record; Admin controls configuration.

Set up HRMS with Exit Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started