Readings are validated, charges calculated per unit by your rates, invoices generated on your template and pushed where they need to go. The spreadsheet step - where the errors live - disappears.
Everything happens in writing — you'll get a concrete plan back, not a sales call.
| Unit | Previous | Current | Usage | Amount | |
|---|---|---|---|---|---|
| 101 | 1,204 | 1,231 | 27 m³ | $94.50 | ✓ invoice ready |
| 102 | 987 | 1,009 | 22 m³ | $77.00 | ✓ invoice ready |
| 214 | 1,455 | 1,631 | 176 m³ | — | ⚠ spike +340% — review |
| 215 | 2,110 | 2,138 | 28 m³ | $98.00 | ✓ invoice ready |
Illustrative example — your build runs on your own rules, templates and software.
A CSV export from your sub-metering system, photos of analog dials, or an API feed if your meters have one - the pipeline takes what you have.
Impossible jumps, missing units, duplicates, negative usage - flagged now, not after a tenant calls about a $900 water bill.
Your rates, fixed fees, common-area splits - encoded once, applied identically every cycle.
On your template, per unit, with the reading and the math shown - the kind of invoice that doesn't generate a phone call.
Emailed to tenants or pushed into QuickBooks / your PM software. Books and records stay in sync without copy-paste.
Anything odd lands in a review list instead of a tenant's mailbox. Your team reviews the five weird cases, not all two hundred.
Usually gathered in one email thread. No preparation beyond finding the documents you already have.
No - any metered utility: water, electricity, gas, heat. Same pipeline, different rates.
Photos of the dials work - readings get extracted and validated like any other input. When you upgrade to smart meters, the pipeline stays.
Validation catches it before invoicing and routes it to review. A billing run that used to take days becomes an hour - most of it review, not typing.
Send two or three sentences about how this works in your office today. You'll get a concrete answer, not a pitch deck.
Tell me about your process