Can meter reads be accepted electronically?

Yes. Electronic records that show intent, attribution, and reliable retention are admissible under the federal ESIGN Act (15 U.S.C. ch. 96) and most states' UETA frameworks; check state rules for any narrow exceptions.

Are signed attestations legally enforceable?

Electronic attestations that meet intent, consent, attribution, and retention requirements are generally enforceable under ESIGN/UETA. For consumer-facing contexts, ensure any required consumer-disclosure under 15 U.S.C. §7001(c) is provided.

How long must meter-data be retained?

Retain billing and financial records for at least 3 years to meet IRS expectations (IRC §6501(a)); if records include protected health information, follow HIPAA retention rules (45 CFR §164.530(j)) for 6 years.

What if a customer disputes a reading?

Follow the published dispute process, preserve original evidence, run anomaly checks, and document adjustments. Many utilities set a 30-day window for corrections or customer-initiated reviews.

Is notarization or witness required for meter data?

Not typically. Meter reads and attestations rarely require notarization. If a specific jurisdiction or contract requires notarized affidavits, follow local notary law and RON requirements where applicable.

How should I correct submitted data?

Submit a documented correction with the original read reference, corrected value, reason for change, and reviewer identity. Maintain both original and corrected records for auditability.

Electronic Signature
Templates
Miscellaneous
Water Utility Meter Data

Water Utility Meter Data

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

WATER UTILITY METER DATA AGREEMENT

This Water Utility Meter Data Agreement (the Agreement) is made and entered into as of , by and between Utility Company: with principal address (Provider), and Data Recipient: with principal address (Recipient).

WHEREAS

WHEREAS, Provider operates water meters and associated metering systems and collects usage, interval and related telemetry data from such meters; and

WHEREAS, Recipient requires certain meter data for the Permitted Uses defined below and Provider is willing to supply such meter data subject to the terms and conditions of this Agreement; and

WHEREAS, the parties desire to set forth the scope, delivery, confidentiality, retention and payment terms applicable to the meter data exchange.

SCOPE OF WORK

Summary of Data to Be Provided Specific Meter Identifiers or Accounts Data Elements and Format

DATA DELIVERY, FREQUENCY AND FORMAT

Delivery Frequency: | Delivery Format: | Delivery Method:

Data Time Range Start: Data Time Range End:

ACCURACY, VALIDATION AND SUPPORT

Provider represents that meter readings will be supplied in accordance with Provider's standard metering practices and with a nominal accuracy tolerance of . Recipient shall notify Provider in writing of any material data defects within days of receipt to permit validation and remedial action.

PAYMENT TERMS

Compensation for delivery, processing and support shall be:

Fee Amount (per billing period or total) Payment Schedule

Late payments shall incur interest at the lesser of (a) or (b) the maximum rate permitted by applicable law.

TERM AND TERMINATION

Term Start Date:

Term End Date:

Either party may terminate this Agreement for the other's material breach if such breach remains uncured for a period of days after written notice. Either party may terminate for convenience upon days' prior written notice.

CONFIDENTIALITY

"Confidential Information" means non-public information disclosed by one party to the other in any form, including meter-level usage data, account identifiers, security credentials, and system configurations. Recipient shall (a) hold Confidential Information in strict confidence using at least the same degree of care it uses to protect its own confidential information; (b) use Confidential Information solely for the Permitted Uses described in this Agreement; and (c) not disclose Confidential Information to any third party except to those employees, contractors or agents with a need to know who are bound by confidentiality obligations no less restrictive than those herein. The obligations in this section survive termination for a period of five (5) years, except that personally identifiable information and account-level data shall remain subject to confidentiality for as long as retained.

Permitted Use (briefly describe)

DATA OWNERSHIP, LICENSE AND ACCESS

Provider retains all right, title and interest in and to the raw meter data provided hereunder. Provider grants Recipient a limited, non-exclusive, non-transferable license to use the data solely for the Permitted Uses during the Term. Recipient shall not sell, sublicense or otherwise make the raw meter data available to third parties except as expressly authorized in writing by Provider.

Indicate whether Provider or Recipient is data owner for regulatory purposes: Provider is Data Owner Recipient is Data Owner

SECURITY AND PRIVACY

Provider shall deliver data via secure transmission and implement reasonable technical and organizational measures appropriate to the sensitivity of the meter data, including encryption in transit and at rest where applicable. Recipient shall implement and maintain safeguards to prevent unauthorized access, disclosure or use of the data. Any security incident affecting Confidential Information must be reported to the other party within hours of discovery.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of , without regard to its conflicts of law rules.

LIMITATION OF LIABILITY

Except for willful misconduct or gross negligence, neither party shall be liable for incidental, consequential, special or punitive damages arising from the performance or non-performance of this Agreement. Each party's aggregate liability for any claim arising out of or relating to this Agreement shall not exceed the total fees paid by Recipient to Provider under this Agreement in the twelve (12) months preceding the claim.

ENTIRE AGREEMENT

This Agreement, including all attachments and referenced schedules, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, proposals and communications, whether written or oral, relating to the same. Any amendment must be in writing and signed by authorized representatives of both parties.

MISCELLANEOUS PROVISIONS

If any provision of this Agreement is found invalid or unenforceable, the remaining provisions shall remain in full force and effect. Neither party may assign this Agreement without the prior written consent of the other, except to an acquirer of substantially all of the assigning party's assets.

Provider (Utility Company) Printed Name:

By:

Date:

Recipient Printed Name:

By:

Date:

What the Water Utility Meter Data Records

Water Utility Meter Data is a structured record that captures a meter identifier, service address, account number, meter reading, read date and time, meter type, and the method of capture. Utilities, property managers, and contractors use these records for billing, consumption analysis, leak detection, regulatory reporting, and service verification. Records may be created from manual reads, automated meter reading (AMR) devices, or advanced metering infrastructure (AMI). Electronic delivery and storage are common; electronic versions must preserve the reading, timestamp, and attribution to be reliable for billing or audit purposes.

Why accurate meter data matters to operations and compliance

Accurate Water Utility Meter Data reduces billing disputes, supports timely revenue recognition, enables leak and consumption analysis, and ensures consistent regulatory reporting across jurisdictions.

Typical users and stakeholders for meter-data records

Multiple groups rely on Water Utility Meter Data to operate, reconcile, and report usage accurately.

Utility billing teams responsible for invoicing, rate application, and account reconciliation.
Property managers and landlords who allocate usage across tenants or properties for billing.
Field technicians and meter-read contractors responsible for collecting and validating readings.

Clear ownership of data collection, review, and retention reduces disputes and supports regulatory compliance.

Simple steps to collect and submit a meter reading

Follow a consistent sequence to capture a valid reading, confirm attribution, and deliver the record for billing.

01

Verify Meter: Confirm meter ID and account match before reading.
02

Record Reading: Enter numeric value and unit exactly as displayed.
03

Timestamp and Method: Add date/time and select the capture method.
04

Validate & Submit: Run validation rules, correct errors, then submit to billing.

How to set up an online meter-data workflow

Configure automatic checks, notifications, and attachments to reduce manual corrections.

Field	Configuration
Account Auto-fill	Pull meter and account data from the customer database
Conditional Fields	Show error-code fields only when anomalies are flagged
Validation Rules	Enforce numeric ranges and unit consistency
Notifications	Email or SMS alerts for failed reads or manual review

Typical routing for submitted meter-data records

Meter-data records typically move from capture to validation, billing, and archival in defined system flows.

Capture: Collected in field app or AMI feed and tagged with device ID
Validation: Automated checks flag outliers and missing fields
Billing: Validated reads are posted to billing and invoicing systems
Archive: Finalized records are stored for audit and regulatory reporting

System and format considerations for electronic meter data

Ensure the capture and delivery platform supports required formats, integrations, and secure transport.

File Formats: PDF, CSV, XML, JSON, and XLSX are commonly supported for bulk ingestion and archival
Integrations: Connectors with billing and ERP systems such as Salesforce, NetSuite, Microsoft 365, and Google Workspace facilitate automation
Security: TLS 1.2/1.3 in transit and AES-256 at rest meet common utility security expectations

Select a platform that preserves timestamps, audit trails, and allows secure batch transfers to billing and regulatory systems.

Common timing expectations and reporting windows

Timing varies by utility and jurisdiction; establish clear internal deadlines for reads, corrections, and dispute response.

Monthly Read Cutoff:

Submit final validated reads per billing cycle — typically within 1–7 days after cycle close

Correction Window:

Most utilities allow read corrections or adjustments within 30 days of initial posting

Dispute Response:

Respond to customer disputes within 30 days to avoid billing credits

Regulatory Reporting:

Quarterly or annual reports may be required depending on municipal rules

Retention Start:

Retention clock begins on the read date or invoice date, depending on policy

Key milestones in the meter-data processing timeline

Milestones ensure reads are captured, reviewed, and posted in a predictable sequence.

01

Schedule Reads

Define recurring windows for AMI polls or field visits.

02

Capture Data

Collect readings with device ID and timestamp.

03

Validate Anomalies

Flag and investigate outliers and communication errors.

04

Finalize Billing

Post validated reads to billing and archive records.

Common errors that cause billing disputes or processing delays

Transposed or truncated meter IDs leading to misapplied reads and incorrect billing.
Recording readings with wrong units (gallons vs. cubic feet) or missing decimal placement.
Missing or inconsistent timestamps that prevent proving when the read occurred.
Failure to document capture method or device ID, making audits and warranty claims difficult.

Consequences of inaccurate or late meter-data submissions

Billing Adjustments: Customer credits or refunds may be required

Regulatory Fines: Fines or corrective orders for missed reporting

Contract Liability: Breach claims if contractual SLAs are missed

Operational Costs: Increased field visits and manual audits

Data Privacy: PII exposure risks if records include account-holder details

Loss of Trust: Customer disputes and service complaints increase churn

Use-case examples showing typical meter-data workflows

Two representative scenarios showing how organizations capture, validate, and act on meter readings.

Municipal Water Department

A municipal utility schedules AMI polls daily to monitor consumption spikes

AMI flags anomalies for field follow-up
Finalized reads feed billing, regulatory reports, and a time-stamped archive for audits and customer inquiries.

Multi-Unit Property Manager

A property manager performs monthly manual reads with a mobile app

App validates meter IDs and units at entry
Validated readings are posted to the accounting system and tenant invoices are generated with attached read evidence.

Practical practices to improve accuracy and reduce disputes

Adopt repeatable checks and clear ownership for each stage of the meter-data lifecycle.

Standardize formats and units

Define and enforce consistent number formats, unit designations, and timezone rules to avoid conversion errors across systems and reports.

Use automated validations

Implement range checks, threshold alerts, and duplicate-detection to catch improbable reads before billing.

Preserve audit trails

Record device ID, reader name, timestamp, and method so each read can be attributed for disputes and regulatory review.

Document correction policies

Publish clear procedures and windows for read corrections and dispute handling to reduce escalations and customer friction.

eSignature vendor comparison for submitting and signing meter-data records

Compare typical plan characteristics for platforms used to capture or attest to meter-data records; signNow is listed first per comparison conventions.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	Yes, 7-day free trial	No	No	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Frequently asked questions about Water Utility Meter Data

Answers to common operational, legal, and technical questions about collecting and submitting meter-data records.

Need help? Contact support

Can meter reads be accepted electronically?
Yes. Electronic records that show intent, attribution, and reliable retention are admissible under the federal ESIGN Act (15 U.S.C. ch. 96) and most states' UETA frameworks; check state rules for any narrow exceptions.
Are signed attestations legally enforceable?
Electronic attestations that meet intent, consent, attribution, and retention requirements are generally enforceable under ESIGN/UETA. For consumer-facing contexts, ensure any required consumer-disclosure under 15 U.S.C. §7001(c) is provided.
How long must meter-data be retained?
Retain billing and financial records for at least 3 years to meet IRS expectations (IRC §6501(a)); if records include protected health information, follow HIPAA retention rules (45 CFR §164.530(j)) for 6 years.
What if a customer disputes a reading?
Follow the published dispute process, preserve original evidence, run anomaly checks, and document adjustments. Many utilities set a 30-day window for corrections or customer-initiated reviews.
Is notarization or witness required for meter data?
Not typically. Meter reads and attestations rarely require notarization. If a specific jurisdiction or contract requires notarized affidavits, follow local notary law and RON requirements where applicable.
How should I correct submitted data?
Submit a documented correction with the original read reference, corrected value, reason for change, and reviewer identity. Maintain both original and corrected records for auditability.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now