MB-920 Dynamics 365 ERP Fundamentals: Finance and Supply Chain Foundations

MB-920, Microsoft Dynamics 365 Fundamentals (ERP), retired on December 31, 2025. Its last published scope concentrated on Dynamics 365 Supply Chain Management, Dynamics 365 Finance, and the shared capabilities of finance and operations applications. The exam was designed for beginners who needed to understand how an integrated ERP system supports business processes rather than for experienced consultants configuring every option.

The historical value of MB-920 lies in its process map. Finance explains how organizations record, control, and report monetary activity. Supply Chain Management explains how they plan, buy, store, make, move, and sell physical goods. Shared finance-and-operations capabilities connect those processes across legal entities, workflows, analytics, and the wider Microsoft ecosystem.

Current role-based exams demand much greater depth. MB-310 focuses on financial configuration and control, while MB-330 focuses on supply-chain processes. The retired fundamentals objective set remains useful for understanding the vocabulary and process relationships underneath those advanced roles, but passing MB-920 is no longer possible.

Supply Chain Management followed material from planning through fulfillment

The Supply Chain portion of MB-920 introduced the operational chain that begins with demand and supply planning and continues through purchasing, inventory, warehousing, manufacturing, sales fulfillment, and asset-related work. A fundamentals learner did not need to become a warehouse designer or production planner, but did need to recognize why each function exists and how a transaction in one area affects another.

Inventory provides a clear example. A purchase increases expected supply, receiving changes physical availability, reservation affects what can be promised, warehouse work moves stock, a sales shipment reduces on-hand quantity, and financial posting records the value. The integrated ERP advantage comes from those steps sharing controlled data instead of being reconciled manually across unrelated systems.

Procurement and sourcing balanced availability, cost, and supplier control

Purchasing begins with a requirement and becomes a supplier commitment through requisitions, requests, purchase orders, receipts, and invoices. The organization needs item and vendor data, approval policies, delivery expectations, and matching controls that reflect how it buys. The fundamentals objective was to identify these capabilities and understand their place in the operating cycle.

Procurement is also a control process. A company may need separation between the person requesting goods, the person approving the purchase, the person receiving them, and the person approving payment. ERP configuration makes those responsibilities visible and auditable. That is why supply-chain knowledge cannot be separated completely from finance or security even in an introductory exam.

Warehousing and manufacturing turned supply plans into physical execution

Warehouse management coordinates locations, work, mobile-device activities, picking, packing, replenishment, and shipping. Manufacturing adds bills of materials or formulas, routes, resources, production orders, consumption, and output. MB-920 covered these areas at a recognition level so candidates could match a business scenario to the appropriate Dynamics 365 capability.

The key learning pattern is flow. A plan suggests what should be produced or purchased, a warehouse provides the material, production transforms inputs into outputs, quality and inventory status affect release, and sales demand eventually consumes the finished product. When learners can explain that flow in plain business language, the application terminology becomes much easier to organize.

Dynamics 365 Finance connected operational events to accounting outcomes

Finance coverage included general ledger, accounts payable, accounts receivable, budgeting, fixed assets, cash and bank management, and related controls. Fundamentals candidates needed to understand why operational transactions eventually create accounting entries and why reliable financial reporting depends on the quality of upstream master data and processes.

The modern Dynamics 365 Finance Functional Consultant Associate goes deeper into these responsibilities, but the MB-920 lesson remains useful: accounting is not a separate end-of-month activity layered on top of operations. Vendor invoices, customer billing, inventory value, asset acquisition, expenses, and cash movements all feed the financial picture continuously.

Shared finance and operations capabilities supported multiple legal entities

Organizations may operate several legal entities while still wanting common products, vendors, customers, workflows, reporting practices, or shared services. Finance and operations apps provide structures for companies, organizational hierarchies, currencies, calendars, number sequences, and intercompany processes. The fundamentals exam expected learners to recognize why enterprise structure matters before detailed configuration begins.

Multiple-company design introduces tradeoffs. Standardization reduces complexity and makes reporting easier, but local regulations or business models may require different processes. The right ERP model distinguishes what should be global from what must remain local. Even at fundamentals level, that is a more useful mental model than memorizing a list of administrative screens.

Reporting and analytics depended on trustworthy operational data

ERP systems generate large volumes of transactional data, but raw transactions are not the same as useful information. Workspaces, dashboards, embedded analytics, financial reports, and Power BI experiences can help managers track cash, orders, inventory, production, supplier performance, and other measures. The quality of those outputs depends on consistent processes and dimensions upstream.

Learners should therefore connect reporting questions to data creation. If a manager wants profitability by business unit, the required dimensions must be captured on relevant transactions. If a planner wants reliable available-to-promise information, inventory updates and reservations must be timely. Analytics expose the health of the operating model; they cannot repair missing or inconsistent source data after the fact.

Integration made ERP part of a wider business-application ecosystem

Dynamics 365 Finance and Supply Chain Management connect with Power Platform, Microsoft 365, external systems, data services, and specialized applications. The fundamentals objective was not to design every integration, but to understand why organizations integrate: remove duplicate entry, automate handoffs, expose information to different audiences, and keep core business records synchronized.

A broader view of Dynamics 365 business applications helps place ERP functions in context. Readers can then follow role-specific credentials such as Dynamics 365 Supply Chain Management Functional Consultant Associate when they need deeper implementation detail. The appropriate route depends on the business processes and day-to-day responsibilities the learner actually owns.

MB-920 remains useful as a retired map of ERP process relationships

The strongest way to revisit MB-920 is to walk a few complete business cycles. Procure an item and pay the supplier; produce or receive inventory and move it through a warehouse; sell to a customer and collect payment; acquire an asset and depreciate it; close a period and inspect the resulting reports. Those cycles expose the relationships that the old fundamentals exam was built to teach.

MB-920 ERP fundamentals provide additional historical context. From there, readers should choose current role material based on actual responsibility rather than treating the retired exam as a prerequisite. The enduring value is a coherent picture of finance and supply-chain operations inside one enterprise platform.

Another useful MB-920 lens is the difference between master data and transactions. Items, vendors, customers, warehouses, accounts, dimensions, and calendars define the structure in which work occurs; purchase orders, production orders, sales orders, journals, receipts, and invoices record events inside that structure. Poor master data creates repeated transaction problems, which is why ERP implementation teams spend so much effort defining ownership and standards before volume increases.

The exam also introduced the idea that planning and execution use different time horizons. A forecast or master plan estimates future demand and supply, while warehouse and production processes execute specific work now. Finance then records and reports the economic result. Learners who connect those horizons understand why a change in demand can influence purchasing, manufacturing, inventory, cash requirements, and eventually financial performance.

Exceptions reveal the strength of an ERP design. Short shipments, damaged receipts, invoice mismatches, production scrap, customer returns, credit limits, and late supplier deliveries all disturb the ideal flow. A robust system does not assume every transaction is perfect; it provides statuses, holds, workflows, adjustments, and audit trails that let the organization resolve exceptions without losing control of the original business event.

MB-920 also helps explain why role-based specialization became necessary. A finance consultant must understand accounting configuration in far greater depth than a warehouse supervisor, while a supply-chain consultant needs planning and fulfillment knowledge beyond what a fundamentals credential could test. The retired exam introduced the shared vocabulary, and later credentials divided that vocabulary according to responsibility and implementation depth.

Readers using archived MB-920 resources should therefore separate enduring process knowledge from time-sensitive product detail. The logic of procure-to-pay, order-to-cash, plan-to-produce, and record-to-report remains useful; specific menus, feature names, licensing boundaries, and certification requirements may not. That distinction preserves the educational value of the retired objectives while keeping current career decisions anchored in today's Microsoft certifications. It also exposes where ownership, approvals, and data quality must remain consistent as a transaction crosses functional boundaries.

Project-oriented businesses add another useful ERP scenario. A customer project may combine labor, expenses, purchasing, inventory, billing milestones, and financial recognition. Even where a fundamentals blueprint does not demand detailed project accounting configuration, the scenario demonstrates why an ERP platform benefits from shared customers, dimensions, approvals, and financial posting rules. The same business event can be operational to one team and financial to another.

Asset management provides a similar bridge between operations and finance. Equipment requires maintenance history and operational availability, while fixed assets require capitalization, depreciation, and disposal accounting. The terms are not interchangeable, yet they can describe the same physical object from different perspectives. Understanding those perspectives helps candidates see why integrated applications still need clear domain boundaries rather than one giant undifferentiated record.

Another valuable exercise is to trace a single item across departments. Planning identifies the requirement, procurement sources it, warehousing receives and stores it, production may consume it, sales promises and ships it, and finance values the movement. Following one object through the organization makes ERP integration concrete and exposes which master data and controls each department depends on.