These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Water Utility Management
- Implementation and migration
How a Water Utility Management rollout works
Start with one billing cycle for one organization, reconciled to your current system.
Agree the operating boundary
The system holds meter runs, accounting documents, reviews, journals, periods, cash and operation receipts. Meter reading, payments, supply monitoring and leak detection stay in connected systems. The utility decides tariffs, credit policy and adjustments.
Map the source data
Agree record numbers, partner codes, account codes and the period calendar. Load open documents, opening balances and unapplied receipts.
Configure a bounded pilot
Run one billing cycle for one organization: meter runs, charges, review, posting and cash application.
Rehearse the exceptions
A repeated operation must not post or apply twice, cash must not be applied beyond the receipt or the balance, a preparer cannot approve their own document, and posted scope is corrected only by a compensating entry.
Reconcile and release
Compare charges, ledger totals and balances with your current system, get sign-off from the controller and agree the rollback window.
What the customer provides
- Organizations with currency and timezone, and the team with their roles.
- Chart of accounts, business partners and the period calendar.
- Tariff revisions and recent meter readings.
- Open documents, opening balances and unapplied payments.
Changing it afterwards
Use Proto to prepare changes on a branch. Review changed fields, permissions and reports with the controller and replay the pilot’s exception cases before release. Posted history keeps the rules that applied when it was posted.
Set up Water Utility Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.