AWRA Help Center
Search the same approved public knowledge source used by AwraIQ. Results stay grounded in published AWRA resources, so buyers, customers, and support teams work from one source of truth.
What is new, release notes, changelog history, status updates, and product change tracking.
Human Resources — employee records, leave, attendance and time, payroll and payslips, and employee self-service.
Delivery management — projects and tasks, Kanban board and my tasks, planning and Gantt, agile sprints, time and budget tracking, and flexibility (labels, checklists, templates).
Support desk — tickets, department queues, categories and assignment, SLA timers and escalation, the public intake portal, and staff self-service (My Tickets).
Android, iOS, mobile workflows, barcode scanning, scanner bridge, and field operations.
APIs, webhooks, sync patterns, QuickBooks, connectors, and external system implementation.
Trust, security, privacy, compliance, uptime, access controls, and procurement review resources.
Pricing, plans, subscriptions, ROI estimates, billing conversations, and commercial review.
AWRA Academy courses, lessons, assessments, and verifiable certificates — learn the platform module by module.
Implementation, onboarding, migration, demos, training, rollout, and customer success guidance.
Common questions, support paths, issue diagnosis, exceptions, controls, and operational fixes.
Stock control — item master and locations, counts and adjustments, transfers and approvals, traceability and quality holds, replenishment, and warehouse operations.
Buying — requisitions and approvals, RFQs and quotation comparison, purchase orders and receiving, three-way matching, supplier prequalification, and landed cost.
Selling — quotations and orders, invoicing and credit notes, customer records and statements, receipts and collections, and point of sale with shift reconciliation.
Money — chart of accounts and journals, expenses, budgets and controls, vendor payments, the payments register, aging reports, and period close.
Asset register — tagging and custody, assignment and location history, condition and verification, maintenance, depreciation schedules, and disposal.
The supply base — supplier records and documents, performance scoring, the vendor portal and collaboration, and vendor-side self-service.
Seeing the business — the report catalog, BI Studio and custom report builder, saved filters and scheduled reports, dashboards, and predictive insights.
Making the system act — approval workflows, rules and triggers, the unified action queue, exception handling, alerts and notifications, and scheduled jobs.
Core product documentation, module explainers, operating concepts, and platform overviews.
Browse Help Sections
Each article is backed by approved public knowledge and links back to the authoritative AWRA resource for deeper context. Tap a section to expand it.
Human Resources — employee records, leave, attendance and time, payroll and payslips, and employee self-service.
AWRA Blog
Leave is the first thing employees dispute and attendance is the first thing that quietly corrupts payroll. Both are the same problem: a record that either exists when it happened, or gets reconstructed later from memory.
AWRA Blog
Two things account for most account risk in a small business: passwords one breach away from public, and accounts belonging to people who left. Why an employee record and a user account are not the same object.
AWRA Blog
The 20-minute evening routine that keeps a shop honest — cash, M-Pesa, and card reconciled against the system, shift by shift, variances named.
AWRA Blog
The businesses that supply and service mines run the hardest inventory problem in the region — critical spares nobody can quantify, consumables issued without paperwork, and tools that leave with a contractor. Including where calendar maintenance on the register stops and usage-metered plant maintenance begins.
AWRA Blog
An employee record here does not require a user account, and that is deliberate — in most of the businesses this was built for, a majority of staff have never logged into anything. Every account-shaped feature therefore covers a minority of your people.
AWRA Blog
An employee assigned to four depots needs to be inside the radius of one, not all. Three numbers decide it — a radius you set, a distance the server computes, and an accuracy the phone reports — and only two of them are yours.
AWRA Blog
The statutory stack done right, plus the NGO layer: allocating staff costs to grants, paying casuals and enumerators properly, and the monthly reconciliation triangle.
AWRA Blog
A service on a purchase order is now received by a delivery confirmation, not a check-in. Nothing enters stock, the cost is booked when the work is confirmed, and the people who sign for goods sign for work.
AWRA Blog
Clocking in requires a registered device, and an employee who has not enrolled one is refused with an instruction rather than let through with a warning. The refusal is recorded, and both routes into the clock run the same check in the same order.
AWRA Blog
What competes for a system on payroll day and at the close, what a dedicated queue and scheduler change, and what the Dedicated and Dedicated server tiers each do and do not share.
AWRA Blog
Leave arithmetic and workflow deadlines used to answer the same question differently. They now resolve through one calendar — and the interesting part is what happens when that calendar has no working days in it.
AWRA Blog
A vendor-honest guide for businesses and groups operating in more than one EAC country — why one system beats a copy per country, what "one ERP across the region" actually requires, and the straight answers on tax, e-invoicing and payroll that no platform automates identically across every border.
AWRA Blog
One event can leave the building through eight doors at once. What decides whether a chat integration is an asset or a muted channel is the four questions asked before each door.
AWRA Blog
Payroll here is maintained for one market and configurable for every other. Those are not two grades of the same feature — they are different products, and the difference is who is responsible on the day a rate changes.
AWRA Blog
HR records which department an employee belongs to. Procurement asks which department a login belongs to. Two columns on two tables — and when HR provisions that employee a login, the department does not travel with it.
AWRA Blog
Overtime here is requested, approved, locked into a period and — once you switch it on — priced through payroll at a working-day, rest-day or public-holiday multiple. What remains is putting that cost in front of the approver.
AWRA Blog
Pay from a log and the log starts being written carefully — and creatively, by the same people, for the same reason. What a payout reconciles at the moment of posting, why the direct route records a payment rather than making one, and the lock that does not cover the clock you are paying from.
AWRA Blog
Four statutory deductions, four sets of rules, and rates that move. What a Kenyan payroll run should do, why date-effective rules matter more than the arithmetic, and the reconciliation that catches errors before the money leaves.
AWRA Blog
A project here can pay the people who worked on it, through a document with its own reference, approval and posting date. That is a second way of paying somebody, running beside payroll, and neither one knows about the other.
AWRA Blog
Logging hours tells you what a job cost. It does not pay anybody. Turning unpaid logged time into money that leaves your account — without paying the same hour twice or losing the trail to the bank.
AWRA Blog
Tanzanian payroll is less about clever software and more about clean discipline: PAYE, NSSF, SDL and WCF handled consistently, records that reconcile, and honest expectations about what any system actually automates. A practical, hedged guide.
AWRA Blog
PAYE, NSSF and Local Service Tax are where Ugandan payroll gets fiddly. What a system genuinely helps with, what it does NOT automate the way Kenya's statutory payroll is, and why "confirm with URA" is the most honest line in this guide.
AWRA Blog
PAYE and RSSB contributions are where Rwandan payroll gets exacting. What a system genuinely helps with, what it does NOT automate the way Kenya's statutory payroll is, and why "confirm with RRA/RSSB" is the most honest line in this guide.
AWRA Blog
IPRES, CSS, CNPS and a collective agreement that varies by sector. The most useful thing a foreign software vendor can tell you about Francophone payroll is where its competence stops.
Page 3 of 13 · 290 articles
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.
