Meter readings, consumption and billing without the spreadsheet.
Every organisation that manages multiple usage points — shops, units, parcels, offices — repeats the same cycle: send someone to read the meters, collect the numbers, calculate consumption, check whether anything looks wrong, then invoice or allocate costs. When that cycle runs on paper and spreadsheets, one missed reading or a wrong digit ripples forward into billing disputes and audit gaps. Tenderely BPM ties the meter, the reading, the consumption calculation and the anomaly check into one traceable record, without code.
What does a metering cycle repeat every period?
01
Maintaining meter cards
Each electricity, water, gas or heat meter needs its own identity: location, type, serial number, calibration status and the usage point it belongs to. Without a card, a meter is just a number someone remembers.
02
Collecting periodic readings
At the end of each period someone reads every meter and records the index. When that happens on paper or in a shared spreadsheet, gaps and transcription errors are only found later.
03
Calculating consumption
Consumption is the difference between this period's index and the last. When the formula lives in a spreadsheet that dozens of people touch, the result becomes untrustworthy over time.
04
Applying the tariff
Consumption in units becomes a monetary amount only once a tariff is applied. When tariffs change mid-period, the calculation has to be right for both segments.
05
Catching anomalies before invoicing
A reading that is far outside the normal range — a leak, a misread digit, a faulty meter — should be flagged before a bill goes out, not disputed afterwards.
06
Tracking calibration and installation events
Meters need periodic inspection and stamping. An overdue calibration, a meter swap or a new installation has to be recorded so the history of each usage point stays continuous.
Where does this break down today?
Readings live in a spreadsheet nobody trusts
One person enters the numbers, another checks them, a third invoices from them. When the file has multiple editors and no audit trail, a disputed bill cannot be traced back to its source reading.
Anomalies surface after the invoice
An abnormal consumption figure is easy to spot in a table — but only if someone is looking for it. When nobody checks systematically, the tenant or unit owner receives a wrong bill and the dispute starts there.
Calibration deadlines are missed
A meter whose inspection date has passed is a compliance and billing risk. Without a system that tracks expiry dates and reminds someone, it stays in service unnoticed.
History breaks when a meter is replaced
When a meter is swapped, the new serial number, the closing index of the old meter and the opening index of the new one must all be recorded together. If they are not, the consumption history of that usage point has a gap.
What changes with Tenderely BPM
01
Every meter is a structured record
Type, serial number, calibration date, installation date and the usage point it serves are stored together. The meter card is the single source of truth for everything that follows.
02
Readings form a grid, not a pile of files
Periodic reading collection happens in a structured grid against the meter records you already have. Every entry is timestamped and linked to the reader's identity.
03
Consumption and amounts calculate from the record
Because both the previous and current index live in structured records, consumption and the resulting amount are derived from data rather than re-entered by hand, removing the main source of billing errors.
04
Anomalies are a step in the flow, not an afterthought
An anomaly check can be built into the period-close workflow so that readings outside the expected range are flagged for review before anything is invoiced. The exception is handled inside the same record.
05
Calibration deadlines remind themselves
Give a calibration record an expiry date and Tenderely BPM sends the reminder. Overdue inspections stop being discovered during audits.
06
Installation and swap history stays continuous
A meter installation or replacement is an event recorded on the usage-point record, capturing the closing and opening indexes so the consumption history of each location is never broken.
FAQ
Does the metering module work on its own or does it need to connect to something we already have?
+
It is designed to attach to whatever usage-point record you already manage — a shop, a parcel, a unit or an office. If you do not yet have those records in Tenderely, the module works as a starting point for building them. Nothing has to exist first.
Can field staff record readings from a phone?
+
Yes. The same forms and workflows run on the iOS and Android apps, so a technician walking the site can enter or confirm an index on their phone and the record updates immediately.
Who is allowed to enter or edit a reading?
+
Role-based permissions decide who can submit a reading, who can review flagged anomalies and who can approve a period before invoicing. A field reader and a billing manager see different parts of the same record.
How does the anomaly check work?
+
An anomaly check is a step in the period-close workflow. When a reading falls outside the range you define, the record is routed for review before moving forward. The reviewer can confirm the reading, correct it or raise a site visit — all inside the same traceable record.
Can we report consumption across all usage points for a given period?
+
Yes. Because every reading is a structured record linked to a meter and a usage point, you can build dashboards and reports that show total consumption by period, by meter type, by location group or by any other dimension your records carry.