UBL-CR-010:Disallowed element: cbc:AccountingCostCode
Fix: Invoice Navigator automatically removes the disallowed `cbc:AccountingCostCode` element from your Invoice. Upload your invoice to fix this automatically.
UBL 2.1 Invoice schema does not include `cbc:AccountingCostCode`. 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-010?
UBL-CR-010 is a fatal validation rule defined in the UBL 2.1 specification. It validates the AccountingCostCode element in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: /Invoice/cbc:AccountingCostCode
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-010 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
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-010
- ·Specification: UBL 2.1
How to Fix It
Check order
UBL has strict element ordering
Header order
ID, IssueDate, DueDate, InvoiceTypeCode, etc.
Use validator
Schema validator will show first wrong element
Before / After
<Invoice> <cbc:AccountingCostCode>value</cbc:AccountingCostCode> </Invoice>
<Invoice> <!-- cbc:AccountingCostCode removed for EN 16931 compliance --> </Invoice>
Technical Reference
/Invoice/cbc:AccountingCostCodeCode Example
<!-- UBL Invoice header order -->
<Invoice>
<cbc:UBLVersionID>2.1</cbc:UBLVersionID>
<cbc:CustomizationID>...</cbc:CustomizationID>
<cbc:ProfileID>...</cbc:ProfileID>
<cbc:ID>INV-001</cbc:ID>
<cbc:IssueDate>2024-12-19</cbc:IssueDate>
<!-- etc. in correct order -->
</Invoice>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-010 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
UBL elements must appear in the order defined by the schema.
Reorder elements according to UBL schema. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, UBL-CR-010 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-010 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including elements in wrong order.
UBL-CR-010 is commonly seen in exports from Custom invoice generators. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Errors
Related Content
Last updated: 27 February 2026
Validate your invoice
Drop your XML here to check for UBL-CR-010
Auto-fix UBL-CR-010 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.