How do I fix UBL-CR-439?

Invoice Navigator automatically removes the disallowed `cac:PayerParty` element from your Invoice. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Is UBL-CR-439 a critical error?

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

Can UBL-CR-439 be automatically fixed?

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

Error codes · UBL 2.1

UBL-CR-439In your invoicing software

A UBL invoice should not include the PaymentMeans PaymentMandate PayerParty

This is the rejection, word for word: „[UBL-CR-439] Your invoice contains a PaymentMandate PayerParty element 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 `cac:PayerParty` element from your Invoice.

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:PaymentMandate>
  <cac:PayerParty>value</cac:PayerParty>
</cac:PaymentMandate>

After

<cac:PaymentMandate>
  <!-- cac:PayerParty removed for EN 16931 compliance -->
</cac:PaymentMandate>

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

What the finding looks likeExample

FindingStructure invalid · UBL-CR-439

Location/Invoice/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check