If you are evaluating or already using Microsoft Dynamics 365 Finance & Operations (F&O), you have probably heard terms such as General Ledger, Master Planning, Warehouse Management, or Production Control. But do you know what each capability actually does for the business, how the pieces fit together, and which to prioritize first? This 2026 guide breaks down the core Finance and Supply Chain Management capabilities in practical terms, covering what each one does, the business value it can deliver, and the implementation considerations that can determine whether that value appears after go-live.
Before we begin, it is important to make a distinction when looking at the modules. Microsoft now presents Dynamics 365 Finance and Dynamics 365 Supply Chain Management (SCM) as separate applications within its Finance and Operations application family. Organizations can license and implement these applications according to their requirements, while both share the underlying finance and operations platform. Proactively addressing core during architectural planning prevents operational disruptions across multi-module deployments. In this article, “F&O” is used as shorthand for the combined Finance and SCM capability set commonly considered in an enterprise ERP program.
When implemented with discipline, F&O can improve the financial close, cash visibility, working capital management, inventory accuracy, production planning, fulfillment, and compliance across entities and jurisdictions. The greater value comes from integrating these capabilities into end-to-end business processes such as procure-to-pay, order-to-cash, plan-to-produce, and acquire-to-retire. An ERP with 25 modules that barely speak to one another is still a rather expensive collection of menus.
Core Finance Modules
1. General Ledger
The General Ledger is the financial foundation of Dynamics 365 Finance. It manages the chart of accounts, financial dimensions, journals, allocations, period close, consolidations, and intercompany accounting.
Business value: It provides a consistent basis for financial reporting, management analysis, multi-entity accounting, and audit controls.
Implementation consideration: Account structures, dimensions, fiscal calendars, and posting rules should be established early, as they influence transactions across the broader ERP.
Conducting a formal ensures your chart of accounts and financial dimension hierarchy support complex multi-entity reporting needs.
2. Accounts Payable
Accounts Payable manages the vendor invoice-to-payment cycle, including vendor records, invoice processing, purchase-order matching, approvals, payments, settlements, and credit processing.
Business value: It strengthens invoice control, payment planning, working-capital visibility, and exception management.
Implementation consideration: Approval workflows and three-way matching should align with actual purchasing policies and authority levels.
3. Accounts Receivable
Accounts Receivable manages customer invoicing, credit limits, collections, payments, settlements, credit notes, and dunning.
Business value: It supports stronger cash forecasting, collection discipline, credit control, and visibility into outstanding receivables.
Implementation consideration: AR should be designed in tandem with sales and project invoicing processes.
4. Cash and Bank Management
Cash and Bank Management oversees bank accounts, statements, reconciliations, payments, cash positions, and liquidity forecasting.
Business value: It provides clearer visibility into actual cash positions and expected inflows and outflows across banking relationships.
Implementation consideration: Automated statement imports and reconciliation are especially valuable for organizations managing multiple banks or currencies.
5. Budgeting and Budget Control
Budgeting supports budget preparation, approval, revision, allocation, spending control, and variance analysis.
Business value: It helps organizations maintain spending discipline while providing management with greater visibility into budget performance.
Implementation consideration: Controls should be placed at the appropriate points in the purchasing and expense process so they do not unnecessarily delay routine activities.
6. Fixed Assets and Asset Leasing
Fixed Assets manages acquisition, capitalization, depreciation, transfer, impairment, disposal, and reporting. Asset Leasing adds lease-accounting capabilities.
Business value: It provides accurate asset registers, depreciation records, visibility into capital expenditures, and reporting.
Implementation considerations: Asset categories, depreciation books, and capitalization thresholds should align with statutory and management reporting requirements.
7. Cost Accounting
Cost Accounting provides management with cost analysis using cost elements, cost objects, allocation bases, and overhead rules.
Business value: It helps organizations understand costs and profitability across products, departments, customers, projects, and shared services.
Implementation consideration: Cost models should have clear ownership and be backed by reliable operational data.
8. Tax and Globalization
Tax and Globalization supports tax calculation, tax codes, withholding, reporting, and country-specific regulatory requirements.
Business value: It supports compliant transaction processing and reporting across different entities and jurisdictions.
Implementation consideration: Local requirements in India, such as GST, TDS, e-invoicing, and e-way bills, should be incorporated into the solution design.
Core Supply Chain Management Modules
1. Product Information Management
Product Information Management defines products, variants, configurations, units, categories, attributes, and lifecycle information used throughout supply chain processes.
Business value: Reliable product data supports consistent purchasing, planning, manufacturing, inventory management, warehousing, pricing, and reporting.
Implementation consideration: Product governance should be treated as an ongoing business responsibility, not simply a migration exercise.
Reviewing a structured helps clarify data cleansing requirements and entity mapping rules before importing master records.
2. Procurement and Sourcing
Procurement and Sourcing manages requisitions, sourcing events, RFQs, purchase agreements, purchase orders, receipts, returns, and supplier collaboration activities.
Business value: It improves purchasing control, supplier visibility, spend management, and compliance with procurement policies.
Implementation consideration: Procurement should be designed in collaboration with Accounts Payable to support accurate invoice matching and clear ownership.
3. Inventory Management
Inventory Management manages stock quantities, value, availability, reservations, transfers, counting, and inventory closing.
Business value: It provides better visibility into stock across sites, warehouses, locations, batches, and serial numbers.
Implementation consideration: Inventory dimensions should provide the necessary control without introducing unnecessary transaction complexity.
4. Warehouse Management
Warehouse Management supports directed warehouse operations, mobile processes, waves, replenishment, license plates, picking, and put-away.
Business value: It can improve picking accuracy, warehouse throughput, stock visibility, and replenishment control.
Implementation consideration: WMS should be introduced where warehouse operations genuinely require directed work and more sophisticated execution controls.
5. Master Planning
Master Planning uses demand, supply, inventory, lead times, forecasts, and capacity data to generate planned orders and recommendations.
Business value: It helps reduce stockouts and excess inventory while providing planners with clearer purchasing and production signals.
Implementation consideration: Planning depends heavily on reliable lead times, BOMs, safety stocks, calendars, and inventory records.
6. Production Control
Production Control supports discrete, process, and lean manufacturing, including production orders, BOMs, routes, scheduling, material consumption, and production reporting.
Business value: It provides greater visibility into production schedules, materials, capacity, costs, and manufacturing performance.
Implementation consideration: The selected manufacturing model should reflect how the organization actually produces and costs its products.
7. Transportation Management
Transportation Management manages loads, routes, carriers, freight rates, and shipment-related processes.
Business value: It provides greater visibility into freight costs, carrier performance, shipment planning, and delivery operations.
Implementation consideration: Carrier, lane, route, service, and rate data require clear ownership.
8. Landed Cost
Landed Cost tracks inbound shipments and associated costs such as freight, duty, insurance, and handling.
Business value: It gives import-heavy organizations a clearer view of the true acquisition cost of inventory and its impact on margins.
Implementation consideration: Cost allocation should reflect how the organization actually manages imports and inventory valuation.
9. Asset Management
Asset Management supports equipment and facility maintenance through work orders, preventive maintenance, asset hierarchies, spare parts, labor, and downtime tracking.
Business value: It helps reduce unplanned downtime and improves visibility into maintenance activity and asset costs.
Implementation consideration: Asset Management complements Fixed Assets: one handles operational maintenance, while the other handles financial accounting.
10. Quality Management
Quality Management supports inspections, sampling, test results, quarantine, and nonconformance management.
Business value: It strengthens quality control, traceability, supplier quality, and the management of nonconforming products.
Implementation consideration: Quality controls should fit the actual production and warehouse processes rather than create unnecessary operational delays.
Which modules should go live first?
There is no universal module sequence for F&O. The right starting point depends on the organization’s processes, legacy environment, regulatory requirements, and transformation priorities.
A common approach is to first establish the financial and core master data foundations, then build the operational capabilities most closely aligned with business priorities, such as procurement, inventory, sales fulfilment, warehousing, planning, or production. More specialized capabilities can follow in later phases.
The key is to sequence the rollout around business processes and dependencies, rather than attempting to activate every capability simultaneously.
Engaging specialized ensures that module dependencies, testing schedules, and cutover timelines remain aligned with business goals.
How LevelShift helps organizations implement F&O
At LevelShift, we help organizations design and implement Dynamics 365 F&O focused on business outcomes rather than feature checklists. Our approach begins with end-to-end processes such as procure-to-pay, order-to-cash, plan-to-produce, and acquire-to-retire, then identifies the modules, configurations, integrations, and data foundations needed to support them.
Our F&O implementation expertise covers:
- Business process and solution design
- Finance and supply chain configuration
- Data migration and validation
- Integrations and security
- Testing and deployment
- Phased rollouts and post-go-live support
Whether replacing a legacy ERP, for the first time, or expanding an existing footprint, LevelShift helps organizations balance Microsoft best practices with industry requirements, localization, and long-term scalability.
Conclusion
Dynamics 365 Finance and Supply Chain Management is more than a collection of modules. Its value comes from connecting financial control with the physical processes that keep an organization operating, from purchasing and production through inventory, warehousing, fulfillment, and cash collection.
The right implementation does not require every module to go live at once. It requires clear priorities, sound data and process foundations, and a rollout sequence that gives each capability a defined purpose. For organizations evaluating F&O in 2026, this approach provides a practical foundation for stronger control, better operational visibility, and more informed decision-making.
FAQs
- Is Dynamics 365 F&O a single application?
F&O broadly refers to the finance and operations application family. Dynamics 365 Finance and Supply Chain Management are separate applications that share the underlying platform. - Do organizations need every F&O module?
No. Modules should be selected according to business processes, industry requirements, and implementation priorities. - Which F&O modules should go live first?
There is no universal sequence. Finance, master data, and foundational configuration often come first, followed by operational capabilities aligned with business priorities. - What is the difference between Fixed Assets and Asset Management?
Fixed Assets handles the financial accounting for assets. Asset Management focuses on maintaining operational equipment and facilities. - How long does an F&O implementation take?
It varies by scope, entities, countries, modules, integrations, data complexity, and rollout strategy.