Enterprise ERP is a big move. Here’s everything you wish someone had told you before you signed the contract.
“There’s a reason people joke that D365 Finance & Supply Chain implementations are like remodeling a house while you’re still living in it. There’s truth in that. But here’s what nobody says next: done well, the result is a house that actually works. Let’s talk about how to get there.”
First, Let’s Get Clear on What We’re Talking About
Dynamics 365 Finance & Supply Chain Management (also commonly referred to as D365 F&O, F&O, or FinOps) — which I’ll call F&SCM for the rest of this post, because life is short — is Microsoft’s enterprise-grade ERP solution. When people say “Dynamics 365 Finance and Operations,” they’re talking about this same family of applications. Microsoft split Finance and Supply Chain Management into two distinct apps a few years back, but in most implementations, they travel together as a connected suite.
F&SCM is built for organizations with real complexity: multiple legal entities, multi-currency environments, sophisticated manufacturing or distribution operations, project accounting, global compliance requirements — the works. If Business Central is the right tool for a thriving mid-sized business, F&SCM is the right tool when that business has grown into something that needs enterprise-scale financial controls and supply chain muscle to match.
It is a powerful, deeply capable system. It is also — and I say this with great affection — not simple. The organizations that succeed with it are the ones that go in prepared. So let’s prepare.
Part 1: Things to Think About Before You Commit
I’ve been in enough pre-sales and kickoff conversations to know that the questions that matter most get asked after the contract is signed. Let’s flip that script.
What Is Your Organizational Structure — Really?
F&SCM is built around legal entities. How many do you have? How do they interact? Do you consolidate financials across them? Do your intercompany transactions need to be automated? These aren’t technical questions — they’re business questions, and the answers shape your entire configuration strategy from day one.
How Complex Is Your Supply Chain, Honestly?
Are you a distributor? A manufacturer? Both? Do you use batch or serial tracking? Do you have a warehouse management system today, or will WMS be new to your team? Supply chain complexity is one of the biggest drivers of implementation scope — and underestimating it is one of the most expensive mistakes you can make early on.
Where Do You Operate, and What Does That Mean Legally?
F&SCM has robust localization and compliance capabilities, but they need to be scoped and configured correctly. Multi-country operations mean multi-country tax rules, reporting requirements, and regulatory considerations. Know your footprint before you start designing your system.
What Systems Are You Replacing — and What’s Staying?
Most organizations don’t implement F&SCM in a vacuum. There are integrations to plan: payroll systems, CRM, e-commerce platforms, third-party logistics, EDI partners. Every integration is its own mini-project. Get the full map on paper before anyone writes a single line of configuration.
A word about scope and phasing: F&SCM is extraordinarily capable, which can make it tempting to try to turn on everything at once. Don’t. The organizations that go live successfully are almost always the ones that define a disciplined Phase 1 scope — core finance and the most critical operational modules — and build from there. “We’ll add that in Phase 2” is not a failure. It’s a strategy. A very smart one.
Part 2: What the Implementation Journey Actually Looks Like
F&SCM implementations are longer and more involved than most organizations expect going in. The timeline varies significantly based on scope, but you should plan for months, not weeks. Here’s the honest arc of what you’ll move through:
01 Discovery & Requirements Gathering
Your implementation team needs to understand your business at a deep level before a single configuration decision gets made. This means detailed process walkthroughs — accounts payable, accounts receivable, general ledger, purchasing, inventory, manufacturing, whatever is in scope. This phase is where your internal subject matter experts matter most. The more engaged and informed they are, the better your implementation goes. Skimping on discovery is one of the most reliable ways to create expensive rework later.
02 Solution Design & Fit-Gap Analysis
Once your requirements are documented, your team maps them to what F&SCM does out of the box. Where the system fits your process, great. Where there’s a gap, a decision has to be made: do you adapt your process to the system, configure around it, or build a customization? This is where good judgment matters enormously. Customization has a cost that shows up every time Microsoft releases an update. Challenge yourself to work with the system before you work around it.
03 Build & Configuration
This is where your decisions become settings, parameters, and working system logic. Chart of accounts, financial dimensions, posting profiles, workflows, security roles, number sequences — there are hundreds of configuration points in F&SCM, and they all need to be deliberate. Your team should be reviewing builds in regular cycles, not just at the end. Surprises caught early are called feedback. Surprises caught at go-live are called problems.
04 Data Migration
This phase deserves more attention and more time than almost any organization gives it. Your opening balances, customer and vendor master records, item data, inventory, fixed assets, historical transactions — all of it has to be extracted from your old system, cleaned, mapped, transformed, and loaded into F&SCM. Data migration is the phase where old system sins come to light. Budget significant time for data cleansing before migration even begins, and plan for multiple test migrations before you go live.
05 System Integration Testing & User Acceptance Testing
Testing is not optional and it’s not something to rush. SIT validates that the system works as configured. UAT validates that the system works for your actual users doing their actual jobs. Both matter. Your subject matter experts need to walk through end-to-end scenarios — a purchase order from requisition to invoice matching and payment, a sales order from entry to fulfillment to cash receipt — in a test environment that mirrors production. If they can’t do their job in UAT, they can’t do their job at go-live.
06 Training
F&SCM is complex enough that role-based training isn’t just a nice-to-have — it’s essential. Your AP clerk does not need to understand the General Ledger module in depth. Your Controller does not need to know how to process production orders. Train people on what they need to know to do their specific job, and give them hands-on practice in a sandbox environment before they ever touch live data. Watching someone else navigate the system is not training. Muscle memory is training.
07 Go-Live & Hypercare
The switch gets flipped. Your team does real work in a real system for the first time. It will feel chaotic — that is normal and expected. Hypercare is the period immediately post-go-live when your implementation partner is close, issues get triaged fast, and everyone operates with the understanding that learning is still happening. A well-prepared go-live is still bumpy. A poorly-prepared one is a different level of difficult. Plan hypercare support for at least 30-60 days, depending on your complexity.
Part 3: The Pitfalls — The Ones I See Over and Over Again
F&SCM implementations have their own particular patterns of struggle. These are the ones I’ve watched trip up organizations that were otherwise smart, well-resourced, and genuinely committed to getting it right.
Underestimating the Financial Dimensions Conversation
Financial dimensions are how F&SCM allows you to slice and dice your financial data — by department, cost center, business unit, project, region, whatever matters to your organization. Getting this structure right is foundational. Get it wrong, and your reporting doesn’t work the way leadership expects. Get it really wrong, and you’re looking at a painful redesign down the road. This conversation needs to happen early, involve finance leadership, and be documented thoroughly before configuration begins.
→ Bring your controller and your CFO into the financial dimensions design conversation. Not just your IT lead. The people who actually read the reports need to help design the structure that feeds them.
Treating Security and Roles as an Afterthought
F&SCM has a robust security model — roles, duties, privileges, data-level security. It also means that if you don’t design and test security carefully, users either can’t do their jobs because they’re missing access, or they have access they absolutely shouldn’t have. Both are bad. Security design needs to be part of your build phase, not something you scramble to configure the week before go-live.
→ Map your user roles to system security roles early. Test security in your UAT environment with actual users logging in as themselves. If they can’t access what they need to do their job, that’s a go/no-go issue — find out before go-live, not after.
Customizing Too Early and Too Freely
F&SCM is highly configurable, and there’s a temptation — especially when migrating from a legacy system where everything worked “our way” — to customize the new system to match the old one. Resist this. Customizations complicate upgrades, create technical debt, and often address problems that the standard system actually solves perfectly well once you understand it. Every customization should require a business case that justifies the long-term cost.
→ Establish a decision framework before build begins: who approves customizations, what’s the bar for “this genuinely can’t be solved with configuration,” and how will it be documented. The best F&SCM implementations I’ve seen are the ones that challenged every customization request relentlessly.
Data Migration Getting Deprioritized Until It’s an Emergency
Every project plan has data migration on it. Not every project team treats it with the urgency it deserves. Data migration for an F&SCM implementation involves significant volumes, multiple data entities, and a lot of cleansing work that your own team has to own — your implementation partner can’t clean up fifteen years of vendor master records for you. When data migration gets pushed, everything downstream gets compressed: testing, training, go-live readiness.
→ Start the data cleansing conversation on day one. Assign a data migration lead on the client side. Run test migrations early enough that failures can be corrected without crashing the timeline. Assume it will take longer than the estimate and plan accordingly.
Integration Complexity Getting Discovered Mid-Project
F&SCM rarely lives alone. There are almost always integrations to design, build, and test — and integrations are where projects quietly absorb enormous amounts of time. An EDI connection that “should be straightforward” can take weeks. A payroll system integration with unusual data formats can derail a timeline. Integration complexity that isn’t mapped and scoped in discovery has a way of showing up as a surprise right around UAT, which is the worst possible time for surprises.
→ Do a full integration inventory before discovery closes. Document every system that touches F&SCM data, in any direction. Treat each integration as its own workstream with its own timeline, owner, and test plan.
Planning Optimization: The “We’ll Figure That Out Later” Trap
If your organization uses Supply Chain Management for demand planning or MRP, Planning Optimization is a topic you need to engage with early. Microsoft deprecated the legacy planning engine and Planning Optimization is now the direction forward — and it behaves differently in important ways. Organizations that discover this mid-implementation, or after go-live, are dealing with a much harder retrofit conversation than the one they could have had during design.
→ If supply planning is in scope, make Planning Optimization part of your design conversation from the start. Understand what it does differently from legacy MRP and design your planning parameters accordingly — not as an afterthought.
Part 4: What Microsoft Is Building — The Good Stuff Coming Your Way
Here’s something I genuinely enjoy telling clients: F&SCM is not standing still. Microsoft’s investment in this platform through the 2025 and 2026 release waves is substantial and increasingly focused on the kind of AI-driven automation that actually makes finance and operations teams’ daily lives better — not just technically impressive demos.
AI · Now -> Copilot — Already Inside Your System
Copilot is built directly into F&SCM at no additional license cost, and it’s already doing real work. Hover over a vendor or customer record and Copilot generates a contextual summary pulling transaction history, overdue balances, and key data — without navigating through multiple screens. In Collections, Copilot summarizes overdue accounts and drafts follow-up emails for coordinator review. In the Reconciliation Workspace, it automatically matches ledger entries and surfaces discrepancies for resolution. These are live, practical time-savers available to your team right now.
AI · Wave 2 -> Account Reconciliation Agent
This one is going to change month-end close for a lot of finance teams. The Account Reconciliation Agent proactively detects discrepancies between subledger and general ledger balances, recommends fixes, and maintains a full audit trail of every action taken. Over time, it learns from how your team resolves issues and begins automating the resolution of recurring patterns. The goal is to take something that currently absorbs hours of controller and accounting staff time and compress it dramatically — with full human oversight still in the loop.
Analytics · Wave 2 -> Business Performance Analytics — Getting Smarter
Business Performance Analytics (BPA) is Microsoft’s self-service analytics layer for F&SCM, and it’s getting significant upgrades. Hourly data refreshes (up from twice daily) mean reports reflect near real-time information. A redesigned next-generation data model builder simplifies how finance and IT teams collaborate on reporting structures. And Copilot is now embedded directly in BPA — users can ask questions in plain language and get summarized, contextual answers without needing to call IT or build a custom query. If your team is still exporting to Excel to make sense of system data, BPA is the tool that changes that conversation.
AI · Wave 2 -> Copilot for Finance in Microsoft 365
This is a separate but connected piece worth knowing about: Microsoft 365 Copilot for Finance is now generally available and connects your F&SCM data into Excel and Outlook. Variance analysis that used to take an analyst hours — identifying the drivers behind a budget-to-actual gap, drafting a management summary — is something Copilot can now support in minutes. Customer payment inquiry emails in Outlook can be answered with Copilot pulling live invoice and balance data from F&SCM automatically. It’s the system coming to where your team already works, not the other way around.
Finance · Wave 2 -> New Journal Framework
This is a foundational improvement that accounting teams are going to appreciate. The new journal framework in F&SCM significantly improves performance for large journal imports, adds support for multi-company journal entries in a single transaction, enables voucher-level error handling, and allows you to preview accounting entries before they post. For organizations running high-volume journal processes at period end, this is a meaningful upgrade to both efficiency and control.
Supply Chain · Wave 2 -> Smarter Demand Planning & Supply Chain AI
On the supply chain side, demand forecasting is getting meaningfully more intelligent. External signals — inflation trends, weather events, promotional calendars — can now be incorporated into the forecast model alongside historical sales data. Generative demand insights use AI to identify trends, seasonality, and inventory risks automatically. For manufacturers and distributors managing complex planning cycles, these capabilities address real operational pain points: overstock, stockouts, and the endless manual recalibration of plans that don’t account for what’s happening in the real world.
Supply Chain · Now -> End-to-End Product Traceability
For organizations in regulated industries or those managing complex supply chains, traceability is not optional — and F&SCM is investing heavily here. Full batch and serial number traceability from sourcing through production to customer delivery, forward and backward trace search for quality and recall scenarios, and as-built bill of materials genealogy recording are all part of the current roadmap. If your industry requires chain of custody documentation, this is the kind of native capability that eliminates the need for bolted-on third-party solutions.
Finance · Wave 2 -> Automated Tax Feature Creation
Tax configuration in F&SCM has historically been one of the more painstaking setup processes, especially for organizations with complex multi-jurisdiction needs or those migrating from legacy tax setups. The new automated tax feature creation uses your existing tax master data — tax codes, sales tax groups, item sales tax groups — to automatically generate tax calculation features. Less manual setup, fewer configuration errors, faster adoption of the advanced tax engine. For implementers and for finance teams managing tax compliance across multiple jurisdictions, this matters.
One thing worth flagging on the AI features: The core Copilot assistance capabilities in F&SCM are included in your existing license. The agentic features — like the Account Reconciliation Agent and more autonomous workflow automation — are evolving quickly and some operate on consumption-based billing models. As Microsoft’s licensing evolves alongside these capabilities, it’s worth keeping an eye on the current licensing guide and having that conversation with your partner before you budget for specific agent features at scale.
So What Does All of This Mean for You?
If you’ve read through this and felt simultaneously energized and a little overwhelmed — good. That’s the appropriate reaction. F&SCM is a genuinely powerful platform. It can transform how a complex organization manages its finances, its operations, and its decision-making. It can also be genuinely hard to implement well, especially if the groundwork isn’t laid thoughtfully.
The difference between an F&SCM implementation that leaves people saying “this system changed how we work” and one that leaves people saying “I can’t believe we spent this much money to be this frustrated” is almost always the same thing: preparation, clarity, and the right people asking hard questions before the project begins.
That’s exactly what this series is here to help with. We’re going to go deep on the topics that matter most to the finance and operations professionals who actually live in this system every day — the configuration decisions that have long-term consequences, the features that save time once you know they exist, and the “why does it work this way” explanations that finally make the system click.
Up Next-
We’ll tackle Financial Dimensions in D365 F&SCM — what they are, why the design decision matters more than almost anything else in your implementation, and how to think through the structure before you’re locked into something that doesn’t serve your reporting needs.
Spoiler: this is the conversation that should happen in your second discovery meeting, not your tenth. It’s important to make sure you’re ready for it.
Until then — take good notes, ask your implementation partner the uncomfortable questions, and don’t let anyone convince you that “we’ll figure that out later” is a plan.
— Bobbi
Leave a Reply