Which systems does a Dynamics 365 CIS replace or connect to?
A Dynamics 365 CIS typically replaces the legacy customer information system, the billing engine and the separate CRM tools that surround them. It connects to systems that remain specialist by nature, such as head-end systems, payment providers, market communication hubs and the general ledger.
In practice, the replace-or-connect decision follows one principle: anything that holds customer, contract or tariff logic belongs in the CIS, while anything that serves a distinct technical or financial purpose stays separate and integrates through well-defined interfaces. Commonly replaced components include:
- The legacy CIS and billing platform
- Standalone customer service and CRM applications
- Spreadsheet-based workarounds for tariffs, corrections and exceptions
- Custom document generation and correspondence tools
Commonly connected systems include head-end and metering infrastructure, payment gateways and banks, market participants, workforce management and the corporate ERP. Our customer information system is designed around this pattern, so utilities can retire what is redundant without rebuilding what already works.
How does a Dynamics 365 CIS integrate with ERP and finance?
A Dynamics 365 CIS integrates with ERP and finance by posting billing, payment and adjustment transactions to the general ledger and receivables processes through standard APIs or pre-built connectors. The CIS owns the customer-facing detail, while the ERP owns the financial consolidation, reporting and statutory accounting.
A clean split of responsibilities keeps the interface simple. The CIS holds invoices, customer accounts, payment allocations and dunning status. The finance system receives summarised or transaction-level postings, depending on audit requirements, and returns information such as payment confirmations or credit decisions where needed.
Where a utility already runs Dynamics 365 Finance, the shared Microsoft data model reduces mapping effort considerably. Where it runs a different ERP, an integration layer based on APIs and event messaging keeps the two decoupled, so either side can be upgraded without breaking the other. Reconciliation reporting between the two should be designed in from the start, not added after go-live.
Where do meter data and smart grid systems fit?
Meter data and smart grid systems sit upstream of the CIS. Head-end systems collect raw reads, a meter data management (MDM) layer validates, estimates and aggregates them, and the CIS consumes the billing-ready results to calculate charges against the right tariff.
Separating these layers matters because interval data from smart meters arrives in volumes that billing engines were never built to handle directly. Validation, editing and estimation belong in a dedicated meter data management capability, which then passes clean consumption data to billing. This also supports time-of-use tariffs, demand charges and dynamic pricing without manual intervention.
Other grid-related systems, such as outage management, asset management and demand response platforms, can consume the same validated data through APIs. The CIS then benefits in return, for example by flagging customers affected by an outage or those enrolled in flexibility programmes. The aim is one trusted source of consumption data feeding every downstream process.
What role does Azure play in the wider architecture?
Azure provides the hosting, integration, security and analytics foundation beneath a Dynamics 365 CIS. It delivers elastic compute for billing runs, messaging and integration services for connecting systems, and data platforms for reporting and advanced analytics.
For utilities, the practical benefits fall into four areas:
- Scalability: capacity expands for heavy billing runs and smart meter data peaks, then scales back
- Integration: managed services for APIs, queues and event handling reduce custom code
- Security and resilience: enterprise-grade identity, encryption and disaster recovery are built in
- Insight: data can flow into analytics and AI services for forecasting, anomaly detection and customer insight
Because the CIS and the surrounding services share the same cloud foundation, the architecture stays consistent as it grows. Our approach to cloud technology builds on this, and our standing as a Microsoft partner keeps the platform aligned with Dynamics 365 and Azure updates.
How does a Dynamics 365 CIS differ from a legacy SAP IS-U landscape?
The key difference is architectural. A legacy SAP IS-U landscape is typically a heavily customised, on-premises monolith tied to ERP release cycles, while a Dynamics 365 CIS is a cloud-native platform with configurable utility logic, regular updates and open integration. The latter is easier to adapt, cheaper to evolve and quicker to extend.
With SAP IS-U replacement now a pressing topic for many utilities, the comparison usually comes down to these points:
- Customisation: IS-U landscapes often carry years of bespoke code that complicates upgrades, whereas a configurable cloud platform reduces that technical debt
- Release cadence: cloud updates arrive continuously, rather than through large, risky upgrade projects
- User experience: a modern interface supports management by exception and self-service, rather than transaction-heavy screens
- Integration: API-first design makes connecting new channels, devices and partners far simpler
- Cost profile: infrastructure and maintenance effort shift from fixed, legacy overhead towards predictable cloud consumption
None of this means the legacy system was wrong for its time. It means the demands of smart metering, new tariffs and digital customers have outgrown what it can deliver economically.
How can a utility migrate to a new CIS without disrupting operations?
A utility can migrate without disrupting operations by phasing the programme, cleansing data early, running parallel tests and rehearsing cutover before go-live. The aim is to keep billing and customer service stable throughout, so customers never notice the change.
A practical sequence looks like this:
- Define scope and strategy: decide what is replaced, what is integrated and what is retired
- Cleanse and map data: quality issues are the most common cause of delay, so address them first
- Configure and integrate: build tariffs, processes and interfaces in iterations
- Test in parallel: compare bill outputs from old and new systems on real data
- Rehearse cutover: run multiple dry runs to prove timings and rollback options
- Stabilise and optimise: provide hypercare support after go-live
Timelines vary with size and complexity, but full migrations commonly run from 12 months to several years when phased. Experience with implementation services that follow a structured methodology reduces risk, as does learning from comparable water and energy utilities that have already made the move, such as the journey described in the Waternet cloud story.
What should IT leaders check before committing to this architecture?
IT leaders should verify that the platform handles utility-specific requirements natively, integrates cleanly with their existing landscape, and is backed by proven migration experience. Dynamics 365 alone is not a complete utility billing platform, so the industry solution layered on top matters as much as the core.
A concise checklist helps structure the evaluation:
- Utility depth: support for complex tariffs, multi-commodity billing, market processes and regulatory change
- Meter data readiness: proven handling of interval data and smart meter volumes
- Integration approach: pre-built connectors, open APIs and a clear data model
- Exception handling: automation that surfaces only cases needing human judgement
- Migration track record: references from utilities of similar scale and commodity mix
- Total cost of ownership: including licences, hosting, support and future change
- Roadmap alignment: how the platform keeps pace with Microsoft and market developments
Ask for evidence rather than promises. Reference projects, such as the approach taken at Waterbedrijf Groningen, show how the architecture performs in live utility conditions.
How we help with your Dynamics 365 CIS architecture
We have spent more than 45 years working with energy and utility companies, and MECOMS 365 is the result. Built natively on Microsoft Dynamics 365 and Azure, it brings customer information, billing, meter-to-cash and meter data management into one cloud platform designed for energy suppliers and other utilities. You can explore the full MECOMS 365 solutions to see how the pieces fit together.
When we support a CIS architecture and migration, you can expect:
- A migration strategy that protects live billing and customer service
- Pre-built utility functionality that reduces custom development
- Integration with meter data, ERP, payments and market systems
- Structured data migration, testing, cutover and ongoing support
- Process automation based on management by exception
If you are assessing your options or planning an SAP IS-U replacement, get in touch with us and we will help you map a practical path forward.
Veelgestelde vragen
Where should we start if we want to assess whether a Dynamics 365 CIS fits our utility?
Start with a current-state landscape map that lists every system touching customers, contracts, tariffs, meter data and finance, then mark each as ‘replace’, ‘connect’ or ‘retire’. Pair this with a short list of pain points, such as manual tariff workarounds or slow billing runs, and the volume of smart meter data you expect. This gives you a concrete basis for a fit-gap workshop and vendor demonstrations using your own scenarios rather than generic ones.
What are the most common mistakes utilities make when migrating to a new CIS?
The most frequent mistakes are leaving data cleansing until late in the project, recreating legacy customisations instead of adopting standard functionality, and under-investing in testing. Skipping parallel bill comparisons on real data is particularly risky, because discrepancies in tariffs or corrections often only surface at that stage. Planning multiple cutover rehearsals and a clear rollback option helps avoid unpleasant surprises on go-live day.
What if our ERP is not Dynamics 365 Finance, for example SAP or Oracle?
This is a common situation and entirely workable. Use an integration layer based on APIs and event messaging, for example Azure Integration Services, so the CIS and the ERP stay decoupled. Agree up front which system owns which data, decide whether the ledger receives summarised or transaction-level postings, and build reconciliation reports from day one so finance can trust the numbers.
How do we handle data quality problems in legacy customer and meter records?
Profile your legacy data early to quantify duplicates, missing fields, inconsistent addresses and orphaned meter-to-premise links. Fix issues at the source where possible, and use repeatable migration scripts with validation rules so each trial load improves on the last. Assign business owners to sign off data quality, as technical teams alone cannot decide which customer or contract record is correct.
Can we migrate in phases instead of doing a big-bang cutover?
Yes, and for larger utilities phasing is usually the safer approach. Common slicing strategies include migrating by commodity (for example water before energy), by customer segment (such as commercial before residential) or by region. Each phase should have its own testing, cutover rehearsal and hypercare period, and you need to plan for the temporary integration between old and new systems while both are live.
How should we prepare for smart meter data volumes before go-live?
Make sure validation, estimation and aggregation are handled in a dedicated meter data management layer rather than in the billing engine itself. Run load tests with realistic interval data volumes, including peak periods and catch-up scenarios after communication outages. Also confirm that your Azure capacity settings can scale for billing runs and then scale back to control cost.
How do we build a business case and measure success after the move?
Baseline a few measurable indicators before the project begins, such as cost per bill, billing exception rates, days to bill, call volumes and the effort spent on manual corrections. Include infrastructure, licence, support and future change costs when comparing total cost of ownership with your legacy landscape. After go-live, track the same indicators, since improvements through management by exception and automation typically emerge gradually during the stabilisation phase.
Gerelateerde artikelen
- How does Microsoft Dynamics 365 compare to industry-specific utility software?
- How does AI help utility customer service agents handle more cases?
- What are the most common utility software integration challenges?
- What is the biggest challenge when modernizing utility operations?
- How does the quality of energy invoices affect customer retention?
- How do energy companies manage complex tariff structures in their software?
- What does modernising utility operations actually involve?
- 7 reasons why the cost of legacy systems in the energy sector is higher than it looks
- Which mistakes do energy companies make when switching to a new billing system?
- What is a flexible tariff and how is it technically processed in billing?
- How do you verify the accuracy of meter data before billing?
- What are the consequences of a tariff change for an energy supplier's billing systems?
- How do you choose the right utility CIS provider?
- How does the energy transition impact CIS requirements?
- What is customer engagement in the energy sector?