Only one BT-41 element is allowed on an invoice.
Both PersonName and DepartmentName are provided in the seller's DefinedTradeContact. The rule does not allow both values to be present at the same time.
The seller's contact must not be represented as both a person (BT-41) and a department (BT-41-0) at the same time.
The seller contact includes both a person's name and a department. You can adjust the entry so that both are not provided at the same time.
- Check the values in
SellerTradeParty/DefinedTradeContact. - For the seller contact, use either
Contact.NameorContact.OrgUnit. - Check the call to
SetSellerContact(...)and the values fornameandorgunit. - Generate the invoice again and validate it.
<ram:SellerTradeParty> <ram:DefinedTradeContact> <ram:PersonName>...</ram:PersonName> <ram:DepartmentName>...</ram:DepartmentName> </ram:DefinedTradeContact> </ram:SellerTradeParty>
<ram:SellerTradeParty> <ram:DefinedTradeContact> <ram:PersonName>...</ram:PersonName> </ram:DefinedTradeContact> </ram:SellerTradeParty>
Contact.Name(SellerTradeParty/ DefinedTradeContact: BT-41)Contact.OrgUnit(SellerTradeParty/ DefinedTradeContact: BT-41-0)FacturXInvoice.SetSellerContact(name, orgunit, emailAddress, phoneno, faxno)(name: BT-41; orgunit: BT-41-0)
- Error EN16931 XRechnung (CII) – overwrites CEN severity level "warning" to enforce only one BT-41 "Seller contact point"
- Error EN16931 XRechnung Extension (CII) – overwrites CEN severity level "warning" to enforce only one BT-41 "Seller contact point"
- Error EN16931 XRechnung CVD (CII) – overwrites CEN severity level "warning" to enforce only one BT-41 "Seller contact point"
Technical details
The XPath test fails when PersonName and DepartmentName are both present in the same DefinedTradeContact. It does not require either element to be present.
The rule applies to the seller's contact in SellerTradeParty/DefinedTradeContact within the agreement information.
rule/@context)assert/@test)- 2026-08-312026-08-31 · Addedcustom level "error" for `CII-SR-465` and `CII-SR-466`