Customer Engagement or Finance and Operations: Which Dynamics 365 Do You Actually Need?

What does Customer Engagement do, and what does Finance and Operations do?

Customer Engagement is the CRM side of Dynamics 365. Its apps run on Dataverse and handle everything that happens with a customer before and after an order: leads and opportunities in Sales, cases and service levels in Customer Service, work orders, scheduling and technicians in Field Service, and marketing journeys and unified customer profiles in Customer Insights. Our overview of what Dynamics 365 Customer Engagement is covers each app in more depth.

Finance and Operations is the ERP side for larger organisations. Microsoft calls Finance, Supply Chain Management, Commerce and Human Resources together finance and operations apps. Dynamics 365 Finance covers general ledger, accounts payable, accounts receivable, budgeting, cash and bank management, cost accounting, fixed assets, asset leasing and financial reporting. Supply Chain Management covers inventory, warehouse and transportation management, procurement and sourcing, master planning, manufacturing and production, product information, asset management and service management. Project accounting is documented under Dynamics 365 Project Operations rather than Finance. Our Finance and Operations service describes how Solzet implements them.

Which Dynamics 365 product covers which business need?

Start from the need, not the product name. The table maps the most common needs to the product that carries them and the side of Dynamics 365 it belongs to. Most organisations recognise needs in both columns, which is the point of the next sections.

Where does Business Central fit for smaller organisations?

Business Central is Microsoft's ERP for small and mid-sized organisations. It covers finance, sales, purchasing, inventory, projects, fixed assets, planning, assembly, manufacturing, warehouse management and service management in one system, and it is the usual ERP choice below the scale where Finance and Operations makes sense. For many buyers the real choice is not Customer Engagement or Finance and Operations, but which ERP sits next to their CRM: Business Central or Finance and Operations. Our Business Central vs Finance and Operations comparison sets out the fit rules, and the Business Central service describes how Solzet implements it.

Do most organisations need both a CRM and an ERP?

Most organisations that sell, deliver and invoice need both, even if they buy them years apart. Sales wants credit limits, order status and invoices next to the account; finance wants clean customer records and orders that arrive without rekeying. The questions that decide whether that works are integration questions: which system owns the customer, where prices live, when an opportunity becomes an order, and how errors are caught.

Solzet works on both sides of the Microsoft business stack. We know Dataverse and Dynamics 365 Customer Engagement deeply, and we implement Business Central and Finance and Operations. That means one team designs the CRM, the ERP and the integration between them: Customer Engagement with Business Central through the Dataverse connection and virtual tables, Customer Engagement with Finance and Operations through dual-write and virtual entities, and Power Platform across both.

How do Customer Engagement and Finance and Operations connect?

Microsoft provides two native patterns. Dual-write is out-of-box infrastructure that gives near-real-time, bidirectional integration between customer engagement apps and finance and operations apps through Dataverse, so customers, products and orders exist as rows on both sides. Virtual entities expose finance and operations OData entities in Dataverse as virtual tables, so Customer Engagement can read the data without it being stored in Dataverse. Our guide dual-write vs virtual entities, explained covers when each one fits, and the CRM and ERP integration service covers how Solzet designs them.

How does Customer Engagement connect to Business Central instead?

Business Central connects to Dataverse through the Set up Dataverse connection assisted setup, with one-way or two-way synchronisation, and that connection is Microsoft's route for integrating it with Dynamics 365 Sales. The Business Central Virtual Table app exposes Business Central data in Dataverse as virtual tables without copying it, so the data stays in Business Central. The design choice is the same as on the Finance and Operations side: synchronise what both sides must edit, read live what only one side owns.

What goes wrong when the CRM and the ERP are chosen separately?

The products work; the gap between them is where projects struggle. When the CRM and the ERP are chosen, designed and delivered by different teams, nobody owns the boundary, and the same problems appear.

• Two customer masters that drift apart, so sales and finance disagree about who the customer is.
• Prices and discounts maintained in both systems, with quotes that do not match invoices.
• Integration designed last, after both data models are fixed, so it becomes a set of workarounds.
• Errors that fail silently between the two systems, discovered at month-end.
• Two delivery teams each waiting for the other to change their side.

What if the CRM side does not need Microsoft licensing at all?

Not every organisation needs a Microsoft CRM next to its ERP. Where per-user licensing, unusual workflows or full code ownership matter more than the Microsoft ecosystem, a custom-built CRM on React, Node.js, PostgreSQL or .NET can connect to Business Central or Finance and Operations through their APIs. The decision framework below sets out when each route fits.