UBL-CR-412:A UBL invoice should not include the PaymentMeans PaymentDueDate
Fix: Your invoice contains a PaymentMeans PaymentDueDate element which is not allowed in EN16931 invoices. Use PaymentTerms instead. Upload your invoice to fix this automatically.
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.
The invoice may pass transmission, but this non-compliance can cause problems during tax audits or buyer-side processing.
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 that can cause issues at the receiving end — tax audits, ERP processing, or VAT reconciliation mismatches.
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
How to Fix It
Locate the disallowed element
Open your invoice XML and find cbc:PaymentDueDate at //cac:PaymentMeans/cbc:PaymentDueDate. This element is not permitted in the target e-invoice profile and triggers UBL-CR-412.
Remove cbc:PaymentDueDate
Delete the entire cbc:PaymentDueDate block and its child elements. Your invoice contains a PaymentMeans PaymentDueDate element which is not allowed in EN16931 invoices. Use PaymentTerms instead.
Re-validate your invoice
Upload the corrected invoice to confirm UBL-CR-412 is resolved. If your software consistently adds this element, contact your vendor about their e-invoice export settings.
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 →
Frequently Asked Questions
Your invoice contains a PaymentMeans PaymentDueDate element which is not allowed in EN16931 invoices. Use PaymentTerms instead.
Your invoice contains a PaymentMeans PaymentDueDate element which is not allowed in EN16931 invoices. Use PaymentTerms instead. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
UBL-CR-412 is a warning that may not always cause rejection, but indicates a compliance issue.
Many instances of UBL-CR-412 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for UBL-CR-412
Auto-fix UBL-CR-412 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.