> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nectarclimate.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Sphera
> Sphera integration for integrated sustainability and risk management.
Need help in this area? See [Data Export FAQ](/platform/data-export/faq).
The Sphera integration connects Nectar to SpheraCloud Corporate Sustainability. Nectar pushes per-bill utility data to Sphera's Data Import (DI) channel — via API or as a downloadable spreadsheet — and reads stored values back through the Data Acquisition (DA) channel to compare them against your Nectar data month by month.
## Setup wizard
The first time you configure Sphera, the integration page links to a setup wizard with four steps:
1. **Channels** — Your Sphera host (for example `yourcompany.cs.spheracloud.net`) and API route, plus the channel GUIDs. The DI channel is required for pushing; the DA channel is recommended so Nectar can read values back for comparison.
2. **Credentials** — The connection key and secret for each channel. **Test connection** verifies each channel against the live Sphera API before you continue.
3. **Site mapping** — Nectar [sites](/platform/glossary#site) matched to the Sphera sites discovered through the DA channel, with a smart-match suggestion and the option to exclude sites.
4. **Review** — A summary including the CSV column names used for the DI push.
## Integration page
Navigate to [**Data Export > Integrations > Sphera**](https://dash.nectarclimate.com/data-export/integrations/sphera) for the integration hub — a single-page layout (not tabbed):
* **Page header** — **Archive** and **Settings**
* **Warning banners** — Legacy push-only config, unmapped sites, or missing DA channel (read-back)
* **Status card** — **DI + DA connected**, **DI only (push)**, **Not configured**, or **Legacy config**, with an **Export** button
* **Recent syncs & downloads** — Latest Sphera exports and DI pushes
* **Monthly usage comparison** — When the DA channel is configured, per-site Nectar vs Sphera comparison for a selected site, commodity, and month range
If any sites are not yet mapped to a Sphera site, a warning banner links to site mapping in settings. Unmapped and excluded sites are skipped when pushing to Sphera via API — map or exclude each site so the push covers everything you expect.
### Exporting
Click **Export** to open the export dialog and configure the export:
| Field | Description |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Export name** | A label for this export (appears in Export History) |
| **Date range** | Start and end dates for the billing periods to include |
| **Utility types** | Multi-select to include specific commodities (electricity, gas, water, etc.). Leave empty for all. |
| **Sites** | Multi-select to scope the export to specific sites. Leave empty for all. |
| **Filter by** | Choose whether dates refer to the **meter date** (service period), the **bill date** (invoice date), or the **created date** |
| **File type** | Choose **xlsx** or **csv** |
| **Upload to Sphera** | Toggle on to push the data to Sphera's DI channel via API in addition to downloading the file |
| **Include flagged bills** | Toggle on to include bills that have data quality issues |
Each exported row is one bill and carries the bill's account, meter, invoice, and audit-link metadata so values can be traced back to their source. The export is recorded in your [Export History](/platform/data-export/export-history).
Sphera DI imports **append** — re-pushing a period does not overwrite the previous rows. If you need to correct data already in Sphera, delete the affected entries in Sphera first, then re-push. Nectar shows this reminder before every re-push.
### Monthly usage comparison — find and resolve discrepancies
When the DA channel is configured, the comparison section reads the values stored in Sphera (through the Data Acquisition channel) and diffs them against Nectar's calendarized monthly usage. Use it to confirm Sphera holds the right numbers and to re-push the ones it does not.
**How to use it:**
1. **Set the scope with the filters:**
* **Site** (pinned) — One mapped Sphera site at a time. Only sites mapped through the DA channel appear.
* **Commodity** — The utility type to compare. Only commodities with a configured questionnaire template appear.
* **Months** (required) — The month range to compare; clearing it resets to the current year.
2. **Read the usage chart** — Nectar's calendarized monthly usage and the values stored in Sphera are plotted side by side.
3. **Scan the monthly comparison table** — Each row shows the month, Nectar value, Sphera value, the percentage difference, and a status. **Expand a month** to list the contributing bills that make up Nectar's total for that month; click a bill to open it, or open the matching bills in [Data Inventory](/platform/data-inventory/overview).
**Statuses:**
* **Synced** — Sphera matches your data for that month
* **Diff** — Both sides have data but the values differ
* **Not on Sphera** — Nectar has data Sphera never received
* **Missing in Nectar** — Sphera holds a value your data no longer produces
**Resolving discrepancies:**
* **Per row** — Click **Push** (for *Not on Sphera*) or **Sync** (for *Diff*) on the row to re-push that month.
* **In bulk** — Click **Resync N discrepancies** above the table to re-push every drifted or not-on-Sphera month in one go.
Sphera DI imports **append** — they do not overwrite. Before every re-push, Nectar shows a reminder to delete the existing entries for those months in Sphera first, otherwise the data is duplicated. If Sphera's data collection is **locked** through a cutoff date, months in the locked range are skipped and Nectar tells you which ones.
Sphera processes each import asynchronously, so re-pushed values can take a few minutes to appear in the comparison. If a month is wrong on the Nectar side, fix the bills in [Data Inventory](/platform/data-inventory/overview) before re-pushing.
## Settings
Manage the integration in [**Settings > Company > Integrations > Sphera**](https://dash.nectarclimate.com/settings/company/integrations/sphera):
* **Connection** — Sphera host, API route, and the DI/DA channel credentials (GUID, connection key, and secret per channel), with test-then-save verification
* **Site mapping** — Nectar sites mapped to the Sphera sites discovered through the DA channel, with exclusions
* **Questionnaires** — The Sphera questionnaire template that holds each commodity's data (applies across all sites)
* **Column names** — Overrides for the CSV header names on the DI push, so columns match your Sphera-side import definition
## FAQ
Sphera supports electricity, gas, water, waste, and other utility types. The available options depend on your Nectar data and Sphera configuration.
The Data Import (DI) channel receives data — it is how Nectar pushes bills into Sphera. The Data Acquisition (DA) channel is read-only — Nectar uses it to read the values stored in Sphera for the monthly comparison. You can run the integration with DI alone, but the comparison views require DA credentials.
First delete the affected entries in Sphera — DI imports append, so re-pushing without deleting duplicates the data. Then use the **Resync** action on the comparison (or run a scoped export) to re-push the corrected values.
Yes. Go to [Export History](/platform/data-export/export-history), find the export, and click to open the detail sheet. A **Download** button is available if the file is still within the 90-day retention period.