How do SAP IS-U and MECOMS 365 differ architecturally?
SAP IS-U is an industry solution layered on SAP ERP and written largely in ABAP, whereas MECOMS 365 is a vertical utility solution built on Microsoft Dynamics 365 and Azure. The first is typically run on-premise or in a hosted environment. The second is cloud-first and hosted by Microsoft.
In practice, this changes how the platform behaves day to day. MECOMS 365 uses Dynamics 365 for generic ERP functions such as finance, CRM, procurement, HR and project management, then adds utility functionality on top. Everything sits in one integrated system with one user interface, one database and one set of business logic. That gives you a single version of the truth and only one technology stack to support.
Integration is another architectural difference. MECOMS 365 is modular and API-driven, so it can run stand-alone or alongside existing applications through standard APIs and integration methods. That matters when you need to replace a customer information system step by step rather than in one risky leap.
Which platform is easier to configure and adapt?
MECOMS 365 is generally easier to configure because products, rates and processes are set up through parameters rather than custom code. SAP IS-U can be highly flexible, but adapting it often involves specialist ABAP development, which lengthens change cycles and raises the cost of every new tariff or process.
With MECOMS 365, users create and maintain products by linking commodities with rate structures, taxes and levies, without additional programming. Launching a new market offering becomes a configuration task for the business team instead of a development project for IT.
Regulation is the other adaptability factor. MECOMS 365 provides country templates, which are out-of-the-box implementations of market interaction processes and messages for a given country. These run on the MECOMS Enterprise Extensibility platform, which integrates business processes with your up- and downstream applications. Because the platform is standardised rather than heavily customised, each release is also certified for Microsoft Dynamics, which keeps upgrades predictable.
How do functional capabilities compare for modern utilities?
Both platforms cover the core meter-to-cash process, but MECOMS 365 is designed around modern utility demands such as smart metering, real-time pricing, omnichannel engagement and multi-commodity operations. SAP IS-U delivers strong billing depth, yet newer capabilities often require add-ons or custom work.
Key capabilities to compare include:
- Billing: MECOMS 365 validates invoice lines as they enter the system, detects anomalies before the billing run and uses distributed workloads for fast invoice generation.
- Pricing: An extensible pricing and quoting engine supports supplier-specific rules, hourly billing and integration with third-party calculation engines.
- Payments and collections: A matching engine interprets incoming payments automatically and only asks for human input when uncertainty is high.
- Customer engagement: Self-service portals, intelligent chatbots, marketing automation and AI-driven customer insights are supported natively.
- Multi-commodity support: Water, gas, electricity and district heating are covered in one platform.
Smart meter growth also raises the importance of meter data management, which should sit close to billing so large volumes of consumption data flow cleanly into invoices.
What does total cost of ownership look like?
MECOMS 365 typically lowers total cost of ownership by running on a single Microsoft technology stack, removing the need to maintain separate ERP, CRM and billing environments linked together. SAP IS-U costs are shaped by licensing, hosting, specialist skills and the ongoing expense of custom development.
When comparing options, look beyond the licence price. A realistic comparison should include:
- Infrastructure and hosting, which are managed by Microsoft in a cloud-first model
- The cost of change, including how often tariffs, regulations and processes need updating
- Upgrade effort, especially where heavy customisation has built up over the years
- Specialist resourcing, as ABAP and SAP IS-U expertise can be scarce and expensive
- Integration and support costs across disparate systems
A standardised, certified platform with one version and one support strategy reduces the hidden cost of keeping a customised system alive.
Why are utilities moving away from SAP IS-U?
Utilities are moving away from SAP IS-U mainly because of the pressure of maintenance timelines, the cost and complexity of customisation, and the need for cloud agility. Smart meters, distributed generation and new customer expectations expose the limits of heavily tailored legacy platforms.
Several drivers tend to appear together:
- Roadmap uncertainty: Planned changes to SAP maintenance and product direction force a decision on whether to move or stay, which is why SAP IS-U’s end of maintenance features in so many programme discussions.
- Customisation debt: Years of bespoke development make upgrades slow and risky. Industry analysts have warned against traditional off-the-shelf products carrying customer-specific customisations.
- Customer expectations: Residential customers expect fast, omnichannel service available around the clock.
- Energy transition: Solar, wind and distributed production introduce new processes that legacy systems struggle to support quickly.
How does a migration from SAP IS-U to MECOMS 365 work?
A migration from SAP IS-U to MECOMS 365 follows a structured path: assess the current landscape, define the migration strategy, migrate and validate data, implement and test, then cut over and stabilise. Running phases in a controlled sequence reduces risk to billing continuity.
The typical stages are:
- Discovery and strategy: Map existing processes, interfaces and customisations, and decide what to standardise rather than recreate.
- Data migration: Cleanse, transform and reconcile customer, contract, meter and financial data, with repeated trial loads.
- Implementation: Configure the platform, apply the relevant country template and integrate surrounding applications.
- Testing: Run user acceptance testing and parallel billing comparisons to prove invoices match expectations.
- Cutover and support: Transition to the new platform and move into steady-state support and training.
Strong implementation services that cover every step from project start to business transition make a measurable difference to how smoothly this goes. Customer examples such as Waternet’s cloud journey show how a utility can approach this transformation in practice.
When is MECOMS 365 the better choice than staying on SAP?
MECOMS 365 is the better choice when your priorities are agility, cloud adoption, lower customisation and faster response to market change. Staying on SAP can make sense where a recent, largely standard implementation is stable and your wider enterprise strategy is firmly centred on SAP.
Consider MECOMS 365 if several of these apply:
- Your current system struggles with complex pricing, market communication or large smart meter data volumes
- Product launches or regulatory changes take too long because they depend on development
- You want a cloud-first strategy managed and hosted by Microsoft
- You already use, or plan to adopt, Microsoft tools such as Power BI, Power Apps and Power Automate
- You serve multiple commodities or company roles and want one platform
The decision is rarely purely technical. It combines operating model, budget horizon and appetite for transformation, so a clear comparison against your own requirements is the best next step.
How we help with your SAP IS-U replacement
At Ferranti, we bring more than 45 years of utility expertise to replacing legacy CIS and billing platforms. MECOMS 365 is built on Microsoft Dynamics 365 and Azure, and we are a premium ISV Connect Microsoft partner. We support you across the full lifecycle, including:
- Migration strategy and roadmap planning tailored to your landscape
- Data migration, validation and reconciliation
- Implementation using country templates and a standardised approach
- Testing, cutover and business transition
- Customised training and ongoing product support through our One Version, One Support strategy
You can explore the full range of MECOMS 365 solutions to see how they fit your needs, and see how we work with energy suppliers across the market. Ready to compare options for your own landscape? Contact us to schedule an exploratory call and map out your SAP IS-U replacement.
Veelgestelde vragen
How do I get started with evaluating an SAP IS-U replacement?
Start by documenting your current landscape: list your interfaces, custom ABAP developments, tariff structures and market communication processes. Then rank your requirements (smart meter volumes, multi-commodity support, cloud strategy, regulatory change) and use them as a scorecard when comparing platforms. Request a scripted demo based on your own scenarios, and consider an exploratory call with a vendor or partner to validate fit before committing to a business case.
Can we replace SAP IS-U in phases instead of doing a big-bang cutover?
Yes. Because MECOMS 365 is modular and API-driven, it can run alongside existing applications, so you can replace components such as the CIS, billing or meter data management step by step. A phased approach, for example by commodity, customer segment or business unit, limits risk to billing continuity. Define clear coexistence and interface rules early so data stays consistent between the old and new systems.
How long does a migration from SAP IS-U to MECOMS 365 typically take?
Timelines vary with the number of commodities, customer volumes, data quality and how many existing customisations you decide to retire. Projects that standardise on country templates and avoid recreating legacy customisations generally move faster. Build in time for repeated trial data loads and parallel billing runs, as these are often the steps that determine the final go-live date.
What are the most common mistakes when migrating away from SAP IS-U?
The biggest mistake is recreating every legacy customisation in the new platform, which rebuilds the same customisation debt you wanted to escape. Other frequent pitfalls include underestimating data cleansing effort, skipping parallel billing comparisons, and not involving business users early in configuration and testing. Challenge each custom requirement by asking whether a standard feature or configuration can meet the need.
How do we make sure billing accuracy is preserved during cutover?
Run parallel billing, where the same consumption data is billed in both the old and new systems, and reconcile the invoice outcomes line by line. Combine this with repeated data migration trial loads and reconciliation of customer, contract, meter and financial balances. Set acceptance thresholds in advance and only go live once variances are explained and resolved.
What skills does our team need to run MECOMS 365 after go-live?
Because products, rates and processes are configured through parameters, business analysts and product owners can handle many changes without ABAP-style coding. Your IT team benefits from Microsoft skills such as Dynamics 365, Azure, Power BI, Power Apps and Power Automate. Plan customised training for both business and technical users, and agree on a support model for ongoing product updates.
What if our organisation is heavily invested in SAP elsewhere, such as finance or HR?
You do not necessarily have to replace everything at once. MECOMS 365 can integrate with existing applications through standard APIs, so you can keep SAP for functions like finance or HR while moving billing and customer processes to a utility-specific platform. Evaluate the integration effort and long-term roadmap, and compare the cost of maintaining that integration against consolidating onto a single technology stack.
Gerelateerde artikelen
- Can Microsoft Dynamics 365 replace SAP IS-U?
- What makes legacy systems particularly risky for utility companies?
- 6 integration challenges energy suppliers face when modernizing their IT landscape
- What causes integration failures in utility IT projects?
- How do you modernize a utility company step by step?
- How does utility billing software work for energy companies?
- What Is the role of utility billing in customer experience?
- What are the benefits of automated utility billing?
- How scalable is cloud-based billing software for growing energy companies?
- How does a cloud-based CIS differ from an on-premise solution?
- How do you resolve energy invoice disputes efficiently?
- How does CIS utility software handle customer service management?
- Why should you upgrade your utility CIS in 2026?
- What are the biggest challenges in a CIS implementation?
- How does a CIS manage customer contracts and tariffs?