How do I fix UBL-CR-300?

Invoice Navigator automatically removes the disallowed `cbc:EndpointID` element from your Invoice (UBL-CR-300). You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Is UBL-CR-300 a critical error?

Yes, UBL-CR-300 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted.

Can UBL-CR-300 be automatically fixed?

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

Error codes · UBL 2.1

UBL-CR-300In your invoicing software

A UBL invoice should not include the TaxRepresentativeParty EndpointID

This is the rejection, word for word: „[UBL-CR-300] Your invoice contains an EndpointID element in the TaxRepresentativeParty which is not allowed in EN16931 invoices. This element must be removed.“

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

What we doInvoice Navigator automatically removes the disallowed `cbc:EndpointID` element from your Invoice (UBL-CR-300).

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.

If you enter it yourself in your invoicing software

Before

<cac:TaxRepresentativeParty>
  <cbc:EndpointID>value</cbc:EndpointID>
</cac:TaxRepresentativeParty>

After

<cac:TaxRepresentativeParty>
  <!-- cbc:EndpointID removed for EN 16931 compliance -->
</cac:TaxRepresentativeParty>

Element order is part of the rule: if the element sits in the wrong place, the validator rejects with UBL-CR-300.

What the finding looks likeExample

FindingStructure invalid · UBL-CR-300

Location/Invoice/cac:TaxRepresentativeParty/cbc:EndpointID

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check