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 Disciplinary Module
- Features
- Payroll and benefits
Payroll and benefits
Prepare calendar-based pay runs with employee statements, benefit enrollment and tax filing records.
OverviewPayroll approval queue×
HRMS with Disciplinary Module · Payroll and benefits
New
Payroll approval queue
Approval waits for the reviewer
| Run number | Calendar | Period start | Period end | Pay date | Gross total | |
|---|---|---|---|---|---|---|
| PR-13087 | PC-7177 | 07 Oct | 13 Oct | 21 Oct | 460 | |
| PR-55467 | PC-8539 | 21 Oct | 28 Oct | 31 Oct | 230 | |
| PR-91512 | PC-3453 | 26 Oct | 03 Nov | 05 Nov | 850 | |
| PR-47553 | PC-8750 | 12 Oct | 18 Oct | 21 Oct | 420 | |
| PR-11035 | PC-6726 | 03 Oct | 10 Oct | 14 Oct | 110 |
6 of 6 records
PC-7177Payroll runs · PR-13087
Pending approvalPeriod start07 Oct
Period end13 Oct
Pay date21 Oct
Gross total460
Net total380
What you can do
Run pay against a defined period
A payroll calendar defines the entity, country, currency, frequency and cutoff days. Payroll Admin creates a run for a period and pay date, then reviews its employee count, gross and net totals. Each run links to employee pay statements. Statement lines carry earning, pretax, posttax, tax or employer categories, amount and optional tax jurisdiction. That record path lets payroll trace a run total back to one person’s statement and its lines.
Benefit plans define plan type, country, class, carrier, contribution percentages and effective dates. An enrollment links one employee to a plan, coverage tier, effective date, event and status. HR should check which plan applies before payroll uses its contribution. Tax jurisdictions link locations and statement lines to the appropriate authority; filings link the jurisdiction to a run, due date, amount, status and confirmation reference. Exchange rates are a separate read-only reference for currency conversion where needed.
How the work is organized
- Setup. Admin reviews active plans; Payroll Admin reviews calendars and jurisdictions for the employees in the period.
- Calculation. A run and its statements gather eligible pay amounts, deductions and jurisdiction-tax lines for review.
- Control. A run awaiting approval gets a named decision before posting, payment and later filing reconciliation.
What to agree during setup
Map each employee to the right payroll calendar and currency. Review the cutoff rule, especially for off-cycle, retro, correction and bonus runs. Agree which team approves pay and which team confirms money actually sent. A local status change records the business state; the bank transfer and its confirmation need an explicit external connection where the organization pays electronically. Tax rates and statutory filing rules require jurisdiction-specific setup and expert review.
Reconcile one representative pay statement before running a whole population. Inspect base pay, approved overtime, benefit contribution and tax lines against source records and the applicable jurisdiction. Check the statement’s period against the run and the calendar. A posted or paid run needs a documented correction path; use a later correction run where a prior result must be adjusted.
Check the handoff on an actual case
Select an active employee who has an approved timesheet and an active benefit enrollment. Prepare the regular run for their payroll calendar. Compare the run’s start, end and pay date with the calendar; then inspect the linked statement and lines. Have the authorized reviewer check gross, deductions and net before approval. After payment is confirmed through the organization’s payment process, reconcile the statement’s paid state and the filing record’s due date. Check that a pending timesheet was excluded from the approved input review.
What your team sees
- Payroll approval queue — Runs waiting for a pay decision, with period and totals.
- Pay statements by run — Employee gross, deductions and net linked to the run.
Follow the work through
Use time to pay for the cutoff and benefit to statement for enrollment checks.
What it keeps track of
Data model- Payroll calendars
- Named pay schedules per legal entity, country and currency.
- Payroll runs
- A scheduled execution of payroll for a calendar and period.
- Pay statements
- Per-employee pay statement for a given payroll run.
- Pay statement lines
- Earnings, benefit deductions, taxes and garnishments on a pay statement.
- Benefit plans
- Enrollable benefit plans such as medical, dental, retirement and life.
- Benefit enrollments
- Per-employee enrollment in a benefit plan with dependents and dates.
- Tax jurisdictions
- Tax-authority records driving withholding and filings.
- Tax filings
- Payroll tax filings produced from a run and remitted to an authority.
- Exchange rates
- Read-only effective exchange rates for this app.
Who uses it
Permissions- Payroll Admin
- Prepares and maintains pay and tax records.
- Admin
- Controls access and setup.
- CHRO / VP People
- Reviews the overall result.
- Employee
- Reads their pay statement and benefit enrollment.
Set up HRMS with Disciplinary Module your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.