A MENA municipality serves two audiences at once. The first audience is the Arabic-speaking citizen — the small-business owner in Riyadh, the head of household in Jeddah, the clinic owner in Dammam — whose first language is Arabic and whose interaction with the municipality must be in Arabic to be legitimate. The second audience is the English-speaking expatriate business owner — the franchise operator, the regional manager, the foreign investor — whose first language is English and whose interaction with the municipality must be in English to be efficient. A revenue operation that serves both audiences has to render every invoice, every contract, every license, every certificate, every violation, every objection, every SMS notification, every PDF receipt, every portal label, and every field-collector prompt in both languages, with the same content, the same legal force, and the same audit trail. GovRevenue ships this capability natively through the Live Translations (الترجمة الفورية) module; generic forms tools and mainstream mobile-form apps bolt on Arabic as an interface language and call it bilingual, but the underlying design is not Arabic-first. This article unpacks what live translations means in practice and what generic tools fundamentally cannot do.
What Live Translations means in GovRevenue #
Live Translations is a first-class module that renders every user-facing string in GovRevenue — every field label, every dropdown option, every error message, every PDF template, every SMS template, every portal header, every field-collector prompt — in both Arabic and English, with the language switched at the user's preference. The module is not a translation layer bolted on top of an English-first platform; it is a parallel-content model where every string is stored bilingually in the schema, and the rendering layer picks the appropriate language at display time. The model extends to user-generated content: a field collector's free-text note can be entered in either language, and the supervisor viewing the note sees it in the original language with an automatic translation alongside, flagged as machine-generated for review. A client's registered business name is stored in both Arabic and English (verified against the commercial-registration registry's bilingual record), and every invoice, contract, and license renders the name in both languages on the same document.
The module's most operationally valuable feature is missing-translation tracking. Every string in the platform is tagged with its translation status — translated, missing, or machine-generated — and a dashboard surfaces every missing or machine-generated string to the localisation team for review. The tracking is what makes the bilingual model defensible: an NDMO auditor asking 'is this Arabic translation accurate?' gets a structured answer (the string is translated, reviewed, and signed off; or the string is machine-generated and flagged for review; or the string is missing and falls back to English with a visible flag). Without the tracking, a bilingual platform degrades to a partially-translated English-first platform within a year of deployment, as new fields and templates are added without translation. The tracking closes that loop and keeps the platform genuinely bilingual over time. The module also handles right-to-left rendering natively — the entire UI mirrors when Arabic is selected, with proper text direction, number formatting (Arabic-Indic digits optional), and date formatting (Hijri calendar optional alongside Gregorian).
What generic tools cannot do #
Generic forms tools — Microsoft Forms, Google Forms, Jotform, Typeform — support Arabic as an interface language, which means the form's chrome (the submit button, the navigation arrows, the error messages) renders in Arabic when the user's browser locale is Arabic. But the form's content — the field labels, the dropdown options, the help text, the PDF receipt — is whatever the form author typed, in one language. A trade-license renewal form authored in English renders its content in English even when the form's chrome is Arabic, and the small-business owner filling it out sees a hybrid that is neither fully Arabic nor fully English. The bilingual model requires the form author to author the form twice — once in Arabic, once in English — and to maintain two parallel forms, which no one actually does. The result is that the form degrades to one language within weeks of deployment. Mainstream mobile-form apps (GoCanvas, Device Magic, Fulcrum, KoboToolbox, Magpi) extend this pattern: the app's chrome is bilingual, but the form's content is one language, and the bilingual model is the author's responsibility.
Enterprise accounting platforms are no better. QuickBooks, Xero, and Sage support multiple languages including Arabic at the interface level, but the invoice template's content is one language, the tax codes are in one language, and the chart of accounts is in one language. SAP FICA has stronger multi-language support through its standard translation tables, but the configuration is a custom project, and the bilingual rendering of municipal revenue documents requires a custom Smart Form for each document type, which is exactly the kind of bolt-on work that an NDMO auditor eventually challenges. Survey123 (Esri) supports multiple languages through XLSForm's multi-language feature, but the model is the same as the generic forms tools — the survey's chrome is bilingual, but the survey's content is authored once per language, and the bilingual maintenance is the author's responsibility. The structural gap is that none of these platforms stores content bilingually in the schema; they all store it in one language and translate at display time, which means the bilingual model is the author's responsibility rather than the platform's responsibility. GovRevenue's Live Translations module makes the bilingual model the platform's responsibility, which is the only defensible design for a MENA municipal revenue operation.
A real-world scenario: a bilingual trade-license renewal cycle #
Consider a Saudi municipality running a trade-license renewal drive across a hundred thousand small businesses in Riyadh, Jeddah, and Dammam. The drive touches two audiences simultaneously: Arabic-speaking Saudi business owners (roughly 65% of the portfolio) and English-speaking expatriate business owners (roughly 35%). On GovRevenue, the entire drive renders in both languages natively. The Daily Assignments queue on each collector's device shows the debtor's name in both languages (sourced from the bilingual Clients & Entities record), the invoice amount in both Arabic-Indic and Western digits (per the collector's preference), and the next-action prompt in the collector's preferred language. The WhatsApp template sent to the debtor through Call Tracking renders in the debtor's preferred language (sourced from the client record's language preference), and the debtor's reply in either language is captured and machine-translated for the supervisor's review. The PDF receipt produced by the Payments module renders the invoice's line items, tax computation, and payment confirmation in both languages on the same document, with the municipality's seal and signature block in both languages.
If, mid-drive, the localisation team adds a new SMS template for an escalation warning, the template is authored bilingually in the schema, and the missing-translation tracking dashboard shows it as 'translated and reviewed' once both languages are signed off. If a new field is added to the Invoice Details screen — say, a 'special economic zone flag' — the field's label is authored bilingually, and the dashboard shows it as 'missing Arabic' until the Arabic translation is signed off, with the field falling back to English in the collector's UI with a visible flag. The supervisor reviewing the drive's progress at month-end sees all reports in both languages, and the ministry-of-finance report produced by Export & Reports is bilingual by default, ready for the General Authority for Statistics' national consolidation. On a generic forms tool, the same drive requires authoring the form twice (once in Arabic, once in English), maintaining two parallel forms, and hoping that the two forms stay in sync — which they do not. The drive degrades to one language within weeks, and the audit trail cannot defend the bilingual model. GovRevenue's Live Translations module is what makes the bilingual model defensible, and it is the structural reason why a generic tool is not fit for a MENA municipal revenue operation that has to serve both audiences.
Audit trail and regional fit #
The audit trail is what makes the bilingual model defensible. Every user-facing string is tagged with its translation status, every PDF and SMS is rendered bilingually, and the ministry-of-finance report is bilingual by default. An NDMO auditor asking 'is this invoice's Arabic content accurate?' gets a structured answer — the string is translated, reviewed, and signed off, with the translator's ID and the review timestamp in the audit trail. Live Translations extends to the citizen-facing portal, where the debtor can switch between Arabic and English at any point in the workflow, and the choice is preserved across sessions. The module integrates with the national-identity layers (Absher in Saudi Arabia, UAE Pass in the UAE, Egypt Digital Identity in Egypt) — the identity verification renders in the citizen's preferred language, and the verified identity record is stored bilingually. A generic forms tool cannot produce this audit trail because the bilingual model is the author's responsibility, not the platform's; a generic accounting tool cannot produce it because the content is one language at the schema level. GovRevenue's Live Translations module is what closes that gap, and it is the structural reason why a generic tool is not fit for a MENA municipal revenue operation that has to serve both audiences.
Arabic as an interface language is a chrome translation. Bilingual content at the schema level is a design. MENA municipalities need the second — and only GovRevenue ships it.