How To: Set up Microsoft Dynamics 365 Business Central E-Documents with Logiq

‍

‍

‍

‍

Common Validation Errors When Sending E-Documents in Business Central

‍

‍

This section describes the most common validation errors encountered when sending e-documents (for example PEPPOL BIS 3.0 invoices) from Microsoft Dynamics 365 Business Central using an external access point such as Logiq. The validations described here are enforced by Microsoft Business Central itself before documents are sent externally.

‍

These errors are typically caused by missing or inconsistent master data. In most cases, the document is not transmitted to Logiq or the e-document network because Microsoft Business Central blocks the sending process during validation.

‍

‍

‍

1. Country/Region Code Is Missing or Invalid

‍

Typical error messages include:

- "Country/Region does not exist. Identification fields and values: Code="

- "ISO country code is missing"

- PEPPOL XML generation failed

‍

Cause:

Business Central requires valid ISO country codes when generating structured e-documents. Errors occur if the country is missing, invalid, or not linked to an ISO code.

‍

Where to check:

- Countries/Regions: Ensure the country exists and has an ISO Code

- Company Information: Country/Region Code

- Customer Card: Country/Region Code

- Sales document: Bill-to and Ship-to addresses

‍

‍

‍

2. VAT Registration Number Is Missing

‍

Typical error messages include:

- "VAT Registration No. must have a value"

- "Supplier VAT ID is missing"

‍

Cause:

VAT registration information is required by Microsoft E-Documents and PEPPOL validation rules.

‍

Where to check:

- Company Information: VAT Registration No.

- Customer Card: VAT Registration No. (if required by recipient)

‍

‍

‍

3. GLN or Peppol ID Is Missing or Incorrect (When Used)

‍

Typical error messages include:

- "Party identification is missing"

- "Invalid endpoint identifier"

‍

Cause:

When GLN or Peppol IDs are used, the values must be present and correctly formatted.

‍

Where to check:

- Company Information: GLN and "Use GLN in Electronic Documents"

- Customer Card: Peppol ID or GLN

‍

‍

‍

4. E-Document Workflow Is Not Enabled

‍

Typical symptoms:

- Document posts successfully

- No e-document is created

- Nothing appears on the E-Documents page

‍

Cause:

E-documents are only created and sent when an E-Document workflow is enabled.

‍

Where to check:

- Workflows: Ensure an E-Documents workflow exists and is enabled

‍

‍

‍

5. Document Sending Profile Is Missing or Not Assigned

‍

Typical symptoms:

- Documents post normally but are not sent as e-documents

- E-Documents list remains empty

‍

Cause:

The customer does not have a Document Sending Profile configured for E-Documents.

‍

Where to check:

- Document Sending Profiles

- Customer Card: Document Sending Profile

‍

‍

‍

6. Incomplete Address Data on the Sales Document

‍

Typical error messages include:

- "Postal address is incomplete"

- "Country code missing on document address"

‍

Cause:

The posted document inherits address data from the customer, bill-to, and ship-to addresses. If any address is incomplete, validation fails.

‍

Where to check:

- Original Sales Order or Sales Invoice

- Posted Sales Invoice: Bill-to and Ship-to sections

‍

‍

‍

‍

Important Notes

‍

• Most validation errors occur before documents are sent to Logiq or the e-document network
• Errors are logged on the E-Documents page in Business Central
• These validations are enforced by Microsoft and cannot be overridden by Logiq

‍

‍

‍

‍

‍

‍