How do I fix UBL-CR-665?

This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Is UBL-CR-665 a critical error?

UBL-CR-665 is a warning that may not always cause rejection, but it indicates a potential compliance issue that should be addressed.

Can UBL-CR-665 be automatically fixed?

Yes, UBL-CR-665 can be automatically corrected. The fix is applied without modifying financial fields.

Error codes · EN16931

UBL-CR-665In your invoicing software

A UBL invoice should not include the AdditionalDocumentReference ID schemeID unless the DocumentTypeCode equals '130'

This is the rejection, word for word: „[UBL-CR-665] This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.“

What to have readyNothing. The file has to be re-exported from your invoicing software; we check it again afterwards.

What we doThis UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

What the finding looks likeExample

FindingStructure invalid · UBL-CR-665

Location//cac:AdditionalDocumentReference[not(cbc:DocumentTypeCode='130')]/cbc:ID/@schemeID

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check