Employees, the hours they worked, what they are owed, and what they have been asked to do — with approval authority taken from the org chart rather than from a role.
Codes, national ID, nationality, department, job title, employment type, join date and contract expiry, salary split across basic, housing, transport and other allowances, bank and IBAN, and an Arabic name field. Two reporting lines — direct manager and operational manager — and those are what drive approvals.
Bulk import from a biometric device export, matched on the machine user ID held against each employee and tracked by import batch. Working hours, late minutes, early leave, overtime hours and amount are computed from the shift, and can be recalculated across history when a policy changes.
Shift codes with in and out times, a late-in grace period, and an overtime rate per hour set per shift rather than globally.
Configurable earning and deduction heads, generated per employee per month with present, absent and leave days, gross and net. Payment method, company bank, reference and the uploaded transfer receipt are recorded against the run, and each employee gets a printable salary slip.
Advances given and repayments received as typed transactions with their own numbering, method and reference, printable as slips and soft-deleted rather than erased.
Assign work to an employee with a deadline and notes, broken into an ordered sub-step checklist. Completion raises a notification badge for whoever assigned it.
An administrator connects one Google account once; after that the system mints a Meet link for any meeting without ever prompting an ordinary user. Invitations and cancellations go out by email, and an in-app reminder surfaces the next one.
Payroll errors usually start with attendance data that is re-keyed or never reconciled. The People workspace imports attendance straight from the device export, computes working hours, late minutes, early leave and overtime from each employee’s shift, and carries the result into payroll.
Each shift sets its own grace period and overtime rate rather than one global rule, and the calculation can be re-run across history if a policy changes. Payroll is generated per employee per month from configurable earning and deduction heads, with the payment method, company bank, reference and transfer receipt stored against the run — and a printable salary slip for every employee. Advances and loans, task assignment and meetings sit in the same workspace.
If the device can export attendance to CSV or Excel, yes. Each employee carries the user ID their machine uses, and imports are matched on it and tracked by batch. Field mapping for your specific device is scoped during onboarding.
No, and that is deliberate. Approval authority comes from the direct and operational manager on the employee record, so nobody is handed a powerful role just to sign off their own team.
Yes. Every payroll run produces a printable salary slip per employee, in the print format you design.
Tell us what your company does and which modules you would actually use. We will walk you through the system handling your work — not a slide deck.