Data collection settings

Navigate to Settings > Company to configure how data is collected, validated, and displayed for the selected company. Company admins can edit these pages; other members generally cannot access Company settings unless they are site-only members with access to Sites. If you manage multiple companies, use the company switcher in the sidebar first. This page documents Data Collection, Bill Issues, and Anomaly Detection — the three settings areas that control ingestion defaults and automated quality checks.

---

​

Data Collection page

Open Settings > Company > Data Collection. The page is organized into four cards. Each card is its own form with separate Save changes and Reset actions — saving one card does not save the others.

​

Meter tags

Meter tags are company-defined labels for organizing meters.

• Existing tags appear as badges at the top of the card
• Click Manage tags to create, rename, or delete tags
• Assign tags from a meter’s edit form or in bulk from the meters table
• Tags appear in meter filters (for example Settings > Company > Data meter tag filter on the meters inventory page)

Tags do not change how bills are parsed. They help you filter and report after data arrives.

​

Collection rules

Collection rules control ingestion behavior, processing speed, and which optional fields appear company-wide.

​

Implied metering for wastewater

When a utility bill has water usage but no separate sewer reading, Nectar can estimate wastewater usage from water usage. Example: 1,000 gallons of water with fraction 1.0 creates an estimated 1,000 gallons of sewer usage. See Implied metering for methodology.

​

Cost tracking

The Cost tracking toggle is on by default. It is saved with the Collection rules card. When on, you typically see:

• Total charges on bills in Data Inventory and on bill detail views
• Charge and line-item fields in manual entry (total charges, tax, credits, line items, and related review fields)
• The Cost subtab on site dashboards
• Cost Management in the sidebar (when your subscription includes cost analytics)
• The Export Cost Data card on Data Export

When off, Nectar emphasizes usage, demand, and emissions:

• Cost columns, cost subtabs, and cost navigation entries are hidden
• Manual entry skips charge and line-item steps; submitted bills omit line items even if you had started a draft with them
• Usage data, demand meters (when enabled), and emissions workflows continue unchanged

Some cost analytics capabilities also depend on your subscription. If cost features are missing after enabling the toggle, email [email protected].

​

Dates and forwarding

​

Confirming a start-month change

If you change the Data collection start month from an existing value, Nectar shows a confirmation dialog before saving:

• Moving earlier — Nectar warns that additional historical data may be processed, which can affect billing usage.
• Moving later — Nectar explains that collection applies from the new month forward; existing historical data is not deleted.

Connection-level and account-level start dates override this company default when set. See Data collection start date.

​

Default units

Choose the display unit for each utility type. Usage values are converted to these units in tables, exports, and analytics. Bills may still store native units from the utility; these settings control normalized display.

---

​

Bill issue settings

Open Settings > Company > Bill Issues. This page controls which data quality issues Nectar detects on newly processed bills. Use it to reduce noise from issue types your team routinely accepts. The page has two sections: Company defaults and Custom suppression rules.

​

Company defaults

A table lists every suppressible issue type with a Detect switch per row.

• Detect on — Nectar flags this issue type on new bills (subject to any narrower suppression rule below)
• Detect off — Nectar skips this issue type company-wide unless a custom rule says otherwise

Issue types you can toggle include: Two issue types cannot be turned off at the company level because they indicate data integrity problems that must surface:

• Unmatched account
• Account/meter mismatch

For full definitions, see Issues — issue types or the glossary.

​

Custom suppression rules

When a single utility provider, connection, or account should ignore one issue type, add a custom suppression rule: Inheritance: Bills follow company defaults everywhere except where a custom rule overrides a specific (entity, issue type) pair. Triage open issues from Data Quality > Issues.

---

​

Anomaly detection settings

Open Settings > Company > Anomaly Detection. This page appears only when your company has access to anomaly detection. If you do not see it in the sidebar, contact [email protected].

​

Master toggle

The first card contains Enable anomaly detection for this company.

• Off — No anomaly pipeline runs; threshold configuration is hidden. Per-site override rows are preserved so settings return when you re-enable detection.
• On — Nectar runs detection daily at 00:00 UTC and surfaces results on Data Quality > Anomalies.

Save this toggle separately from the threshold form below.

​

Detection thresholds

When detection is enabled, configure company-wide thresholds in the Anomaly settings form. Settings are grouped by anomaly type: Each spike type uses its own enable toggle and sensitivity per commodity. Bill-level types (late fee, high demand charges) use paired dollar and percent minimums.

​

Per-site overrides

The Per-site configuration card summarizes how many sites inherit company defaults vs have custom rows. Open Manage all sites to edit site-level settings, including the Anomaly Detection tab on individual site settings. Site overrides can adjust individual cells without changing company defaults for other sites.

---

​

How these settings work together

• Data collection start month and default units shape what is collected and how usage is shown
• Bill issue settings control which parsing and matching problems create triage items
• Anomaly detection settings control statistical and rule-based spikes after data is in the platform
• Cost tracking controls whether financial fields appear in inventory, entry, exports, and analytics — independent of usage collection

---

​

Frequently asked questions

See also: Company settings, Issues, Anomalies, Connections — configuration