UBL-CR-412:A UBL invoice should not include the PaymentMeans PaymentDueDate
Your invoice contains a PaymentMeans PaymentDueDate element which is not allowed in EN16931 invoices. Use PaymentTerms instead.
Engine Classification
Remove disallowed PaymentDueDate from PaymentMeans element
Confidence: 90% · Applied automatically in pipeline
What is UBL-CR-412?
UBL-CR-412 is a warning validation rule defined in the EN16931 specification. It validates the PaymentDueDate element in the UBL invoice XML.
This is a soft validation failure. The invoice may pass initial transmission, but non-compliant values in this field can cause problems during tax audits, buyer-side processing, or downstream VAT reconciliation.
Target path: //cac:PaymentMeans/cbc:PaymentDueDate
Why This Error Matters
Invoice will be rejected by PEPPOL/EN16931 validators. Safe to remove - these elements are explicitly prohibited in EN16931 and contain no required business data.
UBL-CR-412 is a soft failure. The invoice may pass initial validation, but the non-compliant field can cause issues at the receiving end — tax authorities may flag it during audits, buyer ERP systems may fail to process it, or VAT reconciliation may produce mismatches. Fixing warnings before they accumulate prevents larger compliance gaps.
Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.
Validator Behavior
- ·Generates validation warning
- ·Fails EN 16931 business rule validation
- ·Error returned: UBL-CR-412
- ·Specification: EN16931
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Incorrect value --> <cbc:PaymentDueDate>INVALID</cbc:PaymentDueDate>
<!-- Corrected value --> <cbc:PaymentDueDate>VALID_VALUE</cbc:PaymentDueDate>
Technical Reference
//cac:PaymentMeans/cbc:PaymentDueDateCommon Causes
- ·Source ERP exports full UBL 2.1 payment/delivery fields instead of EN16931 subset
- ·Generic UBL template includes optional financial elements not needed for e-invoicing
- ·Conversion from another format added unsupported payment elements
- ·Manual XML editing introduced non-standard elements
- ·Invoice software not configured for EN16931 compliance
Seeing this in production? The API handles UBL-CR-412 automatically. See the fix response →
See Also
Last updated: 21 February 2026
Handle UBL-CR-412 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.