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

​
Frequently asked questions

Issues are record-level problems (for example, connection errors or bill anomalies). Completeness gaps indicate missing expected coverage over time.
Not always. It can reflect delayed utility publication, connection downtime, or start-date settings. Validate connection status and expected billing cadence first.
Start with active connection failures, then unresolved bill anomalies, then completeness gaps that affect your reporting period.
Yes, but bills with open issues are excluded by default in exports. You can toggle this in the export wizard. Review your export settings and resolve critical issues before final reporting.
A bill issue is a data quality problem detected on a specific bill — for example, a potential duplicate, missing usage data, or an unmatched account. Each issue has a type, severity, and guided resolution steps. See Glossary — Bill issue.
Open the bill from Data Quality > Issues or click it in the Data Inventory > Bills table. Resolution cards appear above the bill tabs. Follow the guided steps for each issue — options include comparing duplicates, editing data, dismissing the issue, or reporting it to support.
Yes. In the Data Quality > Issues triage inbox, select multiple bills using the checkboxes, then click Bulk actions to resolve a specific issue type across all selected bills at once.
Dismissing marks the issue as resolved — the bill stays in your portfolio and its data is included in analytics and exports. Deleting permanently removes the bill from your inventory. Use delete only when the bill should not exist (e.g., a non-utility document).
The bill is no longer flagged. Its data is included in analytics dashboards and exports. The resolution is recorded in the bill’s audit log.
Retry and narrow filters (company/site/date). If errors persist, capture the URL and error message for support 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.
The cell reflects whether expected usage data (or bills, depending on configuration) exists for that entity and month. Flagged bills, wrong site assignment, or calendar boundaries can still show a gap. Use the gap detail Bills and Usage tabs to see what Nectar counted for the period.

Data quality overview

Summary of quality workflows and detection types.

Issues

Triage and resolve bill data quality issues.

Completeness

Track period-level data coverage and gaps.

Data input FAQ

Troubleshoot upstream collection failures.