Issues
Triage and resolve bill data quality issues with guided resolution steps.
Completeness
Visualize coverage gaps and monitor whether every site has the data you expect.
Anomalies
Detect cost spikes, usage spikes, late fees, and demand charge anomalies across your portfolio.
How it works
Data quality checks run automatically as part of Nectar’s data pipeline:| Check type | Trigger | Examples |
|---|---|---|
| Connection issues | Each weekly connection check | Incorrect password, site down, MFA required |
| Bill issues | Bill processing | Missing usage data, duplicate bill, unmatched account, illegible scan, inferred dates or units |
| Completeness gaps | Daily roll-up | Missing billing periods, sites with no active connections |
Data quality features are actively evolving. New issue types and completeness views are added
regularly.
Related pages
- Troubleshooting connections — resolve connection errors that cause data quality issues
- Sites — view per-site completeness from the site dashboard
- Methodology — understand how Nectar processes and calendarizes bill data
FAQ
What types of issues does Nectar detect?
What types of issues does Nectar detect?
Nectar detects two broad categories of issues:
- Connection issues — problems that prevent bill collection, such as incorrect passwords, expired credentials, MFA challenges, or provider site outages.
- Bill issues — anomalies found during bill processing, such as missing usage data, duplicate bills, unmatched accounts, illegible scans, or inferred dates and units. See Issues for the full list of issue types.
How often are issues updated?
How often are issues updated?
Connection issues are updated each time a connection is checked, which happens on a weekly schedule. Bill issues are created or resolved whenever a bill is processed or reprocessed.