Additional document name at most once for type 916

Warning CII-SR-475 Syntax (UBL/CII)

[CII-SR-475] - Only one AdditionalReferencedDocument Name BT-123 is allowed with TypeCode 916.

Recommendation: The invoice remains valid but should be corrected so that it can be processed automatically.
What is wrong

More than one Name element occurs in total for AdditionalReferencedDocument elements with TypeCode 916. The rule allows at most one such element.

What the rule means

The name identifies the referenced additional document. The rule limits the number of these names for document type 916 to one.

Affected fields BT-123
Please include the document name for type `916` at most once

For documents with TypeCode 916, the invoice contains more than one Name entry. You can limit the names to a single entry.

What to do
  1. Find the AdditionalReferencedDocument entries with TypeCode 916.
  2. Check their Name values.
  3. Check the value through AdditionalReferencedDocument.Name or the name parameter of AddAdditionalReferencedDocument(...).
  4. Regenerate the invoice and validate it again.
What it looks like
✗ Triggers the message 
<ram:AdditionalReferencedDocument>
  <ram:TypeCode>916</ram:TypeCode>
  <ram:Name>Document A</ram:Name>
</ram:AdditionalReferencedDocument>
<ram:AdditionalReferencedDocument>
  <ram:TypeCode>916</ram:TypeCode>
  <ram:Name>Document B</ram:Name>
</ram:AdditionalReferencedDocument>
✓ Correct 
<ram:AdditionalReferencedDocument>
  <ram:TypeCode>916</ram:TypeCode>
  <ram:Name>Document A</ram:Name>
</ram:AdditionalReferencedDocument>
Check in FactoorSharp
  • AdditionalReferencedDocument.Name (BT-123)
  • FacturXInvoice.AddAdditionalReferencedDocument(id, typeCode, issueDateTime, name, referenceTypeCode, attachmentBinaryObject, filename, uriID) (name: BT-123)
Different severity at KoSIT
  • Information EN16931 XRechnung (CII) – overwrites CEN severity level "warning" because CII-SR-475 has a wrong rule context (see https://github.com/ConnectingEurope/eInvoicing-EN16931/issues/508); replaced by BR-TMP-4
  • Information EN16931 XRechnung Extension (CII) – overwrites CEN severity level "warning" because CII-SR-475 has a wrong rule context (see https://github.com/ConnectingEurope/eInvoicing-EN16931/issues/508); replaced by BR-TMP-4
  • Information EN16931 XRechnung CVD (CII) – overwrites CEN severity level "warning" because CII-SR-475 has a wrong rule context (see https://github.com/ConnectingEurope/eInvoicing-EN16931/issues/508); replaced by BR-TMP-4
Technical details

The XPath counts Name elements under AdditionalReferencedDocument whose normalized TypeCode is 916; the test passes when there is at most one match.

Where the rule applies

The rule applies to Name elements in AdditionalReferencedDocument within ApplicableHeaderTradeAgreement when the associated TypeCode is 916.

Context (rule/@context)
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement
Test expression (assert/@test)
count(ram:AdditionalReferencedDocument[normalize-space(ram:TypeCode) = '916']/ ram:Name) <= 1
Changes in the KoSIT validation rules
  • 2026-08-312026-08-31 · Addedcustom level "information" for `CII-SR-475` and `CII-SR-476` because both rules have a wrong rule context in CEN Schematron 1.3.16 (see https://github.com/ConnectingEurope/eInvoicing-EN16931/issues/508); replaced by BR-TMP-4 and BR-TMP-5 in XRechnung Schematron