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.
Implementation, onboarding, migration, demos, training, rollout, and customer success guidance.
AWRA Blog
Ask what your tax is called, not what it costs — then ask who can add a name that is missing. Five questions, four checkable in a trial account, and the first one tells most readers to skip ahead.
AWRA Blog
Ask whether tax mechanism is a property of the country or of your business — then ask whether the vendor would guess it from your industry. The right answer to the second is no.
AWRA Blog
Six markets, one currency, and three purchases that get bundled into one conversation. Two of the three are better bought locally, and one of them should be bought before us.
AWRA Blog
Five exclusions at the top rather than the bottom: no VAT numbers on the invoice, no VIES check, no reverse-charge treatment, no Belastingdienst connection, no Dutch reference customer. Then the questions worth asking everybody else.
AWRA Blog
We do not do US sales tax at all, and that is the first line rather than a footnote. Then what to ask everyone else, what to ignore, and the five things that should take us off your list.
AWRA Blog
If your last return was a claim rather than a payment, one question settles most of the evaluation. We answer it about ourselves first, and the answer is not flattering.
AWRA Blog
Stock gets counted; the financial side has no equivalent. With no manual journal entry, an opening position arrives as real documents or not at all — plus why your chart of accounts has no numbers, and where the statutory book stays.
AWRA Blog
The instinct is to bring eight years across. That is how a clean system ends up full of dirty data. The three categories of record, only one of which travels, and the four hours of deduplication that decide whether your reports mean anything.
AWRA Blog
The UAE has more competent implementers per square kilometre than anywhere else in this corpus, so the interesting question is not who can do it. It is which of three quite different products you are actually shopping for — and where an international vendor should honestly lose.
AWRA Blog
Retail and wholesale in Dar run on thin margins and fast stock. What inventory and point-of-sale software must actually do for a shop counter, a wholesale depot or a multi-branch chain — and how to tell a real capability from a slick demo.
AWRA Blog
For Kigali retailers and distributors, most of the cash is on shelves and in stores — and that is where the least visibility lives. What inventory software must do here, and how to tell a real capability from a demo.
AWRA Blog
Distributors and retailers lose more to untracked stock than to almost anything else. What inventory software must do for a Kampala warehouse or an upcountry shop floor — and how to tell a real capability from a demo.
AWRA Blog
A building becomes a project, a unit becomes a naming convention, a tenant becomes a customer. Which stand-in you pick decides what you can report for five years — and a department will quietly fail you.
AWRA Blog
A spreadsheet import here is all or nothing: one unacceptable row and the entire file is undone. That is the opposite of what most systems do, and it is right for a specific reason — a half-loaded file is worse than no file.
AWRA Blog
The application clock is one value for the whole installation, and the deployed value is Nairobi. Report schedules and workflow calendars each carry their own timezone and honour it properly. Every record stamped anywhere else does not, because there is one clock and it is not a column.
AWRA Blog
The figure you type on day one is what every future variance is measured against. Why the opening count has to be blind, what a proper count costs against copied figures, and how to value stock you are counting in.
AWRA Blog
A shirt in four colours and five sizes is twenty items, which is the correct structure for most retail rather than a workaround — but naming becomes load-bearing. The decision to make before your first five hundred items, and the variant grouping we can add if you outgrow it.
AWRA Blog
A full day in a room three weeks early teaches almost nothing, and everyone involved knows it. Twenty minutes, one role, one task, at the moment of need — plus one uncomfortable rule about who should train the storekeeper.
AWRA Blog
Go-live is the start of the work. The three numbers to record before you switch on, the four reports worth thirty minutes a week, why every threshold you configured is a guess until day 60, and the four signs it is genuinely being used.
AWRA Blog
A customer balance field is written only when somebody creates or edits the customer by hand. No invoice, payment or credit note touches it. And it is the opening balance of every statement and the base of every credit exposure.
AWRA Blog
Four permissions govern who may view, create, edit and delete a proposal. There is no proposals feature — no record, no screen, no address. The permissions describe a plan, because a plan is what a permission list is made of, and buyers read it as evidence.
AWRA Blog
How many suppliers you can keep active is governed by your plan, and switching one on at the limit is refused outright. An ordinary commercial arrangement, and an unusual thing to write about — which is why it is better read here than met mid-migration.
AWRA Blog
Building a module is the visible half of adding one. The other half is declaring it in a dozen registries that decide whether anybody can find it, search it, report on it, recover from it or be told about it.
AWRA Blog
Deleting a workspace is a thirty-day request rather than an action, it can be cancelled for as long as it has not started, and exactly three tables survive it — including the record of the deletion itself.
Page 2 of 6 · 142 articles
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.
