IDARMS – User Manual & Testing Guideline

Overview

This manual documents the functionality of the iDARMS (Integrated District Assembly Revenue Management System) applications so the client/QA team can understand each screen and verify expected behaviour before sign-off.

There are five applications:

App	Used By	Type	Core Purpose
iDARMS Back Office	Internal Staff	Web (Admin)	Entity management, property registration, billing, payments, accounting, GIS mapping, dispute resolution, system configuration
Rate Payer Portal	Rate Payers / Citizens	Web Portal	Manage properties, view/pay bills, track payment history, raise disputes, view reports
LVD Portal	LVD Partners	Web Portal	Import LVD data, view property rates, manage rate information
Rate Payer App	Rate Payers	Mobile App	Add properties, view property details, pay bills, track payment history
Agent App	Field Agents	Mobile App	Add properties, manage billing on behalf of rate payers, inspect properties, and more

!!! info "How to use this guide" Each page below covers one screen or flow. It explains what the screen does, describes every field/element, and lists what should be verified during testing.

Where to Start

Web Applications

Mobile Applications

Application Relationships

iDARMS Back Office (idarms_frontend)
      │
      ├── Manages system data, entities, properties, billing
      │
      ├── Rate Payer Portal (ratepayer_portal)
      │     └── Rate Payer / Property / Bills / Payments / Disputes
      │
      └── LVD Portal (partners_portal)
            └── LVD Import / Rate Data Management

Terminology

Term	Meaning
iDARMS	Integrated District Assembly Revenue Management System
Rate Payer	Property owner registered in the system (two words, capitalized)
MMDA	Metropolitan/Municipal/District Assembly
GIS	Geographic Information System
OTP	One-Time Password
LVD	Land Value Division (property rate data)
GHS / GH₵	Ghana Cedis
POS	Point of Sale