PrimeForce / Modules / Payroll
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.
What it does
Configure pay components and the formulas that value them, group employees into pay groups with their own policies, then execute a run plan period by period. The largest module in the product.
- Multi-step formula engine with bound variables
- Simulate a run, then compare Sim vs Actual
- Input staging and immutable input snapshots
- Numbered recalculation history per run
- Cost-centre splitting at pay-line level
· Fiscal Years
· Pay Groups
· Pay Components
· Formulas
· Salary Structure
· Run Plans
· Input Register
· Payroll Runs
· Payslips
· Disbursements
· Disbursement Documents
What that means in practice.
A formula engine, not a fixed component list
Components are valued by multi-step formulas your team authors, with bound variables and conditions per component. Adding an allowance with its own rule does not need us.
Simulation that mirrors the real model
The simulation tables mirror the live ones line for line — header, employee line, component line. That symmetry is the only reason Sim vs Actual is a genuine comparison rather than an approximation.
Inputs staged, then frozen
Attendance, calendar days, leave, overtime and performance each land in their own staging table, one row per employee per run. At execution the whole input set is snapshotted immutably, so what the run used is recoverable months later.
Recalculation you can audit
Every recalculation is numbered and kept. Mid-period changes are handled as salary slices rather than a retroactive overwrite, and failures surface as run exceptions instead of a silently zeroed figure.
Cost-centre splits at pay-line level
A single pay line can split across cost centres, which is what makes the resulting journal entry mean anything to finance.
Row-level security in the database
Five payroll-run tables carry SQL Server row-level security with both filter and block predicates — company isolation enforced below the application, not only inside it.
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.
Tax & Statutory
The reason this product exists. Statutory compliance is modelled as first-class tables with their own screens — not as custom pay components bolted onto a generic engine.