ZujajFlow — Smart Metering & Utility Billing Platform

ZujajFlow is a smart metering and utility billing platform covering eight meter categories — electricity, cold and hot water, gas, AC cooling, heating, solar and sewerage. It collects sub-meter readings automatically, turns them into consumption and cost analytics, bills tenants for what they used, accepts payment online, and alerts technicians when a meter or a utility develops a fault.

An automatic meter reading (AMR) system gets the numbers off the meter. That is where it stops. ZujajFlow takes those readings and does the work that actually costs you money if it goes wrong — validating them, rolling them up through your building hierarchy, pricing them against your tariffs, producing a defensible tenant bill, collecting the payment and raising the fault. If you already have AMR, ZujajFlow sits on top of it rather than replacing it.

Eight categories: electricity, cold and hot water, gas, AC cooling, heating, solar and sewerage. Cooling and heating are metered in BTU, which covers district-cooling chilled-water meters as well as standalone BTU meters. ZujajFlow is deliberately vendor-agnostic — it reads from the meters, gateways and head-end systems you already have rather than requiring you to replace your metering estate. Where meters are not yet connected, we scope the collection layer as part of the rollout.

Yes, and this is usually the first thing operators want to see. ZujajFlow totals what your sub-meters recorded over the billing period and sets it against the authority’s consolidated figure at the incomer. The difference is your unbilled loss — common-area draw, landlord supply, meter faults or genuine leakage. Most operators have never had that number in front of them before.

No, and this is usually the objection that stalls a metering project. If you run Urbanise, ZujajFlow validates your API credentials and syncs your tenants and properties directly. Otherwise there is bulk Excel import for tenants, units, meters and customers, with a separate validation pass so you see what is wrong with a sheet before any of it is committed. Building the register by hand is the last resort, not the starting point.

Usually yes, and that is the normal way in. If your buildings run Tridium Niagara, ZujajFlow polls your JACE controllers over their REST API on a 15-minute cycle, with concurrency limits and circuit-breaking so a slow controller never stalls the collection run. It also connects over BACnet/IP, KNX, MQTT and Azure IoT Hub, and readings are stored against their OBIS codes, so registers keep their standard meaning rather than being flattened into a single number. Where a site exports readings as files or through an API instead, we ingest that route and validate every batch before it counts.

Yes. The Tenant Edition portal shows an itemised bill with opening and closing readings, units consumed and the tariff applied, and tenants settle it online. Receipts are issued automatically and the payment history stays available to both the tenant and the operator.

ZujajFlow runs a daily reconciliation that matches invoices against payments received and flags every mismatch above your tolerance. You get a dated discrepancy list showing which invoice is short and by how much, with an alert when the gap warrants attention. Alongside it sits the exception handling that utility billing actually generates day to day — cash collection, advance payments and credit balances, overpayments, refunds and reversals, chargebacks, duplicate payments, and manual adjustments that stay attributable and auditable.

Card and bank transfer through Network International, Stripe or PayPal, plus auto-debit for recurring collection. Cash taken at a front desk is recorded against the invoice with a generated receipt, so offline payments reconcile alongside online ones rather than sitting in a separate book.

Automatically, and over the channel they will actually see. ZujajFlow detects nine fault types from the meter data itself — leak, spike, backflow, zero consumption, threshold breach, communication loss, and voltage, power-factor and frequency anomalies. A detected fault raises a ticket on its own, carrying the meter, unit, customer and the anomaly behind it, and a critical anomaly opens at critical priority. The alert goes out by mobile push, SMS or email, technicians work assigned tickets from the mobile app, and anything left sitting climbs an escalation level rather than ageing quietly at the bottom of a list.

By watching flow rate rather than waiting for the monthly total. If a meter holds a continuous flow above your configured minimum rate for three consecutive days — both the day count and the flow threshold are yours to set — ZujajFlow raises it as a critical leak, recording the average flow observed and the threshold it breached. A genuine leak normally surfaces on a bill six weeks later, once the water is long gone; this catches it while it is still running and turns it into an assigned ticket the same day.

Yes. ZujajFlow runs in the cloud or inside your own data centre — which matters for institutions and government-linked entities with data residency requirements, and for sites where the metering network is deliberately kept off the public internet.

Where meters are already connected to an AMR or head-end system, the first building is typically live in 4–8 weeks. Sites that need new gateways, network coverage or meter replacement take longer — usually 3–6 months to full portfolio coverage. Most operators start with a pilot on one building and expand once the numbers are proven.