Customers and service points
Maintain customer or resident details, properties, units, service locations, contacts, documents, account status, ownership or tenancy dates, and the services attached to each location.
Utility & Estate Software Kenya
Utility billing and estate management software built for Kenyan operations
Zamacore helps utility operators, estates, property companies, community managers, and service providers connect customer accounts, meters, readings, tariffs, invoices, M-Pesa collections, balances, maintenance, field work, resident requests, and reporting. Replace fragmented billing lists with one traceable account and service workflow.
Why utility and estate billing becomes difficult to control
A utility account changes through a recurring chain of events. A customer or resident is registered, connected to a service point, assigned a meter or package, billed under a tariff, receives an invoice, makes a payment, and carries a resulting balance. Readings, estimated consumption, tariff changes, adjustments, disconnections, reconnections, and account transfers introduce decisions that must remain understandable months later.
When account details, readings, invoices, M-Pesa statements, maintenance issues, and field actions live in separate tools, disputes take too long to resolve. A payment may exist but remain unmatched. A reading error may become an incorrect invoice. Staff may change balances without a clear reason. Field teams may act using an outdated list. Management cannot distinguish genuine arrears from data and allocation problems.
Utility billing software creates structured relationships between the customer, property, service point, meter, reading, tariff, invoice, receipt, adjustment, field order, and communication. Authorised users can follow the history behind a balance. Exceptions become visible before they spread into repeated billing periods, while predictable work can be automated under agreed controls.
Core utility and estate workflows
Meters and readings
Register meter identifiers, installation and replacement history, reading dates, values, readers, evidence, exceptions, and consumption calculations. Preserve the chain when a meter changes.
Tariffs and recurring billing
Apply approved consumption bands, fixed charges, packages, service charges, penalties, credits, or other billing rules by effective date and account category.
M-Pesa collections
Receive suitable payment references, allocate receipts, flag unmatched transactions, and review balances through M-Pesa reconciliation software.
Arrears and account action
Age balances, organise reminders, record promises or arrangements, approve field action, and distinguish unresolved payment allocation from genuine non-payment.
Maintenance and field service
Create work orders for leaks, faults, inspections, installations, reading checks, disconnections, reconnections, and repairs with assignments, evidence, parts, costs, and closure.
From meter reading to an explainable invoice
Meter-based billing begins with the service point and an active meter record. The system needs the previous accepted reading, current reading, date, source, and any supporting evidence. Validation can identify values that move backwards, consumption far outside the expected range, duplicate periods, missing meters, or readings entered after a replacement.
Approved readings feed tariff rules that are valid for the billing period. The calculation may include consumption bands, minimum charges, fixed service amounts, taxes, adjustments, or carried balances. The generated invoice should preserve the values and rules used so staff can explain the result even after a tariff changes.
Exceptions enter review instead of silently creating charges. An estimated reading can be marked and later corrected according to policy. A disputed meter can generate an inspection request. A replacement maintains the old meter’s closing position and the new meter’s starting record. This traceability improves customer service and protects management from unexplained account changes.
Collections, payment matching, and account governance
Payment collection becomes reliable when every transaction retains its provider reference, amount, date, account information, allocation result, and receipt history. Agreed account-number rules help identify the correct customer or service point. Transactions that cannot be matched confidently remain in an exception queue for authorised review.
Adjustments require the same discipline. Credits, reversals, write-offs, corrections, deposits, and transfers should use defined reasons, permissions, and approvals. Staff should not rewrite historical invoices or payments to make a balance appear correct. A visible adjustment trail explains who changed the account, when, and why.
Daily and period reconciliation compares provider totals, imported or received transactions, allocated receipts, unmatched payments, reversals, and account postings. Management can see whether the gap comes from collection, integration, allocation, or process. This foundation is also useful for estate rent and service-charge workflows connected through property management software.
Estate services beyond billing
Estates and managed communities coordinate more than utility invoices. Resident onboarding, unit occupancy, service charges, visitor or access processes, maintenance, common-area work, supplier activity, announcements, documents, and complaints may all depend on the same property and resident records.
A resident portal can show authorised account information, invoices, receipts, notices, and request history. Residents can report an issue with a category, location, description, and evidence. Staff assign responsibility, communicate progress, record work, and close the request. Managers can review response time, repeated faults, open cases, and service cost by area.
Not every estate needs every module. Discovery should identify which workflows create repeated administration or disputes and connect only the records required for useful service. Property, utility, security, and maintenance responsibilities should remain clear even when they share one platform.
Field operations and maintenance accountability
Reading routes
Organise service points by area or route, assign readers, track completion, capture evidence, and highlight inaccessible or exceptional meters for follow-up.
Connections and inspections
Manage approved installation, activation, inspection, replacement, disconnection, and reconnection orders with responsible teams and completion records.
Faults and repairs
Record reported issues, urgency, location, assigned technician, diagnosis, materials, work completed, cost, customer communication, and final verification.
Stores and equipment
Connect meters, parts, tools, and consumables to receiving, issue, return, adjustment, and the field order that used them through suitable inventory controls.
Workflow automation can route approvals, create field tasks, notify customers, escalate overdue work, and update account stages. Mobile access can support field teams where device and connectivity conditions have been assessed.
WiFi billing and managed access services
Some estates, operators, and community networks provide managed internet access alongside other services. The workflow may include customer registration, packages, vouchers, M-Pesa payments, access activation, router or MikroTik integration, expiry, support, and operator reporting.
Pawa WiFi billing software is Zamacore’s platform for WiFi billing, MikroTik access, M-Pesa packages, vouchers, routers, and operator reports. Buyers should review current product evidence and confirm compatibility with their network design, devices, packages, payment credentials, and support requirements.
Where WiFi is one part of a wider estate operation, integrations can reduce repeated customer and payment records. The design must still preserve which system owns network access, billing, resident identity, and financial reporting.
Management reports for reliable service
Operations teams need reading completion, consumption exceptions, open field work, installation status, maintenance response, stock availability, and service interruptions. Finance needs invoices, collections, allocation, ageing, adjustments, and reconciliation. Customer service needs account history, communication, disputes, and request status. Management needs service coverage, revenue, collection rates, losses, cost, reliability, and risk.
Dashboards should let authorised users move from a total to the underlying accounts and transactions. Which meters missed the billing cycle? Which payments remain unmatched? Which accounts have repeated estimates? Which area has unusual consumption or faults? What completed field work has not updated the account? Which tariffs or services produce unexplained variances?
For complex multi-service operations, custom ERP development can connect billing, procurement, stores, field work, customer service, finance, and management reporting under shared controls.
Implement utility software with controlled data migration
Implementation begins by identifying authoritative customer, property, service-point, meter, tariff, invoice, payment, and balance records. Duplicate accounts, missing meter history, inconsistent identifiers, unexplained adjustments, and unmatched payments need review before cutover. Automating unclear opening data creates faster disputes.
A pilot area, estate, service, or billing cycle can validate readings, calculations, invoice presentation, M-Pesa allocation, field tasks, permissions, and reports. Users test genuine exceptions such as inaccessible meters, replacements, disputed readings, partial payments, account transfers, and reconnections. Training follows the work of billing staff, field teams, finance, customer service, supervisors, and administrators.
After launch, support can cover hosting, backups, monitoring, security updates, integration handling, user assistance, report changes, and planned improvements. Zamacore’s software case studies provide operating evidence for organisations assessing implementation experience.
Build a clearer utility or estate operation
Share your services, accounts, meters, tariffs, M-Pesa setup, billing cycle, field process, maintenance needs, and reporting gaps. We will help define the most practical platform or custom implementation.
Utility and estate software questions
What does utility billing software do?
Utility billing software connects customer or resident accounts, service points, meters, readings, tariffs, invoices, payments, balances, adjustments, disconnections, reconnections, and reports. The modules depend on the utility and operating model.
Can utility software reconcile M-Pesa payments?
Yes. A suitable integration can receive transaction references, allocate payments to accounts, issue receipts, flag unmatched transactions, and produce reconciliation reports. The exact workflow depends on the Paybill, account-number rules, and credentials.
Can the system support water, electricity, WiFi, or estate service charges?
Yes. Different services can use meter-based, recurring, package, consumption, or approved manual billing rules. Each service requires clear tariff, account, billing-period, and adjustment definitions.
Can residents submit maintenance and service requests?
A resident or customer portal can capture requests, location, category, description, evidence, urgency, communication, assignment, progress, and closure. Permissions determine what residents and staff can see.
Can existing account balances and meter records be migrated?
Yes. Customers, properties, service points, meters, readings, tariffs, invoices, payments, and opening balances can be assessed for migration. Data must be cleaned, mapped, validated, and reconciled before cutover.
Can Zamacore build a custom estate or utility platform?
Yes. Custom development can support specialised tariffs, mixed utilities, estate collections, field applications, resident portals, approvals, payment integrations, access services, maintenance, and management reports.