The origin of a measurement value tells you where it came from, for example directly from the device or entered by someone. The reading method indicates how the value was obtained, for example automatically or manually.
If your organisation uses this feature, this information is stored with readings and, depending on your invoice template, can appear as a legend on the invoice. This helps end customers better understand the figures behind their consumption lines.
What origins are there?
Depending on your settings, a measurement value can be labeled with one of these origins:
Device: the value comes from automatic meter reading or standard import without an explicit choice.
Customer: the customer submitted the value, for example via self-entry.
User: a user entered or corrected the value
Estimated: the value was derived or filled in as an estimate, not a direct reading.
The reading method distinguishes between readings that come in automatically and values that were entered manually.
Where do you set origin and reading method?
When the feature is enabled for your organisation, you’ll see extra fields for origin and reading method when adding or editing measurements on the meter. For a new manual measurement, user and manual are often proposed by default; you can adjust this if it fits your situation.
If your organisation does not use this feature, these fields are not shown and origin and reading method are not stored.
What about measurement data from a file (import)?
If origin is enabled, you can include columns for origin and reading method in import files, where your supplier or the import format supports this. If these values are missing from a row, the default values are used (typically Meter and Automatic). Incorrect or unrecognised values in those columns may cause the row to be rejected; correct the values according to the agreed format and re-import.
What do you see on the invoice?
If your invoice template is configured to display origin, a legend may appear with numbers referring to the different origins that occurred during the measurement period. This allows end customers to see whether a start or end reading came from the meter, from the customer, or was estimated, provided that information is available for that period.
The labels for these origins can also be configured via communication/templates and the labels:
Label_OriginLegend_Device, Label_OriginLegend_Customer, Label_OriginLegend_User, Label_OriginLegend_Estimated
Note: Origin and reading method are only available when your organisation has explicitly enabled this option in the settings. Without that option, screens and invoices continue to work as before, but without these labels.
Problem | Solution |
I don’t see any fields for origin or reading method anywhere. | Ask an administrator whether the origin of meter readings option has been enabled for your organisation. Without this setting, the fields are not shown. |
My import file is rejected or reports an error on origin. | Check that the values exactly match what the import format allows. Leave cells empty if defaults are desired, or fill in valid values according to the import profile instructions. |
The legend or the reference to origin is missing on the invoice. | Check whether origin is enabled, whether origin was recorded for the period, and whether your invoice template supports this display. Contact your implementation or billing administrator if needed. |
What is the difference between origin and reading method?
Origin says who or what the source of the value is (Device, Customer, User, Estimated). The reading method indicates how the value was obtained, typically automatic versus manual.
Which default applies to an import if I don’t fill anything in?
If the feature is on and you leave origin or reading method empty, the default values are usually used: Device and Automatic, unless your import has other arrangements about this.
Why does a new manual measurement often show “user” and “manual”?
That’s a practical default for measurements you add yourself in the platform: they are labelled as manually entered by a user. Adjust it if the actual situation is different.







