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.
- HRMS with Document Vault
- Features
- People records
People records
The employee register ties each person to a position, department, location and manager.
OverviewActive employees×
HRMS with Document Vault · People records
New
Active employees
Employees
| Employee ID | Full name | Department | Position | Manager | Hire date | |
|---|---|---|---|---|---|---|
| EI-828 | Full 955 | DPR-150 | PST-6353 | 20 Oct | ||
| EI-744 | Full 857 | DPR-120 | PST-9310 | 23 Oct | ||
| EI-498 | Full 163 | DPR-150 | PST-4930 | 10 Oct | ||
| EI-331 | Full 658 | DPR-120 | PST-5884 | 27 Oct | ||
| EI-908 | Full 638 | DPR-150 | PST-6341 | 06 Oct |
6 of 6 records
EI-828Employees · EMP-31816
ActiveFull nameFull 955
DepartmentDPR-150
PositionPST-6353
Hire date20 Oct
What you can do
People records in daily work
The employee register ties each person to a position, department, location and manager. HR Business Partner checks those references before changing salary, reporting line or employment status. Employment history gives each lifecycle event an effective date and a from and to context, so a transfer can be reviewed as a change rather than a silent overwrite.
The employee register is the starting point for current assignments. An employment history event carries its own effective date and prior and next position or manager. HR Business Partner checks both records when a change affects pay or reporting. Admin reviews compensation changes before they are applied; a dated event should explain why the current employee row changed.
How the work is organized
- Confirm the person. HR Business Partner checks the employee identifier, current position, department and manager.
- Record the change. HR Business Partner enters the effective event with the prior and next context.
- Review the result. Admin checks compensation changes; HR Business Partner compares the employee row with the history event.
What to agree during setup
Agree who can change employee and compensation fields, which legal entity and currency each worker belongs to, and when position changes become effective. Keep the employee identifier stable across payroll, leave and reviews.
For a transfer, agree who records the event and who updates the current assignment. Include the destination position and manager before changing the employee row. Test how an incorrect manager or salary is corrected while retaining the earlier event. A stable employee identifier lets Payroll Admin and L&D Admin find the same person in their own records.
Check the handoff on an actual case
A worker moves from one department to another. HR Business Partner checks the destination position and manager, records a Transfer event with its effective date, and reviews the current employee row. The prior event remains available for a later payroll or headcount question.
HR Business Partner opens Active employees and compares the current assignment with the dated transfer. Admin checks the history event before a pay change proceeds. If the destination position is wrong, HR Business Partner corrects the source event and confirms the employee row again. The reviewer should be able to see the prior and next position without relying on a name match.
What your team sees
- Active employees — Current employee assignments by department, position and manager.
- Reviews in progress — HR Business Partner checks review work linked to an employee after a transfer.
Follow the work through
What it keeps track of
Data model- Employees
- Central person record for every worker; all suite transactions tie back to Employees.
- Employment history
- Every lifecycle event: hire, promotion, transfer, comp change, manager change, leave of absence, termination.
- Positions
- Seat-level org entries that an Employee fills.
- Departments
- Organizational departments with parent hierarchy and cost centers.
- Job titles
- Canonical job titles with job family, level and exempt status.
- Locations
- Physical and remote locations where employees work.
- Pay grades
- Salary bands tied to job titles and positions.
Who uses it
Permissions- HR Business Partner
- Maintains employee, position and history records.
- Admin
- Handles controlled compensation decisions.
- CHRO / VP People
- Can read the employee record for oversight.
Set up HRMS with Document Vault your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.