Payroll · every two weeks
Someone downloads the time clock punches, moves them into a spreadsheet and matches late arrivals, absences and leave by hand before sending pre-payroll. A mistake shows up when an employee questions their pay slip.
We move into one system what your HR team now gathers from time clocks, spreadsheets and folders: attendance, employee records, vacation and the incidents that feed payroll. We implement RHUNO, the HR system we run, or build what your company needs.
Payroll · every two weeks
Someone downloads the time clock punches, moves them into a spreadsheet and matches late arrivals, absences and leave by hand before sending pre-payroll. A mistake shows up when an employee questions their pay slip.
HR · vacation request
An employee asks how many days they are owed. Answering means checking their seniority, what they already took and the legal table, on paper.
Records · file review
Contracts, IDs and certificates sit in folders, some at the office and some at the branch. Finding out who is missing a document means opening them one by one.
What HR teams ask for most. It can be done with RHUNO, built to measure or connected to what you already use.
Reading the time clocks you already have, phone check-in with location for people who work off site, and late arrivals, absences and overtime calculated with your company's rules.
Every employee document in their file, with an expiry date and an alert when one is missing or expires. Each person sees only what their role allows.
Days by seniority under Mexico's Federal Labor Law, requests approved by the direct manager and a balance employees check without having to ask.
Approved absences, late arrivals, leave, sick leave and overtime, ready for your payroll system without keying them in again.
Pay slips, vacation balance, requests and company notices on each employee's phone.
Turnover, absenteeism and headcount by area or branch, from system data instead of a spreadsheet built at month end.
Recruiting, evaluations, training or the questionnaire your audit asks for: if your team needs it and it is not here, we build that too.
Book a callWe read the time clocks already installed, whatever the brand, and deliver incidents in the format your payroll system expects. If a clock does not allow punches to be downloaded, the assessment says so.
A 30-minute call to review how pre-payroll is built today and where employee records live. If RHUNO covers what you need, we start with it; if your company has its own rules, we write the scope and build what is missing.
It depends on how many people and branches there are, how many clocks need reading and whether a connection to the payroll system is needed. We send the price and dates in writing before we start.
How we work: scope, deliveries and maintenanceWe build and run RHUNO, which calculates each person's vacation days under Mexico's Federal Labor Law, takes attendance from time clocks and keeps each employee's digital record. We maintain it every day.
No. If RHUNO covers what you need, it is the fastest way to start. If your company has its own rules, we build the system to measure or connect what you already use.
We work with the clocks already installed. If one does not allow punches to be downloaded, the assessment says so and we propose another way to record attendance.
Yes. Approved incidents come out in the format your payroll system expects, without keying them in again.
Each person signs in with their own access and sees only what applies to them. Employee data is handled under Mexico's personal data protection law.
Yes. Attendance can be recorded from a phone with location, and each branch sees its own headcount.
In a 30-minute call we tell you whether RHUNO covers what you need or what would have to be built.
Documents: Privacy notice · Terms of use