What's New: Enhanced Purchase Order Matching with Copilot (2025 release wave 1)
Purchase order matching enhancements for e-documents with Copilot in 2025 release wave 1, in public preview. Covers matching more entry types, item references as auto-match criteria, the learn matching rule, and adding invoice lines to a purchase order from the matching page.
- Introduction and Key Enhancements Overview
- Problem: Unmatched Additional Invoice Lines
- Solution: Auto-Matching Capabilities and Line Addition
- Demo: Learning Matching Rules with Item References
- Demo: Auto-Matching and Creating New Lines
- Demo: Creating Purchase Order Lines from Invoice
- Summary and Public Preview Status
Overview
The video explains how Copilot-based matching of inbound electronic invoices to purchase orders is extended. The problem shown is additional invoice lines that stay unmatched. The changes let those lines be matched automatically or added to the purchase order directly from the matching page.
Demos cover learning matching rules through item references, auto-matching on later invoices, and creating purchase order lines from imported invoice lines. The presenter says the feature is still in public preview and that further improvements are planned in later waves based on feedback.
Key points
- Matching support is extended beyond general ledger accounts and items to resources, item charges and other entry types (in preview).
- Extra lines from an inbound electronic invoice, such as a transport cost, can be added to the purchase order from the matching page, without creating them manually. Previously the invoice could not be posted because it could not be partially invoiced.
- Auto-matching previously needed 80% string similarity. Existing item references now also count as auto-matching criteria, without running the LLM.
- The learn matching rule lets users mark matched lines so item references are created in the background for future invoices. It works only for GL accounts and items. For GL accounts it uses text to account mapping, and for other types it does nothing.
- On imported lines, the three-dot menu has a create purchase order line action. Units of measure and cost are filled in automatically, and the quantity can be changed. More complex lines can still be created manually.
- Generated item references are marked as autogenerated from the source e-document, so users can trace them back.
- The feature is in public preview, with more improvements planned for later waves before general availability. The presenter asks for feedback.
Features
| Feature | Status | At | Evidence |
|---|---|---|---|
| Support for All Entry Types | preview | 0:29 | “So currently this is still a public preview because we want to improve in a few more places” (12:20) |
| Automatic Extra Line Addition from Invoice | preview, demoed | 0:41 | “So currently this is still a public preview because we want to improve in a few more places” (12:20) |
| Item References for Auto-Matching | preview, demoed | 1:02 | “So currently this is still a public preview because we want to improve in a few more places” (12:20) |
| Learn Matching Rule Feature | preview, demoed | 3:34 | “So currently this is still a public preview because we want to improve in a few more places” (12:20) |
| Create Purchase Order Line from Invoice | preview, demoed | 9:36 | “So currently this is still a public preview because we want to improve in a few more places” (12:20) |
| Auto-Matching Based on 80% Similarity | status not stated, demoed | 4:54 | |
| Copilot Matching with LLM | status not stated, demoed | 5:08 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
- page 6122 “E-Documents” at 4:19
- page “matching page” at 4:30
- page 5736 “Item References” at 7:05
- page 50 “Purchase Order” at 8:56
Not found in BC28-30: page “matching page”.
Quotes
- 0:29 “entries so earlier we supported only general ledger accounts and items but now you can handle with”
- 0:41 “second is that we now we can include extra lines into a purchase order automatically from inbound invoice just imagine we had”
- 3:34 “We previously work only if we had 80% of string similarity but now we added item references. So if we already have item reference”
- 3:55 “every time when LLM finds some similarity some match you can mark the system will automatically create item reference for future usage.”
- 6:33 “that means we are making an item reference in the background and in the future we can automatically match this”
- 9:36 “we have now to do that. Basically on the imported lines you can now click the three dots and we have this create purchase”
- 10:45 “Now, this only works for GL accounts and items. So, GL accounts, we use the text to account mapping if you’re familiar with that.”
- 12:03 “It doesn’t mean that this is everything. Uh this is what we try to to improve based on your feedback on your usage of”
- 12:20 “So currently this is still a public preview because we want to improve in a few more places and please if you know any”
Disclaimers in the video
- 12:03 coming-later: this is what we try to to improve based on your feedback on your usage of this copilot. Idea is to continue improvements in next waves before we finally enable this as a general ability
- 12:20 preview: currently this is still a public preview because we want to improve in a few more places
Presenters (as heard): Alexander, Andre.
