EDI setup
EDI setup
Setup follows the invoicing pattern: e-document setup, vendors and customers set to exchange electronically, and electronic identifiers on both sides. Item reference or GTIN is recommended, and quantities and delivery dates should be filled.
Area: E-Documents. Status: GA. Developer relevance: low. Airtime: 1 min across 1 video.
Status evidence
- Nothing said about status; launch event convention: generally available unless stated otherwise.
Where they talk about it
- What's new in E-Documents: Overview: 2:58 to 4:04 (called "EDI setup requirements" there)
Quotes
- 3:21 "you will need to use electronic identifiers on both sides" - A setup prerequisite for exchanging documents between buyer and seller.
Caveats mentioned
- Item reference or GTIN is recommended so items match on both sides.
Prerequisites mentioned
- Standard e-document setup
- Vendor and customer set up for electronic exchange
- Electronic identifiers (GLN or VAT registration number)
Documented features match
- Exchange EDI documents - medium confidence (llm). Docs say: Public preview, roadmap id 573305. EDI setup
- Product documentation (partial, the article describes the broader feature or mentions this in passing): Set up e-documents, checked 2026-10-02. Lookup Item Reference: Specify whether to search for items by item reference during import. Lookup Item GTIN: Specify whether to search for items by global trade item number. Note: Documents the invoice-oriented e-document setup the EDI setup builds on; no EDI-specific setup (order types, electronic identifiers on both sides for EDI) is described.
Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale.
Tags: e-documents, edi, setup, admin
Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.