Missing final reading
Keep the meter in an exception state until the approved estimation or recovery rule is applied. Store the source gap, method, reviewer, and later correction so the customer-facing amount remains explainable.
Operations guide | Published 2026-10-01 | Reviewed 2026-10-01
Tenant Utility Billing Month-End Validation Checklist
Accurate utility invoices depend on more than collecting a final meter value. This checklist helps property, billing, and facility teams close each cycle with traceable readings, resolved exceptions, correct tenant ownership, approved tariffs, and evidence for later review.
By ConnectME Utility Billing Team. Reviewed by ConnectME Technical Services.
What a sound implementation requires
Before closing a tenant utility billing cycle, confirm the billing population and dates, validate reading completeness and meter identity, resolve exceptions, apply the approved tariff and allocation versions, reconcile tenant move-in or move-out dates, review material variances, and retain an approval trail. Never overwrite a source reading without preserving the original value and reason for correction.
Written for
- Property and community billing teams
- Facility managers and utility operators
- AMR, MDMS, and billing administrators
- Finance, customer service, and audit teams
Checks to complete before acceptance
1. 1. Freeze the billing scope
Make the population, period, and ownership rules explicit before calculation.
- Confirm the cycle start and end timestamps, timezone, cut-off rule, utility type, property, and active account population.
- Reconcile meter serial numbers and service locations with tenant, unit, and move-in or move-out records.
- Record the approved tariff, fixed charges, allocation method, tax treatment, and effective dates for the cycle.
- Separate tenant, common-area, landlord, vacant-unit, and master-meter responsibilities.
2. 2. Validate reading completeness
Prove that each billed quantity has a governed source.
- Check first and last readings, interval coverage, units, multipliers, timestamps, and cumulative-total behavior.
- Flag missing, stale, duplicated, reversed, reset, rollover, estimated, or manually entered readings.
- Compare consumption with recent history and relevant master-meter or portfolio totals to identify material outliers.
- Confirm communication faults and late-arriving values are visible rather than silently converted to zero.
3. 3. Resolve and approve exceptions
Every changed or estimated value needs a reason and an owner.
- Assign each exception to a named reviewer with a due date and documented resolution rule.
- Preserve the source value, corrected or estimated value, method, evidence, author, and approval timestamp.
- Escalate unresolved material exceptions instead of forcing the cycle to close with an unexplained number.
- Retest recurring faults and create maintenance actions for meters, gateways, or mappings that repeatedly fail.
4. 4. Reconcile invoices and evidence
Review the outputs before they become customer-facing records.
- Check quantity, rate, fixed charges, adjustments, prior balance, tax, rounding, and invoice period on representative and high-value accounts.
- Reconcile billed totals with approved consumption and explain material variance from the previous cycle or master-meter balance.
- Confirm invoice recipients, account ownership, and contact records without exposing personal data in analytics or operational exports.
- Archive the cycle summary, tariff version, exception log, approval record, invoice batch, and configuration version under the retention policy.
How the checks apply in real projects
Tenant change during the cycle
Use the governed handover reading and effective occupancy timestamps to split responsibility. A current tenant should not inherit an unexplained balance caused by a late account update.
Chilled-water outlier
Review meter status, flow and temperature context, multiplier, unit, reset history, and comparable periods before treating the value as valid or estimating it. Preserve the evidence used for the decision.
Limits and project responsibility
- This operational checklist does not replace applicable laws, permits, authority regulations, contracts, tariff approvals, accounting controls, or project-specific billing procedures.
- Meter accuracy, suitability, sealing, installation, and use for charging must be confirmed against the applicable service and jurisdiction.
- Personal and payment data require role-based access, retention controls, and secure handling outside public analytics or content systems.
Primary references
- Dubai RSB district cooling metering and billing regulations: Dubai regulatory requirements covering district-cooling metering, billing, meter data, and customer-facing responsibilities.
- Abu Dhabi Department of Energy customer metering regulations: Official Abu Dhabi requirements for customer metering systems, equipment, accuracy, records, and billing use.
Related ConnectME resources
Technical guide FAQ
- What should be checked before tenant utility invoices are issued?
- Confirm the billing period and account population, meter identity, reading completeness, units and multipliers, approved tariff version, occupancy dates, exceptions and estimates, material variances, invoice calculations, and final approval evidence.
- How should an estimated meter reading be recorded?
- Preserve the original missing or invalid state, then record the estimated value, approved method, reason, supporting history, author, approval time, and later reconciliation. Do not replace the source record without an audit trail.
- Can AMR software remove every billing exception?
- No. AMR reduces manual collection and makes exceptions visible, but teams still need governed rules for missing data, tenant changes, tariffs, corrections, approvals, customer disputes, and physical meter faults.