Skip to main content
If your team runs utility operations in spreadsheets, you are not alone. Many teams start there and eventually hit limits on quality control, collaboration, and scale.

How spreadsheet workflows are usually organized

Common spreadsheet setups include columns for:
  • Utility provider and account number
  • Site address or building name
  • Billing period start/end
  • Usage values (for example kWh, therms, gallons)
  • Charges, due dates, and payment status
  • Notes for exceptions and follow-up
These files are flexible, but they become hard to govern when multiple people edit them across monthly cycles.

How your spreadsheet data maps to Nectar

Spreadsheet column groupNectar destinationMigration notes
Client or business-unit columnCompanyUse a stable company ID during import.
Building or address columnsSiteStandardize address formatting before load.
Utility account numberAccountKeep original account numbers for reconciliation.
Meter ID or service point columnsMeterAdd commodity and units if missing.
Billing period + charge columnsBillValidate date boundaries and currency conventions.
Usage and demand columnsUsage dataNormalize units before trend analysis.
Exception notesData Quality issuesConvert free-text notes into structured QA workflows.
1

Audit your source spreadsheets

Identify canonical files, remove duplicates, and define the authoritative columns for each utility type.
2

Standardize format

Normalize headers, dates, units, and account IDs. Nectar provides templates to accelerate this step.
3

Load structure first

Import companies, sites, accounts, and meters before loading bills and usage records.
4

Run historical backfill

Import historical billing periods and usage data, then reconcile totals by month and site.
5

Replace manual collection

Shift future intake to connections, uploads, or magic links.

What improves in Nectar

  • No more version-control issues across spreadsheet files
  • Faster month-end close with structured QA and completeness checks
  • Better accountability through role-based workflows and audit trails
  • Easier downstream reporting with repeatable exports

Features to evaluate in Nectar

Compared with spreadsheet operations, Nectar adds:
  • Automated utility collection workflows
  • Built-in anomaly and missing-data detection
  • Unified analytics and export tooling from the same dataset

Nectar support during migration

Nectar helps you move quickly without losing confidence:
  • Spreadsheet-to-platform mapping support
  • Pilot validation with side-by-side reconciliation
  • Enablement for analysts and reporting teams

Ready to leave spreadsheets behind?