> ## Documentation Index > Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # Meter readings on the handset > Walking a site writing down what the dials say — utility meters and asset hour meters, in one list. Writing down what a dial says, standing in front of it — the most offline job a site has: a basement, a substation cupboard, a locked door. ## Two kinds of meter, one list A utility supply point and an asset's own hour meter are different records under the hood, but from a handset they're the same act — somebody walks up to a dial and writes down a number — so they share one screen rather than two. * **Supply points** feed [energy management](/energy/energy-management): what a utility meter reads, priced from the tariff in force. * **Asset meters** feed [meters and readings](/assets/meters) on the asset itself, and any maintenance due against a reading rather than a date. ## What's on the row The **last reading** is shown before you type the new one — the whole reason it's there rather than a blank box. A register that read 89,412 last month and reads 8,941 today is a transposed digit, and standing in front of the meter is the only place anybody catches that; at month end, it's a negative month somebody has to explain instead. You enter the **register**, never the consumption. What that reading means — the difference from last time, a dial that wrapped around, a replaced meter, what it costs at the tariff in force — is worked out on the server once the reading arrives. ## What "outstanding" means For a supply point, outstanding means **not read this billing period** — there's no schedule on a utility meter, so this is the app's own reading of a month rather than a due date the server enforces. Asset meters aren't held to that: maintenance against a reading is due on whatever the asset's own plans say, not on a calendar the readings screen would have to reimplement, so they're listed plainly with what they last said rather than marked overdue. A reading you've just queued drops off the outstanding list immediately, even before the next sync — the list has to reflect what you just did, not what the server has heard about yet. Meters on an asset, and what maintenance a reading can trigger. Supply points, tariffs, and what a reading is priced at.