These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Feature · Employee records
Example screen with sample data
Employee records
Keep current employment and salary-band decisions connected to the employee history.
OverviewEffective employee changes×
HRMS · Employee records
New
Effective employee changes
Employment history
| Employee | Event type | Effective date | From position | To position | From salary | |
|---|---|---|---|---|---|---|
| Hire | 03 Oct | PST-1930 | PST-8710 | 820 | ||
| Promotion | 03 Oct | PST-1993 | PST-1621 | 520 | ||
| Transfer | 10 Oct | PST-1571 | PST-1783 | 350 | ||
| Comp change | 03 Oct | PST-6329 | PST-9719 | 690 | ||
| Manager change | 12 Oct | PST-1400 | PST-2660 | 220 |
6 of 6 records
PST-1930Employment history · EH-76151
HireEffective date03 Oct
To positionPST-8710
From salary820
To salary110
What you can do
Work from the current employee record
An employee move affects the people who recruit, approve leave and prepare pay. HRMS keeps the position, department, location, manager, pay grade and payroll calendar together. HR Business Partner (HRBP) starts with the employee record when reviewing a transfer or compensation change, then uses employment history to retain the event and its effective date.
The Employees feature page shows the authorized employee population, department headcount navigation and individual detail with native record access. It also identifies compensation band exceptions from the linked pay grade. Compare salary against the matching currency and effective band before deciding whether a change needs escalation.
How the work is organized
- Current employment. The employee record carries the hire date, employment type and status. Active and On leave identify different operating states. A termination date and retained history event explain a departure without erasing the earlier assignment.
- Organizational context. Each position connects a job title to its department, location and pay grade. The employee’s manager provides the default approver for leave requests. Review that relationship when a person moves so the next request reaches the right manager.
- Recorded changes. Employment history retains the event, effective date, previous and new salary, position and manager, plus the person recording it. The lifecycle workflow applies the change. Compensation outside the band waits for CHRO / VP People approval.
What to agree during setup
Agree who prepares employee changes and who maintains organizational records. Map employee accounts to the correct people and configure access to their own records. Decide which readers need compensation information and protect national identity and birth dates through the agreed field restrictions.
Check the payroll calendar, country, entity and currency for the pilot population. Give the master-data owner a sample transfer to review with Payroll Admin before loading the wider workforce. Salary-band comparisons should use a compatible currency; agree any effective-rate connection separately during setup.
Check the handoff on an actual case
Rehearse a promotion with HR Business Partner (HRBP). Inspect the current position and salary, choose the destination position and record the effective date and reason. If the new salary exceeds the destination band, route the decision to CHRO / VP People. Retain the original values so the approver can explain the change.
After application, inspect the employee record beside its employment history. Confirm the new manager can be resolved for the next leave request. Ask Payroll Admin to explain the recorded compensation change and any retro-pay follow-up. Repeat with an unresolved position reference and hold the change for correction before the team treats it as complete.
What your team sees
- Workforce directory — Find current employees with their department, position, manager and employment status.
- Effective employee changes — Review dated lifecycle events beside the previous and new values.
Follow the work through
Use employee changes and separation to rehearse the decision and its handoffs. Follow implementation when preparing employee imports.
What it keeps track of
Data model- Employees
- The central person record that every transaction in the suite ties back to.
- Employment history
- Every lifecycle event: hire, promotion, transfer, comp change, manager change, leave of absence, termination.
- Positions
- Seat-level org entries that employees fill.
- Departments
- Organizational departments with GL cost centers and department heads.
- Job titles
- Canonical job titles with job family, level and exempt status.
- Locations
- Physical and remote work locations with country and tax jurisdiction.
- Pay grades
- Salary bands tied to job titles and positions.
- Payroll calendars
- Named pay schedules with frequency, entity, country and cutoff.
- Exchange rates
- Read-only effective exchange rates for this app.
- Users
- Users
Who uses it
Permissions- HR Business Partner
- (HRBP), CHRO / VP People, Payroll Admin, Employee.
- HR Business Partner
- (HRBP) maintains lifecycle records; CHRO / VP People decides escalated changes through the workflow.
- Payroll Admin
- Reads relevant pay context, and Employee uses permitted self-service access.
Set up HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.