✦ Ensmart BMS Academy Home About Us Products Solutions Case Studies eNews Blog Downloads Team Contact Design Engg Get a Demo →
Home › AI BMS Mentor › Energy Management

Tenant Billing System — Stopping the End-of-Month Argument

Energy Management 46 views ✓ Reviewed by EnSmart engineer Updated 15 hr ago
Copied to clipboard ✓
Tenant Billing System — Stopping the End-of-Month Argument — infographic

A Chennai IT Park, Five Days Lost Every Month

Anbu is the IT park admin at a Chennai multi-tenant tower. The building has four tenants on six floors. Every month-end, the same conversation: ``` Tenant A: "Why did our bill go up 18 percent? Did somebody else's chiller usage get put in our column?" Tenant B: "Floor-7 has 60 employees, we have 110. Why are our bills similar?" Tenant C: "We were closed for the festival week. Why is the common-area charge the same?" Anbu: "Let me check the spreadsheet... I'll come back." ``` Anbu spends the first week of every month re-checking the billing spreadsheet. The spreadsheet uses carpet-area weighting for common areas — a method everyone agrees is fair in principle but no tenant trusts in practice. There is no audit trail. There is no transparency. There is no peace. ``` Anbu's monthly cycle: Day 1-3 Read the LT panel meters by hand Day 3-5 Allocate common-area to tenants by carpet area Day 5-7 Build the spreadsheet, send to tenants Day 7-12 Arguments, recalculations, escalations Day 12-15 Final invoices issued Day 15+ Some tenants still unhappy ``` This is not a billing problem. This is a trust problem. And the trust problem has a technical root — the absence of measurement. Every single one of these problems has one solution — a Tenant Billing System with per-tenant sub-meters and an auto-generated invoice that the tenant can audit themselves.

What a Tenant Billing System Does

``` Hardware layer: One sub-meter per tenant on the main electrical supply One sub-meter per tenant on the dedicated AC supply (if any) One sub-meter per tenant on small-power circuits (if separable) One central meter on the common-area supply Software layer: Reads all sub-meters every 5-15 minutes via Modbus / BACnet Stores 12-month rolling history Allocates common-area energy by an agreed rule Calculates monthly bill per tenant with breakdown Generates GST-compliant invoice Emails or portal-uploads invoice on first of month Provides tenant portal with daily and monthly trend access ``` Once deployed, the billing cycle compresses from 15 days to 1 day, and disputes drop to near zero — because every tenant can see their own data.

Common-Area Allocation — The Rule That Matters

The most contested item in tenant billing is the common-area allocation. Three rules are commonly used: ``` Method 1 — Carpet area Each tenant's share of common-area energy is proportional to their carpet area. Simple, traditional, often perceived as unfair when one tenant uses common areas heavily (e.g., visitor reception). Method 2 — Headcount Each tenant's share is proportional to their employee count. Fair when common areas are about people (lifts, lobbies, parking). Unfair when common areas are technical (chiller plant, DG). Method 3 — Direct + indirect split Direct: tenant's own sub-metered usage (no allocation). Indirect (chiller plant, DG, common HVAC): allocated by AC tonnage installed for that tenant or by floor area served. Most fair for buildings with central HVAC. ``` The right method depends on the building. The TBS implements whichever method the lease agreement specifies — and shows the calculation transparently in the invoice.

What a Tenant Sees

Every tenant has portal access. They log in and see: ``` Their usage today: AC supply kWh today, this week, this month Small power same breakdown Their share of common-area allocation Comparison to last month: Up or down by what percent Day-by-day trend with weekend/weekday breakdown Their estimated bill: Current month-to-date estimate Last month final Same month last year (year-over-year comparison) Their invoice history: Last 12 months PDF invoices, downloadable GST-compliant format HSN code, SAC code per line item ``` When a tenant questions a bill, they look at their own dashboard first. The dashboard answers most questions. Anbu's phone stops ringing.

The Invoice Format

``` EnSmart IT Park - Tenant Billing Invoice for: Tenant A, Floor 3-4 Period: 1-31 October 2026 Direct consumption: AC supply 18,420 kWh @ Rs.9.20/unit = Rs.169,464 Small power 4,180 kWh @ Rs.9.20/unit = Rs.38,456 Common-area allocation: Tenant A share: 2,140 kWh (Allocated by carpet-area rule, calculation shown in attached statement) = Rs.19,688 Sub-total = Rs.227,608 GST @ 18 percent = Rs.40,969 Total invoice amount = Rs.268,577 Payment due: 15 November 2026 Source data: building meter ID BLR-LT-001, tenant sub-meter ID FLR-3-4-AC, FLR-3-4-SP. Trends and raw data available on tenant portal. ``` Every line item is traceable to a specific meter and a specific period. The dispute moves from "I think this is wrong" to "I can see exactly how this was calculated."

The Day-of-Cycle Process

``` Day 1 (1st of month, 00:01) TBS reads all sub-meters at midnight on the 1st. Calculates each tenant's direct consumption for the previous month. Calculates common-area allocation. Generates GST-compliant invoice. Emails to each tenant's accounts contact. Uploads to tenant portal. Day 1 (08:00) Anbu reviews the auto-generated invoices. Approves or, if any anomaly, queries before sending. Day 1-2 Tenants log into portal, verify, raise questions. Anbu answers from the data, not from the spreadsheet. Day 5 All invoices verified, none disputed. Anbu's first week is spent on actual building work, not billing. ``` The process that took 15 days now takes 1 day. The reclaimed time is for actual facility work — projects, tenant relations, energy improvements.

Why Trust Comes From Data, Not From Argument

The end-of-month argument is fundamentally about data quality. When the data is good — sub-metered, time-stamped, traceable — argument has nowhere to go. Tenants either accept the number or point to a specific meter and ask a specific question. Either way, the conversation is short and constructive. When the data is bad — spreadsheets, allocations, manual reads — every disagreement turns into negotiation. There is no ground truth. Both sides argue from different versions of the same number. Trust erodes month after month. A Tenant Billing System gives the building a ground truth. Every tenant trusts the meter, even if they would never trust the spreadsheet. The dispute is not a tenant problem. It is a data problem. Solve the data — sub-meters, invoices, portal — and the dispute disappears. The first week of every month becomes an actual working week.

Related Topics

Related Topics

Related Topics

Related Topics

Was this answer helpful? ✓ Thanks — your feedback was recorded.

Related questions

Have a different question?

✦ Ask the AI BMS Mentor → More from Energy Management →