Microsoft Dynamics 365 Business Central to Peppol BIS Billing 3.0 Integration & Schema Crosswalk
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.
Mandatory Microsoft Dynamics 365 Business Central to Peppol BIS Billing 3.0 Field Crosswalk Matrix
Deterministic attribute mapping from Microsoft Dynamics 365 Business Central payloads to EN 16931 Business Terms (BT) and UBL-2.1 XPaths.
| Microsoft Dynamics 365 Business Central Source Field | EN 16931 Business Term | Target UBL-2.1 XPath | Card. | Transformation & Normalization Rule | Schematron Rule |
|---|---|---|---|---|---|
| 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 ↗ |
Test Your Microsoft Dynamics 365 Business Central Peppol BIS Billing 3.0 XML Export Live
Validate your generated UBL-2.1 payload against EN 16931 & Peppol BIS Billing 3.0 rules directly in your browser.
Missing <cbc:CustomizationID> or value does not declare EN 16931 CIUS compliance.
Remediation: Insert <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>.
Found invalid or lowercase currency code "eur". Expected uppercase ISO 4217 (e.g. "EUR").
Remediation: Replace <cbc:DocumentCurrencyCode>eur</cbc:DocumentCurrencyCode> with uppercase "EUR".
Peppol Schematron forbids empty elements such as <cbc:AdditionalStreetName></cbc:AdditionalStreetName> serialized from null ERP fields.
Remediation: Strip empty <cbc:AdditionalStreetName> nodes prior to XML serialization.
Missing <cbc:EndpointID schemeID="..."> inside <cac:AccountingSupplierParty>/<cac:Party>.
Remediation: Add <cbc:EndpointID schemeID="9930">DE123456789</cbc:EndpointID> as the first child of Seller <cac:Party>.
Buyer <cbc:EndpointID> is either missing or lacks the mandatory EAS @schemeID attribute.
Remediation: Add schemeID="9930" (or "0088" for GLN / "0204" for Leitweg-ID) to Buyer <cbc:EndpointID>.
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.
Remediation: Insert <cbc:BuyerReference>991-12849-74</cbc:BuyerReference> in the document header.
Mathematical discrepancy of 0.05 EUR between InvoiceLine sum (199.95) and LegalMonetaryTotal/LineExtensionAmount (200.00).
Remediation: Set cbc:LineExtensionAmount and cbc:TaxExclusiveAmount to 199.95.
TaxSubtotal/TaxableAmount reports 200.00, but Standard rated ("S") lines total 199.95.
Remediation: Recalculate BT-116 = 199.95, VAT BT-117 = 37.99, and PayableAmount BT-115 = 237.94.
Other ERP to E-Invoicing Compliance Bridges
Unlock Pro Batch XML / PDF Converter ($29/mo) →4 mandatory EN 16931 Business Term mappings
4 mandatory EN 16931 Business Term mappings
4 mandatory EN 16931 Business Term mappings
4 mandatory EN 16931 Business Term mappings