Argus EMS · 19.10.2026 · 6 min read
In a shopping mall, the distribution company's bill often arrives under a single subscription, yet the energy behind it is spread across dozens of stores, food outlets and common areas that belong to no tenant. The management company has to pass that single amount on to tenants in a way that is fair, understandable and auditable. Doing it by estimate weakens both tenant relations and management's own cost control. This guide covers tenant metering architecture, separating common area consumption, allocation keys, and the reconciliation and dispute processes, written for mall technical managers and site managers.
Sound billing starts with a correctly built metering hierarchy. At the top sit the utility meter and the main measurement at the transformer output or the main distribution board. Below that are floor or riser panels, and at the bottom each tenant's own sub-meter. Common area panels (mechanical plant, lighting, car park, vertical transport) should be fed separately from tenant meters and, where possible, measured separately.
How meters are registered matters too. The block, floor and tenant unit each sub-meter belongs to, together with its current transformer ratio and serial number, should be kept in a single register. If this mapping is not updated when stores are merged or split or a tenant changes, consumption is written to the wrong unit. On the communication side, meters read remotely over Modbus RTU/TCP or M-Bus eliminate the date drift and transcription errors of manual index readings. When selecting meters, the accuracy class of the meter and the class of the current transformer should be assessed together; an accurate meter paired with a coarse current transformer brings the whole measurement chain down to the level of the transformer.
The common area is the sum of loads that no single tenant uses on its own but that the mall needs in order to operate. In its simplest form it is the difference between main meter consumption and the total of tenant sub-meters:
Common area + losses = Main meter − Σ Tenant sub-meters
The losses part of this equation is often forgotten. The difference is not made up of common area loads alone; transformer and cable losses, small unmetered loads, meter errors and reading time mismatches all land in the same item. Measuring the large common area loads directly therefore shrinks the unexplained difference and makes the allocation defensible.
| Common area load | Recommended metering point | What to watch in allocation |
|---|---|---|
| HVAC and chiller plant | Mechanical panel, chiller and pump feeders | If it also serves tenant spaces, a separate heating and cooling share per zone should be defined |
| Escalators and lifts | Vertical transport panel | Commonly treated as a general common area item rather than split by floor |
| General lighting | Common area lighting panel | Check that the lighting schedule matches mall opening and closing hours |
| Car park (lighting, jet fans) | Car park panel | The lease should state clearly which tenants use the car park and which do not |
| Water, booster and fire pumps | Pump panel | Largely standby load rather than consumption; disputes over equal shares often start here |
| Losses and unmetered loads | Main meter − sub-meter total | Tracking the ratio month by month reveals the source of sudden jumps |
How common area consumption is passed on to tenants is as much a contractual decision as a technical one. The main allocation keys used in practice are:
Whichever key is chosen, it should be defined explicitly in the lease and not changed from one period to the next. In Türkiye, passing energy costs on to sub-users and invoicing them is a regulatory matter; the model applied should be configured in line with local regulations and the lease agreement.
At every period close, the main measurement and the sub-meter total should be placed side by side. For electricity, main consumption comes from the utility bill or from transformer and main meter measurements; sub-meters show the tenant share within it. Adding sub-meters on top of the main measurement creates double counting, so the two levels should never enter the same total in any report.
For reconciliation to be reliable, both sides must be taken on the same reading dates. The utility bills by reading dates rather than calendar months; if sub-meter indexes are taken on a different day, the difference item is artificially inflated or shrunk. The trend of the difference ratio over time is more meaningful than its value in a single month. A sudden jump points to a newly connected but unmetered load, a meter that has lost communication or an incorrectly configured current transformer ratio. A negative difference is physically impossible; it usually indicates a sub-meter defined twice or a multiplier error.
A dispute over a tenant invoice closes quickly when every step of the calculation can be traced back. The following steps are recommended:
In Argus EMS, each project is defined through a block and unit hierarchy; the unit record holds the unit number, floor and tenant name along with subscriber details such as contract and installation numbers, and sub-meters are linked to their units. Period consumption is summed from the sub-meter's hourly and daily consumption records, and tariff tables are defined for electricity and water as well. When the utility bill is entered, the main invoice keeps that actual amount, while a tenant invoice is produced for each sub-meter by multiplying its consumption by the effective unit price derived from the main bill. Reactive energy penalties are not spread across sub-invoices and stay on the main invoice.
The difference between the main invoice and the total of sub-invoices is reported separately, in quantity and amount, as the common area and losses item; which key is used to pass this difference on to tenants is determined by the lease and applicable regulations. A PDF is generated for each invoice, and payment status is tracked as Pending, Paid or Overdue. The technical manager can then prepare the reconciliation and the dispute file from the same data.
Related Content
Explore the system with your own data in a demo session.