Everything this series of posts has covered, distilled into what Finance most needs to hear in the first week of a D365 F&O implementation—written from the perspective of someone who has seen every mistake in this series made by smart, capable Finance teams who were given the wrong information or not enough information at the right moment.
Dear Finance Director,
You just signed the contract. Somewhere in your organization, an implementation team is being assembled. The kickoff is on the calendar. The statement of work describes an 18-month journey from where your Finance function operates today to where D365 F&O is supposed to take it. The vendor has shown you the demos. The implementation partner has proposed a project plan. Everyone involved is optimistic.
I want to talk to you before the first workshop, because D365 F&O is a genuinely powerful enterprise Finance platform—and it is also an implementation where the decisions made in the first six weeks determine the quality of Finance’s experience with the system for the next decade. I have worked on enough of these implementations to know where Finance goes right and where it goes wrong. And I know that the places where Finance goes wrong are almost never about D365 F&O’s capability. They are about Finance’s engagement with the decisions that shape that capability for the organization.
Here is what I want you to know.
D365 F&O Is Not Self-Configuring—Every Default Is Someone’s Choice
D365 F&O ships with defaults: a default chart of accounts structure, default posting profiles, default approval workflow templates, default period close settings. These defaults are reasonable starting points for an organization that has not yet thought about what it needs. They are not the right configuration for your Finance function, because your Finance function has specific management reporting requirements, specific control requirements, specific close procedures, and a specific regulatory environment that the defaults do not reflect.
Every default that makes it into your live environment without Finance’s deliberate review is a decision Finance did not make. Some of those decisions will be fine. Some will create problems Finance will not discover until the first close, or the first audit, or the first time someone asks for a report that the default configuration cannot produce. The implementation is not self-configuring. Every configuration choice has a Finance consequence. Finance must be in the room when those choices are made.
The Financial Dimension Design Is the Most Consequential Decision in the Implementation
D365 F&O’s financial dimension architecture determines how every transaction is analytically tagged, how every management report can be sliced, how cost accounting allocations work, and how security restrictions can be applied by dimension value. The dimension structure is decided early in the implementation—typically in the first three to four weeks of fit-gap workshops—and it is genuinely difficult to change after transactions have been posted.
Finance must own the dimension design decision. The implementation partner will propose a structure. IT will have a preference based on what is technically straightforward. Operations will want dimensions that support their operational reporting. Finance must ensure the dimension structure supports the management reports Finance is accountable for producing: the legal entity rollup, the departmental P&L, the cost center analysis, the product line margin report. If the proposed dimension structure cannot produce those reports, it is not ready.
Test the proposed dimension structure against every management report on Finance’s reporting calendar before it is finalized. This test takes two hours and prevents the six-month-post-go-live discovery that the dimension structure does not support the Management Reporter configuration Finance needs.
The Implementation Partner Configures D365 F&O—Finance Configures Finance
Your implementation partner knows D365 F&O. They know how to configure it, how to migrate data into it, how to train users on it. What they do not have is your institutional knowledge of how Finance operates under pressure: which reconciliation consistently produces surprises and why, which approval controls matter most to your auditor, what the CFO actually looks for in the management pack that is not obvious from a requirements document.
The best implementations are collaborations, not delegations. Finance provides the operational requirements and the accounting policy decisions. The implementation partner provides the D365 F&O architecture and the configuration expertise. When Finance delegates the requirements-gathering to a junior team member who is not authorized to make accounting policy decisions, the implementation partner makes reasonable choices with insufficient information. Finance inherits those choices.
Assign a senior Finance leader to every major configuration decision area: chart of accounts, financial dimensions, posting profiles, Management Reporter report library, approval workflow design, period close configuration. Not as a reviewer at the end. As a participant throughout.
Management Reporter Is Your Primary Financial Reporting Tool—Build It That Way From Day One
Management Reporter—D365 F&O’s native financial reporting tool—is one of the most capable financial statement platforms in the enterprise ERP market. It produces any financial statement format Finance needs, filtered by legal entity, cost center, project, or any financial dimension, in any currency, with any comparison period. Every management report Finance currently produces in Excel from ERP data exports can be built in Management Reporter and produced directly from D365 F&O without an intermediate step.
The organizations that accomplish this are the ones that include the complete Management Reporter report library in the implementation scope as a Finance-validated deliverable—not as a post-go-live aspiration. The income statement, the balance sheet, the departmental P&L, the budget-versus-actual comparison, the entity rollup, the group consolidation report: all built, all validated against the trial balance, all signed off by Finance before go-live.
If the implementation scope you just agreed to does not include the complete Management Reporter library as a named deliverable with Finance sign-off, add it before the first workshop. Post-go-live Management Reporter builds happen, but they happen while Finance is also running the live close, learning the new system, and managing the inevitable post-go-live issues. The report library Finance builds under those conditions is never as good as the one Finance could have built during implementation when the system was still in test mode and the consequences of getting it wrong were zero.
Your Controls Evidence Must Be Built as You Go—Not Assembled Before the Audit
The external auditor who arrives 12 to 18 months after your go-live will ask Finance for evidence of controls that operated throughout the audit year. User access reviews. Approval workflow evidence. SOD conflict remediation. Change Log coverage of sensitive master data. These are not year-end assembly projects. They are month-by-month governance activities that Finance must establish from the first period of live operations.
Before go-live, Finance defines the controls evidence package: which D365 F&O reports constitute the user access review evidence, where the quarterly access review documentation is archived, how the Approval Entries export demonstrates the approval workflow operated, which Change Log tables are configured and what their exports show. Finance establishes these as operational procedures from Month 1, not as audit preparation tasks in Month 14.
The auditor who receives a complete quarterly access review archive, a configured Change Log, and 12 months of approval workflow evidence has what they need. The auditor who discovers at fieldwork that the access reviews were never conducted, the Change Log was never configured, and the approval workflow bypassed one-third of material journal entries has findings that require management responses and remediation plans. The difference between those two outcomes is the governance infrastructure Finance establishes before the first live period closes.
The Period Close Workspace Is How Finance Governs the Close—Configure It Before the First Period Close
D365 F&O’s Period Close workspace can be a very powerful close management tool. Configured correctly—with 30 to 60 specific task-level entries, dependency mapping between tasks, due dates calibrated to your target close timeline, and backup owner assignments for critical-path tasks—it transforms the close from a 12-day tribal knowledge exercise into a 6-day managed workflow with documented task sequences, real-time completion visibility, and measurable performance data for ongoing improvement.
Most implementations do not configure the Period Close workspace before go-live. It gets pushed to Phase 2, and is then sometimes forgotten or is left as a post-go-live Finance activity. Finance goes live, runs the first close without the workspace configured, discovers it takes 12 days, and then tries to build the configuration while also running monthly closes. The Period Close workspace they build under those conditions is typically generic: five high-level phases rather than 40 specific tasks, no dependency mapping, no backup owner assignments. Finance gets status theater instead of close governance.
The configuration is an implementation deliverable. Finance defines the complete close task structure—every D365 F&O batch job, every subledger reconciliation, every accrual journal, every management report review, every sign-off step—before go-live. The implementation partner helps build it in D365 F&O. Finance validates it in a UAT close simulation. The first live close runs on a fully configured Period Close workspace. The performance data from the first live close becomes the baseline for improvement.
The Health Check Is the Annual Governance Ritual That Keeps Finance Honest
D365 F&O’s power is not static. It grows with each release wave, with each Finance capability Finance adopts, and with each process improvement Finance makes based on close performance data. But the gap between what D365 F&O offers and what Finance uses can also grow—if Finance does not actively maintain the configuration, adopt new capabilities, and measure its own performance against the platform’s potential.
The D365 F&O Finance Health Check in Post 53 of this series is the annual ritual Finance uses to measure that gap honestly and build a prioritized improvement plan. Finance scores itself across six domains: foundation, close process, controls, reporting, master data, and platform ownership. The score reveals where Finance is using D365 F&O well and where the configuration and governance have drifted. The improvement plan closes the gap systematically rather than allowing it to widen silently.
Schedule the first health check for 12 months after go-live. Schedule the second for 24 months. Make it an annual Finance calendar event. Share the results with your CFO. Finance that actively measures and improves its D365 F&O governance is Finance that demonstrates it manages the organization’s most significant Finance infrastructure investment as the strategic asset it is.
One More Thing
So far, I’ve written over 50 posts about Finance’s relationship with D365 F&O. Every post was written for the Finance leader who wants to understand D365 F&O deeply enough to configure it well, maintain it correctly, and demand more from it as the organization grows. Every mistake documented was real. Every fix was actionable.
The information is now available to you, before you make the decisions that determine whether your D365 F&O implementation produces the enterprise Finance platform your organization invested in.
The implementation team is assembling. The workshops are on the calendar. Finance’s seat at the table is reserved.
Use it.
Bobbi
D365 Functional Architect · Recovering Controller
Thank you for reading!
If this post helped you solve a real problem, share it with a Finance colleague who is in the middle of an ERP implementation or a post-go-live optimization. If you have a topic that I haven’t covered, please reach out. This platform is always evolving, and there is one more subject worth exploring.
Leave a Reply