Skip to main content
Use this page to troubleshoot quality checks and completeness gaps.

​
Frequently asked questions

Issues are problems on a bill or meter (for example, a duplicate, unmatched account, or low-confidence field) and, when enabled, anomalies. Completeness gaps indicate missing expected coverage for a month. Connection errors are not Issues inbox rows — fix those in Data Input (see also Data input FAQ).
Not always. It can reflect delayed utility publication, connection downtime, or start-date settings. Validate connection status and expected billing cadence first. See Filling data gaps.
Start with active connection failures in Data Input, then open action-required bill issues (and anomalies if you use them) in the Issues inbox, then completeness gaps that affect your reporting period.
Yes, but bills with unresolved bill-tied issues are excluded by default. Meter issues (site match, address mismatch, container size) do not drop the bill. In the export wizard, use Include bills with unresolved issues (analytics) or Include records with unresolved issues (integrations). Resolve critical issues before final reporting.
A data quality issue is a problem detected on a specific bill or meter — for example, a potential duplicate, missing usage data, or an unmatched account. Each issue has a type, severity, and guided steps under Resolution options in the triage inbox or Issue sheet. See Glossary — Data quality issue.
Open Data Quality > Issues and Anomalies > Triage, or open the bill or meter and click View on the issue alert (if several issues are open, pick one first). Use Resolution options in the detail header or Issue sheet — not cards above tabs. Follow the guided steps for that type: compare on the duplicates pane, Edit dates / Edit usage units, type-specific dismiss, Reassign site, or Contact support.
Yes. In Individual triage, select one or more records of the same Kind (issues or anomalies) with the checkboxes, then click Bulk actions. Choose Begin resolving {type}… (N), Assign site… (N) when meters have location issues, or Export… (N). In Grouped view, check constituent rows and use Resolve selected.
Dismissing marks the issue as resolved — the record stays in your portfolio. After you dismiss a bill-tied issue, that bill returns to analytics and exports; meter issues were never withheld. Deleting permanently removes the bill (for example Delete this bill or Delete the other bill). Use delete only when the record should not exist (wrong document or confirmed duplicate).
Issue badges and alerts clear. If the resolved issues were bill-tied, that bill’s data is included in analytics dashboards and exports again. Who resolved it, when, and any notes are stored on the issue (resolved view and Resolution summary).
Retry and narrow filters (company/site/date). If errors persist, capture the URL and error message and email support@nectarclimate.com so the failing scope can be diagnosed quickly.
For gaps with site context, Inspect opens the Aggregation Inspector for that month. It breaks down how site totals are built from meters, which helps explain unexpected completeness or usage totals. See Completeness for the full sheet layout.
Drilling from a site row into an account can open a second panel on top so you do not lose site context. Close the top panel to return to the main swim lane.
Yes. Filters are stored in the URL—copy the address bar after setting period, severity, sites, and any + Add Filter options to share the same view with a teammate. Large Site selections can live in session storage, so a pasted link may omit the full site list and a teammate may need to re-pick sites.
The cell reflects whether expected usage data (or bills, depending on configuration) exists for that entity and month. Wrong site assignment or calendar boundaries can still show a gap. Open issues do not make a month missing — completeness still counts those bills. Use the gap detail Bills, Excluded, and Inspect tabs (site view), and Trends for the usage chart, to see what Nectar counted for the period.
Yes. Fuel and waste are spot-delivery commodities — deliveries happen on individual days, not continuously. For these commodities, a month is Complete as long as at least one delivery record exists. A month with zero deliveries is Missing. This differs from electricity, gas, and water, which require more continuous day-level coverage.

Data quality overview

Summary of quality workflows and detection types.

Issues

Triage and resolve bill and meter issues (and anomalies).

Anomalies

Cost, usage, and fee anomalies in the same Issues inbox.

Completeness

Track period-level data coverage and gaps.

Savings

Review estimated bill savings (when enabled).

Filling data gaps

Diagnose missing months and choose the right fix.

Data input FAQ

Troubleshoot upstream collection failures.