AWRA OpsHub Search

AWRA Help Center

Find answers, support paths, and rollout guidance fast

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.

Product help Implementation Security reviews Billing & support
Friendly support team helping users find the right answer
3550
Articles
20
Help sections
IQ
Bot-ready

Browse Help Sections

Docs, guides, troubleshooting, billing, security, integrations, mobile, and releases

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.

Show all sections

Troubleshooting

211

Common questions, support paths, issue diagnosis, exceptions, controls, and operational fixes.

AI Data Controls

Switching third-party AI off

Under Settings › AI & Data an administrator switches third-party AI off for the whole organization; nothing is then sent to an AI provider from any in-app feature, and features show their figures without the written summary. The page lists the providers in use and a 30-day log of calls by provider and purpose, never their content.

AWRA Blog

Every Variance and No Score

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

A Financial Year That Does Not Start in January

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

A Discount Nobody Had to Authorise

Many tills record a discount in four columns — a record of what happened, not a control over whether it should have. Here it carries a user, a workspace limit and an approver by PIN. The reason is typed, and recording versus governing is the question to ask of any till.

AWRA Blog

Branch, Department and Project on Every Journal Entry

A ledger can only report by what is on the entry. Every journal entry here carries a department, a branch and a project beside its account, so the income statement reads profit by any of them — and that decides which questions are possible.

AWRA Blog

A Shortfall That Carries a Name

Send a hundred, receive ninety-seven, and a system that records only the three has recorded nothing worth knowing. Here a short receipt has to explain itself — a reason, who is responsible, and the value fixed at receipt — the same way a deliberate return does.

AWRA Blog

Every Tolerance Ships at Zero

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

A Short Delivery Is Not a Refusal

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

Counting the Shop Without Closing It

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

A Register Is a Rhythm, Not a Record

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

An Invoice That Has to Be Approved

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

Every Background Job Leaves a Row

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

A Hold That Does Not Report as One

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

A Count That Writes Nothing

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 Three-Way Match for Work You Cannot Count

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

Expense Claims & Approvals: Stopping the Slow Leak

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

Benevolence Without Exposing the Pastor

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.

Assetization

Turn stock into a tracked asset

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.

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.

Automation Library

Automation examples

The automation library shows how AWRA can automate threshold-based triggers, vendor actions, exception routing, and operational follow-up.

Accounting Automation

Accounting workflows

Accounting automation improves visibility across invoices, reconciliations, reporting, and operationally linked financial controls.

Page 1 of 9 · 211 articles

Still need a human answer?

For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.