Skip to main content
Use this page to troubleshoot export generation and third-party delivery issues.

Frequently asked questions

Open Export History, retry the download, and if needed rerun the export to generate a fresh artifact.
Check date range, site filters, utility filters, and whether flagged bills are excluded. Also confirm data exists in Data Inventory for that scope.
Complete required integration settings (such as API key and customer/account mapping fields), save configuration, then retry export.
Discrepancies typically indicate mismatches between Nectar and the destination platform (for example, missing externally, missing in Nectar, or field-level mismatch).
UI exports are on demand. For recurring jobs, use the API Reference with the Developer guide to automate pulls.
Start with targeted retries using the failed-item list. Full reruns are only necessary when failures are broad or configuration changed globally.
Run controlled tests in Sandbox testing, then compare exported records in both Nectar and the destination platform before production rollout.
The property page compares Nectar to ESPM one commodity at a time. Select utility type and a date range so units and ESPM comparisons line up. See Energy Star.
Same idea, different surfaces: Quick export filters which commodities go into a spreadsheet. Energy Star property detail picks which commodity you are reconciling against Portfolio Manager for that building. Each respects its own form.
Open Export history. Artifacts are retained for a limited window—regenerate if a download expired.

Data export overview

Choose between quick exports and integrations.

Quick export

Generate ad-hoc CSV/XLSX files.

Integrations

Push data to external reporting platforms.

Export history

Re-download and audit recent exports.