Historical certification context reviewed October 27, 2026. Microsoft’s Dynamics 365 Fundamentals (ERP) exam MB-920 retired on December 31, 2025. This article explains the Finance and Operations business concepts formerly introduced through that credential. It does not identify an automatically equivalent replacement or offer instructions for registering for a discontinued exam.
Enterprise resource planning can sound abstract until a business transaction travels between sales, stock, purchasing and finance. The historical MB-920 credential was meant to give learners vocabulary for understanding those connections in Microsoft Dynamics 365. A candidate searching for “Finance and Operations Fundamentals certified” in 2026 needs to know that the exam is retired, but also that the underlying business processes have not ceased to matter. The useful outcome is a grounded picture of how enterprise systems turn operational events into consistent financial and managerial records.
What the former Dynamics 365 Fundamentals exam represented
Microsoft’s MB-920 study guide identifies a retirement date of December 31, 2025. It covered core enterprise-resource-planning capabilities and the role of Dynamics 365 applications in finance and operations processes. The archived MB-920 objectives remain a useful historical record of what the exam emphasized. They are not evidence of a current booking opportunity, and the old fundamental credential should not be described as a direct substitute for present role-based certifications.
The name “Finance and Operations” has been used both for a family of business applications and in past certification titles. That ambiguity matters. An organization may use Dynamics 365 Finance, Supply Chain Management and other applications, but familiarity with their product names does not establish skill in configuration, integrations, reporting or enterprise controls. Conversely, a business analyst who understands purchase orders and financial postings may bring valuable domain knowledge despite never having held the retired certificate.
For a learner deciding what to study, start with a specific role: finance user, supply chain analyst, functional consultant, technical developer or solution architect. Each interacts with the ERP platform differently. A role-neutral fundamentals exam once introduced the landscape, but the right modern curriculum should be selected from current Microsoft Learn content for the intended responsibilities.
How an ERP transaction crosses departmental boundaries
Consider a company that receives a customer order for items not presently in its warehouse. Sales records the order, inventory systems check available and expected stock, purchasing may trigger a replenishment order, and finance eventually records revenue, tax and receivables under the organization’s accounting rules. Each step is a different view of one commercial event. Poorly defined ownership or inconsistent master data can cause the steps to disagree.
An ERP platform coordinates these activities using shared entities, controlled workflows, posting processes and integrations. The purpose is not only convenience. It is to provide traceability: the business should be able to explain why a financial amount appears in its reports and which operational record produced it. A duplicate supplier, incorrect unit of measure or erroneous exchange-rate assumption can propagate across departments if controls are weak.
A practical fundamentals exercise follows a single order from quotation to fulfillment and invoice. Identify which users can approve changes, what documentation supports an exception and where a reversal would be recorded. This reveals why enterprise application knowledge requires business vocabulary as well as familiarity with configuration screens.
Finance processes that shape system design
Finance functions typically depend on general ledger structures, accounts payable, accounts receivable, budgeting, cash management and reporting. These are not merely isolated features. For example, the chart of accounts and financial dimensions influence how operations can report profitability by department, product or region. A seemingly harmless configuration decision can limit the questions management can answer later.
Accounts payable requires controls around supplier identity, purchasing authorization and invoice matching. Accounts receivable connects customer invoices, payment allocation and collections. Even in a carefully automated workflow, a person must understand when transactions should be blocked, approved or investigated. This is why segregation of duties and audit trails belong in an ERP learning plan from the beginning.
For a starter project, design approval rules for vendor invoices above a threshold and specify how a finance controller would investigate a mismatch between purchase order, receipt and invoice amount. Describe a valid exception and the evidence required before payment. The exact software screens are less important than the transactional logic and the control objective they implement.
Supply chain knowledge and operational accuracy
Supply chain operations involve sourcing, inventory valuation, warehouses, production and distribution. The basic challenge is to make reliable decisions about what to buy, where to store it and when to deliver it. Enterprise applications help coordinate those decisions, but their results depend on master data quality and clearly defined processes. An incorrect lead time can produce stockouts even if the planning algorithm runs exactly as configured.
Inventory management introduces important distinctions among physical stock, available stock, reserved stock and stock expected from suppliers. A warehouse manager and finance controller may examine the same item from different perspectives. The system needs to reconcile inventory transactions with financial valuation without obscuring the reasons for discrepancies. Product variants, batch and serial tracking, units of measure and location structures add further complexity.
A useful case study traces a returned product. The warehouse may inspect and restock it, sales may issue a credit, and finance must account for the reversal. If the return is damaged, the transaction can involve different inventory disposition and accounting treatment. An analyst who maps the correct exceptions shows deeper ERP understanding than someone who memorizes a list of Dynamics 365 modules.
For a more advanced manufacturing or distribution scenario, the site’s Dynamics 365 manufacturing and supply chain practices discussion can extend the business-process analysis. It is supporting context, not an endorsement of a new exam code.
Governance, security and implementation realities
ERP implementations are particularly sensitive to access controls. A user who can create a vendor, approve an invoice and execute payment may have excessive authority, even if every action is logged. Role design should reflect segregation of duties, business approval policies and the principle of least privilege. Administrators must also decide how temporary access is granted and removed during support incidents.
Data migration is another hidden risk. When moving from a legacy accounting or warehouse system, teams need to reconcile opening balances, customer records, product identifiers, inventory quantities and incomplete transactions. A successful import without errors does not prove financial or operational correctness. Representatives from each business function should validate totals and sample transaction histories before go-live.
Integration choices also affect reliability. A payment platform, e-commerce system, transportation provider or business intelligence tool may exchange information with ERP components through supported interfaces. The architect and functional leads need to decide how late or duplicate messages are handled, who owns a failed transaction, and what happens if a dependent system is unavailable during peak operations. Monitoring and support runbooks turn those questions into manageable practices.
A well-run rollout includes change communications and adoption planning. Even technically sound workflows can fail when staff do not understand new approval steps, labels or exception procedures. Training should use realistic tasks—creating a purchase requisition, reconciling a return, approving a supplier adjustment—rather than relying entirely on demonstrations of product navigation.
What a beginner should learn after MB-920 retirement
Start with a business process map instead of an arbitrary certificate comparison. For a finance role, focus on general ledger, receivables, payables, reporting and control responsibilities. For a supply chain role, begin with procurement, inventory, warehousing and fulfillment. Ask where the two worlds intersect, and learn the records that connect them. Only then choose current training modules and confirm whether a relevant Microsoft credential is still offered.
People considering a functional consultant career will benefit from understanding requirement gathering, configuration choices, test planning and stakeholder collaboration. Developers need integration, extensibility, security and deployment concepts. Architects need to evaluate whether standard capabilities meet the business need and what risks customizations introduce. The retired fundamentals syllabus cannot substitute for these deeper practical skills.
Use official Microsoft product documentation and role-focused learning paths rather than unaudited exam banks. If an older site promises “current MB-920 questions” or a guaranteed pass, its exam-status claim is outdated. Study materials should identify a current objective version where applicable and explain business processes in ways that can be tested with example transactions.
Someone who holds the historical credential can accurately describe it with its earning date and show how the knowledge informed later work. Those who do not should not spend money trying to take a retired fundamentals exam. They can instead build an ERP process portfolio and pursue live qualifications only when those qualifications meaningfully align with their role.
The enduring purpose of Finance and Operations fundamentals
The broad value of an introductory ERP education is learning to recognize dependencies. A sale can affect inventory and receivables; a procurement decision can change inventory valuation and cash flow; a security rule can protect the business while slowing an approval process. Understanding the consequences of each transaction helps users and implementation teams make better decisions.
In October 2026, MB-920 is a historical identifier. Microsoft’s retired exam notice and archived objectives should appear alongside any discussion of it. The better question is not which discontinued test once represented these topics, but whether a learner can trace, validate and improve cross-functional business processes. That ability is transferable across applications and remains professionally relevant long after an exam code disappears.
Continue exploring the technologies and certification concepts that matter most to you.