Skip to main content
Video walkthrough coming soon. A Loom video demonstrating this feature will be added here.
If you’re using utility data for carbon reporting, energy procurement, or ESG disclosures, accuracy matters. A missing month of electricity data or a wrongly-matched meter can throw off your entire report. That’s why Nectar gives you tools to catch problems before they reach your downstream systems. Think of Data Quality as the inspection step between collecting your data and using it. Just like an accountant reviews financials before filing taxes, you should review your utility data before submitting a CDP report or feeding numbers into your carbon accounting platform.
Screenshot coming soon. A screenshot of this feature will be added here.

Issues dashboard

Think of the Issues page as your quality control checklist. It shows two types of problems: connection issues (problems getting data from a utility portal) and bill issues (problems with the data itself).

Connection issues

Connection issues mean Nectar can’t log in to a utility portal to collect new bills. These are the digital equivalent of a locked mailbox — the bills are there, but Nectar can’t reach them. Common causes include:
  • Password changed — someone updated the password on the utility website, but Nectar still has the old one
  • MFA needed — the utility portal is asking for a verification code or security question that Nectar can’t answer automatically
  • Portal unavailable — the utility’s website is temporarily down for maintenance or has been redesigned
  • Account locked — too many failed login attempts, or the utility has disabled the account
Each connection issue links directly to the affected connection, so you can jump in and fix it. For step-by-step resolution instructions, see the troubleshooting guide.

Bill issues

A flagged bill is one that Nectar’s system — or a human reviewer — has marked as needing a second look. Imagine a bookkeeper who puts a sticky note on a receipt that looks suspicious. That’s essentially what a flag is.
FlagWhat it meansReal-world example
Potential duplicateTwo bills have overlapping dates and matching accountsThe same January electric bill was downloaded twice because the utility posted it in two formats
Illegible billThe PDF couldn’t be fully read by Nectar’s AIA scanned paper bill with coffee stains or low resolution
Unmatched accountThe bill’s account number doesn’t match any known accountA new account was added to the utility portal that Nectar hasn’t seen before
Missing usageCharges were found but no usage dataA summary bill that shows dollar amounts but not kWh or therms
Extraction errorProcessing failed entirelyA bill in an unusual format or a corrupted PDF
To resolve a flagged bill, click through to it and review the extracted data. You can correct values, unflag the bill once it looks right, or delete it if it’s truly a duplicate.

Data completeness

Completeness tracking helps you answer the question: “Do I have all the data I need?” This is especially important if you’re preparing for a CDP submission or an annual sustainability report where every site and every month must be accounted for. Think of it like taking attendance. If you manage 50 buildings and need 12 months of electricity data for each, that’s 600 data points you need. Completeness tracking tells you exactly how many of those 600 you actually have.

Coverage timeline

The completeness page displays a coverage timeline — a visual grid where each row represents an entity (a site-utility pair, account, or meter) and each column represents a billing period. Cells are color-coded: green checkmarks for complete periods, red crosses for missing data, and dashed outlines for future months. You can switch between three views using the group by control:
  • Sites — Rows show site-utility combinations (e.g., “Building A — Electricity”), grouped by site name.
  • Accounts — Rows show individual billing accounts, grouped by connection name.
  • Meters — Rows show individual meters, grouped by account number. (Admin only.)

Gap detail sheet

Click any cell in the timeline to open a detailed side panel. The gap detail sheet shows the status of that specific entity and period, along with four tabs of supporting data:
  • Bills — Shows bills covering the target month plus the months immediately before and after, for context.
  • Meters — A per-meter breakdown showing which meters have data and which do not.
  • Usage — A historical usage chart with gap months highlighted, so you can see patterns.
  • All Gaps — Every gap for this entity in the current reporting period, with the ability to navigate between them.

Resolving data gaps

When you find missing data, you can take action directly from the gap detail sheet:
1

Upload the missing bill

Click Upload bill to open the upload page, where you can add a missing PDF or CSV document. Nectar will extract the data automatically.
2

Enter data manually

Click Enter manually to open the manual entry form. Use this when you know the consumption and cost values from an email or a paper bill.
3

View in Data Inventory

Jump to the Bills table filtered to this entity to investigate what data already exists.

Filtering and sorting

The completeness page provides several ways to focus on the data that matters most:
  • Period — Select a reporting period using the month range filter. When first visiting the page, you can choose from quick presets like “Last 12 Months” or the current calendar year.
  • Coverage — Filter entities by severity tier: Critical (0–50%), Low (50–75%), Fair (75–95%), or Good (95–100%).
  • Site — Narrow the view to specific sites.
  • Sort — Order entities by name (A→Z or Z→A) or by coverage percentage (lowest or highest first).
Data quality features are actively evolving. New completeness metrics, automated gap detection, and anomaly flagging are in development. Check the changelog for updates.

FAQ

For CDP submissions and most sustainability reports, you should aim for 100% completeness across the reporting period. In practice, 95% or higher is considered strong. If you’re below 90%, there are likely systemic gaps — maybe a connection is broken, or a group of accounts was added late. Start by fixing the largest gaps first.
Navigate to Data Quality > Completeness and select a reporting period. The coverage timeline highlights missing periods with red cells. The summary statistics at the top show the total number of gaps across your portfolio.
Nectar flags a bill as a potential duplicate when it finds another bill with overlapping service dates for the same account. This often happens when a utility posts the same bill in multiple formats (PDF and CSV, for instance), or when a bill is manually uploaded that Nectar had already collected automatically. Open both bills, compare them, and delete the true duplicate.
It depends on the type. A simple password update takes minutes — you update the credentials in Nectar and the connection resumes. MFA challenges might require coordination with the account holder. Portal outages resolve on their own when the utility’s website comes back online. For issues under investigation by the Nectar team, resolution typically takes a few business days.
Gray dashed cells with a dot represent future months — billing periods that haven’t occurred yet. No data is expected for these periods, and they don’t affect your completeness score.
Yes. If you have utility data in a spreadsheet, email, or another system, you can upload it or enter it manually in Nectar. Once the data is in your inventory, it counts toward completeness. The source doesn’t matter — what matters is that the data exists and is accurate.
Completeness tracking starts from the data collection start date configured for each connection or account. If you set the start date to January 2023, Nectar will track completeness from that point forward. It won’t flag gaps before your configured start date because you’ve told Nectar you don’t need data from before then.