Buyer contact: do not provide both a name and a department

Error CII-SR-466 Syntax (UBL/CII)

Only one BT-56 element is allowed on an invoice.

Mandatory rule: As long as it is violated, the invoice is invalid and will be rejected by validators.
What is wrong

Both PersonName and DepartmentName are provided in the buyer's DefinedTradeContact. The rule does not allow both values to be present at the same time.

What the rule means

The buyer's contact must not be represented as both a person (BT-56) and a department (BT-56-0) at the same time.

Affected fields BT-56
Please do not provide both a name and a department for the buyer contact

The buyer 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.

What to do
  1. Check the values in BuyerTradeParty/DefinedTradeContact.
  2. For the buyer contact, use either Contact.Name or Contact.OrgUnit.
  3. Check the call to SetBuyerContact(...) and the values for name and orgunit.
  4. Generate the invoice again and validate it.
What it looks like
✗ Triggers the message 
<ram:BuyerTradeParty>
  <ram:DefinedTradeContact>
    <ram:PersonName>...</ram:PersonName>
    <ram:DepartmentName>...</ram:DepartmentName>
  </ram:DefinedTradeContact>
</ram:BuyerTradeParty>
✓ Correct 
<ram:BuyerTradeParty>
  <ram:DefinedTradeContact>
    <ram:PersonName>...</ram:PersonName>
  </ram:DefinedTradeContact>
</ram:BuyerTradeParty>
Check in FactoorSharp
  • Contact.Name (BuyerTradeParty/ DefinedTradeContact: BT-56)
  • Contact.OrgUnit (BuyerTradeParty/ DefinedTradeContact: BT-56-0)
  • FacturXInvoice.SetBuyerContact(name, orgunit, emailAddress, phoneno, faxno) (name: BT-56; orgunit: BT-56-0)
Different severity at KoSIT
  • Error EN16931 XRechnung (CII) – overwrites CEN severity level "warning" to enforce only one BT-56 "Buyer contact point"
  • Error EN16931 XRechnung Extension (CII) – overwrites CEN severity level "warning" to enforce only one BT-56 "Buyer contact point"
  • Error EN16931 XRechnung CVD (CII) – overwrites CEN severity level "warning" to enforce only one BT-56 "Buyer 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.

Where the rule applies

The rule applies to the buyer's contact in BuyerTradeParty/DefinedTradeContact within the agreement information.

Context (rule/@context)
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement
Test expression (assert/@test)
not( ram:BuyerTradeParty/ram:DefinedTradeContact/ram:PersonName and ram:BuyerTradeParty/ram:DefinedTradeContact/ram:DepartmentName )
Changes in the KoSIT validation rules
  • 2026-08-312026-08-31 · Addedcustom level "error" for `CII-SR-465` and `CII-SR-466`