AWRA OpsHub Search

For Egypt

The operations layer, alongside whatever handles your compliance

We do not integrate with the Egyptian Tax Authority, our interface is in English, and Egyptian statutory payroll is not ours. What we do run is everything underneath: stock that is true continuously, procurement that refuses, route and cash custody, and imported cost measured at the rate that actually applied.

Sound familiar?

If any of these ring true, you are exactly who this was built for.

A cost that was never real

Goods priced at the rate assumed when the order was placed, paid weeks later at a different one, with duty and clearing arriving later still. The margin looks fine and was gone before the first sale.

A van full of stock the system has no word for

Loaded in the morning, cashed up at night, and forty drops in between that nobody recorded — so a shortfall has forty explanations and no evidence.

Two systems that both think they own the stock

A compliance product and an operations product with no written boundary between them is the most reliable way to end up trusting neither.

Evidence assembled under pressure

The quote, the approval, the delivery note and the invoice all exist — in four places, held by three people, retrievable only by whoever remembers.

How teams get started

1

Settle your fiscal layer first

Establish your ETA obligation with the authority or your adviser and choose whatever satisfies it. Every other decision here is downstream of that answer.

2

Draw the boundary in writing

Customers, items, prices, stock, invoice numbering — one owner each, agreed before go-live and visible to both vendors. This is the step that decides whether two systems is stable or painful.

3

Then run a real month

Your sites, your routes, your imports and your approval chains, on your data, with training for the people who key transactions rather than the people who read reports.

Frequently asked questions

Do you integrate with ETA electronic invoicing?

No, and we would rather lead with that than have you find it in month three. There is no connection to the Egyptian Tax Authority of any kind — nothing is structured, submitted, registered or retrieved, and no e-receipt is produced. Our only fiscal e-invoicing integration is Kenya's eTIMS and it is Kenya-only. Where an Egyptian obligation applies to you, a separate compliant solution handles it and AWRA runs the operations layer alongside it. Confirm the scope and timing of your own obligation with the ETA or your tax adviser.

Is the interface available in Arabic?

No. The interface is English only, there is no right-to-left layout, and documents such as invoices and purchase orders are produced in English. This is a genuine limitation rather than a setting, and for organizations whose warehouse, route or branch staff work in Arabic it is likely to be disqualifying — in which case an Egyptian vendor is the better purchase and we will say so. For organizations whose back office works in English it is usually a non-issue. Test it with the person who will actually key transactions.

Does it handle the Egyptian pound and VAT?

The pound and an Egypt VAT rate ship as built-in presets, and every sales and purchase line separates net, tax and gross at the point of capture. Foreign-currency purchases record the rate actually applied to that transaction rather than a standing rate, and landed cost folds duty, freight, clearing and inland transport into true unit cost. We ship one maintained VAT preset rather than a maintained rate history; additional tax lines are configurable but yours to keep current. Confirm all rates and treatment with the ETA or your adviser.

What about Egyptian payroll?

Our maintained statutory payroll engine covers Kenya only. Egyptian income tax withholding and social insurance are not calculated, no statutory output is produced, and nothing is submitted or remitted on your behalf. We recommend an Egyptian payroll specialist for that layer, with AWRA holding employee records, attendance, leave and payroll cost allocation to projects and cost centres.

Does the system know the Egyptian working week?

Once you set it. Non-working days are configured per organization, so ticking Friday and Saturday makes leave-day arithmetic and the attendance present-rate average follow the Egyptian week. Public holidays are configured separately. Two limits worth knowing rather than discovering: workflow due dates read their own business calendar, which has to be set to match, and ticket SLA targets and ageing buckets count elapsed calendar time rather than working days.

So when does AWRA make sense for an Egyptian organization?

When your fiscal obligation is already handled by a compliance product or a local specialist, your back office works comfortably in English, and your real problem is operational — stock across sites, route and cash custody, procurement governance, imported cost, assets, or project and donor attribution. That is a real and reasonably common shape, particularly for importers, distributors, international organizations and group subsidiaries. Outside it, buy locally.

Where does support come from?

Nairobi, with remote onboarding and live training in English. Cairo is one hour behind us, so your working day overlaps ours almost entirely.

Find out quickly whether we fit

Tell us your fiscal arrangement and your working language. In one call we can usually say whether the operations layer is worth discussing or whether you should buy from an Egyptian vendor.