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 helpImplementationSecurity reviewsBilling & support
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
We use necessary cookies for secure sessions. With your permission, we also use cookies and browser storage for preferences, analytics, and demo engagement. Privacy Policy
AWRA OpsHub
Cookie settings
Cookie Consent Manager
Necessary cookies stay on for login, CSRF protection, and security. You can choose the optional categories below.
Overview
General Information
AWRA uses cookies and browser storage to keep public pages secure, remember selected preferences, measure website performance, and manage demo engagement prompts.
You can choose whether functional and marketing engagement storage apply. Analytics measurement is always active in this AWRA setup.
These settings apply to AWRA public website experiences such as the homepage, feature pages, pricing calculator, blog, help center, and request-demo page. Authenticated dashboard and vendor portal sessions still rely on required security cookies.
Required
Always active
Functional
Optional
Analytics
Always active
Marketing
Optional
For more context on privacy handling, open the Privacy Policy.
Required Cookies
Required Cookies
Always Active
Required cookies and storage support basic website delivery, secure sessions, request protection, and remembering the consent choice itself.
These cannot be switched off from this manager because disabling them would break login/session behavior, form protection, or the ability to remember the privacy choice you save.
Cookie details
Session security: keeps secure server sessions working while browsing AWRA.
CSRF protection: helps verify form submissions and protect requests.
Consent record: stores the preference decision so the banner does not keep asking after a choice is saved.
Examples: Laravel session cookies, CSRF tokens, and the AWRA consent preference record.
Duration: session security can expire with the browser/session; saved consent can last longer so the same browser remembers the choice.
Functional Cookies
Functional Cookies
Functional storage improves the public website experience by remembering interface choices, helper states, dismissed notices, and short-lived interaction preferences.
Turning this off does not stop secure required cookies or analytics. It only limits optional convenience memory.
If disabled, AWRA may show some helper prompts again or forget non-essential display choices. Core public pages, contact forms, and request-demo forms still work.
Cookie details
UI preferences: remembered display choices and helper states where available.
Dismissed notices: session-level or preference-level memory for notices the visitor has closed.
Frequency helpers: optional browser storage that prevents repeated prompts when allowed.
Examples: localStorage or sessionStorage values for dismissed banners, guide/helper states, and lightweight public-page preferences.
Effect when off: AWRA avoids optional convenience memory unless it is also allowed through marketing and engagement preferences.
Analytics Cookies
Analytics Cookies
Always Active
Analytics helps AWRA understand public page performance, traffic patterns, and content usefulness so we can improve the marketing website.
This category does not by itself enable demo popups, exit-intent prompts, or advertising pixels. Those are controlled by Marketing & engagement.
In this AWRA setup, Google Analytics and Google Tag Manager measurement are treated as mandatory website measurement and remain active.
Cookie details
Google Analytics / GTM: measures aggregate traffic and page activity.
Performance insight: helps identify which public pages, docs, and demo paths visitors use.
Operational signal: supports website quality decisions without enabling demo popups by itself.
Examples: Google measurement identifiers such as GA/GTM tags and related browser identifiers set by Google scripts.
Use: page views, source/referrer trends, public content performance, and product education page effectiveness.
Marketing & engagement
Marketing & engagement
Marketing and engagement storage supports demo prompts, exit-intent prompts, campaign attribution, and future advertising pixels.
When disabled, AWRA will not auto-open demo or exit-intent popups. CTA buttons can still open a form because that is a direct visitor action.
When enabled, AWRA can remember that a visitor already saw, dismissed, or submitted a demo prompt so the same popup is not repeated aggressively.
Cookie details
Demo prompt memory: tracks whether an auto prompt or exit prompt was recently dismissed.
Demo submission memory: avoids asking again after a visitor submits a demo request.
Campaign context: keeps source page, referrer, and UTM context available for demo requests.
Examples: popup frequency caps, demo-submitted flags, engagement source fields, and UTM/referrer context.
Effect when off: auto demo prompts and exit-intent prompts stay blocked; normal navigation and manually clicked CTA buttons still work.