When a municipality signs on to GovRevenue, the gap between contract and first collected dirham, riyal, or pound is measured in hours, not months. The platform is gated enterprise onboarding rather than self-serve signup, which means every rollout begins with a structured handoff from the Ukkera support team. From that point onward, a finance director or operations manager can have invoices imported, collectors assigned, and the first field visit underway before lunch. This quick-start walks through the six steps that take a municipality from an empty dashboard to a reconciled payment in roughly fifteen minutes of focused configuration work — and aligns the deployment with the Saudi Paperless Government mandate anchored in Vision 2030, the UAE Government Services 2031 agenda, and Egypt Digital Egypt, all of which expect authenticated digital records rather than paper forms.
Step 1 — Contact support to open the dashboard #
The first action is a support request. From the GovRevenue product page on ukkera.org, click the registration link, which funnels into the support queue rather than a payment page. The support team confirms the municipality name, the primary administrator, and the production environment. Within a few hours, you receive credentials to GovRevenue Manager — the analytics and decision hub for finance teams. At this stage, you should already have on hand the legal entity name (Arabic and English), the head of finance, the head of field operations, and the Saudi NDMO or UAE PDPL data-residency confirmation that determines where your tenant is provisioned. A common mistake is to begin configuring features before the tenant is correctly scoped — the support team will confirm the Google Cloud KSA region (for Saudi municipalities), the Saudi CETR compliance posture, or the UAE local data centre. Skipping this step risks a downstream data-residency conflict during an NDMO audit. Once the tenant is open and the administrator is logged in, the dashboard is empty by design — there is no demo data to clean up. Everything you build from here is real and production-grade from day one.
Step 2 — Set up the municipality as a first-class entity #
GovRevenue treats the municipality as a first-class entity on every record — invoice, license, certificate, contract, payment, and field visit. This is the structural difference between a purpose-built revenue platform and a generic invoicing tool. In the Organization & Geography module, model the parent organization, the relevant departments, the province (محافظة), the municipality itself, and the streets or districts the collectors will cover. The hierarchy is not decorative: it scopes Daily Assignments, Roles & Permissions, and reporting across the entire platform.
Under Clients & Entities, register the top revenue-generating entities you will collect from — businesses, property owners, leaseholders, utility subscribers. Each entity carries national-identity data (Absher for Saudi individuals and establishments, UAE Pass for the Emirates, Egypt Digital Identity for Egyptian governorates), tax identification, and municipality reference. The entity registry is what lets a collector in the field pull up a debtor’s complete invoice, license, and violation history in a single side panel — the Client & Invoice Panel — rather than toggling between disconnected screens.
Step 3 — Import invoices via the Import Engine #
A new municipality rarely starts with zero receivables; usually there is a backlog of unpaid invoices in spreadsheets, a legacy finance system, or paper ledgers. The Import Engine ingests these as a spreadsheet with column-mapping rules, live validation, duplication checks, and rejected-record tracking. You map each spreadsheet column to a GovRevenue field — invoice number, client, amount, tax period, municipality, revenue classification, due date — and the engine flags rows that fail validation rather than silently dropping them. Before importing, define the Revenue Catalog and Revenue Classification that scope each invoice line. These are not free-text tags; they are structured codes that feed Collection Targets by revenue × municipality, and that finance ministries expect to see in audit-ready reporting. Once the catalog is in place, the import is a single operation — a few thousand invoices become live records in the Invoice Management module, each carrying workflow state, tax fields, amounts, and municipality. From this moment, every invoice is a workflowed object, not a static line item.
Step 4 — Configure Workflow Routing #
Workflow Routing moves invoices forward by classification through click-priority steps for follow-up. An invoice classified as “overdue — high value” should reach the field collector’s queue ahead of a freshly-issued reminder; Workflow Routing is what makes that ordering deterministic. Configure the routing rules once at the municipality level — by revenue classification, by debtor segment, by amount threshold, by aging bucket — and every imported invoice inherits the right path automatically. This eliminates the dispatcher’s morning ritual of manually matching collectors to debtors.
Pair Workflow Routing with Financial Years and Collection Targets so that the year’s collection goals are visible to supervisors in real time, scoped per revenue and per municipality. A mid-sized Saudi municipality might set annual targets across trade-license renewals, plot leases, and waste-service fees; each target is importable from a spreadsheet through the same Import Engine. With routing, financial years, and targets configured together, the platform stops being a passive ledger and becomes an active enforcement engine.
Step 5 — Assign collectors and provision the Field app #
Under Roles & Permissions, define the collector role with create and view rights scoped to assignments, calls, visits, GIS Actions, and the Client & Invoice Panel — without edit rights on invoices, contracts, or settlement batches. Then add each collector as a user under that role. Collectors download GovRevenue Field — the mobile companion — to their Android device and sign in with the same SSO. The Field app immediately surfaces the collector’s Daily Assignments, Unpaid Invoices, License Lookup, and Certificate Lookup. Profile & Preferences lets each collector set language (Arabic or English) and notification preferences. For each collector, set territory and assignment weighting in Daily Assignments — a collector in Jeddah’s Al-Balad district should not receive assignments in North Jeddah, and Daily Assignments respects that boundary by routing only the in-territory queue. At the same moment, configure Push Notifications and In-App Notifications so collectors are alerted when a new high-priority assignment lands in their queue. These notifications reference the specific record and the required action, not a generic “you have updates” message.
Step 6 — Run the first field visit with Daily Assignments #
With the queue populated, a collector opens GovRevenue Field at the start of the shift and pulls up Daily Assignments. They tap the highest-priority task — an overdue trade-license renewal fee, for example — and the Client & Invoice Panel reveals the debtor’s invoice history, linked license, and any open violations. The collector places a call (logged through Call Tracking with WhatsApp contact status), then conducts a Field Visit with GPS capture and a photo of the storefront. A GIS Action verifies the trade license against the geocoded registry while the collector is still on site. Payment is recorded against the originating invoice, with the receipt queued for sync when the collector returns to coverage.
Back at headquarters, the finance manager opens GovRevenue Manager and sees the visit, the photo, the GIS verification, and the payment in a single audit trail — all timestamped and geo-located. The Settlement Batches module groups the day’s revenues and reconciles each invoice line, closing the loop from invoice to settlement. In a single morning, the municipality has gone from an empty dashboard to a fully evidenced collection — without a single paper note.