InvoiceValidator.eu

BR-DE-22

fatalXRechnung 3.0.2 (Germany)profileCIIUBL

Das "filename"-Attribut aller "EmbeddedDocumentBinaryObject"-Elemente muss eindeutig sein

Why it fails

Two embedded attachments share the same filename attribute.

How to fix it

Give every EmbeddedDocumentBinaryObject a distinct filename. Receivers write attachments to one directory, so duplicates would overwrite each other.

What the validator checks

CII — context —

count(//ram:AdditionalReferencedDocument) = count(//ram:AdditionalReferencedDocument[not(./ram:AttachmentBinaryObject/@filename = preceding-sibling::ram:AdditionalReferencedDocument/ram:AttachmentBinaryObject/@filename)])

UBL — context —

count(cac:AdditionalDocumentReference) = count(cac:AdditionalDocumentReference[not(./cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@filename = preceding-sibling::cac:AdditionalDocumentReference/cac:Attachment/cbc:EmbeddedDocumentBinaryObject/@filename)])

Related rules

Part of BR-DE — XRechnung (Germany).

Check your own invoice against BR-DE-22

…or paste the XML instead

Nothing is stored, and the whole invoice is checked, not just this rule. A PDF only works if it is Factur-X / ZUGFeRD — a PDF with the invoice XML inside it.