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
Selling — quotations and orders, invoicing and credit notes, customer records and statements, receipts and collections, and point of sale with shift reconciliation.
Yes — AWRA OpsHub is available in Solomon Islands. Your organization is set up in the Solomon Islands Dollar (SBD) with Sales Tax configured on signup. We have not written a full Solomon Islands market guide yet, so this page states what configures automatically and what stays with local specialists.
Yes — AWRA OpsHub is available in Timor-Leste. Your organization is set up in the US Dollar (USD) with Sales Tax configured on signup. We have not written a full Timor-Leste market guide yet, so this page states what configures automatically and what stays with local specialists.
In Mexico an invoice goes to SAT before it goes to your customer, and comes back with a folio and the state's digital seal. We do not do that, and this page says exactly which fields we would need and which one we do not have at all.
Portugal does not only regulate what an invoice says. It regulates the program that issues it — certified by the tax authority, listed on a public register, issuing from series registered in advance. We are not on that register. Here is exactly what that rules out, what it does not, and how far the product already is.
Ireland runs five VAT rates simultaneously and the right one is a property of each line. Our schema resolves tax for the organization and gives an item two possible outcomes: the default rate, or zero. Here is exactly where that bites, and what we do not do.
A Dutch cross-border invoice has to name the buyer's VAT identification number and say in words why no VAT was charged. Our invoice document prints neither, and there is no VIES check anywhere in the product. Here is exactly what our invoice carries, what it does not, and what that means before you shortlist us.
Japan's qualified invoice system does not only say what your invoice must show. It says how the consumption tax may be rounded — once per tax rate, per invoice — and the yen has no minor unit. What our arithmetic does instead, with the figure, and the three fields a qualified invoice needs that our schema does not hold.
US sales tax is destination-based, so the rate depends on where your customer is. Our code asks who the customer is in four places and answers from the organization every time — and the customer record has no state field. Measured, published, and not sold around.
Sales tax on goods is federal; sales tax on services is provincial, levied separately by each province and the capital territory. So the authority a figure is owed to depends on what you sold. Our invoice line holds a rate and no payee — measured against our own schema, with what that costs stated plainly.
A Brazilian invoice line carries ICMS, IPI, PIS and COFINS at once — ISS instead on services — and the reform adds CBS and IBS on top for a seven-year overlap. Our invoice line holds one tax rate. What that means, measured against our own schema, and the parts of running a Brazilian operation it does not touch.
A customer statement takes everything you've invoiced and everything they've paid, lays it out in date order with a running balance, and lands in their inbox as a clean, branded PDF — for whatever period you ask for.
AWRA Document Vault gives teams a governed layer for transaction attachments, receipts, contracts, supplier files, invoice evidence, asset documents, field photos, and secure document history.
Refer, resell, or implement — and earn up to 20% revenue share for 2 full years on every client you bring to AWRA OpsHub. Built for agencies, freelancers, NGO consultants, and sales partners across Africa.
AWRA Payments & Collections helps teams record partial payments, track overdue balances, preserve receipts, follow up on collections, and keep finance visibility connected to every invoice, POS sale, and operational document.
That sounds like it should not need saying. It does, because a quiet three-day buffer is a common default and it produces the worst possible conversation: your figure and your customer's figure disagree about the same invoice, and neither of you can see why.
Blog Category All blog articles Archives Search articles in . Earlier articles No articles match your search yet — try another keyword. Articles coming soon We're writing guides right now. Meanwhile, explore the rest of the blog.
The average number of days it takes to collect payment after a sale.
Page 3 of 4 · 86 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.