Each meter can have multiple identifiers — typed key-value pairs that Nectar uses for bill matching and display. Identifiers are extracted from utility documents during processing and stored on the meter record.
Bill matching — When a document is processed, extracted identifier values are compared against identifiers stored on each meter in the company. The meter whose identifiers match the document is linked to the usage data. All extracted identifiers must be present on the meter, and any extra identifiers on the meter must appear somewhere in the document text.
Display (Primary ID) — The platform resolves a single identifier value to display for each meter using a priority system. This displayed value is called the Primary ID. The resolution checks account-level preferences first, then falls back to a standard type ordering (METER > POD > ELECTRIC_CHOICE > PREMISE > SUBMETER > ESI > CHOICE_ID > SUB_ACCOUNT > ACCOUNT > SUMMARY_ACCOUNT > MPR > ICP > NMI > MIRN), then any available identifier.
Each account can configure a primary identifier type and secondary identifier type. These control which identifier is displayed as the Primary ID for all meters under that account. For example, setting the primary identifier type to ACCOUNT means the account number is shown instead of the meter serial number.
When utility providers consolidate or restructure accounts, Nectar links related records so reporting reflects the primary active account.Subaccounts link to the active account:In analytics and exports, this helps prevent duplicate counting.
An account can have meters at multiple sites. This commonly happens when a single utility login covers buildings at different addresses. Each meter is assigned to its own site based on address matching, while the account itself stays linked to the connection that discovered it.In analytics and exports, each meter’s data rolls up to its assigned site — not to the account’s site.
Meters can be assigned tags — company-defined labels for filtering and organization. Tags are managed per company and can be assigned individually or in bulk. Each tag has an id and a name. The tags field on the meter response returns the list of assigned tags.
Mirror sites are used for data completeness estimation. When a site is configured with a mirror, it uses the mirror site’s data as a proxy for missing periods. This is useful when a new site has no historical data but a similar building nearby can serve as a reasonable estimate until actual bills arrive.
