AI account reconciliation in Dynamics 365: what the agent clears, and the part it hands back

Reconciliation is the month-end grind every finance team knows: match the entries, chase the breaks, explain the differences, before the books can close. It's exactly the shape of work AI should take off a controller's plate — repetitive, rule-driven, high-volume — and Microsoft's Account Reconciliation Agent for Dynamics 365 Finance is built to do just that.

If you're asking "can AI do our reconciliation," the honest answer is: it can do a lot of it, now, natively — and there's a specific part it hands back, which is worth understanding before you decide whether the first-party agent is enough.

What the agent does well

The Account Reconciliation Agent resolves reconciliation exceptions in bulk, and it's getting more capable — enabled by legal entity and module, with limits, notifications and expanded suggestion summaries so a controller can see what it did and why.

The right model is operate by exception: the agent clears the matches and the standard breaks, and surfaces the ones that genuinely need judgement, with a summary of its reasoning. Your close stops being "work through every line" and becomes "review what the agent couldn't settle." For a lot of reconciliations that run close to standard, that is a real, native win — turn it on.

The part it hands back

An exception-clearing agent is excellent at the exceptions it was built for. The ones it hands back tend to cluster in four places, and in a complex estate that's where the month-end time actually goes:

1. Reconciliations that span your customizations. If the break involves a custom entity, an ISV subledger, or logic the agent can't see, it can't settle it — it reasons over standard Finance, and your customization is invisible to it. (Reaching it needs governed MCP Action tools.)
2. Non-standard sources. A reconciliation against a bank format, an external system or a spreadsheet the agent wasn't built to read is a hand-back.
3. Judgement breaks. Differences that need a decision — accept, write off, investigate — based on materiality thresholds and policy that are yours. That decision stays with a person, and the policy behind it has to be codified (as business skills) for the agent to even pre-sort them well.
4. The audit and control layer. Who approved the write-off, segregation of duties on the adjustment, the trail from break to resolution — the controls your auditors will ask about are yours to own, not the agent's. (See agent governance.)

None of this is a knock on the agent. It's the honest 80/20: the first-party agent clears the volume, and the remaining slice — the custom, the non-standard, the judgement, the controls — is where a complex Finance team still needs more than out-of-the-box.

How to close the last gap

The fastest path isn't replacing the Account Reconciliation Agent — it's extending it: let it clear what it clears, and build the specific pieces that let it reach your reconciliations. Your customized subledgers exposed as governed actions, your materiality and write-off policy codified as skills, and the audit trail and approvals your controls require. The agent handles the volume; the build handles the part that used to eat your close.

If month-end still runs long because the reconciliations that matter are the ones the agent hands back, tell us which reconciliations eat your close — the first conversation is about which of them an agent could actually reach, and what it would take.