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.
Assetization
Stock leaves inventory through the normal adjustment and approval path and arrives in the asset register with a custodian and a movement history, linked to the adjustment in both directions.
Automation Library
The automation library shows how AWRA can automate threshold-based triggers, vendor actions, exception routing, and operational follow-up.
AWRA Blog
A stocktake here does not change your stock. It raises adjustments somebody has to approve — so a counter can report what they counted and cannot set the record. The best decision in the module, and the three things it stops short of.
AWRA Blog
A discount at this till is four columns: the sale, the line, a free-text description and an amount. No approver, no reason code, no limit and no user. It is a record of what happened, not a control over whether it should have.
AWRA Blog
A discount at the till is an amount and a sentence — no approver, no reason code, no percentage, no person on the record. A stock write-off of the same value needs a dedicated permission and a second pair of eyes no permission can override.
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
Ten stock statuses are declared. One counts as sellable and five count as a hold. The other four are neither — so stock put into one of them cannot be sold and is reported as not being on hold, which is the worst of both descriptions.
AWRA Blog
You can record that an asset was verified. You cannot start a verification, assign it, track what is outstanding or close it. The stock module can do all four for a count — which makes this a design inconsistency rather than a missing feature.
AWRA Blog
Receiving more than was ordered is blocked. Receiving less is recorded and accepted. That asymmetry is the whole design of the check at the receiving door, and the reasoning applies to a great many controls that get built symmetrically and then bypassed.
AWRA Blog
Send a hundred, receive ninety-seven, and the system records the three. Not why, not who, not what they were worth. Returning goods deliberately does require a reason — so the intentional act must explain itself and the unexplained one does not.
AWRA Blog
A delivery confirmation counts as received in the three-way match, so an order is not ready to pay while a service on it is unconfirmed, and paying past the match needs its own permission and a reason.
AWRA Blog
An invoice is not created and sent in one act. It is drafted, approved by a named person at a recorded time, confirmed, then sent — and a customer over their credit limit stops it dead at approval. Having a lifecycle at all is the unusual part.
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
Every background job writes a row when it starts and updates it when it finishes, with its runtime, its queue, its attempt count and — on failure — the exception. The monitor is also written so it can never break the job it is watching.
AWRA Blog
Four matching tolerances on a purchase order, and every one ships at zero, so any variance at all is a discrepancy. Over-receipt is refused, payment on a discrepancy is blocked, and an override is wiped the moment the documents change and the order reconciles.
AWRA Blog
Every count records the variance on every line — quantity out, value out, held against a review threshold. Then the session closes and the numbers stop. Nothing turns a year of variances into an accuracy figure, a trend, or an answer to which site is drifting. The data is complete; the measurement was never built.
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
This product has full imprest control — a float, recorded movements, an expected balance, a count and a variance — running on the till today. Extending the same control to the back-office cash box is a straightforward addition we can make.
Page 1 of 8 · 176 articles
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.