Start here
Useful property water billing software connects each charge to a unit, customer, meter reading and billing period, then keeps confirmed payments, outstanding balances and disputes visible. For Kenyan property managers, the priority is traceable records and clear follow-up—not a dashboard that simply shows every payment attempt as money received.
Start with the building, unit, customer and meter
A building is not a customer account, and a meter is not the same thing as a tenant. Keeping these records separate helps a property manager handle move-ins, shared areas, meter replacements and payment questions without rewriting the history of the unit.
Before choosing software, map one real workflow on paper: where the water comes from, which meter measures the building inlet, which meters serve individual units and who is responsible for each account. Record shared-area use separately rather than silently distributing an unexplained difference.
The minimum records to connect
The exact information needed depends on the property and its service arrangements. Start with records the team can maintain reliably and add integrations after the ownership and billing rules are clear.
| Record | Useful information | Why it matters |
|---|---|---|
| Unit | Building, unit label and service connection | Keeps charges attached to the right place |
| Customer | Account and relevant occupancy period | Separates the person from the permanent meter |
| Meter | Serial, type, display unit and reading source | Makes readings interpretable |
| Bill | Period, readings, rates and charge components | Explains how the amount was calculated |
| Payment | Reference, currency, state and allocation | Shows what actually reduced the balance |
Evaluate billing and payments as separate workflows
A neat invoice screen cannot explain a payment allocated to the wrong unit. Ask how the software deals with an unknown reference, a partial payment, a reversal and a transaction that is still pending. The original amount and currency should remain visible when the reporting view changes.
Also ask how the team records payments made outside the platform. A recorded cash or bank payment should retain its source and supporting reference; entering it manually does not make it a provider-verified transaction.
Make every resident message useful
A bill message should identify the unit, billing period, amount and where to get help. Payment instructions should come from the authorized property or water provider. When a customer disputes a reading, the team should be able to find the original observation and explain any correction.
Before sending a reminder, check for pending payments and open disputes. Store a draft separately from delivery status, and avoid claiming a message was delivered merely because someone pressed a send button.
Questions to ask before a pilot
A small pilot is easier to assess when the team agrees what successful records look like. Use a few representative units, including a manual meter and an account with a payment exception.
- Can a resident see only the accounts they are authorized to access?
- Can the operator explain a bill from its period, readings and charge components?
- Can a tenant change without replacing the meter’s historical identity?
- Are pending, confirmed, manually recorded and reversed payments distinct?
- Can a maintenance invoice be traced back to the reported fault?
- Can the team export records and identify the source of each value?
Try a sample workflow before connecting a property
The WaterPesa operator preview groups daily tasks into water, meters, customers and payments, maintenance and settings. Its sample records let a property team explore the order of the work before deciding which account tools and integrations it needs.
Public demos are not a connected building ledger. Live utility links, payment rails, messaging and telemetry require the relevant setup and permissions. Use the preview to assess the workflow, then verify the exact capabilities available for your property.
Common questions
Does water billing software require smart meters?
No. A workflow can use manual readings if their source, time, unit and meter identity are recorded. Features that need interval telemetry require an appropriate connected source.
Can a property manager track payments made outside the app?
A billing workflow can record external-payment evidence, but the record should remain clearly identified as manually recorded unless independently verified.
Does a provider listing mean the property is connected?
No. Finding a provider in a directory is not proof of an integration, partnership or authorization to access that provider’s accounts.
Put it into practice
Explore the workflow
Use fictional records to try the next steps. Live payments, messages and equipment connections depend on your enabled integrations.