PrimeForce / Modules / Human Resources
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.
What it does
The employee master is the spine of the product. Create and maintain employee records, attach the salary card that drives payroll, and action confirmations, transfers and exits from the Lifecycle Dashboard rather than burying them in a form.
- Effective-dated salary card — a raise is a new row
- Around 20 employee sub-records: documents, dependents, education, skills
- CNIC uniqueness enforced per company
- Separation types carry gratuity and notice rules
- Final settlement closes the loop
· Employee Profile
· Salary Card
· Lifecycle Events
· Separation Types
· Final Settlements
What that means in practice.
A salary card that keeps its history
Per-employee pay is stored per component and effective-dated, unique on company, employee, component and effective-from date. A raise inserts a row; it never overwrites one. That is what lets a recalculation of an old period still use the numbers that period actually ran on.
Around twenty sub-records per employee
Bank accounts, dependents, documents, education, emergency contacts, prior experience, insurance and enrolments, languages, licences, medical records, nationalities, nine-box placement, references, skills and skill profiles, disability records and awards — each a real table, not a free-text field.
CNIC uniqueness, per company, with the collision named
A duplicate CNIC is rejected with the employee code and full name of the record already holding it, so the person entering it can resolve it without asking anyone. Uniqueness is scoped to the company, so the same person can exist under two employers.
Separation types as configuration
Each separation type carries whether it is gratuity-eligible, whether misconduct forfeits gratuity, which way notice runs, the default notice days and the statutory payment window. Exit entitlement is a data decision your HR team owns, not a code change.
Lifecycle events as records, not edits
Probation reviews, increments, transfers and employment-status changes are their own rows with their own history. The Lifecycle Dashboard is where they get actioned.
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.
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.
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.