Do you integrate with ZATCA or the Fatoora platform?
No, and there is no partial answer hiding behind that. We do not onboard a generation unit, we hold no cryptographic certificate, we do not produce UBL 2.1 XML, we do not apply a stamp, and we make no clearance or reporting call to Fatoora. Our only fiscal e-invoicing integration anywhere in the product is Kenya's eTIMS, and it is not portable to another regime. Because the integration phase now reaches essentially every VAT-registered business in the Kingdom, this means AWRA cannot be the system that issues your tax invoices in Saudi Arabia — full stop. Confirm the scope and timing of your own obligation with ZATCA or your tax adviser; waves are notified to taxpayers directly and a vendor is the wrong source for it.
Then what does the architecture actually look like?
A ZATCA-accredited provider or a certified local package owns document issuance and clearance. AWRA runs the operation upstream and around it — procurement, stock, site materials, plant, cost and evidence. The seam is the part worth negotiating: we would insist that the UUID, hash and clearance status come back and get written onto our sales record, and that the cleared document is attached to the transaction. That single discipline is what turns "are all our sales cleared?" from an audit-week reconstruction into a report. It is also the question to put to whichever provider you pick, because not all of them will hand the identifier back cleanly, and finding that out afterwards is expensive.
Does it handle the riyal and 15% VAT?
The riyal ships as a base currency preset and 15% ships as a built-in VAT rate, with net, tax and gross separated on every sales and purchase line at the point of capture. Two honest caveats. First, we ship one maintained preset rather than a maintained rate history, and we do not interpret zero-rating, exemption or reverse-charge positions — a preset is a default you own, and the treatment is a question for ZATCA or your adviser. Second, the peg to the dollar means the riyal is rarely where your currency risk lives; it sits on what you import in, which is why foreign-currency purchases here stay in their own currency at the rate actually applied rather than a standing monthly one.
Is the interface available in Arabic?
No — English only, no right-to-left layout, and documents produced in English. We want to be blunt rather than reassuring, because this is the single most common reason we are the wrong fit in this market. In the UAE the commercial floor overwhelmingly already runs in English and it is usually a non-issue. In Saudi Arabia that is much less reliably true: Arabic is the working language for a large proportion of site supervisors, storekeepers and finance staff, and you may be expected to issue Arabic-language documents. Test it with the people who would key transactions, not with your finance director, and treat a "they will manage" as a no.
Do you produce a Mudad or WPS file, or handle GOSI and Nitaqat?
No to all of it. Our maintained statutory payroll engine covers Kenya only, so no wage file is produced for Mudad or the Wage Protection System, no GOSI contribution is calculated or remitted, no contract is registered on Qiwa, and no Nitaqat banding is tracked. This one deserves emphasis over the usual payroll disclaimer, because in Saudi Arabia these are not merely financial obligations — a missed GOSI or wage deadline can freeze services tied to your establishment, including work permits and iqama renewals, which stops hiring rather than just costing a penalty. Keep that with a Saudi payroll bureau or an HR platform wired into those portals. What travels is the employee side: records, contracts, leave with balances, and payroll cost allocated to projects and cost centres.
We are a contractor — do you handle payment applications and retention?
No, and we would rather lose the deal on this sentence than in month four. There is no interim payment application, no bill-of-quantities remeasurement, no retention held and released against a certificate, no variation register and no subcontractor back-charge workflow. Our project module is budget, hours, milestones, cost rates and cost attribution — the cost side, not the valuation side. What we do cover properly is the half that usually leaks: materials procured and received against a job, site stores as real stock locations, plant and tools under named custody, consumption attributed to the project, and offline capture that works where there is no signal. Most contractors we work with keep a measurement package for valuation and use us underneath it, which is a stable split as long as the export between them is agreed at the start.
Where does support come from, and does the working week work?
Nairobi, with remote onboarding and live training in English — and unusually, no time difference at all: Riyadh and Nairobi are both UTC+3, so your working hours and ours are the same hours. The working week does differ, and it is configured rather than assumed: set Friday and Saturday as your non-working days once and the organization's leave arithmetic, workflow due dates and escalation timers, and helpdesk response clocks all read that setting, along with the public holidays you enter. An approval deadline will not fall due on your weekend because the system assumed a Saturday–Sunday one.