Dynamics 365 Finance and Operations Modules Guide 2026

TL;DR

• Treat Dynamics 365 F&O as 2 core ERP applications: Finance and Supply Chain Management.
• Choose applications from end-to-end processes, then establish finance, product, security, integration, and master-data foundations.
• Inventory and Warehouse Management solve different problems. Scope Project Operations, Commerce, and Human Resources separately, and verify current licensing before purchase.

Microsoft’s documentation lists the feature areas for Dynamics 365 Finance separately from the operational areas in Dynamics 365 Supply Chain Management. That official split is the basis for the module map below.

Dynamics 365 F&O means two core ERP applications

Dynamics 365 F&O is useful shorthand, but it is not a single module bundle. For practical scoping, start with 2 core applications: Finance for accounting and financial control, and Supply Chain Management for product, inventory, procurement, warehouse, planning, manufacturing, and asset operations.

Both applications use the finance and operations platform, so processes can cross the boundary. A purchase receipt in Supply Chain Management, for example, can create inventory and accounting effects that ultimately reach the ledger. Shared technology does not remove the need to design ownership, security, posting, and testing across the process.

Application	Primary responsibility	Typical process owners
Dynamics 365 Finance	Record-to-report, procure-to-pay accounting, order-to-cash accounting, cash, assets, budgets, tax, and reporting	Finance, accounting, treasury, tax, and controllership
Dynamics 365 Supply Chain Management	Product data, procurement operations, inventory, warehouses, transportation, planning, production, maintenance, and costing	Procurement, planning, manufacturing, logistics, warehouse, and operations teams

If you first need the product-level distinction, read what Dynamics 365 Finance and Operations is. If you are choosing between ERP tiers, compare Business Central with Finance and Operations before designing modules.

Finance modules control accounting, cash, assets, and reporting

Dynamics 365 Finance provides the financial system of record. Its modules share ledger structures, financial dimensions, posting profiles, currencies, calendars, and controls. The first design priority is therefore the accounting model; configuring isolated screens before that foundation creates rework in every downstream process.

Microsoft’s Finance feature directory includes accounts payable, accounts receivable, budgeting, cash and bank management, cost accounting, financial reporting, fixed assets, asset leasing, and other financial management areas.

Finance area	What it controls	Design decision that matters
General ledger	Main accounts, fiscal periods, journals, financial dimensions, consolidations, allocations, and close	Chart of accounts and dimension governance across legal entities
Accounts payable	Vendors, invoices, matching, approvals, payment proposals, and settlements	Invoice controls, posting profiles, payment methods, and approval authority
Accounts receivable	Customers, invoices, payments, credit, collections, and settlements	Credit policy, collection process, posting, and integration with order entry
Cash and bank management	Bank accounts, payment files, statements, reconciliation, and cash visibility	Bank formats, reconciliation rules, segregation of duties, and cutover balances
Fixed assets and asset leasing	Asset acquisition, depreciation, disposal, books, and lease schedules	Accounting policy, capitalization thresholds, books, and posting integration
Budgeting and business planning	Budget registers, budget control, planning workflows, and analysis	Planning ownership and where enforcement should warn or stop a transaction
Tax and regulatory features	Sales tax, withholding, electronic reporting, and country or region requirements	Legal-entity obligations and the supported localization for each jurisdiction
Financial reporting and analytics	Statements, management reporting, account analysis, and performance views	Definitions, data ownership, reconciliation, and report distribution

The ledger is not just another row in that table. Microsoft explains that subledgers such as accounts payable, accounts receivable, inventory, fixed assets, tax, and production generate detailed entries that transfer to the ledger through accounting rules and posting profiles. See the official ledger and subledger accounting overview.

In implementation work, I validate sample postings early. A vendor invoice, customer invoice, inventory receipt, asset acquisition, payment, and foreign-currency transaction will expose weak account structures faster than a long configuration review. The objective is traceable accounting, not merely a successful posting message.

Supply Chain Management modules run products and physical operations

Dynamics 365 Supply Chain Management controls the flow of products, materials, capacity, and operational work. Its modules are connected by shared product data, inventory dimensions, units, sites, warehouses, calendars, resources, costing, and order policies. Poor master data decisions therefore spread quickly across planning and execution.

Product, procurement, and inventory form the transaction base

Product information management defines released products, variants, units, categories, bills of materials, formulas, and lifecycle controls. This data must be stable before teams can reliably buy, plan, make, store, or sell an item.

Procurement and sourcing covers requisitions, requests for quotation, purchase agreements, purchase orders, vendor collaboration, receiving, and procurement policies. Approval design should reflect actual financial authority and exception handling, rather than copying an old workflow step for step.

Inventory Management records on-hand quantities and inventory transactions by the dimensions enabled for each item. It also supports transfers, counting, reservations, quality processes, and inventory costing. Costing method and dimension design are foundational choices because they affect availability, valuation, planning, and close.

Warehouse Management adds execution logic

Warehouse Management is not a renamed inventory screen. It adds directed warehouse work through concepts such as locations, location directives, work templates, waves, replenishment, mobile-device menus, license plates, and cycle counting. Microsoft maintains a dedicated Warehouse Management overview because this is an execution system with its own architecture and operating model.

I scope Warehouse Management around real movements: receive, inspect, put away, replenish, pick, pack, stage, load, count, and reverse. Each flow needs realistic items, units, locations, equipment, exceptions, and user devices in testing. A diagram that covers only the happy path is not enough for a distribution centre.

Planning and manufacturing turn demand into supply

Master planning evaluates demand, supply, lead times, coverage settings, and capacity to propose planned purchase, transfer, or production orders. The module depends on credible item coverage, calendars, lead times, inventory, and open-order data. Microsoft’s master planning learning path describes how planning balances material and capacity needs.

Production control supports production orders, bills of materials, routes, scheduling, material consumption, shop-floor reporting, and finished-goods receipt. Process and lean manufacturing introduce different structures and execution patterns. Choose the manufacturing mode from actual production methods rather than enabling every available feature.

Transportation, landed cost, assets, and costing extend the operating model

Transportation Management supports loads, routes, rates, carriers, freight, and settlement. Landed Cost addresses inbound voyages and cost allocation. Asset Management supports maintenance requests, work orders, assets, functional locations, and schedules. Cost management connects product costing and inventory valuation to operational transactions.

These areas are valuable when the process requires them, but each brings data and integration dependencies. For example, maintenance planning needs a trustworthy asset hierarchy, while transportation rating needs credible lanes, carriers, services, and rate data. Scope them from the operating problem, not because their menu items are visible.

Adjacent Dynamics 365 applications require separate scope decisions

Project Operations, Commerce, and Human Resources are related applications, but they should not be described as ordinary Finance or Supply Chain Management modules. Each has its own deployment, integration, security, data, and licensing questions. Treating them as checkboxes understates the work needed to operate them.

Related application	Use it when	Confirm before committing
Dynamics 365 Project Operations	Work is sold and delivered through projects, resources, time, expenses, milestones, or project billing	Deployment model, Finance integration, project accounting, data ownership, and licensing
Dynamics 365 Commerce	The business operates stores, call centres, e-commerce, pricing, promotions, and omnichannel fulfilment	Channel architecture, point of sale, payments, product data, inventory visibility, and back-office dependencies
Dynamics 365 Human Resources	HR teams need employee, leave, benefits, compensation, performance, or related workforce processes	Required capabilities, worker-data integration, privacy, payroll boundary, and licensing

Microsoft documents multiple Project Operations deployment models. A Dataverse-only deployment is different from a scenario integrated with finance and operations apps, so the architecture must follow the process. Start with Microsoft’s Project Operations deployment-type comparison before assuming that project functionality is included in an existing ERP design.

Use the current Dynamics 365 licensing guidance to validate application subscriptions, attach eligibility, activity rights, and device scenarios. Avoid copying prices or entitlements from an old proposal into a new solution design.

Choose applications and modules from end-to-end processes

The strongest scope starts with the transactions the business must complete and control. Map each process from trigger to accounting outcome, identify the responsible application, then include only the modules required for a coherent first release. This reveals dependencies that a module wish list hides.

Operating model	Likely application scope	Modules to investigate first
Multi-entity services business	Finance	General ledger, AP, AR, cash and bank, budgeting, fixed assets, financial reporting
Wholesale distribution	Finance and Supply Chain Management	Product information, procurement, inventory, Warehouse Management where execution requires it, sales orders, costing, GL, AP, and AR
Discrete manufacturing	Finance and Supply Chain Management	Product information, engineering data, planning, production control, inventory, procurement, costing, GL, AP, and AR
Process manufacturing	Finance and Supply Chain Management	Formulas and process manufacturing, batch controls, quality, planning, inventory, procurement, costing, and finance
Project-based services	Finance with Project Operations assessment	Project contracts, resources, time and expense, project accounting, billing, GL, AP, and AR
Omnichannel retail	Finance, Supply Chain Management, and Commerce assessment	Products, pricing, channels, point of sale, inventory, fulfilment, warehouse, and financial posting
Asset-intensive operations	Finance and Supply Chain Management	Asset Management, procurement, inventory, maintenance, fixed assets, AP, and GL

The table is a discovery starting point, not a licensing quote. Two companies in the same industry can need different modules because their fulfilment model, legal entities, warehouse complexity, manufacturing method, or control requirements differ.

For help turning process evidence into a bounded design, review our Dynamics 365 implementation services. Licensing and project budget questions are covered separately in the Dynamics 365 Finance and Operations cost guide.

Sequence modules around dependencies and operational risk

Module sequencing should protect the operating model. Establish shared foundations first, prove the smallest complete process, and expand only after its data, controls, integrations, and support procedures work. This approach reduces the chance that later modules force expensive redesign of early assumptions.

I use the following sequence as a planning framework:

1. Define legal entities, organizations, products, financial dimensions, calendars, security, and integration ownership.
2. Configure the minimum end-to-end processes required for the first operational release.
3. Migrate representative master and opening data early enough to test real exceptions.
4. Validate posting, settlement, inventory, approvals, reporting, interfaces, and recovery with process owners.
5. Add advanced execution modules only when their prerequisites and operating teams are ready.

This is not a universal phase plan. A warehouse replacement may require Warehouse Management on the first day, while a finance-led transformation may defer advanced planning. The defensible sequence is the one supported by dependencies, business continuity, test evidence, and an owned cutover plan.

Related Finance and Operations reading

• What Dynamics 365 Finance and Operations is
• Finance and Operations features
• Finance and Operations cost

Sources

These official Microsoft references define the application boundaries and functional areas summarized above. Use them to verify current product behavior and deployment options, then consult the current licensing guide for commercial rights. Feature availability can still depend on version, region, deployment model, configuration, and licenses, so confirm those constraints during solution design.

• Microsoft Learn: Dynamics 365 Finance feature directory
• Microsoft Learn: Dynamics 365 Supply Chain Management documentation
• Microsoft Learn: Ledger and subledger accounting overview
• Microsoft Learn: Warehouse Management overview
• Microsoft Learn: Master planning learning path
• Microsoft: Dynamics 365 licensing guidance