Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
All role-based solutions
People operations
Run leave, attendance and payroll from one employee record.
HR and payroll teams use AWRA to hold contracts, leave, attendance, shifts and payroll on one employee record — for the staff who log in and the many who never will.
Hold every employee as a record without spending a login on each one.
Let staff request leave, clock in and read their payslips from a PIN-protected link on their own phone.
Carry approved attendance and overtime into a payroll run that computes statutory deductions and posts to the payments register.
Why this page exists
Built around the problems this team actually owns.
The page connects role-specific pain points to AWRA workflows and implementation resources, so prospects can inspect fit without guessing which module matters.
1
Leave is tracked on paper forms and balances are argued about at year-end.
2
Attendance arrives as a spreadsheet the day before payroll closes.
3
Statutory rates change and the payroll workbook is edited by hand.
Operating workflows
A practical workflow map for hr & payroll teams.
Leave without the paperwork
Staff request leave through self-service, balances count working days against your own working week and public holidays, and approvals route to the manager.
Attendance to timesheet
Clock-ins verified by GPS geofence, site QR or trusted device roll up into a monthly timesheet with derived overtime, approved and locked before payroll reads it.
Payroll close
Run, review and approve the payroll, post it to the payments register, and issue payslips and the P9A from the same frozen figures.
Before you shortlist us
The same page, without the sales gloss.
Everything above describes what hr & payroll teams can do with AWRA. This is where the claims are separated into what is built, what is not yet, and what we have decided is not ours to do.
What AWRA OpsHub does today
- An employee is not a user. Staff exist as records without consuming a login, and a record links to a login only for the people who need to sign in.
- Leave days are counted on your configured working week and public holidays, monthly-accrual leave types accrue on a schedule, and the same calendar drives the helpdesk business-hours clock.
- Clock-ins are checked against a GPS geofence first, with a site QR and a trusted device as further factors. A failed geofence with a valid site QR is flagged for review rather than passed.
- Overtime is derived from the shift against actual hours, and a monthly timesheet is approved and locked before payroll reads it.
- For Kenya, PAYE, NSSF, SHIF and the housing levy are maintained as versioned rule sets with effective dates, so last year’s payslips keep computing on last year’s rules.
- The P9A is rebuilt from finalised payslips and the rule versions each one used, so a certificate reproduced later matches the one issued.
- An approved run posts to the payments register per employee, with a journal posting for the run’s total net pay.
- For Kenya, a calculated run gives you upload files — a P10 CSV for iTax, the NSSF return workbook and a SHIF contribution schedule — with a readiness list naming anyone missing a KRA PIN, NSSF number or national ID. You upload each file yourself.
- Approved overtime can be priced into gross pay, switched on in HR settings, as an earning line each for working-day, rest-day and public-holiday overtime at multiples you set.
- Performance reviews run in cycles on the same employee record: a self-review, a line-manager review rating each goal and the whole, and an acknowledgement by the employee, with the manager’s ratings hidden from the employee until the review is completed.
More we can add to your workspace
- A payout rail. Approving a run records payroll as paid and writes the payments and the journal; the money itself moves however you pay staff today, and no bank file or mobile-money disbursement is produced.
- Maintained statutory rules beyond Kenya. A run for another country computes gross pay, allowances and voluntary deductions on the same engine; that country’s income tax and social security rules are the build.
- Portal submission of the return files. The P10, NSSF and SHIF files are produced and you upload them; sending them to iTax, NSSF and SHA for you, and SHA’s exact upload layout, are the build.
- 360° and peer feedback in a review cycle, with calibration across reviewers and ratings that can feed a pay review.
- A staff loan or salary-advance ledger. A recurring deduction can be given an end date today; a balance that runs down with each payslip is the addition.
Where we point you to a specialist
- We will not file or remit on your behalf. A filing obligation stays with the employer whatever the software, so what we do is make every figure reconstructable when your accountant asks.
- We will not advise on how somebody should be classified or paid. Employee or contractor, and how a benefit is treated, are questions for your adviser; we compute what the rules say and show the working.
The payout rail is the obvious build: it would hold the run as pending and settle it on a webhook, as the existing M-Pesa and Paystack vendor payment flows already do. Peer feedback, a loan ledger and another country’s rules are each a written specification, a timeline and a price agreed before any work begins.
Take one question into any payroll demo: approve a run, then ask where the money went. Here it went nowhere and the record says paid, which is correct for a system that computes rather than disburses — provided you knew it before you bought.
Modules to inspect
The AWRA surface area this team will use most.
Employees & Contracts Leave Attendance & Shifts Timesheets & Overtime Payroll & Statutory Self-Service Portals Approvals Hub Document Vault
Metrics to discuss
01
Attendance rate
02
Approved overtime
03
Timesheets locked on time
04
Leave balance accuracy
Next-best links
Enterprise resources for a serious evaluation.
Use these links for product review, implementation planning, pricing, self-serve help, and sales follow-up.
Related roles
Compare adjacent operating teams.
Owners
AWRA OpsHub helps owners see cash, stock, purchasing, sales, and risk without waiting for end-of-week reports.
Finance Teams
Finance teams use AWRA to connect invoices, receipts, stock value, purchase commitments, and reporting without chasing every department.
Procurement Teams
Procurement teams standardize requests, approvals, RFQs, vendor scoring, purchase orders, and receiving in one workflow.
Warehouse Teams
Warehouse teams use AWRA to control receiving, slotting, transfers, counts, scanner workflows, and exception approvals.
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.