XRechnung CII rejected by current KoSIT config: CII writer emits both PersonName and DepartmentName in DefinedTradeContact (CII-SR-465 / CII-SR-466)

[kobima6813]

Version: ZUGFeRD-csharp 18.0.1 / master @ 58f530e, .NET 8. InvoiceDescriptor.Save(..., ZUGFeRDVersion.Version23, Profile.XRechnung, ZUGFeRDFormats.CII).

What happens
When a seller (or buyer) contact has both a name and an OrgUnit (e.g. SetSellerContact("Max Mustermann", "Muster-Einkauf", ...)), InvoiceDescriptor23CIIWriter writes both ram:PersonName and ram:DepartmentName into the same ram:DefinedTradeContact. In the EN 16931 CII binding, both elements carry BT-41 (BT-56 for the buyer). The current CEN rules have:
CII-SR-465: not(SellerTradeParty/DefinedTradeContact/PersonName and SellerTradeParty/DefinedTradeContact/DepartmentName) (CII-SR-466 is the same rule for the buyer).
The KoSIT XRechnung 3.0.2 configuration released 2026-08-31 raises CII-SR-465/466 to error (<s:customLevel level="error">CII-SR-465</s:customLevel>), so these XRechnung-CII invoices are now rejected. The library's own InvoiceProvider.CreateInvoice() test invoice is one of them.

Repro

var desc = new InvoiceProvider().CreateInvoice();   // ZUGFeRD.Test sample
desc.Save("out.xml", ZUGFeRDVersion.Version23, Profile.XRechnung, ZUGFeRDFormats.CII);

<ram:DefinedTradeContact>
  <ram:PersonName>Max Mustermann</ram:PersonName>
  <ram:DepartmentName>Muster-Einkauf</ram:DepartmentName>
  ...

Validators

• KoSIT 1.6.3 + XRechnung 3.0.2 config 2026-08-31: reject, [CII-SR-465] - Only one BT-41 element is allowed on an invoice.
• CEN EN16931 CII XSLT @ 6e35e0a: CII-SR-465 (warning level in plain EN 16931)

The same invoice saved as XRechnung UBL is accepted (UBL has only cac:Contact/cbc:Name).

Suggested fix
For CII, write only one of the two (for example PersonName, falling back to DepartmentName when there is no name), or join them into PersonName ("Max Mustermann, Muster-Einkauf"). At least do this for the XRechnung and EN16931 profiles. Extended can keep both if FNFE allows it there. Also update the test sample.

[stephanstapel]

Hi @kobima6813 ,
thanks. This is a known issue. You can easily prevent it by just setting one of the two in your mapping.

[kobima6813]

Thanks, that makes sense. I've noted the workaround (set only one of the two) in the conformance matrix: https://kobima6813.github.io/einvoice-conformance-matrix/#zugferd-csharp