[Bug]: XRechnung – Invalid XML Generated When Customer is missing data.

[miljance]

Describe the issue

When a Sales Invoice is posted for a customer record that is missing mandatory master data (e.g., address fields, email), the generated xRechnung XML file is invalid.
The XML export does not enforce validation of required customer fields before posting, which results in missing elements in the XML.
As a consequence, the file fails validation in the official xRechnung validator with multiple errors related to incomplete customer address information.

Expected behavior

• A posted Sales Invoice should always produce a valid xRechnung XML file.
• If mandatory customer data is missing, the system should prevent posting until the required information is completed.
• Users should not discover XML errors only after posting; the export must remain compliant with posted document values.

Steps to reproduce

Repro

1. Use Business Central for Germany.
2. Enable E-Document Service for XRechnung.
3. In setup:
   • Set Buyer Reference Mandatory = Yes
   • Set Buyer Reference = Your Reference
4. Configure a Workflow for XRechnung (per docs).
5. Configure a Document Sending Profile for XRechnung (per docs) and mark it as default.
6. Create a new domestic customer without using customer templates.
7. Enter only a name for the customer (no address, no email).
8. Assign posting groups: Gen. Bus. Posting Group, VAT Bus. Posting Group, and Customer Posting Group (e.g., INLAND).
9. Create a new Sales Invoice for this customer and enter any value in Your Reference.
10. Add a Sales Line with any value (e.g., 4.000,00 EUR).
11. Post the Sales Invoice.
12. Open the Posted Sales Invoice.
13. Navigate to Related → E-Document → Open E-Document.
14. From E-Document Logs, export the XML file.
15. Upload the file to the xRechnung Validator.
16. Observe the errors: validator reports multiple missing address fields.

Additional context

Fixes
AB#609594

I will provide a fix for a bug

• I will provide a fix for a bug

[miljance]

@djukicmilica @AleksanderGladkov

[miljance]

@JesperSchulz also a germen topic, can you move it to ALAppExtension please?

[pri-kise]

@miljance is this really a german topic?
Currently there are the subscribers
on event OnBeforeReleaseSalesDoc in codeunit 6103 "E-Document Subscription"
and
on event OnAfterCheckAndUpdate in codeunit 6103 "E-Document Subscription".

This should trigger the e document check.

Or is this a german issue that there's missing the normal peppol validation?

Additional Info:
The Peppol Validation is moved from the BaseApp to BCApps (microsoft/BCApps#4931)

[miljance]

@pri-kise good question. I know that CheckCompanyInfoMandatory is in the codeunit xRechnungFormat so my guess was that a customer check should also happen here. But it seems you might be right. This should be probably catched by Peppol validation. The Peppol validation codeunit however is in the base app as far as I can tell. There is a codeunit "EDoc PEPPOL BIS 3.0 DE" in german E-Documents but only for referencing the codeunit from the E-Document module which in turn references a codeunit from the Base app.

😅🔍🧩

[miljance]

Well, I guess the incident should not be moved until I debug and find out in which of the three repos the change should be made.

[miljance]

Ok, found out, this is a problem in xRechnung. I guess also in Zugferd because I do not see non of those two using PEPPOL validations. The PEPPOL does not allow posting a sales document when those fields are missing. So, @JesperSchulz please move it to ALAppExtensions where xRechnung and Zugferd live. The question is, if the check for xRechnung and Zugferd should be the same as the default PEPPOL checks but I can clarify with @altotovi .