PrimeForce / Modules / Leave Management
Leave Management
Twenty-six entities, eighteen of them under database-level row security. Balances move only through logged transactions.
What it does
Define leave types and the policies that grant them, publish holiday calendars and the working week, then process applications against live balances. Accrual runs monthly without anyone touching it.
- Policy resolution by grade and tenure band
- Automatic monthly accrual
- Day-level applications — half-days are exact
- Year-end carry forward with its own log
- Encashment protected against double submission
· Team Applications
· Leave Balances
· Leave Types
· Leave Policies
· Holiday Calendars
· Manual Adjustment
· Admin Leave Entry
· Leave Encashments
· Year-End Processing
What that means in practice.
Policy resolved by grade and tenure
Entitlement comes from the policy that matches the employee’s grade and tenure band, with per-type rules underneath it. One policy set covers a whole workforce without per-employee overrides.
Accrual on a schedule, not a reminder
A background job accrues leave for every company at 01:00 UTC on the first of each month. Nobody has to remember.
Applications resolved to the day
Each application expands into one row per date, unique on application and date, so half-days, holiday exclusions and working-week rules are exact rather than estimated from a date range.
Year-end that leaves a trail
Carry-forward writes its own log, and the Carry Forward report reads it. Encashment carries an idempotency key so a request that times out client-side cannot become two payments.
Leave liability as a finance number
The Leave Liability report exists for finance rather than HR — accrued, unused leave valued at current basis.
See it against your own numbers.
Bring a payroll period you have already closed. We configure the components, run it, and show you the variance against your figures.
Other modules.
Human Resources
Every other module reads from the employee master. It holds the record, the salary card that values it, and the lifecycle events that change either one.
Organization
Ten master tables, every code unique per company. This is the structure payroll costs against and workflow routes through.
Payroll
Sixty-nine entities and the longest chain in the product: run plan, staged inputs, snapshot, pay line, component line, cost-centre split, journal entry.