UBL-CR-009:Disallowed element: cbc:PaymentAlternativeCurrencyCode
UBL 2.1 Invoice schema does not include `cbc:PaymentAlternativeCurrencyCode`. This element must be removed for EN 16931 compliance.
Engine Classification
Remove disallowed UBL element per EN16931 specification
Confidence: 95% · Applied automatically in pipeline
What is UBL-CR-009?
UBL-CR-009 is a fatal validation rule defined in the UBL 2.1 specification. It validates the PaymentAlternativeCurrencyCode element in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: /Invoice/cbc:PaymentAlternativeCurrencyCode
Why This Error Matters
Invoice will be rejected by PEPPOL/EN16931 validators. Safe to remove - this element is explicitly prohibited and contains no required business data.
UBL-CR-009 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
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
- ·Causes invoice rejection
- ·Fails UBL schema validation
- ·Error returned: UBL-CR-009
- ·Specification: UBL 2.1
How to Fix It
Check schema
Verify attribute is UBL 2.1 defined
Common valid attributes
currencyID, schemeID, listID, name
Remove invalid
Delete or move to extension area
Before / After
<Invoice> <cbc:PaymentAlternativeCurrencyCode>value</cbc:PaymentAlternativeCurrencyCode> </Invoice>
<Invoice> <!-- cbc:PaymentAlternativeCurrencyCode removed for EN 16931 compliance --> </Invoice>
Technical Reference
/Invoice/cbc:PaymentAlternativeCurrencyCodeCode Example
<!-- BAD: -->
<cbc:ID type="invoice">123</cbc:ID>
<!-- GOOD: -->
<cbc:ID>123</cbc:ID>Common Causes
- ·Source ERP exports full UBL 2.1 instead of EN16931 subset
- ·Generic UBL template includes optional elements not needed for e-invoicing
- ·Conversion from another format added unsupported elements
- ·Manual XML editing introduced non-standard elements
- ·Invoice software not configured for EN16931 compliance
Seeing this in production? The API handles UBL-CR-009 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Element contains an attribute not defined in UBL 2.1 schema.
Remove non-standard attributes from elements. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, UBL-CR-009 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.
Many instances of UBL-CR-009 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 unknown attribute.
UBL-CR-009 is commonly seen in exports from Custom invoice generators. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
See Also
Related Errors
Last updated: 27 February 2026
Handle UBL-CR-009 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.