Quick answer: D365 produces clean financial data. It does not produce the narrative-rich, branded board pack your directors actually read. Closing that last mile takes purpose-built automation not another Excel template.
Your D365 Went Live. Your Board Pack Still Takes Three Days. Let’s Talk About That.
Half of finance teams need more than five business days to close the books. One in four take more than seven. The industry target is three to five (Ledge, 2025).
If you just spent eighteen months and seven figures implementing Dynamics 365 Finance, that statistic is going to sting.
You bought the cloud ERP. You ran the change management. You survived the go-live. The data flows. The ledgers balance. And then month-end arrives and you are still, somehow, sitting in Excel on a Saturday morning rebuilding a board pack from scratch.
This is the part nobody warned you about.
D365 does exactly what the sales deck promised. It processes transactions, maintains the ledger, and spits out trial balances, P&Ls, and balance sheets on demand. Your board does not care about any of that. Your board wants variance commentary. Trend charts. Multi-entity consolidations that actually reconcile. A narrative explaining what happened, why it happened, and what you are going to do about it.
The gap between “ERP output” and “board-ready document” is where finance controllers lose their weekends. And it is wider than anything the implementation partner disclosed.
Why Dynamics 365 Reporting Falls Short of Board-Ready Output
D365 Financial Reporting generates data. Not documents.
The Financial Reporter module is structured, reliable, and auditable inside the ERP. It also cannot produce a branded, narrative-driven board pack that a committee or investor group expects. Users cannot even export to Excel without manually selecting export options and detail levels every single time (Microsoft Dynamics 365 Community, 2025).
So the board pack assembly happens outside the ERP. That is where the trouble starts.
Controllers export. Paste into templates. Rebuild charts. Hand-write variance commentary. Manually consolidate entity by entity. The audit trail D365 so carefully maintains internally breaks the moment data crosses the Excel boundary. Microsoft’s own documentation recommends exporting to PDF “if you require an immutable audit copy,” which is a polite way of admitting the Excel workflow introduces lineage risk you cannot defend to auditors (Microsoft, 2025).
For multi-entity groups it gets worse. Intercompany eliminations, FX translation, segment consolidation, each one adds manual steps. D365 gives you raw consolidated data. Getting it to something a non-executive director can read and act on is all human effort.
Why 94% of Finance Teams Still Live in Excel, Even on Cloud ERP
Here is the stat that should make every ERP vendor uncomfortable.
94% of finance teams still use Excel for close activities. Half of them cite it as the main reason their close runs slow (Ledge, 2025). These are not teams on twenty-year-old on-prem systems. These are teams running D365, NetSuite, Oracle Cloud, SAP S/4HANA.
Excel is not sticking around because controllers lack better tools. It is sticking around because the last mile of financial reporting, the formatting, commentary, charts, cross-references, the storytelling, has no native home inside any ERP ever built. The spreadsheet becomes the bridge by default.
The downstream damage is predictable. Version control breaks the moment two people touch the same template. Formula errors surface at exactly the wrong moment, usually in front of the audit committee. And the tie-out between what D365 says and what the final pack shows becomes a monthly manual exercise.
The 94% of CFOs who report regretting their ERP implementation tend to point at exactly this dynamic (Accountex, 2025). The system works. The reporting automation stack around it never actually got built.
Does Microsoft Copilot Close the D365 Board Pack Gap?
Short answer: no.
Longer answer: Microsoft is investing serious money in AI for D365. Copilot for Finance has been generally available since October 2025 and targets in-ERP workflow automation, accelerated reconciliations, automated invoice processing, and natural language queries against ledger data. Microsoft claims a 50% reduction in invoice processing time and 25 to 30% reduction in close time for fully deployed orgs (Microsoft, 2025).
Those are real wins for the operational close.
None of them touch the board pack.
Copilot optimises what happens inside D365. The variance commentary, the management narrative, the branded formatting, the multi-section document tying financial results to strategic context, all of that lives downstream and stays manual.
Gartner expects embedded AI in cloud ERP to drive 30% faster financial close by 2028 (CPA Practice Advisor, 2026). They also warn that 70% of organisations will not have AI-ready ERP data by 2027 (Gartner, 2025). Translation: the gap between what AI can theoretically do inside your ERP and what your team can actually do is going to persist for years.
The 2026 Wave 1 release improves Financial Reporting in Business Central with better layouts, automated distribution, and multi-report consolidation. Nice to have. Still not a board pack.
What Actually Takes the Longest in a D365 Board Pack
It is not data extraction. It is variance commentary.
D365 can generate budget-versus-actual figures in seconds. That is not the bottleneck. The bottleneck is explaining them.
Your board does not want to be told OPEX is 12% over budget. They want to know why it is over budget, whether it is timing or structural, and what management is doing about it.
That commentary is entirely manual. The controller cross-references operational data, calls department heads, and synthesises context no ERP captures natively. Knowing how to present variance analysis to a board is its own discipline, and D365 does not help with any of it.
Then come the dependencies. 56% of finance teams cite regional or departmental dependencies as their top close obstacle (Ledge, 2025). The D365 data may be ready on day one. Waiting on context from sales, HR, and product pushes the pack to day five or later. Every time.
How to Automate Dynamics 365 Reporting for Board Packs
The teams that have compressed their cycle to two or three days did not do it by getting better at Excel.
They did it by removing the manual steps between ERP output and finished document. Full stop.
With D365 Finance properly configured and paired with purpose-built reporting automation, group close can drop to two days and the board pack can land on day three, versus the 10 to 14 days typical for multi-entity consolidation (Encore Business Solutions, 2025). A Forrester Total Economic Impact study put D365 Finance ROI at up to 122% over three years when paired with proper automation (Forrester, 2025).
The pattern that actually works:
- Connect directly to ERP data. APIs or validated pipelines. No manual exports, no copy-paste, no “final_final_v3.xlsx.”
- Automate the mechanical work. Formatting, chart generation, variance calculations, multi-entity consolidation. All of it.
- Keep the controller in control of the story. Overrides, strategic context, the narrative layer. That stays human because it has to.
This is the same shift happening across board pack automation for NetSuite and D365 shops. Nothing revolutionary. Just overdue.
Where Claryx.ai Fits
Claryx.ai does not try to be a better Excel connector or another module inside D365.
We deploy AI agents that connect to your accounting or ERP data and generate the financial core of board packs, investor updates, and management reports. The agents handle variance analysis, consolidation formatting, and structured commentary. The finance controller reviews the reasoning, overrides where business judgment says otherwise, and writes the strategic narrative only they can write.
Every output traces back to source data through governed pipelines. The audit trail that breaks the moment you export to Excel stays intact.
For controllers stuck in the last-mile gap between D365 and the board pack, the workflow shifts from “build from scratch” to “review and approve.”
That is the difference between a three-day close and a ten-day close.
The Bottom Line for Mid-Market Controllers
The gap between ERP data and board-ready output is not a technology failure. D365 does what it was designed to do.
The problem is that board-level financial reporting requires a type of output no ERP was ever built to produce: narrative-rich, visually polished, contextually informed documents that combine numbers with judgment.
Closing the gap means accepting three things:
- Your ERP is a data engine, not a document engine. That is fine. Stop asking it to be both.
- Excel is a symptom, not the cause. Ripping it out without replacing the workflow just breaks things.
- AI can automate the mechanical portion of board pack assembly. It cannot replace the controller’s judgment, interpretation, or narrative. Anyone telling you otherwise has never sat in a board meeting.
The teams reporting in two days instead of ten have stopped trying to stretch D365 into something it is not. They built the bridge between structured ERP data and the finished document the board actually reads.
Everyone else is still in Excel.
FAQ
Why does Dynamics 365 reporting still require Excel? D365 generates structured data, not formatted board-ready documents. The last mile, covering variance commentary, branded formatting, and narrative, has no native home in the ERP, so Excel fills the gap by default.
Can Microsoft Copilot for Finance replace manual board pack work? No. Copilot accelerates in-ERP workflows like reconciliation and invoice processing. Board pack assembly, variance commentary, and branded formatting sit outside its scope.
How long should a monthly close take with D365 Finance? The industry target is three to five business days. Teams with proper reporting automation layered on top of D365 routinely hit day two or three for the close and day three for the board pack.
What is the biggest bottleneck in D365 board pack preparation? Variance commentary. The numbers come from D365 in seconds. Explaining them (timing versus structural, root cause, management response) takes days.
Does D365 maintain the audit trail when data moves to Excel? No. D365 maintains lineage internally, but the trail breaks the moment data is exported. Microsoft’s own guidance recommends PDF exports for immutable audit copies, which does not solve the board pack problem.
References
Accountex. (2025). CFO survey: ERP implementation regret and reporting automation gaps. Accountex Report. https://www.accountex.com/
CPA Practice Advisor. (2026, January). Gartner forecasts: Embedded AI in cloud ERP to drive faster financial close by 2028. CPA Practice Advisor. https://www.cpapracticeadvisor.com/
Encore Business Solutions. (2025). Multi-entity consolidation benchmarks for Microsoft Dynamics 365 Finance. Encore Business Solutions. https://www.encorebusiness.com/
Forrester Research. (2025). The Total Economic Impact™ of Microsoft Dynamics 365 Finance. Forrester Consulting. https://www.microsoft.com/en-us/dynamics-365/
Gartner. (2025). Predicts 2025: AI readiness in cloud ERP platforms. Gartner Research. https://www.gartner.com/
Ledge. (2025). The state of the financial close: Benchmarks and bottlenecks. Ledge. https://www.ledge.io/
Microsoft. (2025, October). Copilot for Finance in Dynamics 365: General availability and performance benchmarks. Microsoft Learn. https://learn.microsoft.com/en-us/dynamics365/
Microsoft Dynamics 365 Community. (2025). Financial Reporting: Export options and user workflows [Community forum discussion]. Microsoft Dynamics 365 Community. https://community.dynamics.com/
