Every utility billing team knows what a smooth billing cycle feels like, and what it feels like when that cycle breaks down.
The read doesn’t come through. The validation flags something unexplained. The bill goes out late, or worse, goes out wrong. The phone rings. A customer is angry. Your billing team is pulling data from two different systems, trying to reconcile a difference that shouldn’t exist, while the next billing period is approaching.
These breakdowns are almost never caused by bad data at the meter. The majority of the time it’s related to the integration, or lack of integration, between the AMI system, the Meter Data Management (MDM) platform and/or the Customer Information System (CIS) that produces customer bills.
That integration is the subject of this article. Specifically, we’re going to walk through what it looks like and what it means for billing accuracy, staff efficiency, and the customer experience.
With 84% of utility meters now using AMI according to NRECA’s April 2025 analysis, and the U.S. Energy Information Administration (EIA) reporting approximately 119 million smart meter installations nationwide, interval reads have moved from a technical aspiration to an operational reality. How well that data flows determines whether your utility runs efficiently or spends its days dealing with the consequences of systems that don’t work as one.
What the Meter-to-Cash Process Entails
Before we discuss integration, let’s define the process. It’s not a single handoff, it’s a chain of interconnected steps, each of which depends on the one before it.
Step 1: Data Collection at the Meter
Everything begins at the smart meter. Your AMI network collects interval reads, often every 15 minutes, and transmits them back through the AMI headend to your MDM platform. At this stage, data quality varies. Some reads arrive clean and complete. Others arrive with gaps, anomalies, or duplicate values that need to be corrected.
The AMI headend’s job is collection and routing. It pulls data from meters and passes it to the MDM. What it does not do is validate that data for billing use. That’s a critically important distinction — one every billing team should understand. The headend gets data out of the meter. The MDM makes it safe for billing.
Step 2: Validation, Estimation, and Editing (VEE)
Once interval data arrives in the MDM, it goes through Validation, Estimation, and Editing (VEE). This is the quality control layer of the meter-to-cash process, and it’s where the MDM earns its keep.
Validation checks every read against a set of configurable rules: is this read within the expected range for this account? Does it align with adjacent intervals? Is there a gap in the timeline that suggests a communication failure? Reads that fail validation are flagged for review or sent to estimation.
Estimation fills gaps in the data using statistical methods including historical usage patterns, weather adjustments, or reads from neighboring meters. It’s not guesswork; it’s a rules-based process that produces a defensible, auditable estimate that can be used for billing purposes.
Editing allows billing staff to review flagged intervals, override estimates if necessary, and resolve exceptions before data flows to the CIS. Done well, VEE is nearly invisible and is a background process that catches problems before they become bills. Done poorly, or not done at all, it’s the source of the high bill complaints and billing corrections that consume your team’s time and your customer’s patience.
Step 3: Data Transfer to the CIS
With interval data validated, estimated where necessary, and reviewed, the MDM passes it to the Customer Information System (CIS) for billing. This integration is key; it’s where patchwork systems break down.
In a native integration, this transfer happens automatically, on a defined schedule, in a format the CIS can consume directly. Exception flags from VEE travel alongside the data, giving billing staff the context they need to understand any accounts that required manual review. The CIS knows what it received, when it received it, and whether any intervals were estimated.
Step 4: Rate Application and Bill Generation
Once validated data is in the CIS, the billing engine applies the appropriate rate structure: flat rate, time-of-use (TOU), demand charge, tiered block, wholesale power cost adjustment, or any combination thereof. For utilities with complex rate portfolios this step requires an engine that can handle granular interval data on a large scale.
The final billing process reflects usage data, rate calculations, any adjustments or credits, and customer account information to produce the final bill. In an integrated system, this is an automated workflow. In a disconnected system, it often requires manual intervention at multiple points and each intervention is an opportunity for error.
Step 5: Delivery, Payment, and Posting
Once the bill is delivered according to the customer’s preference: paper, Interactive Voice Response (IVR), or online portal, any errors become much more expensive for the utility to resolve. Every billing dispute and credit adjustment has its root somewhere in the meter-to-cash chain.
Where Integration Breaks Down and What It Costs
The meter-to-cash process sounds straightforward in theory. In practice, it’s all about integration.
Data formatting. MDM and CIS platforms may use different data schemas. What the MDM exports as a validated interval file may require reformatting before the CIS can consume it.
Timing failures. Native integrations run on automated, defined schedules. Non-native integrations often depend on scheduled file exports, middleware jobs, or manual processes that can fail silently, leaving the CIS waiting for data that isn’t coming.
Audit trail gaps. When a customer disputes a bill, your team needs to be able to trace the data from the meter read to the billing calculation.
Staff overhead. A lack of integration creates manual work including logging into multiple systems, reconciling data discrepancies, re-running estimates, and making billing corrections. That translates to a real cost.
What Native MDM and CIS Integration Actually Looks Like
Native integration means MDM and CIS are designed to share data and not just exchange files. The distinction matters at every stage of the meter-to-cash process.
A Single Data Model
In a natively integrated platform, MDM and CIS share a common data model. Interval reads, VEE results, exception flags, account identifiers, and rate parameters all exist in a unified structure.
Automated, Scheduled Data Flow
Native integration runs automatically on a defined schedule. Validated interval data moves from MDM to CIS without manual intervention, on a schedule that supports your billing cycle. When the CIS needs to pull usage data for billing, it knows exactly where to look and what format to expect.
The Real-World Impact: Accuracy, Efficiency, and Customer Experience
The case for native integration isn’t theoretical. It shows up in ways that matter to every utility.
Billing Accuracy
When MDM and CIS integration is native, billing errors are rare exceptions rather than routine occurrences. The reduction in billing corrections, credit adjustments, and customer disputes is directly proportional to the quality of the integration.
Staff Efficiency
For a billing team, often two or three people managing tens of thousands of accounts, a native integration is the difference between a manageable workload and a constant firefight. Every billing cycle that runs cleanly, without manual intervention, is staff capacity recovered for customer service, process improvement, and work that does require human judgment.
Native integration doesn’t eliminate the need for skilled billing staff. It eliminates the busy work that keeps skilled billing staff from doing their best work.
Customer Experience
Customers don’t care about MDM or CIS. They care about whether their bill is right, whether it’s easy to pay, and whether their utility can answer their questions clearly when they call. All three of those things are better when the meter-to-cash process works as one continuous, integrated system.
What to Look for in MDM and CIS Integration
If you’re evaluating MDM and CIS platforms, the integration architecture deserves scrutiny. Here are the questions to ask.
- Is the integration between the MDM and CIS built and maintained by the same company? Or does it rely on a third-party code, middleware, or custom ETL?
- Can billing staff clearly see which intervals were estimated or edited?
- What is the data transfer schedule, and what happens when a transfer fails? Are there alerts, or does a failure only surface when billing staff notice missing data?
- How does the integration handle a rate change? If a new rate structure or wholesale power cost adjustment is added to the CIS, how quickly does the MDM data format align?
- What does the integration look like for accounts with special circumstances – net metering, demand billing, TOU with peak window changes? Are those handled natively or do they require manual workarounds?
- Can you speak with other utilities that run this specific MDM and CIS integration?
The answers to these questions will tell you whether you’re looking at integration as a feature or integration as an architecture. The difference will determine how your billing team operates for the next decade.
CentralView MDM and CIS: Built as One
CSA’s CentralView[1]platform was built with the meter-to-cash process as a core design principle, not an afterthought. CentralView MDM and CentralView CIS share a common data architecture, so interval data moves from collection through VEE processing to billing without translation, format conversion, or middleware dependencies.
VEE exception context is fully visible. The audit trail is complete and accessible in one interface. Rate changes apply cleanly. And because both the MDM and CIS come from CSA, you get support from the people who developed them, not two separate support queues pointing at each other.
Conclusion: Integration Is Not a Feature – It’s the Foundation
The meter-to-cash process is the operational spine of the billing operation. When it works, everything is simpler. That’s what CSA’s CentralView MDM and CIS platform deliver.
See how CentralView MDM and CIS work together. Request a Demo →
Related Reading:
- MDM Software for Electric Utilities: Why One Size Does Not Fit All
- What Is Meter Data Management? A Complete Guide for Electric Utilities
- AMI Data Integration Challenges — and How a Purpose-Built MDM Solves Them
- MDM Software for Electric Utilities: Why One Size Does Not Fit All
[1] CentralView is Central Service Association (CSA) Trademark