What causes the UBL-CR-002 error?

The UBL invoice must use the correct XML namespaces for UBL 2.1.

How do I fix UBL-CR-002?

Add the correct UBL 2.1 namespace declarations to your invoice root element. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Is UBL-CR-002 a critical error?

Yes, UBL-CR-002 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.

Can UBL-CR-002 be automatically fixed?

Many instances of UBL-CR-002 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invalid or missing namespace.

Which accounting software causes UBL-CR-002?

UBL-CR-002 is commonly seen in exports from Custom XML generators, Template errors. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.

Error codes · ubl-2.1

UBL-CR-002In your invoicing software

UBLVersionID must be 2.1 or absent

This is the rejection, word for word: „[UBL-CR-002] A UBL invoice should not include UBLVersionID or it must be version 2.1 for EN 16931 compliance.“

XPath: /Invoice namespace declaration

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

What we doAdd the correct UBL 2.1 namespace declarations to your invoice root element.

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-002

Location/Invoice/cbc:UBLVersionID

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check

Often appears together with

UBL-CR-001Disallowed element: ext:UBLExtensions