Skip to content

People and payroll

HR information and payroll information are separately permissioned. The reviewed HR controller uses hr:read for reading and hr:manage for changes. Payroll uses distinct permissions for reading, running, approving, and posting. HR access alone does not grant access to pay.

Employee and employment records

Open Employees. Distinguish the person's identity from their employment record. Employment associates the person with a company and the working details relevant to that engagement.

Review identifiers, start/end dates, status, and organizational assignment. Changes to employment dates can affect downstream eligibility, so verify the intended period before saving. Use fictional records for training and keep payroll material restricted to authorized users.

Leave and attendance

The Leave & Attendance interface offers request and attendance information, with approval/rejection/cancellation actions where permitted. Review the employee, dates, days, reason, unpaid classification, and decision note. A request submitted is not the same as leave approved.

Before payroll calculation, resolve relevant attendance or leave issues and verify how the selected payroll configuration consumes them. Do not assume every leave label has an automatic salary consequence.

Configure pay

Use Payroll Components to define supported pay elements. Use Employee Pay for pay revisions and their effective context. A revision should preserve when the new terms begin; overwriting an old amount without considering dates can make later review difficult.

Confirm the earning/deduction classification, amount or formula, effective dates, and posting configuration. Country-specific statutory treatment needs separate subject review; the academy does not establish payroll compliance.

Calculate a payroll run

Open Payroll Runs, create the intended run/period, and review which employees are included. Calculate starts the calculation. The reviewed controller starts work and exposes progress rather than holding a single request open for the full calculation.

Wait for the reported result and inspect exceptions. Review gross amounts, deductions, and net pay employee by employee where needed. The interface provides explanatory detail and supports a distinct single-employee recalculation path after correction.

Approve and post

Calculation, approval, and ledger posting are separate actions with separate permissions:

ActionPermission
Read payrollpayroll:read
Configure/run calculationspayroll:run
Approve payroll amountspayroll:approve
Post to the ledgerpayroll:post

Review totals before approval. Use Post to ledger only when the run is ready and the posting period/mappings are correct. Inspect the resulting journal. An approved or posted payroll run is not proof that employees' bank accounts have received payment.

Reconcile and correct

Compare run totals, employee details, payslips, the journal, and actual payment evidence. After a calculation timeout, inspect progress and run status before starting another run. After posting, use the authorized correction process rather than editing historical pay data to force agreement.

OSERP Atlas · Understand every field. Master every workflow.