Troubleshooting
Troubleshooting and support paths
The help center routes troubleshooting questions to published articles, AwraIQ, or human support when a buyer or customer needs more context.
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.
Common questions, support paths, issue diagnosis, exceptions, controls, and operational fixes.
Troubleshooting
The help center routes troubleshooting questions to published articles, AwraIQ, or human support when a buyer or customer needs more context.
Accounting Automation
Accounting automation improves visibility across invoices, reconciliations, reporting, and operationally linked financial controls.
Automation Library
The automation library shows how AWRA can automate threshold-based triggers, vendor actions, exception routing, and operational follow-up.
AWRA Blog
Egypt closes 30 June, Japan and India 31 March, Ethiopia on a date that is not the first of any Gregorian month. Our ledger turns out to be immune because it never modelled a year at all — and the damage is done by four convenience buttons and a handful of defaults that all assume 1 January.
AWRA Blog
The routine that proves your books and your bank agree — and the most reliable way to catch errors, missed transactions, and fraud early. Why frequency is everything.
AWRA Blog
Hospital bills, school fees, funeral costs. The most pastorally sensitive money a church handles, usually the least controlled — and the person an informal process fails to protect is the minister.
AWRA Blog
Cycle counting only works if the system can stop the sale that happens mid-count. This one does — the freeze reaches the till with a readable reason — plus blind counts, assignments and thresholds that clear the noise. One dimension is missing.
AWRA Blog
When an invoice is wrong you do not edit it — you issue a credit or debit note. Which one, who issues it, and why editing the original is the mistake to avoid (including under eTIMS).
AWRA Blog
Bamako is three days from Dakar and the truck is not a rounding error. Corridor distribution, border custody, and why the in-transit window is the number your stock report quietly refuses to show you.
AWRA Blog
Nobody ever went bust on expense claims, which is why they go unmanaged for years. The four structural gaps that make ordinary behaviour expensive, and the approval design that closes them.
AWRA Blog
First-expiry-first-out is a sentence in a procedure manual and a suggestion at the point of issue. What decides whether it actually happens is which batch the system proposes when somebody is dispensing at four in the afternoon with a queue.
AWRA Blog
A shop sells and a store issues, and the difference decides which movements the replenishment maths can see. Why a hospital store's reorder points work when the same building's pharmacy counter stays silent — and the ward dimension you have to choose before go-live.
AWRA Blog
The generator that failed had been serviced twice in four years and nobody could say when. Maintenance as a recorded movement, the rising-frequency pattern that decides repair versus replace, and why there is no scheduler.
AWRA Blog
A second shop doubles your revenue and quadruples your blind spots. What breaks when a Nigerian retailer goes from one location to several, and the controls that decide whether the third branch makes money or quietly consumes it.
AWRA Blog
Every vendor says yes to "does it work offline". The word bundles six unrelated capabilities and a product can hold any subset of them. Here is the operation-by-operation list for AWRA — including the till, which needs a connection — and the questions that make every other vendor be equally specific.
AWRA Blog
One question, two modules, and the report builder will not answer it. Why a report is built on exactly one dataset, the silent error that constraint prevents, and the thirty-four prebuilt reports that exist because of it.
AWRA Blog
EAC currencies differ in unit value by roughly thirty times, so adding two of them together produces a number that looks reasonable and is wrong by an order of magnitude. Three ways a system can answer "what did we spend", only one of them honest — and a report of ours that adds Ugandan shillings to Kenyan ones and calls a budget breached on the result.
AWRA Blog
Vendors sell "Southern Africa" as one market. It is four buying problems wearing one label — a replacement decision in South Africa, a support-depth decision in Botswana, a currency-discipline decision in Zambia, and a record-what-happened decision in Zimbabwe.
AWRA Blog
Small money, large risk — the place where controls are weakest and leakage most common. The simple imprest system that keeps small cash honest without smothering it.
AWRA Blog
A requisition is an internal request to buy; a PO is an external commitment to a supplier. Confusing them is how organizations get bound to spend nobody approved.
AWRA Blog
The batch loop — plan, issue, produce, receive, reconcile — and the two numbers per batch that separate measured processors from hopeful ones.
AWRA Blog
Stock is where most Kenyan businesses keep the largest share of their working capital and the smallest share of their attention. The six controls that account for nearly all recoverable loss, in the order they pay for themselves.
AWRA Blog
An auditor asks to see one that was refused. Our product answers that well in the two places it records decisions properly — item master changes and deletions, both with segregation of duties. In the generic workflow engine, which has by far the richer approval model, the approver receives a task whose four states do not include yes or no.
AWRA Blog
Our budget module gets the hard part right: money leaves a budget when the order is approved, not when it is paid, and a cancelled order releases the commitment. What it does next is the part to know about — it works out that you are over, approves the request anyway, and sends a notification explaining why. A control refuses; this one explains.
Page 1 of 6 · 129 articles
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.
