MECOMS 365 adds the utility-specific layer that standard Microsoft Dynamics 365 lacks: a customer information system, billing and rating engine, meter data management, and market processes for electricity, gas, water and district heating. It is built natively on Dynamics 365 and Azure, so your finance, HR and procurement modules stay in place. Dynamics 365 is a strong enterprise platform, but it was never designed to bill a prosumer or validate millions of interval reads. The sections below explain which gaps MECOMS 365 closes and how it supports a utility CIS migration.

Which utility gaps does standard Dynamics 365 leave open?

Standard Dynamics 365 leaves open the core utility processes: meter-to-cash, tariff and rate management, smart meter data handling, market messaging and settlement. It offers excellent CRM, finance and operations tooling, but it has no native data models or billing logic for the way energy and water are measured, priced and invoiced.

The most visible gaps appear where energy markets are changing fastest:

  • Prosumers and bi-directional flows: Net metering and rooftop solar require tracking consumption and injection separately at the meter, applying different tariff components to each direction and reconciling settlement data with market operators.
  • Interval and smart meter data: Handling 15-minute values, validation, estimation and exception management at scale is outside standard functionality.
  • Multi-commodity complexity: Gas depends on calorific value, temperature and pressure, while water and heat have their own measurement rules.
  • Utility contract conditions: Automatic renewal, auto-balancing, cash-out and take-or-pay arrangements need purpose-built contract management.

A utility-specific extension fills these gaps. The key question is whether it is built natively on Dynamics 365 or bolted on from outside. A native solution shares the same data model, security framework and upgrade path, so Microsoft updates do not break the utility layer. Loosely integrated products often need rework after each release, adding cost and risk over time. You can see how the MECOMS 365 solutions are structured on that native foundation.

How does MECOMS 365 handle utility billing and rating?

MECOMS 365 handles utility billing through an integrated meter-to-cash process: you create products, sell them as contracts, bill customers using several methods, and manage credit and collections on the same platform. A configurable rating engine applies the right tariffs automatically, including real-time pricing and billing out of the box.

Within the customer information system, billing is a core process rather than an add-on. It is designed to deliver accurate bills quickly, encourage timely payment and maximise the payment rate across every customer segment. A flexible rate engine matters because utility tariffs change frequently. New pricing structures should be configurable without custom development.

On the commercial side, a pricing and quoting framework supports supplier-specific rules and calculations, and it can integrate with third-party pricing engines. For B2B customers, advanced contract conditions such as automatic renewal, auto-balancing, cash-out and take-or-pay are supported. For residential customers, smart metering is making hourly billing and other smart pricing mechanisms the new standard, and the platform processes that data natively.

What meter data and smart grid capabilities does MECOMS 365 include?

MECOMS 365 includes native meter data management: two-way communication with smart meters, automatic meter reading as a core process, validation and estimation of interval data, and exception handling. It processes large volumes of smart meter data and feeds it directly into billing, without custom middleware.

The meter data management capabilities cover several practical needs:

  • Exceptions and anomalies: Missing reads are estimated automatically from consumption profiles or historical data. Other anomalies are flagged so a specialist agent can act on them.
  • Mixed meter parks: Manual, automatic and smart meters are handled simultaneously, which enables a gradual infrastructure upgrade rather than a risky big bang.
  • Consumption analytics: The platform acts as a data hub, providing billing-ready data to customer portals, third parties and other utility applications.
  • Energy transition use cases: Tighter 15-minute intervals, local energy communities and peer-to-peer energy trading are supported through flexible product configuration.

Integration with existing systems, such as MV90, is supported, so you do not have to discard your current metering investments to benefit from a modern data layer.

How does MECOMS 365 improve customer engagement in Dynamics 365?

MECOMS 365 improves customer engagement by combining Dynamics 365 CRM strengths with utility context. Agents get a 360-degree view of each customer, including contracts, invoices and cases, while customers get self-service portals, apps and intelligent chatbots built on the same platform as the back office.

Complexity damages customer service, and the energy market is inherently complex. An omnichannel approach reduces that burden for both customers and employees. Because engagement tools share data with billing and metering, a customer enquiry about a bill can be answered from a single screen rather than across several systems.

The same data supports proactive communication and analytics. Smart meter insights can be presented to customers through self-service tools, helping them understand their consumption. In a competitive residential market where loyalty is never guaranteed, that visibility is a practical way to raise satisfaction while lowering contact volumes. Process automation and management by exception then free your teams to focus on the cases that genuinely need attention.

How does the Azure foundation benefit a utility CIS migration?

The Azure foundation benefits a utility CIS migration by providing scalable, secure cloud infrastructure with enterprise-grade security controls, audit logging and regulatory support. It removes the need to maintain on-premises hardware and lets your platform scale for volume peaks, new customer segments and market expansion.

Running on Dynamics 365 and Azure also simplifies the architecture. The same technology stack covers CIS, billing, finance and HR, which avoids data silos and reduces the number of integrations your team must maintain. The platform is open, supports on-premises, cloud and hybrid integration, and centralises integration points in one flexible layer.

For migration itself, the safest approach is to run parallel environments, with the legacy system processing live transactions while migrated data is validated in the new platform. Plan a thorough data mapping exercise and a cleansing phase focused on customer accounts, meter point data and billing history, as these carry the highest risk of post-go-live errors. Collaboration with a premium Microsoft partner helps keep release compatibility under control.

Is MECOMS 365 a good fit for replacing SAP IS-U?

Yes, MECOMS 365 is a strong candidate for replacing SAP IS-U, particularly for utilities seeking a cloud-native platform with lower customisation overhead. It covers the same meter-to-cash scope, adds modern engagement and smart meter capabilities, and uses a Microsoft-based architecture that many IT teams already know.

Several factors make the case strong. Heavy customisation is one of the most common modernisation challenges, but many workarounds built into a legacy system are standard functionality in a modern integrated platform. Document every customisation and map it against the target platform, as this often reduces the total configuration burden instead of adding to it.

Evaluate fit against criteria such as:

  • Native build on Dynamics 365 rather than loose integration
  • Support for every commodity you supply within one platform
  • Smart meter and interval data handling at scale
  • Market messaging and regulatory reporting for your country
  • A vendor track record in your sector and geography

Real-world references help. Water utilities, for example, have taken this route, as shown in the Waternet cloud journey. Implementation timelines depend on organisation size and complexity, but because core utility logic is already encoded in the platform, the work centres on configuration, data migration and integration rather than development from scratch. Rollouts are typically measured in months rather than years, with phased go-live options to reduce risk.

How we help with Dynamics 365 for utilities

We help energy suppliers and utilities replace fragmented legacy systems with MECOMS 365, a platform built on Microsoft Dynamics 365 and Azure. With more than 45 years of utility experience and over 54 clients in 18 countries, we guide your organisation from initial scoping through to live operations. Here is what we bring:

  • Integrated billing and CIS: A unified engine for complex tariffs, interval data and high invoice volumes.
  • Meter data management: Native smart meter ingestion, validation and processing at scale.
  • Customer engagement tools: Self-service, proactive communication and faster query resolution on the same platform.
  • Process automation: Management by exception to reduce manual workload.
  • Migration expertise: Strategy, data migration, testing, cutover and ongoing support through our implementation services.

If you are weighing up a CIS migration or an SAP IS-U replacement, we would be glad to talk through your options. Contact us to start the conversation about what a modernisation roadmap could look like for your organisation.

Veelgestelde vragen

How do I get started with a MECOMS 365 implementation?

Begin with a scoping phase that inventories your commodities, customer segments, tariffs, meter types and existing integrations. From there, define a target process map for meter-to-cash, prioritise which processes go live first, and decide whether a phased or single go-live suits your risk appetite. Involving business users, IT and finance from the outset helps avoid surprises during data migration and testing.

Can I keep my existing Dynamics 365 finance, HR and procurement modules?

Yes. Because MECOMS 365 is built natively on Dynamics 365 and Azure, it shares the same data model, security framework and upgrade path as your existing modules. You add the utility layer (CIS, billing, meter data and market processes) without replacing the finance, HR or procurement functionality you already rely on. Review your current Dynamics 365 customisations beforehand so they can be aligned with the utility layer.

What data should I clean up before migrating from a legacy CIS?

Focus first on customer accounts, meter point data and billing history, as these carry the highest risk of post-go-live errors. Remove duplicates, correct address and meter point identifiers, and decide how much billing history genuinely needs to move versus be archived. Run test migrations repeatedly and reconcile results against the legacy system before cutover.

What if my utility has a mixed meter park with manual, automatic and smart meters?

This is a common situation and does not need to block your migration. MECOMS 365 handles manual, automatic and smart meters at the same time, so you can upgrade your metering infrastructure gradually rather than in a risky big bang. Existing systems such as MV90 can also be integrated, protecting your current metering investments.

How should I handle customisations from my current system, such as SAP IS-U?

Document every existing customisation and map it against the target platform’s standard functionality. Many workarounds built into legacy systems are standard features in a modern integrated platform, so you may find that a significant share no longer needs to be rebuilt. For the remainder, favour configuration over custom development to keep future upgrades simple.

How can I reduce risk during go-live?

Run parallel environments so the legacy system continues processing live transactions while migrated data is validated in the new platform. Combine this with a phased rollout, for example by commodity or customer segment, and agree clear acceptance criteria for each phase. Rehearse the cutover plan and have a defined rollback path before the final switch.

How do I prepare my team for the change to management by exception?

Start by identifying which routine tasks, such as estimating missing reads or standard billing runs, will be automated, and redefine agent roles around handling flagged exceptions and complex cases. Provide role-based training before go-live and use test environments so staff can practise with realistic scenarios. Gathering feedback in the first weeks after launch helps you tune exception rules and thresholds.

Gerelateerde artikelen