Your First Field Collection on GovRevenue: A Quick Guide

The first field collection a municipality runs on GovRevenue sets the tone for every collection that follows. Done well, it shows collectors that the system removes friction rather than adding it; done poorly, it sends them back to paper notes within a week. This guide walks through the collector’s first visit, step by step, using the modules a municipal collector touches every day: GovRevenue Field, Daily Assignments, Call Tracking with WhatsApp status, Field Visits, GIS Actions, and Payments. The whole loop — from opening the app to recording a reconciled payment — can run inside thirty minutes of focused work, even on a poor connection.

Step 1 — Open GovRevenue Field and view Daily Assignments #

The collector signs in to GovRevenue Field — the mobile companion built for collectors — using the same SSO as the back-office team. The home screen surfaces the day’s Daily Assignments: a list of inbound collection tasks routed to this collector by territory, debtor, invoice type, and follow-up priority. Each task already carries call, visit, and GIS actions on the assigned record — there is no need to search for the debtor or guess which invoice to chase first. A high-priority task — say, an overdue trade-license renewal fee for a shop in the assigned district — appears at the top of the queue.

Tapping the task opens the Client & Invoice Panel — a side panel showing the debtor’s details, their full invoice history, linked licenses, and any open violations. The collector knows, before leaving the office, the invoice amount, the original issue date, the linked trade license, and whether the debtor has previously objected to the invoice through the Objections module. This context is what turns the visit from an awkward knock on the door into a structured enforcement conversation.

Step 2 — Call the debtor and log via Call Tracking with WhatsApp status #

Before driving to the site, the collector places a call. Call Tracking logs every client call with three fields that matter for downstream audit: outcome, reason, and WhatsApp contact status. WhatsApp is the dominant B2C channel in MENA, and treating it as a first-class contact status — rather than a free-text note — is what makes the call log useful to a supervisor reviewing the day. The collector selects an outcome (reached, no answer, wrong number, deferred), a reason (payment reminder, license renewal, objection follow-up), and a WhatsApp status (sent, delivered, read, replied).

If the debtor answers, the collector confirms the visit window and the amount due. If not, the collector sends a WhatsApp message through the linked number — the WhatsApp status then drives the next routing decision in Workflow Routing. A read receipt is treated differently from a delivered-only message, which is treated differently from a reply. This is how a MENA debt-collection operation gets a structured contact history rather than a pile of disorganized phone notes.

Step 3 — Conduct the Field Visit with GPS and photo capture #

On arrival, the collector opens Field Visits and starts a new visit record against the assigned task. The Field app captures geo location from the device GPS chip — not from a network-based lookup, so coordinates are accurate even in basements or rural plots without coverage. The collector photographs the storefront, the trade license, and any supporting documents through Photo & Document Capture. Each photo is geo-tagged and timestamped automatically; the collector does not type coordinates or note times manually.

If the debtor disputes the invoice during the visit, the collector uses Invoice Extensions to record the amendment type and reference, and the Objections module to track the objection against the originating invoice. Both actions are timestamped and linked to the visit, so a supervisor reviewing the day can reconstruct the conversation. The collector’s job is to capture evidence — not to adjudicate the dispute on the street. The platform’s job is to make that evidence audit-ready by the time it syncs.

Step 4 — Verify the license via GIS Actions #

Before leaving, the collector runs a GIS Action to verify the trade license against the geocoded municipality registry. GIS Actions pairs the field device’s GPS with a geocoded license registry and requires a photograph of the certificate. If the certificate photograph matches the registry entry for this location, the verification passes; if not, the platform flags a mismatch and routes the case for supervisor review. This is the difference between a collector who can only photograph a paper certificate and one who can verify it against the source of truth while still on site.

GIS Actions also handles certificate verification through Certificate Lookup — useful when a debtor presents a health certificate, a fire-safety certificate, or a municipal occupancy certificate rather than a trade license. Both verifications are timestamped and linked to the originating license or certificate record. For an auditor, this produces an evidence chain that begins with the assignment, runs through the call, the visit, the photograph, and ends with the GIS verification — all in a single audit trail under the Visits & Activities ledger.

Step 5 — Record the payment against the originating invoice #

If the debtor pays — by card terminal, cash, bank transfer, or another approved channel — the collector opens Payments and records the payment against the originating invoice. The payment carries amount, payment date, client, and revenue line item. This is the structural difference between a revenue platform and a generic form tool: the payment is linked to the invoice at the data-model level, not reconciled manually in a spreadsheet later. Settlement Batches then groups the day’s revenues and reconciles each invoice line, closing the loop for the finance team back at headquarters.

If the connection drops during the visit — common in dense urban canyons, basements, or rural plots — Offline Resilience keeps the collector working. Every interaction writes locally first and joins a persistent queue that drains automatically when coverage returns. The collector sees a clear badge on each queued record (pending, syncing, synced, failed); the supervisor sees the same status in GovRevenue Manager. There is no “the form didn’t submit” failure mode that pushes the collector back to paper.