Learn how to use active ERPat modules through role-based instructions, standard operating procedures, field legends, standards, compliance reminders, and step-by-step workflows. Every guide is synchronized from the owning module and versioned whenever its instructions change.
Showing 7 of 478 synchronized guides.
Lookup reference for ERPat Water Utility: every sidebar screen and its URL, all twenty-seven database tables grouped by purpose, the twelve status lifecycles and what each state means, the demo dataset that ships with the module, and the reports and exports available.
Answers to the questions Water Utility operators actually ask: why a screen or button is missing, why a bill will not compute or post, why a senior discount did not apply, how to fix a wrong reading or a wrong receipt, plus a glossary of the module's vocabulary.
First-run setup for the ERPat Water Utility module: run the migrations, enable the module, grant the water_utility permissions to the right roles, load the sample district with the demo seeder, and take a guided first walk through every screen.
Overview of the ERPat Water Utility module: how a water district runs meter reading, effective-dated tariff billing, official-receipt cashiering, collections, enforcement, advisories and the MyWater customer app inside ERPat.
Administering ERPat Water Utility: the fourteen module settings, the thirty-eight permission keys and the duty separations they enforce, building and approving an effective-dated tariff, official-receipt numbering, the scheduled jobs, the audit trail, and the Field Service, portal, SMS and API integrations.
Standard operating procedures for running a billing month in ERPat Water Utility: opening a reading cycle, capturing and validating meter reads, computing and posting a bill run, receipting payments into a teller batch, and working the enforcement ladder.
The evidence behind this guide: which live Water Utility module files were read, which facts were confirmed against the running database rather than assumed, the verification runs that produced the demo figures, and the open questions and gaps found while writing it.