Issues

Navigate to Data Quality > Issues to open the triage inbox — a dedicated workspace for reviewing and resolving data quality issues on your bills and meters.

​

Triage inbox

The Individual triage view uses a split-pane layout:

• Left panel — A scrollable list of records (bills or meters) that have open issues. Each row shows key identifiers, site, and a primary issue-type badge with the detail underneath.
• Right panel — When you select a record, the right panel fills with the full-pane bill document preview (or, for issues about a meter, a meter context view that flips through the bills observed on that meter). A collapsible context rail anchored to the right edge surfaces what the system found, the verdict, suggested actions, and supporting evidence. A sticky footer dock at the bottom shows the active issue’s severity and a Resolve dropdown.

When you’re elsewhere in the platform (a bill page, a meter page) and an issue applies, an inline alert with a View action opens the same investigation in an Issue sheet — the same content as the right pane, in a slide-over that overlays the current page.

​

Filtering

Use the filter bar at the top to narrow the list:

• Status — Toggle between Open (default), Resolved, or All issues
• Issue type — Filter by one of the six top-level issue categories (Inference, Duplicates, Account match, Meter issues, Unusable bill, Other)
• Site, Connection, Utility provider, Bill date, Created date, and more — add from the + Add filter menu

​

Issue types

Nectar automatically detects these issue types during bill and meter processing. Issues are organized into two flag levels:

​

Action required

These issues indicate a problem that needs resolution before the data can be trusted in analytics and exports.

​

Review and verify

These issues flag bill data that was inferred rather than extracted directly. The data may be correct, but you should verify it.

​

Meter issues

These issues are about a meter rather than a bill, and surface when a meter’s location can’t be matched confidently.

​

When is data excluded?

Whether a bill’s usage and cost are withheld from analytics depends on what the issue is about — not on its “Action required” / “Review and verify” label.

• Issues about a bill (for example, a potential duplicate or an unmatched account) withhold that bill’s usage and cost from analytics dashboards and exports until the issue is resolved.
• Issues about a meter (for example, a low-confidence site or address match) don’t withhold usage.

When you open an analytics view (site, account, meter, or portfolio) where bills are withheld, a banner tells you how many bills are affected and links straight to the issues responsible.

​

Resolving issues

Select a record in the left panel to open the investigation in the right panel. The footer dock at the bottom of the panel surfaces the active issue’s severity (red for action-required, amber for review-and-verify, blue for informational) and a Resolve dropdown driven by that issue’s resolution config:

• Compare duplicates — Opens a side-by-side document comparison for potential duplicates
• Assign account / Assign site — Reassign a bill or meter to the correct account or site
• Edit dates / units / container / address — Open a focused editor to correct inferred or missing values
• Apply suggestion — When the context rail surfaces a strong suggested value (e.g. units the system is confident about), an Apply: <value> link prefills the edit dialog so you only have to confirm
• Dismiss — Mark the issue as resolved with an optional note explaining why
• Delete record — Permanently remove the record if it should not be in your portfolio
• Report to support — Send the issue to the Nectar team for further investigation

After resolving all issues on a record, the triage inbox automatically advances to the next record with open issues.

​

Bulk resolution

To resolve the same issue type across multiple records at once:

​

Grouped triage and Overview

In addition to the per-record Individual view, the Issues module exposes two complementary surfaces for spotting patterns:

• Grouped triage — Switches the triage page to roll issues up by connection, account, datasource (utility provider), or site, depending on which issue type is in scope. For example, hundreds of duplicate flags might collapse into a handful of connections that share the same root cause; a verdict-driven footer lets you act on the entire selection at once. The grouped view requires an Issue Type filter to be set so the rollup stays focused.
• Overview — A dashboard of tiles at /data-quality/issues/overview summarizing open issues across the portfolio: a stat strip (open / action-required / resolved), a per-type breakdown, top utility providers and top sites by open-issue volume, and quick links into Triage and the Issues settings page.

​

What happens when issues are resolved?

• The record is no longer flagged in your data inventory
• If it was an issue tied to a bill, that bill’s usage and cost are included in analytics dashboards and exports again
• The resolution is recorded in the audit log with the user who resolved it and any notes

See also: Glossary — Data quality issue, Bill detail