Dynamics 365 Finance & Supply Chain Management · agent · accounts payable

The invoice nobody typed. Checked, matched, waiting for you.

The AP Invoice Agent reads vendor invoices out of the accounts-payable inbox, checks each one against what is already in Dynamics 365, and enters it as a pending invoice created from the purchase order — so Dynamics 365's own three-way match runs on every line, against the goods receipt. It never posts and it never pays: accounts payable reviews, decides on a Microsoft Teams card, and posts. Built and demonstrated on request against your own environment.

Status: built, demonstrated on request. No customer is running it today, and this page says so where it matters.

What happens today

What accounts payable does with an invoice today

Vendors email invoices to accounts payable as PDFs, as scans, and as photographs taken on a phone. Somebody prints them and types them into Dynamics 365 by hand.

In a real buyer conversation the approver named three things, in this order: the manual data entry, the risk of paying the same bill twice, and the work of checking each invoice against the purchase order and the goods receipt.

None of those is a technology problem on its own. Together they are why an invoice sits for days before anyone can pay it, and why the duplicate that does slip through is found by a vendor statement rather than by a control.

The room

Who asks for this, and what they ask about

Three people in the same building, with three different first questions. The agent has to answer all three or it does not get bought.

AP managers

Less keying, fewer errors, and a short list of the invoices that genuinely need a human eye rather than a queue of everything.

CFO and controller

No double payments, a trail that survives an audit, and people still approving what gets posted.

CPO and procurement leads

Every invoice checked against the purchase order and against what was actually received, not just against itself.

Best fit: distributors and manufacturers on Dynamics 365 Finance & Supply Chain Management with a high volume of purchase-order invoices.

The mechanism

From the inbox to a pending invoice, without typing

Six steps. The order matters: the duplicate check happens before anything is created, so a duplicate never exists in Dynamics 365 even briefly.

01

A vendor emails the invoice

To the accounts-payable inbox, as a PDF, a scanned PDF or a photograph. Logos and email-signature images are ignored rather than read as content.

02

The agent reads it

Vendor, invoice number, date, purchase order, lines and amounts — from the vendor's own layout, not from a template we asked them to use.

03

It checks for a duplicate first

Before anything is created, it looks in Dynamics 365 for the same invoice number, and for a look-alike on the same purchase order with a different number.

04

It creates the invoice from the purchase order

So the goods receipt is linked and Dynamics 365's own three-way match runs on every line, on quantity and on price. Standard processing, not a side table.

05

It saves it as pending

Pending, never posted and never paid. Accounts payable reviews and posts exactly as they do today.

06

A Teams card says what happened

One card per invoice. Where a decision is needed the card carries the buttons, and the decision records who made it.

Time from the email arriving to the Teams card appearing: about three minutes, with no typing. Measured in testing in a Dynamics 365 demo company in November 2026 — a demo-environment measurement, not a customer result.

Tested, case by case

The seven cases it was tested against

All of these were run in November 2026 in a Dynamics 365 demo company, across three vendors with different invoice layouts and United States date formats. Scanned PDFs and phone photographs were read as well as ordinary PDFs.

The caseWhat the agent doesThe cardWhy it matters
A new invoiceEntered as pending, linked to its goods receipt, three-way match passed on every lineGreen — invoice enteredNo typing; ready for accounts payable to review and post
The same invoice sent again, as a photo instead of a PDFBlocked. Nothing is entered, and there is no override button on the cardRed — duplicate blockedThe same bill cannot be paid twice
A look-alike: different number, same vendor, same PO, same line, same amountNothing entered. The card shows the evidence — that both together would bill twice what was received — and a person decidesAmber — possible duplicate, your decisionCatches the duplicate an invoice-number check cannot see
A second part-invoice on the same PO, after a split deliveryShows what is already billed against what has been received, and enters it against its own receipt once accounts payable confirmsAmber, then blue — approved by APPartial deliveries work, and the approval is recorded
A multi-line invoice in the vendor's own layout, with no Dynamics item numbers on itEvery line matched to the purchase order by description, and every line three-way matchedGreenWorks on real vendor invoices, not only tidy templates
The vendor bills more than was receivedEnters only the quantity that was actually received, and flags the remainder for a personGreen, with a noteNothing is paid for goods that have not arrived
Not an invoice, unreadable, or the PO cannot be foundNothing is entered, and the card explains whyAmber — needs attentionNothing fails silently
Beyond the standard check

What it does that the standard behaviour does not

It catches the duplicates a number check misses

Dynamics 365 checks for a repeated invoice number. The agent also catches a look-alike with a different number but the same vendor, purchase order, line and amount — and the same invoice sent again in a different format, such as a photograph of a PDF it has already seen.

People stay in control

Invoices are saved as pending. A person reviews and posts. Duplicate decisions are made by a person, on the Teams card, and the card records who decided.

It reads photographs and scans

Not only clean PDFs. A phone photograph of a paper invoice is read the same way, which is what the inbox actually contains.

It leaves an audit trail

Every card records what happened, and every decision records who made it. The trail is the by-product of the work, not a report somebody has to assemble afterwards.

It changes nothing in Dynamics 365

It does not alter purchase orders, receipts or system setup. It uses standard Dynamics 365 processing, and everything is logged.

Where it stops

Where it stops, on purpose

An agent in accounts payable is a privileged thing. These are the limits it is built with, not settings somebody could turn off.

It never posts and never pays
The invoice is saved as pending. Posting is a person's action, in the same screen they use today.
It sees what the user's role sees
The agent operates inside the Dynamics 365 security role of the user it runs as. It cannot read or do anything that role could not.
It runs in your own Microsoft environment
The data stays with you. Processing is standard and logged.
Purchase-order invoices only
An invoice with no purchase order behind it is not its job today.
Nothing received means nothing entered
If no part of the order has been received, the agent enters nothing and raises a needs-attention card. Holding the invoice until the warehouse confirms receipt is in development and works in testing.
Status, stated exactly

Where it stands today, exactly

We publish a status against everything we show, because “we do that” is the sentence that wastes a buyer's quarter.

Built, demonstrated on request

Reading the invoice, the duplicate and look-alike checks, creation from the purchase order, the three-way match and the Teams card

Runs today against a Dynamics 365 demo company, across the seven cases above and three vendor layouts. A live run on your own sandbox is the next step, not a different product.

In development

Holding an invoice until the warehouse confirms the receipt

Works in testing. Named as roadmap until it has run outside testing.

Blueprint

Invoices with no purchase order behind them

Designed; nothing built. It is a different matching problem and it is honest to say so.

No customer is running this today, and we do not imply one is. What exists is the software and a demonstration against your own environment.

Microsoft documents it · we implement it

The Dynamics 365 behaviour this agent is built on

Every step above uses a documented Dynamics 365 mechanism rather than a side system. Microsoft's pages say how each one behaves; what they do not cover is what shipping it against a live accounts-payable process involves.

01vendor invoices

What Microsoft documents
An invoice that cannot be matched is held in accounts payable rather than paid.Vendor invoices overview
What implementing it involves
Held invoices are where the cost of the skipped step finally becomes visible, usually weeks later and to a team that did not cause it. The accrual for goods received and not invoiced is missing too, so the month closes understated — which is why this reads as a procurement nuisance and lands as an audit finding.

02three-way matching

What Microsoft documents
Three-way matching compares the invoice quantity against the quantity on the matched product receipt, and a mismatch raises a matching error.Three-way matching policies
What implementing it involves
The match is why a missing receipt is a finance problem rather than a paperwork one. No receipt means no match, the invoice holds, and the supplier is unpaid for a reason nobody in accounts payable can fix from their own desk. Services usually run two-way, order against invoice, because nothing is received — and mixing the two policies on one vendor is a common source of stuck invoices.

03product receipts

What Microsoft documents
A product receipt is how a delivery against a purchase order is recorded, and posting it moves the line to received.Product receipt against purchase orders
What implementing it involves
This is the step that gets skipped, and the reason is organisational rather than technical: the person who physically took the delivery often has no reason to open the ERP, and sometimes no licence for it. Any fix that assumes they will log in has already failed. The posting has to happen where that person already is.

04purchase orders in Supply Chain Management

What Microsoft documents
A purchase order carries a header and one line per item, each line with its own ordered quantity, received quantity and dates.Purchase order overview
What implementing it involves
Per line is the whole difficulty. One line can be complete while its neighbour is three weeks late, so anything that chases "an order" chases the wrong unit. Ordered minus received is the deliver remainder, and a partial delivery leaves part of a line open — which is exactly the case hand-built reports get wrong.

05Azure AI Document Intelligence

What Microsoft documents
Document Intelligence extracts text, key-value pairs, tables and structure from documents.Azure Document Intelligence
What implementing it involves
Extraction is solved well enough to stop being the interesting problem. What a legal or finance team needs next is judgement against their own position — this clause versus the one their counsel accepts — and that is a playbook the customer owns and a model does not.

06Adaptive Cards in Teams

What Microsoft documents
Adaptive Cards are the structured, interactive message format for Teams, carrying inputs and submit actions.Card types in Teams
What implementing it involves
A card is the right place to put a decision because it arrives where the person is and it carries the numbers already filled in. The design constraint is that it must be answerable in one pass by somebody holding a phone in a warehouse — which rules out most of what a form designer would put on it.

07role-based security in finance and operations

What Microsoft documents
Access in finance and operations apps is granted through roles, duties and privileges rather than per-user permissions.Role-based security
What implementing it involves
The model is sound and almost every estate has drifted from it — roles accreted over years of go-lives, with segregation-of-duties conflicts nobody has looked at since. An agent makes that drift material, because it will exercise every permission it has been given, consistently, at machine speed.
Asked before every demo

The questions accounts payable asks first

Does it post or pay invoices?
No. It saves them as pending. Your accounts-payable team reviews and posts exactly as they do today, in the same screen.
Dynamics 365 already checks for duplicate invoices. Why would we need this?
Dynamics 365 checks whether the invoice number has been used before. The agent also catches the look-alike that carries a different number but the same vendor, purchase order, line and amount, and the same invoice sent again in a different format — a photograph of a PDF it has already read, for instance. Those are the ones that reach a payment run.
Can it read photographs and scans, or only proper PDFs?
Scanned PDFs and phone photographs are read as well as ordinary PDFs. Logos and email-signature images are ignored rather than treated as content.
What happens if the goods have not been received yet?
If nothing has been received, the agent enters nothing and raises a needs-attention card explaining why. If part has been received, it enters only that part and flags the rest. Holding the invoice until the warehouse confirms receipt is in development and works in testing.
What if the vendor bills more than we received?
It enters only the quantity that was received and flags the difference on the Teams card for a person to settle with the vendor.
What about invoices that have no purchase order?
Not today. The agent works with purchase-order invoices. Non-PO invoices are a different matching problem, and we would rather say so than imply coverage we have not built.
Is our data secure?
It runs in your own Microsoft environment, so the data stays with you. The agent can only see and do what the Dynamics 365 security role it runs as allows, and all processing is standard and logged.
Does it change our Dynamics 365 setup?
No. It does not change purchase orders, receipts or configuration. It uses the standard invoice-from-purchase-order path, which is why Dynamics 365's own three-way match runs on every line.
Who approves an exception?
Your accounts-payable team, by pressing a button on the Teams card. The card records who decided and when, so the exception has an owner rather than a history of emails.
Has this run for a customer?
No, and we will not pretend otherwise. It is built, and it is demonstrated on request against a Dynamics 365 demo company or a sandbox copy of your own environment. Every claim on this page is about what the software does, not about who is using it.

Bring one week of your AP inbox

A recorded run against a demo company first, then a sandbox copy of your own Finance & Supply Chain Management environment, your own vendors' layouts and your own purchase orders. If the duplicates and the keying are not where your accounts-payable week goes, we will say so.

AI in Dynamics 365

Talk to a Dynamics engineer

Schedule a call