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
- Frequently asked questions
Questions, answered
Answers about HRMS employee work, workflow decisions and provider boundaries.
HRMS
11 questions
Can't find it? Write to support@erp.ai.
How do I get started?
Click Get started, then use Proto to configure HRMS for your business. Choose a pilot department and payroll calendar, import the referenced employee and position records, then rehearse an offer, joining tasks, leave and an internal payroll pre-check with the responsible team.
What does HRMS cover?
Recruiting, accepted-offer provisioning, current employee records and lifecycle history, joining and leaving tasks, leave balances, timesheets, payroll preparation, benefits, performance and learning. The Employees page also supports authorized employee detail, department headcount navigation and linked salary-band exceptions.
Who decides an offer outside the salary band?
CHRO / VP People decides out-of-band compensation through the workflow. HR Business Partner (HRBP) handles in-band approval. The comparison uses the linked position pay grade and a compatible currency; missing or conflicting band data needs resolution before a decision.
Can employees see another person's pay?
Configure Employee self-service for the person’s own records. Map accounts to employees, then test pay statements and reports with different Employee accounts. Include attempts to open another person’s records before enabling self-service for the wider team.
How are leave balances updated?
Submission reserves pending days. Approval releases pending days, adds taken days and records the approval date; rejection or cancellation releases pending days. A needed balance is created for the employee and leave type so the movement is retained. Requested days include the start date, end date and any intervening weekends. Confirm this calendar-day basis and approval-time treatment with the team during the pilot.
What should we agree before running payroll?
Agree the calendar, active employee population, earnings basis and benefit deductions with Payroll Admin. Configure tax calculation with the payroll owner before live use. Agree the run approval responsibility and rehearse the tax service confirmation route alongside the internal pre-check.
Does a pay status confirm money was delivered?
A prepared or internally approved run needs a separately verified payment connection and actual outcome evidence. The posting date records the run’s entry to Posted. Bank delivery, accounting posting and tax filing remain distinct handoffs to configure and reconcile.
Are benefit elections automatically accepted by the carrier?
The enrollment workflow validates the plan window and enrollment event before activating the internal election and computing contributions. Configure carrier delivery separately and reconcile its confirmed coverage response with the active election.
How do performance and learning avoid duplicate assignments?
Cycle opening and new-hire learning check existing employee assignments before creating needed work. Rehearse a repeated cycle update and a hire with an existing required enrollment. Compare the original assignments afterward and confirm that each person retains the intended work without another copy.
How should we review performance dates?
Agree how submission, release and acknowledgment dates are recorded. During the pilot, compare each date with the actual review action before using it in a report. Keep the assigned reviewer, cycle and subject visible when discussing any discrepancy.
What confirms separation is finished?
Marking the employee Terminated starts retained history and offboarding work. Inspect each task’s status, evidence and responsible assignee, including the final-pay payroll run link. Identity-provider revocation, equipment return and settlement need the actual responsible system’s confirmed outcome.
Set up HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.