Set up and use E-Documents

Path: Business functionality > Finance > Set up and use E-Documents · tier official · system finance · narrative reviewed (checked by Opus)

Overview

The E-Documents app manages electronic invoices and other business documents in Business Central. It supports localization for multiple countries and can be extended for specific requirements. The overview page is the place to start, followed by the setup page, which covers e-document services, workflows and document sending profiles.

Connectivity has two sides. Connectors to external access points (Pagero, Avalara, Logiq, ExFlow, B2BRouter) are described in one page, and a second page covers installing the E-Document Core app and connector apps from Microsoft Marketplace. A separate page covers connecting to Outlook, SharePoint and OneDrive to import vendor invoices and receipts.

Day-to-day use is split into sales and purchase pages. Sales covers creating and sending e-invoices and credit memos and checking status and logs. Purchase covers receiving, matching and processing incoming documents. A page for developers describes the interfaces that localization apps and ISVs use to add formats and services.

Key points

• Setup covers e-document services, workflows and document sending profiles, with PEPPOL BIS 3.0, Data Exchange formats and the clearance model (page lists version 24.0).
• External connectors listed: Pagero, Avalara, Logiq, ExFlow and B2BRouter, with OAuth 2.0 authentication.
• Endpoint connector setup needs the E-Document Core app plus connector apps from Microsoft Marketplace, then connection setup, GLN configuration, customer e-document setup and workflow configuration.
• Microsoft 365 connectors (Outlook, SharePoint, OneDrive) import vendor invoices and receipts for accounts payable, using E-Document Services and Service Integration V2.
• Sales: create and send e-invoices and credit memos in Peppol formats, and view e-document status and logs.
• Purchase: handles invoices, orders and credit memos, with automatic matching, Copilot purchase order matching, text-to-account mapping, item reference mapping and vendor configuration.
• Extensibility covers document format creation, service integration, async sending, batch processing, response handling and receiving (page lists 2025 release wave 1).

Learn pages

• Connect E-Documents to external access points: Learn how to set up E-Documents in Business Central to send and receive electronic documents with different external access points.
• Connect e-documents to Microsoft 365 applications: Learn how to integrate e-documents with Microsoft 365 applications.
• E-documents overview: Learn about e-documents in Business Central and how they streamline business transactions with automated document management and local compliance features.
• Extending the e-documents functionality: Learn how to extend e-documents functionality with specific requirements.
• Set Up E-documents: Learn how to set up e-documents in Business Central with step-by-step configuration of services, formats, workflows, and document sending profiles.
• Set up the E-Documents connector with external endpoints: This article explains how to set up E-Documents functionality when connected to external endpoints.
• Use e-documents in sales: Learn how to use e-documents functionality that is related to sales.
• Use E-Documents in the purchase process: Learn how to set up vendors and handle purchase invoices, orders, and credit memos using e-documents in Dynamics 365 Business Central.

Videos, posts and code changes

Linked by a Haiku matcher with a grounding quote from the item’s summary (link/topics.ts); machine-generated.

• #10029 [Main]-Import of e-documents with format ZUGfERD & XRECHNUNG fail with error message You cannot insert a purchase line without a purchase header in German localisation (code change): “Import of e-documents with format ZUGfERD & XRECHNUNG fail with error message”
• #10631 Integration/main to releases 29.x 31a860b5 (code change): “enhancements to e-document processing, expense report policy evaluations”
• #10755 Migrate Http Web Request Mgt. callers to native HttpClient (code change): “OData metadata download and the Microsoft 365 E-Document GraphClient”
• #10799 Remove OnPrem scope from Table 1226 “Payment Export Data”.SetSwissExport (code change): “Payment Export Data table is now callable from Cloud extensions”
• #11483 [E-Documents Core] - Linkage & Traceability (code change): “E-Documents module now provides linkage and traceability by adding lookup functions”
• #9578 [E-Documents Core] - Enabling remittance advice export via E-Documents (payment journal + posted payments) (code change): “E-Documents now supports exporting remittance advice from payment journals and posted vendor payments”
• #9646 [Bug]: [DE] XRechnung/ZUGFeRD — no posting-time error when SELLER CONTACT (BG-6) source data is incomplete, producing non-compliant e-invoices (code change): “E-Document posting now validates that seller contact information”
• #9648 [master]-[BE] [PEPPOL] There is a problem between the totals on the invoice printout and the XML PEPPOL with Payment discount (code change): “Fixed discrepancy between invoice printout and PEPPOL XML totals”
• #9749 OIOUBL fixes after schematron update (code change): “OIOUBL export now correctly handles discounts by reporting them with proper VAT categories”
• #9878 Add buyer order reference to ZUGFeRD export (code change): “ZUGFeRD export now includes the buyer order reference”
• What’s new in E-Documents: Overview (2026 release wave 2) (video): “EDI functionality in Business Central; Purchase order EDI document type; Sales order automatic creation from EDI”
• What’s New: E-Documents Connectors (2025 release wave 1) (video): “E-Documents Connectors; connectors; electronic invoicing; integration setup”
• What’s New: E-Documents ZUGFeRD Format (2025 release wave 2) (video): “E-Documents ZUGFeRD Format; zugferd; pdf-a3; germany; invoicing”
• What’s New: E-Documents and Clearance Model (2025 release wave 2) (video): “clearance model; e-documents; regulatory compliance; e-invoicing; workflow”
• What’s New: E-Documents (2024 release wave 2) (video): “e-documents; electronic invoicing; avalara; pagero; b2b; b2g; connectors”
• What’s New: E-Documents Localizations (2025 release wave 1) (video): “e-documents; localizations; peppol; factura; ubl; pdf/a; electronic invoicing”

Business Central pages and reports

The pages, reports and queries this hub’s Learn pages name (ms.search.form, API reference), joined to the code by exact object id (data/index/docs-objects.json); a page shows the table it runs on.

• Page 42 “Sales Order” · on Table 36 “Sales Header”
• Page 43 “Sales Invoice” · on Table 36 “Sales Header”
• Page 50 “Purchase Order” · on Table 38 “Purchase Header”
• Page 51 “Purchase Invoice” · on Table 38 “Purchase Header”
• Page 132 “Posted Sales Invoice” · on Table 112 “Sales Invoice Header”
• Page 138 “Posted Purchase Invoice” · on Table 122 “Purch. Inv. Header”
• Page 359 “Document Sending Profiles” · on Table 60 “Document Sending Profile”
• Page 360 “Document Sending Profile” · on Table 60 “Document Sending Profile”
• Page 6103 “E-Document Services” · on Table 6103 “E-Document Service”
• Page 6121 “E-Document” · on Table 6121 “E-Document”
• Page 6133 “E-Document Service” · on Table 6103 “E-Document Service”
• Page 6167 “E-Doc. Order Line Matching” · captioned “Purchase Order Matching” · on Table 6121 “E-Document”
• Page 9301 “Sales Invoice List” · captioned “Sales Invoices” · on Table 36 “Sales Header”
• Page 9305 “Sales Order List” · captioned “Sales Orders” · on Table 36 “Sales Header”
• Page 9307 “Purchase Order List” · captioned “Purchase Orders” · on Table 38 “Purchase Header”
• Page 9308 “Purchase Invoices” · on Table 38 “Purchase Header”

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.