TL;DR
In the vendor invoice automation workspace, under Documents not invoiced. It is an accounts payable view, which is why procurement rarely finds it.
*In the vendor invoice automation workspace, in a section called Documents not invoiced. It is an accounts-payable workspace, which is why procurement teams routinely do not know it exists. It gives you the list. It does not give you the reason* — and the reason is the part that costs money.
Where exactly does this live?
Microsoft names the section and what it holds:
"The Documents not invoiced section contains grids that show documents that are awaiting vendor invoices."
The workspace is the vendor invoice automation workspace, reached through accounts payable. That placement is the practical problem: the people who created the open lines sit in procurement and goods-in, and the view that lists them sits in finance.
So the common failure is organisational, not technical. Finance can see a growing list and cannot resolve it. Procurement could resolve it and never sees the list. Nothing in the product is broken; the information and the authority are in different rooms.
What is actually in the grids?
The headline grid is the one most people want:
"The Open purchase orders grid shows all purchase orders that aren't yet fully invoiced. Use the Invoice now button to create a vendor invoice for a purchase order."
*Note Microsoft's wording — "aren't yet fully invoiced".* A partially invoiced order appears here, which is correct and also the source of a lot of confusion — a line can be half-billed and entirely in order.
And there is a product receipts grid, which is the one that matters for accruals: "The Product receipts grid shows purchase receipt transactions that aren't yet fully invoiced."
*The Invoice now action is worth knowing about* because it shortens the usual route. You do not have to leave the workspace to raise the vendor invoice against the order you are looking at.
What else is on this workspace?
A pending-state summary, and it answers a different question:
"The tiles in the Summary of pending invoices section of the My work view give an overview of the state of your vendor invoices. You can see journals that aren't yet posted and invoices that are on hold."
Unposted journals and on-hold invoices are a separate problem from uninvoiced receipts, and they are easy to conflate at month-end. One is "the vendor has not billed us". The other is "the bill is here and stuck inside our own process."
There is also a journals group, and it is conditional. Microsoft: "When the feature is turned on, you also see three tiles grouped together on the workspace in a section called Journals. The tiles are titled Journals, Journals - Assigned to me, and Invoice pool." The feature is Allow vendor invoice recovery, set on the Invoice tab of accounts payable parameters — so if you cannot see these tiles, they are switched off rather than missing.
Invoice pool is the one to check before raising an exception report. An invoice sitting in the pool has arrived and has simply not been registered yet.
The company trap, and Microsoft documents it
This one catches people out, and it is published behaviour.
"The information in the Summary of pending invoices section is for the company that is set as the default company for your sign-in."
So the summary tiles can be showing a different legal entity from the grids you are reading. Microsoft describes the mechanism plainly: you can set a company filter to view another company's information, and "You can then select a tile in the workspace to go the related page in the selected company."
And creation follows the filter, not your sign-in. Microsoft's own example: if you are "signed in to the UMSF company, but the company filter is set to GBSI", then when you create a new record "you create the record in the GBSI company."
### Read that twice before a month-end review The pending summary follows your default company. New records follow the filter. In a multi-entity group, a reviewer can be looking at one entity's tiles while creating documents in another. Check both before you trust a number off this workspace.
What this view will not tell you
Why any particular line is open.
The grids give age, value, vendor and document. They do not distinguish a delivery the vendor has not billed yet from a receipt that was posted twice — and those two need opposite responses. The first needs patience, the second needs cancelling.
That distinction is not in the ledger. It is in the delivery note, the gate log, or the memory of the person who signed for the pallet. The workspace is where you find out that a question exists; it is not where the question gets answered, which is why the shapes have to be worked out separately.
About Cognilium Cognilium builds AI optimization apps for Microsoft Dynamics 365 — companion apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Dynamics is your system of record. Cognilium is your system of intelligence. https://cognilium.ai · https://www.linkedin.com/company/37180269/
Agentic ERP. We build turnkey AI optimization apps for Dynamics 365 — sidecar applications that run in your own Azure tenancy and solve the calculations a standard ERP is not built to compute. Built on Azure OpenAI, Microsoft Fabric and Copilot Studio. We build these on request, against your data and your environment.
More on the boundary between what Copilot does and what you build: Agentic ERP on Dynamics 365.
If finance is reporting a list that procurement never sees, that gap is usually the whole problem. Bring both views to a 15-minute call.
Sources
- Vendor invoice automation workspace · fetched and read in full 2026-10-21
- Automated vendor invoicing processes overview · fetched and read 2026-10-21
Sources and fact-check
| # | § | Claim | Tier | Primary source | Verdict |
|---|---|---|---|---|---|
| 1 | 1 | "The Documents not invoiced section contains grids that show documents that are awaiting vendor invoices" | T1 — verbatim, section name character-exact | vendor-invoices-workspace | PASS |
| 2 | 1 | The placement is the organisational problem — finance sees it, procurement resolves it | T2 — ours, an argument about org design, no figure attached | — | PASS |
| 3 | 2 | "The Open purchase orders grid shows all purchase orders that aren't yet fully invoiced. Use the Invoice now button to create a vendor invoice for a purchase order" | T1 — verbatim | Same page | PASS |
| 4 | 2 | "Its Product receipts grid shows purchase receipt transactions that aren't yet fully invoiced" | T1 — verbatim | Same page | PASS |
| 5 | 3 | "The tiles in the Summary of pending invoices section of the My work view… journals that aren't yet posted and invoices that are on hold" | T1 — verbatim | Same page | PASS |
| 6 | 3 | The three journal tiles — Journals, Journals - Assigned to me, Invoice pool | T1 — verbatim, tile names character-exact including Microsoft's hyphen spacing | Same page | PASS |
| 7 | 3 | Invoice pool is worth checking before raising an exception | T2 — ours, practical advice | — | PASS |
| 8 | 4 | "The information in the Summary of pending invoices section is for the company that is set as the default company for your sign-in" | T1 — verbatim | Same page | PASS |
| 9 | 4 | The UMSF / GBSI example — signed in to one, filter set to another, record created in the filtered company | T1 — verbatim, Microsoft's own example company codes preserved | Same page | PASS |
| 10 | 4 | A reviewer can read one entity's tiles while creating in another | T2 — ours, the consequence of 8 and 9 | — | PASS |
| 11 | 5 | The grids do not distinguish a not-yet-billed delivery from a duplicate receipt | T2 — ours. An absence claim about the view, bounded to the fields the page documents (age, value, vendor, document) and not asserted of every report in the product | — | PASS |
Tier summary: 6 × T1 (all verbatim), 5 × T2 — 0 × T4.
### ⚠️ Claim 11 is an absence and is bounded "The grids give you the list, never the reason" is a claim about this workspace as Microsoft documents it. It is not a claim that no report anywhere in finance and operations distinguishes those cases. The body states what the grids do carry, which is what bounds it.
🔴 No pricing. No rate, currency or cost figure anywhere. Microsoft's example company codes UMSF and GBSI are reproduced as published — they are demo-data entity codes, not customer names.
No figures of ours. No volume, no ageing threshold, no customer, no result.
Share this article
Procure-to-Pay Agent Operations
Topic Cluster
