Skip to main content
If you rely on Cass for utility invoice processing and payment-adjacent services, Nectar can become your operational system for utility data quality, structure, and downstream analytics.

How Cass workflows are usually organized

Public Cass materials commonly emphasize:
  • High-volume invoice intake and processing
  • Payment and disbursement management
  • Cost allocation and ERP-ready reporting outputs
This setup is effective for payable operations. Teams often need an additional layer for utility data normalization, meter-level context, and sustainability analytics.

How your Cass data maps to Nectar

Cass-style source conceptNectar destinationMigration notes
Business unit or cost-center hierarchyCompany + siteKeep allocation hierarchy and reporting tags.
Vendor and utility account referencesAccountPreserve account IDs and utility metadata.
Facility-level utility service pointsMeterAdd commodity and units for analytics consistency.
Invoice headers and line-item chargesBillRetain invoice numbers, service periods, and charge categories.
Consumption and demand detailsUsage dataNormalize units and fill missing metadata before cutover.
Cost allocation outputsData Export viewsRebuild allocation-ready exports for finance consumers.
1

Capture current reporting requirements

Document allocation dimensions, required fields, and month-end reconciliation expectations.
2

Extract historical invoice and usage data

Pull account, invoice, and consumption datasets for a representative historical window.
3

Map to Nectar operational model

Align costs and usage to companies, sites, accounts, and meters, then validate source IDs.
4

Pilot and reconcile outputs

Validate pilot results against existing Cass outputs for totals, periods, and allocation tags.
5

Scale and cut over

Expand to full portfolio, then transition recurring reporting and QA into Nectar.

What improves in Nectar

  • More utility-context detail for each invoice and usage record
  • Better issue detection and correction before downstream reporting
  • Stronger bridge between payable data and sustainability analytics

Features to evaluate in Nectar

Depending on your current Cass operating model, Nectar may add:
  • Utility-specific onboarding workflows for ongoing source collection
  • Built-in Data Quality monitoring for anomalies and missing periods
  • Richer analytics across commodity, site, and historical trends

Nectar support during migration

Nectar provides:
  • Mapping design sessions with finance and operations stakeholders
  • Pilot-side reconciliation and sign-off checkpoints
  • Cutover support and post-launch optimization

Ready to migrate from Cass?