A module for every HR process, all on the same data
From payroll to recruitment, 23 modules connect to one core. A change you make on one screen takes effect on the others immediately; there is no transfer between modules, no second data entry and no separate licence.
One licence, per user • Web and mobile • Modules switched on as you need them
Modules are not separate screens, they are parts of one system
This is where the difference begins between putting separate software side by side and working on a single platform.
An employee is defined once
The joining record is created in one place. Employee records, payroll, attendance and leave all read the same record; a department change applies to every one of them at once.
The same approval flow in every module
Leave, expenses, advances, assets and shift swaps all use the same approval engine. A manager approves them from a single list.
Permissions granted from one place
Role-based access is defined centrally rather than module by module. A branch manager sees only their own location’s data.
Reports come from the same pool
Data produced by every module lands in a shared reporting layer. You compare absence against payroll cost on the same screen.
23 modules, under five headings
You do not need to switch them all on at once; the headings show which module takes on which job.
Time and attendance
4 modulesThis is where the single answer to “who worked when” is produced. Timesheets come out of these modules and go to payroll without passing through anyone’s hands.
Pay and cost
3 modulesEvery penny that goes to an employee is calculated in the same place: salary, bonus, deduction, advance and expense all collect into one accounting transfer.
Employee file
5 modulesEvery document, signature and assigned asset that builds up from joining to leaving sits in the same file, and comes out of one place at audit.
Recruitment and development
4 modulesThe same person card moves from the candidate pool to the first-year review; nothing is re-entered when a candidate becomes an employee.
Daily operations
7 modulesThe work HR spends most of its day on: collecting requests, announcing, reminding and reporting.
We do not switch everything on day one
Rollout starts with whatever is costing you the most time. The three starting orders we see most often in the field:
Shift-based manufacturing and hotels
Hours go on record first; once timesheets are clean, the payroll close gets shorter.
- Time & attendance
- Shift planning
- Timesheets and overtime
- Payroll
Leave and employee records come next.
Multi-site retail and field teams
Bringing deskless employees into the system is the fastest win.
- Mobile app
- Leave management
- Requests and approvals
- Announcements and alerts
Attendance and expense modules are added after that.
Office-based companies
Scattered spreadsheets and folders come together in one employee file first.
- Employee records
- Leave management
- Performance
- Expense management
Recruitment and training modules open next.
Modules connect outward, not just to each other
Payroll output goes to accounting, the employee card to your ERP, and clock records to your existing turnstiles and card readers. Ready-made connectors are part of the standard package.
- ERP: SAP, Oracle, Microsoft, Logo, IFS, Infor, Epicor, Canias
- Devices: card readers, turnstiles and biometric terminals
- Accounting: bank payment files and statutory filing outputs
Frequently asked about the modules
Let’s work out together which modules to start with
In the discovery call we listen to your current processes and map out the module set and sequence that fits you.
