Top Up Credits β†’
InvoiceSpec / ERP Crosswalks / dynamics-365-business-central-to-peppol-bis-3
SOURCE: MICROSOFT DYNAMICS 365 BUSINESS CENTRAL β†’ TARGET: PEPPOL BIS BILLING 3.0 (UBL-2.1) Mandate: 2026-01-01 (EU)

Microsoft Dynamics 365 Business Central to Peppol BIS Billing 3.0 Schema Crosswalk & XML Compiler

01. Architectural Gap Analysis

Why Native Microsoft Dynamics 365 Business Central Exports Fail Peppol BIS 3.0 Validation

1. **Missing mandatory BT-10 (Buyer Reference)**: Business Central's `salesInvoices` API does not expose a dedicated field for the buyer reference (BT-10), which is required by Peppol BIS 3.0 (BR-DE-15). The `externalDocumentNumber` field is often used, but it is not guaranteed to be populated or may contain non-compliant values.

2. **Incorrect VAT identifier mapping**: The `taxRegistrationNumber` field in Business Central may contain a domestic VAT number without the required country prefix (e.g., 'DE' for Germany). Peppol requires the VAT identifier to be in the format 'CCNNNN...' (BR-CL-01). Additionally, the scheme ID must be set to 'VAT' for VAT numbers, but Business Central does not provide this metadata.

3. **Rounding and total mismatches**: Business Central calculates totals using its own rounding rules, which may differ from the EN 16931 rules (BR-CO-10, BR-CO-15). For example, line item amounts may be rounded to 2 decimals, but the sum of lines may not equal the invoice total excluding VAT due to rounding at the header level. This causes validation failures on BR-CO-10 and BR-CO-15.

02. Microsoft Dynamics 365 Business Central to UBL-2.1 Field Crosswalk Table
Microsoft Dynamics 365 Business Central API Field EN 16931 Business Term Target UBL-2.1 XPath Card. Normalization Rule Assertion
number String, e.g., 'INV-1001' BT-1 /Invoice/cbc:ID 1..1 Trim whitespace and use as-is. Ensure it is unique per invoice and does not exceed 50 characters. BR-02 β†—
invoiceDate Date, e.g., '2023-10-15' BT-2 /Invoice/cbc:IssueDate 1..1 Format as 'YYYY-MM-DD' (ISO 8601). If the source is a datetime, extract the date part. BR-01 β†—
customerNumber String, e.g., 'CUST-123' BT-10 /Invoice/cbc:BuyerReference 0..1 If customerNumber is empty or null, use a fallback value like 'NA'. Otherwise, trim and use as-is. Note: Peppol BIS 3.0 requires BT-10 for German invoices (BR-DE-15), so ensure it is populated. BR-DE-15 β†—
taxRegistrationNumber String, e.g., 'DE123456789' BT-31 /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID 0..1 Remove any spaces or special characters. Ensure it starts with a 2-letter country code (e.g., 'DE'). If missing, prepend the country code from the seller's address. Set the schemeID attribute to 'VAT'. BR-CL-01 β†—
03. Live Microsoft Dynamics 365 Business Central β†’ Peppol BIS Billing 3.0 Workbench
1 CREDITS
invoice.xmlUBL-2.1
DETECTED SOURCEShopify
BT-131 LINE SUM199.95 EUR
BT-106 HEADER200.00 EUR
SCHEMATRON: 7 FATAL, 1 WARNΒ· 1ms
Peppol BIS Billing 3.0
BR-01An Invoice shall have a valid EN 16931 Specification identifier (BT-24)
Spec & Diff
xpath: /ubl:Invoice/cbc:CustomizationID

Missing <cbc:CustomizationID> or value does not declare EN 16931 CIUS compliance.

fix: Insert <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>.

BR-CL-01Document currency code (BT-5) MUST belong to ISO 4217 uppercase code list
Spec & Diff
xpath: /ubl:Invoice/cbc:DocumentCurrencyCode

Found invalid or lowercase currency code "eur". Expected uppercase ISO 4217 (e.g. "EUR").

fix: Replace <cbc:DocumentCurrencyCode>eur</cbc:DocumentCurrencyCode> with uppercase "EUR".

PEPPOL-EN16931-R008Document MUST NOT contain empty XML elements (found 1: <cbc:AdditionalStreetName>)
Spec & Diff
xpath: //cbc:AdditionalStreetName[not(node())]

Peppol Schematron forbids empty elements such as <cbc:AdditionalStreetName></cbc:AdditionalStreetName> serialized from null ERP fields.

fix: Strip empty <cbc:AdditionalStreetName> nodes prior to XML serialization.

PEPPOL-EN16931-R020Seller electronic address (BT-34) MUST be provided with a valid EAS @schemeID
Spec & Diff
xpath: /ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

Missing <cbc:EndpointID schemeID="..."> inside <cac:AccountingSupplierParty>/<cac:Party>.

fix: Add <cbc:EndpointID schemeID="9930">DE123456789</cbc:EndpointID> as the first child of Seller <cac:Party>.

PEPPOL-EN16931-R010Buyer electronic address (BT-49) MUST include a valid EAS @schemeID attribute
Spec & Diff
xpath: /ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID

Buyer <cbc:EndpointID> is either missing or lacks the mandatory EAS @schemeID attribute.

fix: Add schemeID="9930" (or "0088" for GLN / "0204" for Leitweg-ID) to Buyer <cbc:EndpointID>.

BR-DE-15Buyer reference / Leitweg-ID (BT-10) is missing
Spec & Diff
xpath: /ubl:Invoice/cbc:BuyerReference

No <cbc:BuyerReference> (BT-10) found. Mandatory in XRechnung 3.0 (BR-DE-15) and required in Peppol BIS 3.0 (PEPPOL-EN16931-R003) when OrderReference is absent.

fix: Insert <cbc:BuyerReference>991-12849-74</cbc:BuyerReference> in the document header.

BR-CO-10Sum of Invoice line net amount (BT-106 = 200.00) != sum of lines (BT-131 = 199.95)
Spec & Diff
xpath: /ubl:Invoice/cac:LegalMonetaryTotal/cbc:LineExtensionAmount

Mathematical discrepancy of 0.05 EUR between InvoiceLine sum (199.95) and LegalMonetaryTotal/LineExtensionAmount (200.00).

fix: Set cbc:LineExtensionAmount and cbc:TaxExclusiveAmount to 199.95.

BR-S-08Standard rate VAT TaxableAmount (BT-116 = 200.00) does not match S-rated lines (199.95)
Spec & Diff
xpath: /ubl:Invoice/cac:TaxTotal/cac:TaxSubtotal/cbc:TaxableAmount

TaxSubtotal/TaxableAmount reports 200.00, but Standard rated ("S") lines total 199.95.

fix: Recalculate BT-116 = 199.95, VAT BT-117 = 37.99, and PayableAmount BT-115 = 237.94.

Automate Microsoft Dynamics 365 Business Central β†’ Peppol BIS Billing 3.0 AP Delivery

Deploy certified Peppol Access Point & ZUGFeRD ERP connector

04. Other ERP Compliance Matrices