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.
- Education & School ERP
- Features
- People and payroll
People and payroll
Give HR, payroll and employees a consistent record of employment, approved time and pay. People and payroll carries effective employee changes into the right pay period while preserving the authority and source evidence behind each result.
OverviewMy Team Leave Requests×
Education & School ERP · People and payroll
New
My Team Leave Requests
Leave requests
| Request number | Employee | Leave type | Start date | End date | Days | |
|---|---|---|---|---|---|---|
| LR-23017 | Sofia Haddad | Study leave | 17 Oct | 19 Oct | 17,289.56 | |
| LR-71279 | Priya Shah | Unpaid leave | 13 Oct | 20 Oct | 9,726.24 | |
| LR-49148 | Daniel Kim | Sick leave | 27 Oct | 05 Nov | 15,221.26 | |
| LR-37088 | Owen Fitzgerald | Family care leave | 03 Nov | 08 Nov | 13,931.97 | |
| LR-71013 | Minh Nguyen | Family care leave | 22 Oct | 27 Oct | 45,694.29 |
6 of 6 records
Annual leave for family travelLeave requests · LR-23017
SubmittedEmployeeSofia Haddad
Leave typeStudy leave
Start date17 Oct
End date19 Oct
Days17,289.56
What you can do
Maintain the employee's effective record
Employees belong to an entity, position, department, manager and pay calendar. Employment dates, status and payroll eligibility determine which population belongs in a run. Positions retain approved headcount and effective assignments; an as-of filled count supports planning without pretending that the count alone authorizes a hire.
HR Manager or Payroll Administrator proposes sensitive bank, identity or compensation changes. A different person in the other role reviews the old/new values, effective time and evidence. Approved changes apply through that controlled path; broad employee-master access cannot bypass it.
Effective compensation history preserves the salary or hourly rate applicable to prior periods. Changing today’s rate does not overwrite the basis of an already approved pay statement or turn a retroactive difference into another full payment.
Employee-level pay, national identity and bank fields remain masked according to the specific access policy, including for broad administrative and finance roles. Payroll approval can expose authorized totals and exceptions without granting every reviewer unrestricted personal details. Employees see their own statements and balances.
Count leave from the actual work schedule
Leave types specify paid or unpaid treatment, accrual, carry-over and required evidence. Requests use the employee’s working schedule and holiday calendar. A single half-day remains a half-day even when start and end are the same date; two endpoint flags cannot turn it into zero.
Overlapping requests are checked across their actual dates. Requests spanning leave years or accounting periods retain the correct allocations. Submitted and approved leave reserve the entitlement once, and moving approved leave to Taken transfers the usage without reducing availability again.
The assigned manager approves within their Employee authority; Plant Manager handles assigned plant requests. HR Manager can act through an active scoped delegation. The actual delegate and principal remain visible, and the requester cannot approve their own absence.
Preserve approved time and its cost split
Timesheet lines retain worked dates, hours, cost centres and any work-order operation. Daily limits, overlap, job ownership and unpaid-leave conflicts are checked before approval. Managers approve within scope, with Plant Manager responsible for the assigned plant population.
Approved source lines are consumed once by payroll and, where appropriate, WIP costing. A recalculation cannot pay the same hours or absorb their labour twice. Corrections link back to original approved lines and use the authorized current posting period where a historical period is closed.
When an employee works across cost centres or jobs, those allocations follow the pay and journal lines. A position default fills genuinely unallocated scope; it does not replace the approved distribution of actual work.
Calculate from configured components
| Component basis | Evidence retained with the result |
|---|---|
| Salary or fixed amount | Effective compensation and employee eligibility |
| Hourly or overtime | Approved source hours, rate and configured multiplier |
| Benefit or deduction | Effective employee election and configured amount or percentage |
| Statutory result | Jurisdiction, effective configuration or external-service calculation evidence |
Earnings, employee deductions, taxes and employer contributions retain explicit signs and separate totals. Employer pension or benefit expense is not automatically payroll tax. Statement currency and conversion to run and entity totals are preserved rather than summing unlike amounts.
Statutory rules are configured for the actual jurisdiction and provider scope. Missing or unverified calculation evidence remains an exception for review; the generic component list does not establish legal compliance for every country.
Review, post and reconcile settlement
Payroll Administrator prepares the eligible entity and calendar population and compares statements with the prior accepted basis. Controller, independent of the preparer, approves the complete frozen run and its exceptions before authorized financial effects.
The journal records components by account and the retained cost distribution. Work-order labour absorption is reconciled with actual payroll expense without adding the same labour to WIP again. Gross, deductions, employer costs and net liabilities reconcile to the statements.
Controller releases the approved protected bank instruction. Authenticated bank outcomes distinguish acknowledgment, acceptance and settlement; Finance Clerk reconciles masked totals. Authoritative pre-settlement rejection releases reservations without cash reversal; uncertainty retains them. Reconciled retries cannot pay employees again.
Correct past pay without replaying it
Retro and correction runs reference original runs, statements and components and post only the approved delta. YTD uses effective posted payroll and linked corrections, excluding superseded drafts and duplicate source consumption.
Parallel payroll is a rehearsal. It produces comparison results without ledger, bank, leave, time-consumption or YTD effects. Opening payroll and leave history also use reviewed nonposting migration evidence rather than fabricated executable runs.
My Team Leave Requests, My Timesheets and Open Payroll Runs show pending work. Recruiting, performance and learning remain separate HR scope.
What it keeps track of
Data model- Employees
- Effective employment, role, limit and protected pay reference data. HR/payroll proposals and independent activation history govern sensitive fields; derived summaries do not overwrite the history.
- Positions
- Approved positions in the organisation chart. Headcount is planned and filled against positions, and a position carries the grade and reporting line an employee inherits.
- Leave types
- Leave policy per entity: what is paid, how it accrues, how much carries over, whether evidence is required.
- Holiday calendars
- Public holidays per entity or country, one row per holiday, used to count leave days and to set pay dates.
- Leave requests
- Calendar-resolved daily leave scope reserved on submission and approved by a distinct eligible manager or formally delegated actor.
- Leave balances
- Accrued, taken and available leave per employee, leave type and year.
- Timesheets
- Hours per employee per pay period, approved by the manager before payroll picks them up. The lines carry the split by day, cost centre and work order.
- Timesheet lines
- One line per day and charge: the hours, their type, and the cost centre, work order and operation they charge.
- Pay components
- Earning, deduction, employer-contribution and tax codes per jurisdiction, each with the account it posts to. The payroll engine computes a statement as a set of these.
- Payroll runs
- Effective eligible payroll population and calculation snapshot per entity/pay calendar, reviewed independently and posted only for an operational run.
- Pay statements
- Per-employee pay-currency totals with explicit conversion to functional payroll aggregates and separately confirmed payment instructions.
- Pay statement lines
- Effective component calculations and signed correction lineage, with operational YTD totals and exact time/leave allocations.
- Employee pay components
- Effective employee eligibility and calculation parameters for pay, deductions, benefits and statutory components.
- Compensation history
- Immutable approved effective salary/hourly and sensitive employment change history for calculation and retro deltas.
- Work calendars
- Effective employee workweek, hours and holiday jurisdiction; leave and payable time use the same daily basis.
- Work calendar days
- Resolved dated calendar overrides and scheduled hours support partial days, holidays and cross-year allocation.
- Leave entries
- Append-only daily leave reservation, taken, accrual, carryover and correction effects by balance year.
- Payroll allocations
- Exact time/leave/component scope consumed by an operational payroll line, with distinct WIP absorption and salary-clearing effects.
- Payroll opening balances
- Approved nonposting cutover YTD amounts by employee, component and tax year; not a fresh payroll payment or GL charge.
Who uses it
Permissions- HR Manager
- Governs employment and leave.
- Payroll Administrator
- Prepares pay. Each reviews sensitive changes proposed by the other.
- Employee
- Submits own leave and time.
- Plant Manager
- Approves assigned plant inputs.
- Controller
- Approves payroll and financial reconciliation.
- Admin
- Maintains identity and approval limits.
Set up Education & School ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.