In brief
Microsoft has replaced the old SSRS reconciliation reports with an Account reconciliation workspace (from D365 Finance 10.0.44) that reconciles the general ledger against AP, AR, tax and bank subledgers in the background, and an Account Reconciliation Agent (production-ready preview) that recommends the fix for each exception. The agent suggests, a human accepts, and every action is logged. It runs on Copilot Studio under its own agent identity — so pilot it in a test environment with proper governance before it goes anywhere near production.
For years, account reconciliation in Dynamics 365 Finance meant the same ritual. Run an SSRS report. Export it. Scroll until you found the line that didn’t tie out. Then start the detective work, usually on day three of close, usually after someone in the board pack had already asked why the numbers moved.
That era is ending. Microsoft has shipped a new Account reconciliation workspace and an Account Reconciliation Agent that sits on top of it. Microsoft’s FastTrack team has a TechTalk walking through the setup and a live demo, and it’s worth your time if you own the close.
Here’s the honest version of what it is, what it does today, and what you need in place before you switch it on.
The old way was reactive by design
The SSRS reconciliation reports did one job: they told you, after the fact, where the general ledger and the subledgers disagreed. You ran them, you read them, you reacted.
That’s the problem. A report is a snapshot of a mess that already happened. By the time you’re reading it, the transaction is a week old, the person who posted it has moved on, and you’re reconstructing intent from a voucher number. Most finance teams I work with don’t have a reconciliation problem. They have a timing problem. They find the breaks too late to fix them calmly.
What changed: from report to workspace
The new Account reconciliation feature, available from Dynamics 365 Finance version 10.0.44, reconciles your general ledger against the accounts payable, accounts receivable, tax, and bank subledgers. It runs in the background on a schedule you control. By default the process automation runs every six hours, and you can tune that up or down depending on how hard your team leans on the workspace.
Instead of a report, you get a live workspace. Tiles at the top show open exceptions for the period, addressed exceptions, transactions that reconciled automatically, and agent-recommended actions. The grid below breaks everything down by module and legal entity. Red means there are exceptions to clear. Green means Fully reconciled. When a period is closed and fully reconciled, it captures a snapshot so you have a defensible record of what tied out and how.
The workspace handles three exception types, and the available actions change depending on which one you’re looking at:
- In subledger, not in ledger — create a journal entry, link transactions, or accept without change.
- In ledger, not in subledger — reverse the GL voucher, link transactions, accept without change, or create an adjusting journal entry.
- Amount mismatch — accept without change, or create an adjusting journal entry.
Version 10.0.46 sharpened the experience further: you can reverse straight from the workspace, the linking flow improved, and creating a journal entry now opens a slider rather than throwing you back to the original transaction page. Small changes. They add up over a close.
Where the agent comes in
The workspace already saves you time. The Account Reconciliation Agent is the part that changes the shape of the work.
When an exception is raised, the agent evaluates it and recommends the action it thinks you should take. For a voucher amount mismatch, it might recommend Create journal entry, and you either accept that or pick from the other available actions. Today the agent reasons over two exception types: voucher amount mismatch and pending accounting transferred to the general ledger. That’s a deliberately narrow start, and I’d rather Microsoft ship a narrow agent that’s right than a broad one that guesses.
Two things matter more than the recommendations themselves.
First, you stay in control. The agent suggests. A human accepts. Every addressed exception can be undone, which moves it straight back to the open list so you can rework it. Nothing posts behind your back.
Second, everything is logged. The Activity pane shows a timeline where agent actions appear as “Fix suggested by agent,” followed by the “Reconciled” entry when the break is cleared. For anyone who has ever been asked by an auditor “who cleared this and why,” that audit trail is the quiet headline of the whole release.
One caveat worth knowing: the plain-language summary of the suggested action currently renders only when the user language is set to EN-US. Other languages still get the recommended action, just not the narrative summary.
The bit most people will skip: this is an agent, and agents need governance
Here’s where finance and IT have to talk to each other, because the Account Reconciliation Agent isn’t a feature flag you flip and forget. It’s a real agent running on Power Platform, and it follows the same rules every agent should.
Under the hood it runs on Microsoft Copilot Studio and a set of Power Automate flows, and it taps the new Dynamics 365 ERP Model Context Protocol to read and act on finance data. The agent runs under its own dedicated agent identity user with explicitly assigned security roles, in both Dataverse and Finance. That’s least privilege done properly. If you’re letting an agent touch the ledger, it should have its own identity, its own roles, and its own audit trail, not a borrowed admin account.
This is the part I’d want every CFO and CIO aligned on before go-live. The agent is useful. It’s also a new actor inside your financial controls, and it needs to be governed like one.
What you need before you switch it on
The agent is a production ready preview today, and the documentation is prerelease and subject to change. Right now Microsoft activates it for you while they finish work on configuration flexibility and predictable credit consumption, so there’s a request form in the loop. Treat this as something to pilot in a test environment, not flip on in production this quarter.
When you’re ready, here’s the short version of the prerequisites from the setup and configuration guide:
- Dynamics 365 Finance 10.0.44 or later (10.0.47 or later if you want the ERP Model Context Protocol capabilities).
- Turn on the Immersive Home, Agent management, and (Production ready preview) Account reconciliation agent features. The ERP MCP server feature is optional.
- Up-to-date Power Platform packages: Copilot for finance and operations apps (1.0.3048.2+) and Copilot in Microsoft Dynamics 365 Finance (1.0.3049.1+).
- A dedicated agent identity user with a licence that allows premium connectors, plus the right security roles. In Dataverse: Finance and Operations basic user, the Account reconciliation agent role, and Environment maker. In Finance: Account reconciliation agent and System user.
- Deploy either through the new Agent deployment wizard in the Copilot Hub in Power Platform admin centre, or manually by creating the Dataverse, Copilot Studio, and Fin & Ops Apps connections and activating the flows.
One practical tip that isn’t in the headline: set the reconciliation start date sensibly. If you’ve already reconciled through August with your old process, set the start date to 1 September so the automation only evaluates the periods you haven’t closed. Don’t make it reprocess history it doesn’t need to.
The takeaway
A reconciliation report tells you what already broke. An agent that watches the workspace, flags the break, recommends the fix, logs every move, and hands you the final decision is a different operating model. That’s the move from a reactive close to a continuous one.
It’s early. It’s a preview. It handles a narrow set of exceptions today and Microsoft is still tuning the consumption model. But the direction is clear, and the teams that pilot this now, with proper agent governance from day one, will be the ones running a calm close while everyone else is still exporting SSRS reports on day three.
Your ledger is only as good as the controls behind it. This is a chance to make those controls proactive.
Resources
- Account Reconciliation Agent (production ready preview) — Microsoft Learn
- Set up and configure the Account reconciliation agent (production ready preview) — Microsoft Learn
- Account reconciliation (workspace overview) — Microsoft Learn
- Dynamics 365 Account Reconciliation Agent v1 — FastTrack TechTalk
- Transforming Financial Close in D365 F&O — podcast session (LinkedIn)