Dynamics 365 guides
Dynamics 365Peppol BIS 3.0

Peppol BIS 3.0 in Dynamics 365

Dynamics 365 Finance uses the Electronic Invoicing add-in (available via Microsoft Globalization Studio) for Peppol. This guide covers the complete setup path—from enabling features in Lifecycle Services (LCS) to configuring Pagero or other Access Points, with specific focus on the ProfileID configuration that causes most rejections.

Prerequisites

  • Dynamics 365 Finance version 10.0.29 or later
  • Electronic Invoicing add-in license (included in Finance or separate)
  • Azure Key Vault configured for certificate storage (for Peppol AS4)
  • Peppol Access Point subscription (Pagero has native integration, others via API)
  • Company and customers in countries with Peppol support

Step-by-Step Setup

1

Enable Electronic Invoicing in Feature Management and LCS

Dynamics 365 Finance → Workspaces → Feature management → search "Electronic invoicing integration" → Enable. Then: Lifecycle Services (LCS) → Environment details → Maintain → Enable Electronic Invoicing. This provisions the Azure-based e-invoicing service. Allow 10-15 minutes for provisioning.

2

Import Peppol BIS 3.0 configuration from Global Repository

Workspaces → Globalization Studio → Electronic document configurations → Import from Global repository. Select "Peppol BIS Billing 3.0 (NL)" or your country variant. This imports the ER format with ProfileID and CustomizationID already set. Verify ProfileID = "urn:fdc:peppol.eu:2017:poacc:billing:01:1.0" in format designer.

3

Configure your company Peppol Participant ID

Organization administration → Organizations → Legal entities → select your company → Registration IDs tab. Add registration type "Peppol Endpoint" with your participant ID. Format: schemeID:identifier (e.g., "0106:12345678" for NL KVK). This maps to AccountingSupplierParty/EndpointID in the UBL output.

4

Set up customer Peppol IDs and Document Sending Profiles

Accounts receivable → Customers → All customers → select customer → Registration IDs. Add "Peppol Endpoint" with customer's participant ID. Then: Sales and marketing → Setup → Document sending profiles → create profile with "Electronic document: Peppol BIS Invoice" format. Assign profile to customer.

5

Connect Access Point: Pagero or third-party via Electronic invoicing setup

Workspaces → Electronic invoicing → Setup → Service environments → create environment. For Pagero: use built-in connector, enter Pagero customer ID and API credentials. For others: configure custom integration via Azure Logic Apps or direct API. Test by sending to your own Peppol ID first.

Common Dynamics 365 Errors

PEPPOL-EN16931-R001Missing Business Process
Full guide →

Why this happens in Dynamics 365

Dynamics 365 Electronic Invoicing configurations from Global repository may not include the correct ProfileID. Custom configurations created before 2022 often miss this mandatory field.

How to fix it

In Electronic reporting > Configurations > format design, add ProfileID element with value urn:fdc:peppol.eu:2017:poacc:billing:01:1.0 to the UBL header.

PEPPOL-EN16931-R010Invalid Buyer Endpoint Scheme ID
Full guide →

Why this happens in Dynamics 365

Customer Peppol IDs imported from external CRM or CSV uploads often lack the schemeID attribute. Dynamics stores the number but not the scheme context.

How to fix it

Update customer master with proper schemeID: Accounts receivable > Customers > E-Document > set EndpointID scheme (0088 for GLN, 9925 for BE VAT, etc.).

BR-CO-18Invoice Total Rounding
Full guide →

Why this happens in Dynamics 365

Multi-currency projects converted to EUR invoices may have minor rounding discrepancies. Also occurs with complex discount structures applied at both line and document level.

How to fix it

Review currency conversion settings in General ledger > Currencies. Use "Round by" setting of 0.01 for EUR transactions.

BR-16Duplicate Line Identifiers
Full guide →

Why this happens in Dynamics 365

Copying sales orders or using templates in Dynamics can create invoices with duplicate line IDs. The Electronic document format may not regenerate unique IDs.

How to fix it

In format design, ensure LineID element uses auto-increment or line number field, not copied data.

Pre-Export Checklist for Dynamics 365

Before exporting Peppol BIS 3.0 from Dynamics 365, verify these items:

  • 1
    Verify customer Peppol participant ID has correct schemeID attribute
  • 2
    Confirm Electronic invoicing feature is enabled in Feature management
  • 3
    Check ProfileID is set in format configuration
  • 4
    Ensure document sending profile is assigned to customer
  • 5
    Test Access Point connectivity in Electronic document settings
  • 6
    Verify line IDs are unique (no duplicates from copied orders)

Testing Your Setup

Use Dynamics 365 test company or sandbox environment. Create a test sales invoice and export using the Peppol format to verify output.

💡 Microsoft provides Peppol test scenarios in Dynamics 365 documentation. Search "Electronic invoicing testing" in Microsoft Learn.

Validate Your Output

Export your invoice XML from Dynamics 365 and validate with Invoice Navigator Peppol validator before transmission.

Validate Peppol BIS 3.0

FAQ

Which Access Points work with Dynamics 365?
Dynamics 365 integrates with multiple Access Points including Pagero (native integration), Basware, and other certified Peppol providers. Check Microsoft AppSource for certified connectors.
Can Business Central send Peppol invoices?
Yes, Business Central has built-in Peppol BIS 3.0 support. Configure the electronic document format and sending profile in Setup.

Related Guides

Dynamics 365 XRechnung Setup

Ready to Test Your Dynamics 365 Export?

Upload your Peppol BIS 3.0 invoice and get instant compliance feedback with Dynamics 365-specific recommendations.

Validate Peppol BIS 3.0 Invoice