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
Six independent countries share the East Caribbean dollar and charge four different rates of VAT. No conversion, no revaluation, one price list — so nothing in a finance system signals that a second market exists, and the safeguard that stops it adding unlike currencies is exactly what hides six separate tax positions.
Colombian law makes the buyer confirm two things by electronic message before a credit purchase supports any deduction: that the invoice arrived, and that the goods did. The second is a statement about the world that only a receiving process can make — which turns the most improvised record in procurement into the one the money waits on.
Two of the reasons on your stock-issue list post revenue and cash at the item's selling price, with no customer, no invoice and no tax. Nothing in the label the storekeeper reads says which two.
Its validity is measured in kilometres, it can expire while the goods are still moving, and it is checked by a person at a roadside. Almost every failure comes from managing it as a compliance artefact.
Most board packs are assembled by hand in the four days before the meeting. What belongs in one, why a certified definition beats four accurate spreadsheets, and the four choices that make two reports disagree.
Almost every compliance obligation belongs to finance and is performed at a desk. This one belongs to the buyer and is discharged on a loading bay — by somebody who has never been told they are part of a control.
Passbooks, receipt books and cheque leaves are accountable documents, not consumables. A stock count that agrees on quantity while nobody knows which numbers went where is not a control at all.
Most approval controls ship as a settings toggle nobody finds. Expense approval switches itself on when you grant the permission — which makes the grant the policy decision, and removes the second source of truth.
Somebody leaves on Friday. Four separate things still connect their handset to your system, they are revoked in four different places, and one of them has no button at all. The actual offboarding sequence, and why the blunt step comes first.
One boolean per item decides whether VAT is added on top or extracted from within. Get it wrong on an imported catalogue and every sale is out by sixteen percent — quietly, until somebody reconciles a return.
Saint Lucia charges 12.5%, 10% or 7% depending on what is sold and who sells it — and "who" is settled by counting bedrooms. Five or more and you are a hotel. Four and you are not, on the same street, selling the same night. A hotel guest's folio carries three rates before breakfast.
Bhutan's GST commenced on 1 January 2026 at 5%. Its own Act had said 7% since 2020, and 7% was never charged for a single day — so a researcher who goes to the primary source, reads it properly and stops there publishes a forty per cent error. Going to the statute is necessary. It is not sufficient.
Cost-to-income is the one ratio every SACCO board knows and almost none can defend. Most societies could move theirs five points through classification alone — which means the number currently carries no information.
A manufacturer withdraws a lot number at four on a Friday. The question is asked in their unit and answered in yours — and if those were never connected at the receiving door, no amount of effort now can connect them. What a batch trace returns, and exactly where it stops.
A tenant asks why their receipt is numbered 58 when last month's was 41. It is a fair question with an answer — and until August 2026 the honest answer for five document types was that the missing numbers belonged to somebody else's business.
Somebody ticked "tax exempt" on a customer and the customer kept being charged. No error, nothing on screen, no reason to doubt it. The one-sentence test that separates a missing feature from a broken promise — and the afternoon that finds them in your own system.
A hand-drawn mark on a screen proves almost nothing on its own — nobody can read a signature, which is close to the definition of one. What makes it evidence is the printed name beside it, the timestamp, and one rule about when it can no longer be changed.
Withholding became an advance rather than a final tax, which turns a cost into a receivable — but only against a certificate. Where the certificates live in an inbox, the credit is unclaimable in practice and the same profit is taxed twice.
Taiwan runs two tax mechanisms inside one statute. Most businesses deduct what they paid a supplier; financial businesses cannot. The same payment is a receivable for one and a cost for the other — and nothing about that is a percentage.
A sales tax with no input credit is not a smaller VAT. It is a different animal, and treating it as recoverable builds an asset account nobody can ever collect while understating the cost of everything it should have been part of.
Colombia caps a till receipt at five UVT and Chile publishes a new unit value every single day. Both are legal limits denominated in something other than currency, so a system that stores them as an amount is not wrong yet — it is correct with an expiry date nobody wrote down, and it goes stale without any event occurring at all.
Zero-rated, exempt and reverse-charged all print as nothing and mean different things for who accounts for the tax and what can be recovered. Our schema has two values for the three, no value for the third — and charges the standard rate if you invent one.
Nauru, the Federated States of Micronesia and Solomon Islands all put nothing on the invoice line, and a system configured identically for the three would be wrong in two of them. The differences are not academic — one needs a rate per location, one needs tax carried into landed cost, and one genuinely needs nothing.
The most oversold line in Tanzanian software buying, explained straight: what TRA's EFD receipting and 18% VAT actually require, what an operations system should and should not claim, and how to buy on evidence rather than a confident tone of voice.
Page 5 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.