AI Agents for Dynamics
365 Payables
A third of a typical Dynamics match queue was never an exception. It failed because the logic expects one receipt per invoice.
- Dynamics matches invoice to purchase order and product receipt. The order is always there and the receipt frequently is not, which produces most of the queue.
- Only one match state is a finance decision. The rest sit in the AP queue because that is where invoices land, not because AP can act on them.
- In a worked queue of 214, 75 needed no human decision. They failed because the matcher expects one receipt per invoice, which is not how receiving works.
- Vendor default dimensions populate the analysis without anybody choosing. Purchase order dimensions carry the requester's intent and should win.
- The count of invoice lines whose dimensions exactly match the vendor default is the cheapest coding control in Dynamics and almost nobody reports it.
AI agents for Dynamics 365 Finance accounts payable group the vendor invoice match queue by cause rather than by value, aggregate partial product receipts instead of failing them, and check financial dimensions against the purchase order rather than accepting a vendor default. ChatFin routes each group to the owner who can resolve it and approves nothing.
The queue is smaller than it looks. In a worked month, 44 of 214 unmatched invoices covered several partial deliveries and 31 were price differences already inside tolerance. Neither needed a person. They appeared as exceptions because the matching logic expects one receipt per invoice, and receiving does not work that way.
The product receipt is the leg that breaks the match
Dynamics 365 matches a vendor invoice against the purchase order and the product receipt. The order is always there. The receipt frequently is not, and that single gap produces most of the exception queue.
| Match state | What it means | Who resolves it |
|---|---|---|
| Order and receipt both present | A real price or quantity question | Procurement |
| Order present, no receipt | Goods not booked in | Receiving or the requester |
| Receipt partial across deliveries | Normal, not an exception | Nobody, if the matcher aggregates |
| Order closed early | Nothing to match against | The requester |
| No order at all | Non PO spend | Approval by policy |
Only the first row is a finance decision. The rest are somebody else's, and they sit in the AP queue because that is where invoices land rather than because AP can act on them.
ChatFin groups the queue by match state and routes each group to the owner who can resolve it, rather than returning a longer list to accounts payable. Where ChatFin aggregates partial receipts, a whole class of exception disappears rather than being worked faster.
Financial dimensions on the invoice line
Dynamics carries the analysis in financial dimensions, and a default dimension on the vendor will populate them without anybody choosing. The invoice posts, the total is right, and the dimensional view is wrong.
ChatFin compares dimensions on the invoice line to the purchase order first and flags where they came from a vendor default instead.
A worked exception queue, 214 invoices
214 vendor invoices unmatched at month end. The team works the top thirty by value. Grouped by cause it is six, and two need nobody.
| Cause | Invoices | Value | Owner |
|---|---|---|---|
| No product receipt yet | 81 | 294,000 | Receiving |
| Partial receipts, invoice covers several | 44 | 118,000 | Nobody. Aggregate and match |
| Price within tolerance | 31 | 62,000 | Nobody. A rule already covers it |
| Price outside tolerance | 23 | 187,000 | Procurement, four vendors |
| Purchase order closed early | 19 | 94,000 | The requester |
| Non PO above the policy limit | 16 | 71,000 | Approval by policy |
Seventy five of the 214 need no human decision at all. They are exceptions because the match logic expects one receipt per invoice, which is not how receiving works.
Where this underperforms
Three.
ChatFin reports what share of the queue needs no decision before it reports an automation rate, because a third of a typical queue is not an exception.
Deeper in Dynamics 365 payables
Three use cases sit under this hub, in build and shown rather than linked.
Worked on this page
Vendor follow up for missing invoices · AP inbox automation · Invoice intake and document extraction
Covered as sections here
3 way matching · Financial dimensions · Approval routing · Duplicate detection · Non PO spend
Questions Dynamics 365 payables teams ask first
Why do so many Dynamics invoices fail matching?
Because the product receipt is missing or partial. The purchase order is always there, so the failure is nearly always on the receipt leg. In a worked queue of 214 unmatched invoices, 81 were waiting on goods to be booked in and 44 covered several partial deliveries against one invoice. The second group is not an exception at all if the matcher aggregates receipts, which ChatFin does.
What is the risk with vendor default dimensions?
They populate the analysis without anybody choosing. A vendor supplying two departments has one default and every invoice inherits it, so the invoice posts, the total is right and the dimensional view is wrong. Purchase order dimensions carry the requester's intent and should take precedence. ChatFin flags lines whose dimensions exactly match the vendor default, which is the cheapest coding control available.
Who should the exception queue actually go to?
Mostly not finance. Of six causes in a worked queue, one was procurement, one was receiving, one was the requester, one was policy approval and two needed nobody. Invoices land in AP because that is where invoices land, not because AP can resolve them. ChatFin groups by cause and routes to the owner, which is what moves cycle time rather than processing faster.
214 exceptions, six causes, 75 that needed nobody.
ChatFin aggregates partial product receipts, applies the tolerance rules already configured and names the rule it used, then groups what remains by cause.
Dimensions are checked against the purchase order rather than the vendor default, and approval stays in Dynamics under a named person.
Bring one month of unmatched invoices. The comparison takes an hour.
Book a demoAll images are served from the Pexels content network. No third party product screenshots, vendor logos or licensed media are used on this page.
Bring one month of unmatched invoices.
We will group them by cause through ChatFin and show you what share never needed a person at all.