HRMS
People, presence and requests — on the record every module uses.
Xelium One's People directory and Xelium Pulse give HR one record for each person, with attendance, leave and corrections that route to the right manager. The same People directory powers approvals, Pulse and reports.
The problem
The people list exists five times.
Different lists, different answers
HR, attendance, recruiting and billing keep their own list of people, and they rarely agree.
Requests that disappear
Leave and corrections go by email, so approvals are slow and unrecorded.
History overwritten
Correcting attendance often means editing the original, so nobody can see what changed.
Two approaches
The traditional approach, and the Xelium approach
Traditional approach
An HR system for records and a separate attendance or leave tool, joined by uploads.
- New joiners entered again after recruiting has already captured them.
- Reporting lines kept in a spreadsheet for approvals.
- Payroll inputs assembled by hand from several exports.
The Xelium approach
One People record, shared by every module, with Pulse for the working day.
- Reporting managers in People decide who approves each request.
- Corrections are separate records — the original is always kept.
- Nobody approves their own request.
Key capabilities
What it does
Each capability shows whether it is available today or coming soon.
Employee directory, departments and reporting managers
AvailableProfiles, departments, reporting managers and current or former status.
Check-in, check-out, breaks and attendance
AvailableCheck-in, check-out and breaks, with logged hours against expected hours.
Leave and work-from-home requests with approvals
AvailableLeave and work-from-home requests, approved by the reporting manager or HR.
Attendance corrections that never overwrite the original
AvailableCorrections for missed check-ins or check-outs, kept alongside the original.
Attendance reports with CSV download
AvailableAttendance for a period per person, ready to download for payroll.
A joined placement becomes a People record automatically
Coming soonA joined placement creates the person's People record, without re-typing.
Module details:PeopleXelium PulseXelium One Core
Connected advantage
What connection changes
HR records aren't an island: recruiting feeds them and reporting reads them.
- Offer
- Joining
- People
- Attendance
- Reports
- People records are used by Pulse, approvals and Reports; a joined placement becoming a People record automatically is coming soon.
- Roles and access come from the person's role in Core.
- Xelium One doesn't run payroll; attendance reports download as CSV for your payroll process.
AI advantage
AI with a job to do
Answers for managers and employees, limited to what each may see.
- Illustration · example dataAvailable
How do I correct yesterday's missed check-out?
Open your attendance, choose yesterday and send a correction. Your manager approves it; the original stays on record.
How it answers: Guided help from the handbook, with a link to the page where you make the request yourself.
- Illustration · example dataAvailable
Which requests are waiting for my approval?
A short list of pending leave and correction requests from your team, each linking to the request.
How it answers: Uses the same approval rule as the requests page.
Analytics advantage
Answers from the same records
Workforce reporting built from attendance and requests as they happen.
- Attendance totals per person for any period up to 92 days, with CSV.Available
- Headcount, attendance and leave trends in your own report layouts.Coming soon
- Available
- Works in Xelium One today.
- Coming soon
- Not live for customers yet — being built, or not built yet.
- Simulated in demo
- Shown in the sales demo with fictional sample data. Nothing real happens.
Give HR one record to trust.
Book a demo of People and Pulse, or read what's included.