What does CII-SR-476 mean?
CII-SR-476 is a syntax rule of EN 16931 for CII. It allows only one ram:AttachmentBinaryObject (BT-125) on attachments with TypeCode 916 and counts all attachments of the invoice together, not each one on its own. But the standard allows any number of attachments (BG-24). From two embedded attachments on, the warning therefore always appears; the invoice stays valid.
Common causes of CII-SR-476
- The invoice has two or more embedded attachments, such as a timesheet and a list of hours.
- Each attachment correctly sits in its own ram:AdditionalReferencedDocument with TypeCode 916.
How to fix CII-SR-476
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-125 along this XPath:
//ram:ApplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument/ram:AttachmentBinaryObject - Apply the fix. Harmless: the rule counts all attachments of the invoice together instead of each one on its own. EN 16931 explicitly allows several attachments (BG-24 any number of times). The invoice stays valid.
- Validate again. Save the file and validate it again to check that CII-SR-476 is no longer reported.
Harmless: the rule counts all attachments of the invoice together instead of each one on its own. EN 16931 explicitly allows several attachments (BG-24 any number of times). The invoice stays valid.
//ram:ApplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument/ram:AttachmentBinaryObjectFrequent questions about CII-SR-476
Is CII-SR-476 an error?
Can I avoid the warning?
Related error codes
Check CII-SR-476 automatically
Instead of digging through the XML by hand you can validate your ZUGFeRD or XRechnung file online: upload the PDF or the XML and you get every error with rule ID, affected field, fix and XPath, as a readable report or as JSON through the API.