--- title: "WattEY Metering" headline: "WattEY Metering: photo-verified tenant billing" description: "Ali Ahmed built WattEY Metering: Android meter capture and web tenant billing, with photo evidence, arrears tracking and monthly reconciliation." canonical_url: https://alioahmed.com/work/wattey-metering type: case-study role: "Head of Energy Systems & Product Engineering" date_label: "2026 – present" status: live date_modified: 2026-10-27 author: name: "Ali Ahmed" url: https://alioahmed.com/ orcid: https://orcid.org/0009-0007-4265-3295 key_figures: - "5 consecutive months closed" - "668 readings captured" - "100% of them carry a photograph" - "0.45% needed a retake" entities: - name: "WattEY Metering" type: SoftwareApplication - name: "Wattey Energy" type: Organization url: https://watteyenergy.pk/ same_as: - https://bijlibachao.pk/ - name: "WattEY Metering chain of custody" type: DefinedTermSet - name: "Water and Power Development Authority" type: GovernmentOrganization url: http://www.wapda.gov.pk/ same_as: - https://www.wikidata.org/wiki/Q7973437 - name: "Lahore Electric Supply Company" type: Organization url: https://en.wikipedia.org/wiki/Lahore_Electric_Supply_Company same_as: - https://www.wikidata.org/wiki/Q15982516 - https://en.wikipedia.org/wiki/Lahore_Electric_Supply_Company - name: "Google Cloud Vision AI" type: SoftwareApplication url: https://cloud.google.com/vision/ same_as: - https://www.wikidata.org/wiki/Q59898818 person_same_as: - https://www.linkedin.com/in/alioahmed/ - https://github.com/alioahmed - https://orcid.org/0009-0007-4265-3295 - https://x.com/Alioahmed_ - https://about.me/alioahmed - https://dev.to/alioahmed - https://medium.com/@alioahmed - https://hashnode.com/@alioahmed - https://substack.com/@alioahmed - https://huggingface.co/alioahmed - https://bsky.app/profile/alioahmed.bsky.social - https://mastodon.social/@alioahmed - https://www.kaggle.com/alioahmed - https://www.producthunt.com/@alioahmed - https://www.patreon.com/cw/alioahmed - https://www.goodreads.com/user/show/202106301-ali-ahmed - https://fueler.io/alioahmed - https://gitlab.com/alioahmed - https://linktr.ee/alioahmed - https://topmate.io/alioahmed related: - https://alioahmed.com/work/wattey - https://alioahmed.com/work/electricity-sub-billing - https://alioahmed.com/work/sts - https://alioahmed.com/work/bijli-bachao - https://alioahmed.com/work/solar-performance-cloud full_corpus: https://alioahmed.com/llms-full.txt site_index: https://alioahmed.com/llms.txt --- # WattEY Metering > WattEY Metering is a meter-reading and tenant-billing system built by Ali Ahmed at Wattey Energy (formerly BijliBachao.pk). An Android app captures photographs and confirmed readings; a web portal reviews the evidence, generates bills, tracks arrears and freezes monthly records. The 25 August 2026 production snapshot documents five closed billing cycles and 668 photographed readings at Mall of Mureedkay, a shopping mall in Punjab. **Canonical URL:** https://alioahmed.com/work/wattey-metering **Role:** Head of Energy Systems & Product Engineering — 2026 – present **Summary:** Ali Ahmed built WattEY Metering: Android meter capture and web tenant billing, with photo evidence, arrears tracking and monthly reconciliation. ## Key figures - **5** — consecutive months closed - **668** — readings captured - **100%** — of them carry a photograph - **0.45%** — needed a retake ### A bill is only worth what it can survive. A Pakistani shopping mall has one utility connection and hundreds of units behind it. The flagship is a roughly 545-unit property in Punjab, with 129 shops onboarded into the system and about 111 meters billed every month. Somebody walks the building with a notebook writing down meter numbers; somebody else retypes them into a spreadsheet, where a formula nobody can audit turns them into bills. Once a month a shopkeeper says the reading is wrong, and there is no proof either way. The tenant bills almost reconcile against the utility bill — almost — and the gap is the owner’s loss. This is the quiet leakage in every multi-tenant property: disputes that cannot be settled, a shortfall that cannot be explained, and hours of spreadsheet work producing a number nobody fully trusts. WattEY Metering’s answer is not a better invoice. Any spreadsheet can produce an invoice. What a building manager actually lacks is the ability to prove one — so the system was built backwards from the dispute, and the invoice falls out of the evidence rather than the other way round. ### A photograph is not proof. A chain is. Attaching a picture to a meter reading is the easy idea, and it is where most photo-verified billing stops. It does not survive a real dispute, because a photograph taken and approved by the same person proves nothing a handwritten number did not already prove. What holds is a chain of five links, and removing any one of them collapses the other four back into a spreadsheet. Every reading is captured with a timestamped image of the meter face, retained with the reading record. Connected cloud OCR proposes the number from that image and records how confident it is, so a poor read is flagged for review rather than quietly trusted. The field operator who captures a reading cannot approve it — the app permits capture and nothing else, no rates, no billing, no approval. A wrong reading is corrected by an audited retake rather than an overwrite, so the original stays in the record and the correction is visible as a correction. And at month end the figures freeze. That interdependence is the engineering insight. A photo alone is theatre if the same hand can bless it. Separation of duties is theatre if a number can be silently overwritten. An audit trail is theatre if the closed month can be quietly amended. ### The month has to close, and four numbers have to tie. “The numbers never quite add up” is not a complaint about arithmetic. It is that the tenant invoices and the utility bill describe two different worlds, and the gap between them is the owner’s loss with no name on it. A multi-tenant property has four quantities that must reconcile every month: what was bought from the utility, what was generated on the roof, what was billed to tenants, and what the common areas consumed. WattEY Metering ties them in one ledger — solar credited against building consumption without being counted twice, and shared lighting and lifts billed to the building rather than back to a shop. That reconciliation is what turns billing software into a book of account. Then it stops moving. At close the readings, bills and payments become read-only; reopening is possible, because sometimes it must be, and is recorded against a named role and a timestamp. A set of books that can be quietly amended after everyone agreed to it is not a record. The states a real property is actually in are on the page too, because every naive schema breaks on them: a shop between leases that still has a meter and still accrues common-area load, tenants registered without a unit who must not receive a bill, and shops deactivated without being deleted so their history survives. ### What the production record actually shows. Read-only queries against the production database on 25 August 2026 settle what this chapter can claim, and the measured version is stronger than the marketing one it replaces. Five consecutive monthly cycles have been closed — March through July 2026 — each in the first week of the month following, with a sixth in flight. That regular cadence is the difference between a pilot and a production system. The first reading was taken on 5 March 2026 and the platform has run continuously since. Across those cycles 668 readings have been captured, and 668 of them carry a photograph. All 668 reading records in that snapshot carry an image. The property unit count, shops onboarded, active billed meters and total reading records have different denominators; retake records must not be mistaken for additional deployed meters. The retake workflow is demonstrably used and rarely needed: three retake requests against 668 readings, about 0.45 per cent — one fulfilled, two cancelled after review. The cancellations matter as much as the fulfilment, because they show triage happening rather than a workflow nobody touches. Two months have genuinely been reopened after closing, in March and April 2026, and the ledger retained the complete record through both — the claim that reopening is survivable is not a design intention but something the system has actually done. Sixty-one closed bills have since been settled as arrears, so the carry-forward loop is exercised rather than theoretical. Seventeen of the ninety-eight meter-holding tenants hold more than one meter, and the largest holds five — which is why consolidated invoicing exists at all. ### Where the chain ends: the evidence prints on the bill. Every guarantee described above happens inside the system. The bill is where the evidence leaves it and lands in the hand of the person being charged — which is why the platform team, asked what the single strongest thing about the product is, names this document first. Two photographs of the meter print on the bill itself: a cropped view of the display and the full meter face, both timestamped. A tenant disputing the figure is not asked to trust a database; they are holding the picture. The correspondence is checkable on the paper — the display in the photograph reads 24429, and the bill states a current reading of 24,429. The step most likely to be disputed is the one most visibly worked out. A CT-metered connection reads a fraction of the real current and has to be multiplied up, so the bill prints the arithmetic in full: a meter difference of 445 multiplied by a factor of ten gives 4,450 effective units. Arrears arrive the same way — two carried months and a late fee itemised above the current charge, with the grand total showing its own components, and the amount written out in words in the Lakh convention beneath. A tear-off payment slip completes it. A demonstration bill from the production generator: the template, arithmetic and amount-in-words are the product’s own, the tenant and property are fictitious, and the meter photographs are real. ### Supply, consumption and collections in one record Every other guarantee in this system makes a bill defensible. One of them makes the whole building legible, and it is the piece an outsider never guesses. The ledger compares recorded supply with metered consumption. A gap prompts investigation: physical losses, unmetered loads, faulty readings or mismatched periods can all contribute. The difference alone does not establish theft or its cause. The power ledger sets the whole property out as one equation: what came in, from the utility and from the roof; what the shops used; what the owner’s own common areas used, charged to the owner and never to tenants; what leaked, colour-graded; what was billed against what was actually collected; and finally net recovery against the utility bill — the building’s real profit. The platform team names it, unprompted, as the strongest screen the product has, alongside a bill that carries the meter photograph on it. ### Four decisions, each removing a class of error. The billing page is read-only by design. Bills derive from readings and rates, so there is no field to edit and nothing to fudge — a whole category of dispute, and of fraud, removed by declining to offer the control in the first place. Rates resolve per shop, then per tenant, then to a property default, so an anchor tenant on a negotiated rate and an ordinary shop are both billed correctly from one system rather than from a parallel spreadsheet of exceptions. Heavy three-phase connections meter only a fraction of the real current and have to be multiplied up by a CT factor — and that multiplication is printed on the tenant’s own bill, so it can be checked rather than taken on trust. Deactivating a tenant carries their shops and meters with it, and nothing is ever destroyed, so a property that changes shape does not lose its history. ### One formula, published — and four roles that separate. Consumption is the current reading minus the previous one. The amount is consumption times the per-unit rate times the meter’s multiplying factor. Tax applies to the amount, and the total adds arrears and any late fee. That is the whole calculation, it is identical for every shop, and the tenant can see it. Transparent arithmetic is what ends a dispute; a total on its own restarts one. Transformer-stepped meters carry a multiplying factor applied in the bill line rather than in somebody’s head, and a tenant holding several units receives one consolidated invoice with a line per meter. Four roles exist and the gaps between them are the audit story: a super administrator who can close and reopen months, an administrator who manages billing and approvals, a billing manager who generates bills and closes the month, and an operator who can capture a reading and do nothing else. The capture app works offline and synchronises when signal returns, with duplicate prevention holding inside the offline queue, because basements and service corridors are the normal case in this building type rather than the exception. Three weeks takes a property from signed contract to a live cycle. ### A real category. A specific delivery. Tenant billing and utility submetering are established property-management workflows. WattEY Metering’s case is the system Ali delivered for Mall of Mureedkay, a shopping mall in Punjab: photographic evidence, operator confirmation and a billing period that can be reconciled. Shopping malls & commercial plazas: The demonstrated setting: one bulk utility connection, many metered shops and a property team handling collection. Configure the property’s meters, rates, roles and billing periods. Office buildings & industrial estates: A potential adaptation where tenants occupy separately metered suites or units behind a shared connection. Validate meter factors, negotiated rates, common-area treatment and local billing rules. Residential & mixed-use properties: A related problem with different occupancy and settlement rules. Resident turnover needs additional treatment. Use the separate Sub-Billing chapter to examine mid-period move-ins and move-outs. Inspection & asset records: The capture-and-review pattern can transfer to field records that need photographs, offline queues and attributed corrections. Redesign the domain model and review workflow; this is not an existing WattEY Metering deployment. Only the shopping-mall deployment is claimed here. Other settings are potential adaptations; equivalent features, regulatory suitability and deployments are not implied. ### Established examples of the problem category - [Yardi — Submetering Services](https://www.yardi.com/product/submetering-services/) — Property submetering and utility-billing workflows. - [ista — Commercial Submetering](https://www.ista.com/uk/commercial-industrial/services/submetering/) — Commercial properties and consumption-based tenant billing. - [Esri — QuickCapture offline records](https://doc.esri.com/en/arcgis-quickcapture/latest/capture/guidedtour-capture.html) — Field records that upload after connectivity returns. ### Built for the person walking the building. The mobile app is part of the delivered system. Operators use it to select a meter, photograph the display, confirm the reading and send it to the billing team. The Android app is built with React Native and Expo. Find the next meter: Floor-ordered shop lists and a meter picker keep the route organised. Unread meters and retake requests stay visible. Keep the evidence: A camera alignment guide frames the display. The app retains the full photograph and the cropped meter display alongside the confirmed value. Work through weak signal: Readings and images queue in local storage when connectivity is unavailable. Uploads resume when the connection returns; failures remain visible for retry. Hand over to the portal: The portal receives readings for review, including retakes. Cloud OCR uses the web application’s authenticated proxy and requires a connection; offline capture uses operator entry. The codebase supports an iOS build, but no iOS distribution is established by this case study. Deployment figures on this page are the 25 August 2026 snapshot; source inspection confirms features, not new production totals. ### What the billing layer unlocked. Wattey Energy (formerly BijliBachao.pk) sells a service it calls Solar Share System: commercial solar EPC bundled with WattEY Metering, where the building owner installs the array and every tenant receives a photo-verified bill crediting solar units against grid units. Read the dependency in that description and the argument is finished. A landlord cannot sell rooftop generation to their own tenants on the strength of a spreadsheet — the tenants have to accept the bill, or the arrangement is a monthly argument about money. The billing layer is not a supporting feature of that service; it is the precondition for it existing at all. Without a bill the tenants accept, the roof stays a roof. That is the checkable version of what changed because Ali was there: he built the thing that made a commercial service line possible. ### What transfers, once you take the meters out. Strip the electricity out and WattEY Metering is a machine for capturing evidence in the field, reading it automatically without over-trusting the read, and turning it into a figure two parties who disagree can both rely on. Six things generalise. Capture evidence rather than data, so the artefact that proves a value is recorded at the same instant as the value. Make the automation declare its own confidence, because an extraction that cannot say how sure it is will be trusted uniformly, including when it is wrong. Never let one hand both capture and approve. Correct by appending rather than overwriting, so a mistake stays visible. Close the period and make reopening an attributed act. And assume no signal, because field work happens where there is none. The same capture-and-review pattern can inform stock audits, equipment inspections and field logistics. These are potential adaptations requiring their own domain rules and validation, not deployments or compliance claims. ### What this page does not claim. It runs on one property. Everything here describes a single deployment, and no portfolio is implied. One shopping-mall deployment is documented; potential uses in other industries are labelled as adaptations. Production totals are dated 25 August 2026; the earlier product-screen example represents one billing period. Client identities, tenant names, deployment tariff rates and deployment financial totals are not published. The demonstration bill contains real meter photographs, retained at Ali’s request. No measured time saving, revenue recovery or general OCR accuracy percentage is claimed. ## FAQ ### What did Ali Ahmed actually build in WattEY Metering? 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. ### What was the real insight behind this product? 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. ### Why is capture separated from approval? 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. ### Why are the screenshots on this page redacted? 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. ### Which figures on this page are uncertain? 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. ### What did this software actually make possible commercially? 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. ### Which established products address this problem category? 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. ### What measured results does this case study establish? 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. ### What transfers from this to a problem that is not about electricity? 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. ### Did Ali build a mobile app as well as the web portal? 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. ### Does the app read meters with OCR while offline? 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. ### How do WattEY Metering and residential Sub-Billing differ? 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. ### Does every captured reading use a server-issued timestamp? 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. ### How do retakes work with the one-reading-per-month rule? 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. --- Rendered from the structured content at https://alioahmed.com/work/wattey-metering. Facts trace to the canonical bio; render, don't reword.