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
Bahrain's characteristic risk is not competitive or operational. It is a cross-border documentary burden sized for a much larger company, held together by one person who is very good at their job.
Bangladesh puts suppliers on one of two registers. A registered supplier charges VAT you reclaim; an enlisted one charges a turnover tax you cannot. Two quotes at the same figure are therefore not the same cost, the cheaper-looking one is usually the smaller business, and no purchasing comparison we have seen can tell them apart.
Our engine computes each Canadian levy against its own base and hands back the breakdown. The document then stores a single blended rate and discards it — so the total is right and the split, which is the only thing either return needs, is gone.
A scheme can come in under budget and be heading for a special levy, because the operating shortfall quietly ate the reserve contribution. Only line-level variance shows it — a total never will.
What VAT and Ethiopia's move toward electronic invoicing actually require of a business system — with an honest line between what operations software should do, what it should not claim, and what stays with the Ministry of Revenue and your accountant.
Four countries, four standard rates, four electronic-invoicing regimes that do not talk to each other. An orientation for a group trading across all four — what differs, what your system should handle, and why "confirm with each authority" is the only honest way to write this. Hedged; not tax advice.
The document that turns "the delivery arrived" into a fact the system can trust — what a GRN records, why it must be independent of the buyer, and how it anchors the three-way match.
Telling the system the shelf was right and the record was wrong. Done well it is an audit trail of reality; done casually it is where inventory fraud hides.
Every AI feature is a data transfer decision wearing a friendly button. The complete inventory: what each feature sends, to whom, what never crosses the boundary, and how to answer your compliance officer.
Almost every finance system stores one tax rate per country and no date. That is correct until the first credit note against a pre-change invoice, and then it is confidently wrong with nothing to warn you.
You bought twenty laptops as stock and four are now staff equipment. That is a unit leaving your stock ledger and reappearing as a tracked asset — in two phases, with an approval in the middle and a cost basis inherited from your weighted average.
A cascading tax charges tax on tax. A credit-invoice tax does not. Liberia switches from one to the other on 1 January 2027, and the five percentage points are the least interesting part of it.
Exporters and zero-rated suppliers reclaim tax rather than remit it. That makes input tax the number the whole return turns on, and it is the number most accounting systems never record as tax.
We could capture a signature in ten places and could not answer the question a store manager actually asks. Recording evidence and controlling for its absence are two different capabilities, and shipping the first one is the easy half — plus the one design decision that separates a usable exception report from noise.
Kenyan businesses make everyone an administrator in the first two weeks because it stops the complaints — and deletes the meaning of every other control. Getting back to least privilege without blocking work.
A figure nobody should have appears in a group chat. Running a report and exporting it are two separate recorded acts here — which is the distinction that makes the question answerable at all.
One page, five parts: four measured numbers, one deliberately blank, the full cost including your own hours, a paragraph on what you are not buying, and three numbers with a ninety-day review date.
Two different documents doing two different jobs, and conflating them is the most common mistake in Kenyan fixed-asset practice. Exactly which one this is, what the dashboard value trend really computes, and what that means for your year-end.
Whether MyInvois applies to you has three separate tests. Only the first is about your own revenue, and the two nobody runs are the ones that produce the surprises.
Audit Logs A tamper-evident record of what happened in your workspace — who did it, when, from where — that you can filter, export, and cryptographically verify. Audit Logs sit under Security . Every audited action writes a row holding the
Compliance Evidence Packs Build one downloadable, checksummed archive of the records an auditor asks for — audit logs, approvals, deletion history, access history, document activity and signature coverage — instead of exporting six screens
Document Vault Keep contracts, licences, certificates and policies in one classified store where every view and download is recorded — instead of in an email thread or a shared drive nobody controls. The Document Vault sits under Security .
Troubleshooting: Login Issues Use this guide when you cannot sign in, reset your password, complete MFA, find your workspace, or access AWRA after an invitation. Login problems usually come from a wrong email address, expired invitation, fo
MFA & Account Safety This Security Basics guide helps users understand safe account behavior, MFA, role visibility, and access support paths. Use this page when you need practical help with MFA & Account Safety. It keeps the older help topi
Page 6 of 9 · 210 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.