How Do You Automate Bill Retrieval for Water Utilities?
Water utilities almost never offer a way to pull billing data automatically. Electric and gas providers at least have an industry standard for sharing usage data electronically, even if adoption is spotty. Water utilities were mostly left out of that standard entirely. Deck retrieves water bill data straight from the provider’s own portal, so a workflow doesn’t have to wait for a standard that most water utilities never adopted in the first place.
How Does Deck Retrieve Water Utility Bill Data?
Deck retrieves water utility bill data by authenticating into the provider’s customer portal directly and returning the bill contents as structured JSON, regardless of whether that provider supports any kind of automated data sharing. Deck is a computer use agent platform that automates workflows by operating any web interface directly, so the target system never has to expose an API for it to work.
The retrieval runs in four steps:
- Authenticate. Deck logs into the water utility’s customer portal using stored credentials, handling whatever login flow the provider runs, from a modern SSO screen to a decades-old municipal login form.
- Locate the bill. Deck navigates to the current billing period, whether the utility presents it as an HTML statement, a locked PDF, or a scanned image behind a download link.
- Extract the fields. Deck reads usage, charges, and due dates into a defined schema, accounting for the fact that no two water utilities lay out a bill the same way.
- Return structured output. Results come back as schema-validated JSON, ready to feed a downstream billing or reporting system.
This matters because the electric and gas industry has Green Button, a standard some utilities use to share usage data automatically once a customer authorizes it. Water utilities have seen only limited adoption of anything similar. For most water providers, the portal is still the only door in.
Why Doesn’t a Data-Sharing Standard or Municipal Portal API Already Solve This?
Green Button covers a meaningful share of electric and gas utilities, but coverage among water utilities is far thinner. Many water utilities are municipally owned, run on decades-old billing systems, and were never brought into that kind of data-sharing initiative in the first place. Services built around Green Button, like UtilityAPI, work well for the utilities that participate, but they have nothing to offer for the ones that don’t, which is most water providers.
Custom scripts built against a specific water utility’s portal face the same fragility problem every scraper does, magnified by the fact that municipal IT budgets rarely prioritize a stable, unchanging interface. A script that works today can break the next time the utility’s vendor pushes an update, and small municipal providers often give little to no notice before doing so.
Manual retrieval, someone logging into each water provider’s portal and copying the bill by hand, is still the default for most organizations managing water accounts across multiple jurisdictions. It works at small scale and breaks down the moment a portfolio spans more than a handful of municipalities.
What Does This Look Like Across a Multi-State Water Utility Footprint?
A multi-site operator, think a manufacturer or a healthcare system with facilities in a dozen states, ends up with water service from a dozen different municipal or regional providers, almost none of which offer a way to pull data automatically. Getting one consolidated view of water spend means someone checking a dozen unrelated portals every billing cycle. Deck’s use cases in bill fetch cover exactly this shape of retrieval: authenticated, per-provider access normalized into one structure, regardless of what each utility does or doesn’t support.
FAQs
Does Deck work with water utilities that don’t support automated data sharing?
Deck authenticates directly into a water utility’s customer portal, so it works regardless of whether that provider supports Green Button or any other data-sharing standard.
Is Deck a replacement for a Green Button-based service like UtilityAPI?
For utilities that participate in Green Button, a service built around that standard can be a fine option. Deck fills the gap for the water utilities, which is most of them, that don’t participate at all.
What is the difference between electric utility data access and water utility data access?
Electric and gas utilities have a meaningful base of Green Button adoption to draw on. Water utilities largely don’t, which means portal-based retrieval is often the only viable path to bill and usage data.
How long does it take to set up water utility bill retrieval with Deck?
Most individual water utility integrations go live within a couple of weeks, since Deck’s authentication and extraction infrastructure already exists and adapts to each provider’s specific portal.
Ready to get started?
See how Deck can connect your product to any system — no APIs needed.
Build my Agent →