Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
People Operations · Built on your platform
AWRA HR & People — run your people the way you already run your operations.
AWRA People & HR is a full human-resources pillar layered onto the platform you already trust — the same secure identity, approvals, audit trail and money-out ledger that power your inventory, procurement and finance. One clean system of record for every person, from the day they apply to the day they leave: recruitment, onboarding, leave, attendance, statutory payroll, expense claims, performance reviews and offboarding, all live today.
Employee ≠ Login
People, not seats
One ledger
Payroll = money-out
Multi-currency
Statutory-ready
Hire to exit
One record throughout
Why HR belongs here
Most HR systems start from zero. Yours starts at 80%.
A standalone HR tool has to rebuild the boring, expensive foundations before it delivers a single payslip. AWRA already runs them in production — so People & HR inherits workspace isolation, identity, role-based access, approval workflows, custom fields, a full audit trail and a reconciled money-out ledger on day one.
Airtight data isolation
Every employee, document and pay record is walled off to your organization by the same guardrails that protect your stock and invoices — tested, not bolted on.
Identity & RBAC
Reuses your existing users, roles and granular permissions. HR actions are gated (view / add / edit / approve / run payroll) exactly like every other module.
Approval workflows
The same engine that approves purchase orders and prequalification approves leave and payroll runs — no second workflow system to learn.
Custom fields
Add organization-specific fields to employees and contracts without a migration, using the configuration layer already wired across modules.
Immutable audit trail
Who changed a salary, terminated a contract, or exported PII — captured automatically with user tracking on every HR model.
One money-out ledger
Approved payroll posts into the same ledger as vendor payments and surfaces in the cross-module Payments Register — a single reconciliation surface.
The core rule
An employee is a person — not a login.
Most of your workforce will never sign in. Treating an employee as a user account breaks the moment a cleaner, a driver or a field technician needs a record but not a password. AWRA models employees as first-class entities with an optional, nullable link to a platform user. Employment lifecycle never touches authentication state.
- Most employees exist with no login at all — and that is the normal case, not an edge case.
- One person can be an employee in one organization and a vendor contact in another, without collision.
- Terminating or suspending an employee changes HR status only — it never silently locks or deletes an account.
- When access is needed, provision a login from the employee in one click — with a role you choose and a forced password reset.
Deliberate build order
Employees first. Payroll next. Then the whole lifecycle.
We shipped along the dependency chain, not perceived importance. Clean employee and time data had to exist before payroll — garbage in becomes wrong salaries, and payroll errors carry legal consequences. With that foundation in place, the lifecycle around it followed: hiring people in, settling them in, reviewing their work, repaying what they spend, and seeing them out properly.
Employee Management
Employees, positions, org hierarchy, employment contracts, emergency contacts, secure documents, bulk import and optional login provisioning — a complete system of record.
Explore Employee ManagementLeave Management
Leave types and balances, regional public-holiday calendars, multi-level approvals reusing the existing engine, a team calendar, notifications, and self-service including a secure no-login option.
Explore Leave ManagementAttendance & Time
A daily register captured four ways, shifts and weekly rosters, auto-detected overtime, an attendance dashboard, and monthly timesheets you approve and lock — payroll-ready and leave/holiday aware.
Explore Attendance & TimePayroll
Configurable statutory payroll: salary plus the income-tax and social-contribution rules for each region you operate in, versioned and effective-dated, with optional overtime pay by kind of day, frozen payslips, upload-ready return files where rules are maintained, and approved runs posting into your money-out ledger.
Explore PayrollRecruitment
Vacancies with a hiring manager, applicants moving through each stage with their CVs kept confidential, interviews with feedback from the interviewer, and a hire that creates the employee record.
Onboarding & Offboarding
Checklist templates that start on hire and on exit, with each step owned by HR, the line manager, the employee or a named person, and ticked off by whoever owns it.
Performance Reviews
Review cycles with weighted goals: a self-review, the reviewer’s ratings and an overall rating, then the employee’s acknowledgement and response.
Expense Claims
Staff claim back what they spend with receipts attached; someone else approves, and the money is repaid through payroll untaxed or paid directly.
The moat
HR that is wired into the rest of the business.
A siloed HR app gives you a database. AWRA gives you connections — because people touch assets, money, access and operations every day, and those links already exist in the platform.
People ↔ Assets
Link an employee to an asset custodian and their profile shows exactly which assets they hold — accountability across onboarding and exit. Available today.
Payroll → Payments Register
Approved payroll runs post as money-out beside vendor payments, so finance reconciles one surface instead of two.
Employee ↔ User
Provision or de-provision a login from the employee record, closing the access-control loop on hire and termination.
People → Operations
Work assignment targets employees, and capacity respects their leave and attendance — an unavailable assignee is flagged on the task.
Headcount → Billing
Per-employee HR seats plug into the same subscription billing engine that runs the rest of your account — buy, reduce and renew seats like user seats. HR expands the revenue model, not just the feature list.
HR → Analytics & BI
Headcount, turnover, absenteeism, leave liability and payroll cost by department feed the custom-reports and BI builder.
Hire → Onboarding
Hiring an applicant creates their employee record on probation, sets the hiring manager as line manager, and starts the onboarding checklist.
Expense Claims → Payroll
An approved claim can be repaid on the next payslip as an untaxed line, and is marked repaid when that run posts.
Reporting Line → Reviews
Line managers review their own people, interview candidates and tick their onboarding steps without needing any HR access.
Built for where you operate
Statutory rules that are configurable, versioned and auditable.
Payroll is a regulatory commitment, not a feature. Each region's tax and contribution rates are stored as versioned, effective-dated configuration — never hard-coded — so a rate change never retroactively rewrites a closed run, and adding a new country is configuration, not a rebuild. Employee records already capture the identifiers payroll needs.
Income tax
Bands + relief, per region
Social security
Pension / provident contributions
Health
Statutory health contribution
Local levies
Region-specific deductions
Captured on every employee today
- National ID, tax ID, and social-security & health identifiers
- Employment type & status, hire and end dates
- Department, position & grade, and reporting line
- Employment contract with basic salary & currency (for payroll)
PII and (later) bank details are encrypted at rest and access-audited.
Questions
What teams ask before adopting HR.
Do employees need login accounts?
No. Most employees never log in. An employee is a person record with an optional link to a platform user — you only provision a login when someone actually needs access.
Is any of this live yet?
Yes, all of it: Employee Management, Leave, Attendance & Time and Payroll, and around them Recruitment, Onboarding & Offboarding, Performance Reviews and Expense Claims.
Do line managers need HR access to take part?
No. A manager reviews their own people, gives interview feedback and ticks the onboarding steps that are theirs without holding any HR permission. What they can see is limited to what is theirs.
Can staff claim back expenses?
Yes. Staff submit claims with receipts from their own self-service page. Someone other than the claimant approves them, and they are repaid through payroll as an untaxed line or paid directly with a reference.
Why was payroll built last?
Payroll was deliberately sequenced after clean employee, leave and attendance data existed — garbage in becomes wrong salaries, and payroll errors carry legal consequences. It ships scoped to fixed salary plus the statutory deductions for the regions you operate in, with runs posting to your existing ledger.
How does HR affect billing?
HR is a premium module gated by subscription plan, with per-employee pricing that plugs into the same billing engine that runs the rest of your subscription.
Is our people data isolated and secure?
Yes. HR uses the same data isolation, role-based permissions, encrypted document vault and audit trail as every other module — enforced by the platform, not re-implemented.
Can HR data reach our reports?
Yes. Headcount, turnover, absenteeism, leave liability and payroll cost by department feed both a dedicated HR analytics view and the custom-reports and BI builder you already use.
Explore the module
Every part of HR, in detail.
The four foundation modules, and the operating layers underneath them.
Help Center
Need a quick answer while you read?
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.
AWRA HR & People