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.
You can invoice in another currency, record the rate that applied and take payment in it. The ledger posts each document in base currency at its own rate and books the realised gain or loss when payment lands at another. What it keeps is one set of books — and revaluing what is still open at month end stays with your accountant.
An aging bucket measures collection risk, and that is the whole of it only while the money holds still. West Africa contains both cases at once — a currency pegged at a fixed parity and two that float — so the same report, with the same columns, means two different things depending which office you are sitting in.
The card-data question worth asking a point-of-sale vendor is not how the number is encrypted — it is whether there is anywhere to put one. Our payments table has seven columns and no card among them, which is the strongest position available and has a price we would rather state than let you find.
Collections fail between the first reminder and the first phone call. The dunning ladder sends staged messages by email, SMS and WhatsApp at the days overdue you choose, escalates to your own team, pauses for a customer on a plan — and lets a saved card pay a recurring invoice before anyone is chased.
The Marshall Islands passed a consumption tax in 2025 that applies to supplies made on or after 1 October 2026. Between those two dates sits every quotation, contract and recurring invoice a business raises — and almost no finance system can hold a rate and a date at the same time, including ours.
Four decisions hide inside every return, and collapsing them into one hurried moment is what breaks the records. Why restocking must be deliberate, how exchanges are really two transactions, and how unrecorded refunds manufacture till shortages.
Every quotation, invoice and till sale carries eight fields recording the conditions it was raised under — country, currency, tax type, rate, enabled, inclusive, exchange rate and a timestamp. Change any of those settings tomorrow and the document does not move.
In Egypt "is it localized?" has five different answers depending on which layer you mean — language, currency, tax rate, e-invoicing, working week. A layer-by-layer buyer's guide, including the one where we tell you to look elsewhere.
Overdue invoice reminders are gated by one clock per organisation rather than one per invoice. That decision is what stops credit control becoming a reason your customers filter your address — and it has a consequence worth planning around.
Every foreign-currency invoice and supplier bill carries its exchange rate, posts in base currency at that rate, and books a realised gain or loss when it is paid at another. Without a rate, nothing posts — and reports never add currencies.
A payment record carries a reference, a transaction id, an attachment, who recorded it, the balance after it, its currency and the journal entry it produced. It belongs to exactly one invoice — so one transfer settling four invoices needs four records.
In several Gulf markets a customer settles an invoice by handing over a cheque dated six weeks out. The invoice is closed as far as they are concerned, the money is not yours yet, and our receivables model has only two states.
Exposure is the opening balance plus every open invoice plus the one you are raising. What the check measures, why paying frees headroom immediately, and the setting that silently switches it all off.
The list was built where the business started, and it goes out unchanged to the other islands because nothing in the transaction suggests otherwise — same currency, same language, same group. Everything else has changed.
The cheapest sale a business can make is the second one to a customer it already has — and the reason most do not make it is that the record of the first sale lives in a salesperson's phone.
A return against last year's sale is credited at last year's rate. Our credit note holds one amount and no tax split, so it cannot express that — and nothing will tell you.
Your customer master holds what you need to know about a customer. It has nowhere to hold what your customer asserts about themselves — and some documents will not clear without it.
One invoice per student, a unique payment reference, all channels into one ledger — how bursars end the evening matching game and make arrears report themselves.
A document whose identity the state issues, a channel it nominates, and — in one market — a rounding rule it writes into law. The question here is never whether your invoicing is electronic.
A statutory pay period that is not a month, a rate that belongs to a date, three markets with no sales tax for three different reasons, and one whose tax has not started yet.
Everywhere else, voiding a document is something you do. Here it is something you ask for — and your customer can say no, or say nothing, which is worse.
Arabic and French interfaces, e-invoicing mandates, and VAT from 14% to 20%.
Page 1 of 5 · 99 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.