A bill is only worth what it can survive.

The whole system: the mobile capture application, the OCR pipeline that reads a meter face and scores its own confidence, the approval workflow that separates capture from validation, the billing engine and its single published formula, the arrears and payment tracking, the reconciliation against the utility bill, and the month-close that freezes the books. He leads it as Head of Energy Systems & Product Engineering at BijliBachao.pk.

That the deliverable is not the invoice. Any spreadsheet can produce an invoice; what a building manager actually lacks is the ability to prove one. So the system was built around evidence — a photograph retained behind every reading, a formula shown to the person being billed, and a month that can be frozen — and the invoice falls out of it. Getting that ordering right is the product decision; everything downstream is ordinary engineering.

Because a reading that the same person can both take and approve is not evidence of anything. An operator in WattEY Metering can capture and nothing else — no rates, no billing, no approval — and a manager reviews each reading against its own photograph and last month’s figure, requesting an audited retake rather than editing a number silently. Without that separation the photographs would be decoration.

Because the raw captures contained real tenant names, shop trading names, meter serial numbers, the operator’s email address and, on one screen, the property owner’s monthly profit and loss. The tenants are small shopkeepers who never agreed to appear on a portfolio. The screens are shown because they are real and running; the people in them are not the evidence, and neither is the client’s margin.

Very few, and that is recent. Read-only queries against the production database on 25 August 2026 replaced the page’s earlier figures, several of which were wrong — the scale twice over, and the optical-character-recognition accuracy twice over. Four outcome percentages that had circulated in marketing material were traced to a document listing them as typical results for a hypothetical property, with no baseline and no measurement anywhere, and were dropped rather than softened. Two billing-cycle claims failed the same check and were dropped too. No speed figure is stated for the automatic reading because no timing telemetry is stored, and no offline-capture count is given because synced readings cannot be distinguished after the fact. What remains is measured.

A rooftop with a customer. Wattey Energy (formerly BijliBachao.pk) sells a service it calls Solar Share System, which is commercial solar EPC bundled with WattEY Metering: the owner installs the array and each tenant gets a photo-verified bill crediting solar units against grid units. A landlord cannot sell rooftop generation to their own tenants on the strength of a spreadsheet, because the tenants have to accept the bill. The billing layer is the precondition for that service existing, not a feature of it.

Yardi publishes property submetering and utility-billing services, and ista publishes commercial submetering for consumption-based tenant billing. These establish the problem category. WattEY Metering is Ali’s delivery for one shopping mall; these companies are not partners or endorsers, and equivalent features or deployments are not claimed.

The 25 August 2026 production snapshot documents 5 closed monthly cycles, 668 readings with photographs and 61 arrears settlements. These establish repeated use of the workflow. No measured time saving, revenue recovery or general OCR accuracy percentage is claimed.

The shape is general: field staff capturing data on a phone in places with no signal, an automated read of that capture that has to declare its own confidence, an approval path where the capturer is not the approver, a computation that has to be explainable to the person it charges, and a periodic close that makes the record immutable. That is stock audit, asset inspection and field logistics. These are potential adaptations requiring their own domain model and validation; they are not WattEY Metering deployments.

Yes. The delivered system includes a React Native / Expo Android app for operator meter capture, plus a web portal for review, billing, payments and monthly close. The app selects meters, retains photographs, supports retakes and queues readings for upload.

Cloud OCR requires connectivity because it calls Google Cloud Vision through the web application’s authenticated proxy. The app can retain a photograph and an operator-entered reading offline, then upload the queued record when connectivity returns. Offline OCR is not claimed.

WattEY Metering handles commercial shop and meter billing through monthly periods. The separate Sub-Billing case study addresses residents who move in and out mid-period. The evidence and reconciliation ideas transfer, but occupancy rules and settlement calculations require a different domain model.

Connected capture requests server time. Offline capture, or a failed server-time request, uses the device clock and retains that time with the queued reading. The case study therefore describes operational capture timestamps, not a universal guarantee against clock changes.

The database uniqueness rule applies to original readings for each meter and billing month. Retakes are exempt from that rule and are linked to the review workflow; the billing calculation chooses the applicable retake instead of adding a second bill for the same meter.