At most one AttachmentBinaryObject with TypeCode 916

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

[CII-SR-476] - Only one AdditionalReferencedDocument AttachmentBinaryObject BT-125 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 AttachmentBinaryObject is present under AdditionalReferencedDocument elements with TypeCode 916. This combination may occur no more than once in total.

What the rule means

The rule limits the invoice to one embedded document with document type code 916 (BT-125). This keeps the number of attachments for this reference type unambiguous.

Affected fields BT-125
Please include no more than one document with `TypeCode` 916 as an `AttachmentBinaryObject`

The invoice contains multiple embedded documents with TypeCode 916. You can limit this to one document.

What to do
  1. Check the AdditionalReferencedDocument entries created with TypeCode 916.
  2. Check the call to AddAdditionalReferencedDocument(...) and the value for attachmentBinaryObject.
  3. Make sure there is no more than one associated AttachmentBinaryObject in total.
  4. Generate the invoice again and validate it.
What it looks like
✗ Triggers the message 
<ram:AdditionalReferencedDocument>
  <ram:TypeCode>916</ram:TypeCode>
  <ram:AttachmentBinaryObject>...</ram:AttachmentBinaryObject>
</ram:AdditionalReferencedDocument>
<ram:AdditionalReferencedDocument>
  <ram:TypeCode>916</ram:TypeCode>
  <ram:AttachmentBinaryObject>...</ram:AttachmentBinaryObject>
</ram:AdditionalReferencedDocument>
✓ Correct 
<ram:AdditionalReferencedDocument>
  <ram:TypeCode>916</ram:TypeCode>
  <ram:AttachmentBinaryObject>...</ram:AttachmentBinaryObject>
</ram:AdditionalReferencedDocument>
Check in FactoorSharp
  • AdditionalReferencedDocument.AttachmentBinaryObject (BT-125)
  • AdditionalReferencedDocument.Filename (BT-125-2)
  • FacturXInvoice.AddAdditionalReferencedDocument(id, typeCode, issueDateTime, name, referenceTypeCode, attachmentBinaryObject, filename, uriID) (attachmentBinaryObject: BT-125)
Different severity at KoSIT
  • Information EN16931 XRechnung (CII) – overwrites CEN severity level "warning" because CII-SR-476 has a wrong rule context (see https://github.com/ConnectingEurope/eInvoicing-EN16931/issues/508); replaced by BR-TMP-5
  • Information EN16931 XRechnung Extension (CII) – overwrites CEN severity level "warning" because CII-SR-476 has a wrong rule context (see https://github.com/ConnectingEurope/eInvoicing-EN16931/issues/508); replaced by BR-TMP-5
  • Information EN16931 XRechnung CVD (CII) – overwrites CEN severity level "warning" because CII-SR-476 has a wrong rule context (see https://github.com/ConnectingEurope/eInvoicing-EN16931/issues/508); replaced by BR-TMP-5
Technical details

The test counts AttachmentBinaryObject elements under AdditionalReferencedDocument elements whose normalized TypeCode equals the text value 916. The count must be no greater than 1.

Where the rule applies

The rule applies to referenced documents in the invoice's ApplicableHeaderTradeAgreement.

Context (rule/@context)
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement
Test expression (assert/@test)
count(ram:AdditionalReferencedDocument[normalize-space(ram:TypeCode) = '916']/ ram:AttachmentBinaryObject) <= 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