Currency & Billing
How pricing and currency work in AWRA: clear plan pricing, paying in your local currency, and viewing your figures in a currency you prefer.
AWRA keeps money clear and consistent. Your business works in a single currency for all its records, while you can choose to view figures in another currency on screen for convenience.
Who Uses This Page
- Organization admins choosing a display currency.
- Anyone reviewing dashboards, reports, and lists.
- Anyone with a question about plan pricing.
Your Organization Currency
Your organization works in one currency, based on your country. All your records — sales, invoices, quotations, purchase orders, and payments — are kept in that currency, which keeps your books consistent. You can see it in Account → Organization settings. If you ever need it changed, contact the AWRA team.
Viewing Figures in Another Currency
You can set an optional display currency for your organization. When set, dashboards, on-screen reports, and list views show your figures in that currency as a clearly-marked approximate value, so you can read totals in a currency you think in.
- Open Account → Organization settings.
- Choose a Display currency, or leave it blank to keep your own currency.
- Save. Dashboards, reports, and lists now show the approximate amounts.
- To switch back, clear the display currency.
What Always Stays the Same
The display currency only changes what you see on dashboards and lists. Your official documents always remain in your organization currency:
- Invoices and receipts.
- Customer statements.
- Accounting and reports you export.
- Every PDF.
Plan Pricing & Payment
AWRA subscription plans are shown in US Dollars as a simple reference price, and you pay in your local currency using familiar methods such as M-Pesa and card. Annual plans include one month free.
Partners
In the partner portal, partners are paid in their local currency and can also choose a display currency to view their figures in a currency they prefer.
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.