Anomaly detection is off by default. Turn it on in Settings > Company > Data Quality > Anomaly detection. Once enabled, Nectar checks your data automatically every day, and you can run a check on demand at any time.
What Nectar looks for
Each anomaly points you to the relevant site or account and time period, plus a commodity when applicable.
How detection works
For usage, cost, and unit-price anomalies, Nectar compares each site against its own recent history and accounts for weather. This helps prevent normal seasonal swings from being flagged.Weather-aware detection uses historical temperature data from Open-Meteo, licensed under CC BY 4.0. Nectar processes this data into heating and cooling degree days for each site and period.
Sensitivity
Weather-aware anomaly types have a sensitivity setting:
Higher sensitivity catches more, but may include some patterns that turn out to be normal. Lower sensitivity is quieter but may miss smaller changes. Other anomaly types use settings suited to their check, such as a minimum charge amount or an archive grace period.
Where to find anomalies
Anomalies appear in your Data Quality inbox alongside other data quality items — there’s no separate page to check. From the inbox you can:- Filter to anomalies (and by type, site, or commodity) to focus your review.
- Open an anomaly to review its evidence. Depending on the type, this may be a trend chart, bill-cost view, or table of flagged bills.
- Resolve it once you’ve addressed it, or dismiss it if it isn’t a real problem.
Getting value out of anomalies
- Catch overspend early. Cost and unit-price anomalies highlight bills that cost more than expected — often a rate change, a billing error, or a usage problem worth chasing.
- Stop paying avoidable fees. Interest-charge anomalies surface late fees so you can fix the underlying payment or billing issue.
- Spot operational issues. Usage anomalies (including unexpected drops) can reveal equipment left running, meters that stopped reporting, or changes in how a building is used.
Improving accuracy
If an anomaly’s chart shows gaps or unexpectedly low months, the underlying data may be incomplete — and incomplete history can make a normal period look unusual. Records with open data quality issues (such as unmatched accounts) are left out of the analysis. If a site has many unresolved issues, resolve them in your Data Quality inbox — the next check will use the corrected data and produce more accurate results.Related pages
- Data Quality overview — issues, completeness, and anomalies
- Data collection settings — company-level data quality controls
- Sites — view per-site data