#9646 [Bug]: [DE] XRechnung/ZUGFeRD — no posting-time error when SELLER CONTACT (BG-6) source data is incomplete, producing non-compliant e-invoices
E-Document posting now validates that seller contact information (from salesperson or company data) is complete before generating XRechnung/ZUGFeRD e-invoices, preventing non-compliant XML that would fail validation.
- 5files
- 3AL files
- 3objects
Pull request · merged into main (BC30) on 2026-09-22 by miljance (community contribution) · 5 files (+717 -0), 3 AL · fix · tier official · reviewed (checked by Opus)
What changed
- New check that seller contact data (BG-6) is complete, run from the Check of the XRechnung and ZUGFeRD formats
- Salesperson Name, Phone No. and E-Mail are required when a salesperson is set and exists; otherwise Company Information Contact Person and Phone No. are required
- Company Information E-Mail is not checked again because the existing BT-34 check already requires it
- Error messages name the missing field and the source it was expected from
- Documents with incomplete contact data that used to post will now fail; 11 tests added to each format’s test suite
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 11038 “E-Document DE Helper”, EDocumentDE (DE layer): modified
- Codeunit 13914 “XRechnung Format”, EDocumentDE (DE layer): modified
- Codeunit 13920 “ZUGFeRD Format”, EDocumentDE (DE layer): modified
Also merged into
- #11817 into
releases/29.xon 2026-09-24
Context
- Fixes: #8416 [Bug]: [DE] XRechnung/ZUGFeRD — no posting-time error when SELLER CONTACT (BG-6) source data is incomplete, producing non-compliant e-invoices (closed)
- Work items: AB#650455
- Labels: ADO: Sync, From Fork, Team: Finance
- Systems: integration
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).