UBL-CR-264:A UBL invoice should not include the AccountingCustomerParty BuyerContact
Fix: Invoice Navigator automatically removes the disallowed `cac:BuyerContact` element from your Invoice. Upload your invoice to fix this automatically.
Your invoice contains a BuyerContact element in the AccountingCustomerParty which is not allowed in EN16931 invoices. Use Party/Contact instead.
Engine Classification
Remove disallowed UBL element per EN16931 specification
Confidence: 95% · Applied automatically in pipeline
What is UBL-CR-264?
UBL-CR-264 is a fatal validation rule defined in the UBL 2.1 specification. It validates the BuyerContact element under AccountingCustomerParty 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/cac:AccountingCustomerParty/cac:BuyerContact
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-264 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-264
- ·Specification: UBL 2.1
How to Fix It
Locate the disallowed element
Open your invoice XML and find cac:BuyerContact at /Invoice/cac:AccountingCustomerParty/cac:BuyerContact. This element is not permitted in the target e-invoice profile and triggers UBL-CR-264.
Remove cac:BuyerContact
Delete the entire cac:BuyerContact block and its child elements. Invoice Navigator automatically removes the disallowed `cac:BuyerContact` element from your Invoice.
Re-validate your invoice
Upload the corrected invoice to confirm UBL-CR-264 is resolved. If your software consistently adds this element, contact your vendor about their e-invoice export settings.
Before / After
<cac:AccountingCustomerParty> <cac:BuyerContact>value</cac:BuyerContact> </cac:AccountingCustomerParty>
<cac:AccountingCustomerParty> <!-- cac:BuyerContact removed for EN 16931 compliance --> </cac:AccountingCustomerParty>
Technical Reference
/Invoice/cac:AccountingCustomerParty/cac:BuyerContactCommon Causes
- ·Source ERP exports full UBL 2.1 party fields instead of EN16931 subset
- ·Generic UBL template includes optional party elements not needed for e-invoicing
- ·Conversion from another format added unsupported party elements
- ·Manual XML editing introduced non-standard party elements
- ·Invoice software not configured for EN16931 compliance on party data
Seeing this in production? The API handles UBL-CR-264 automatically. See the fix response →
Frequently Asked Questions
Your invoice contains a BuyerContact element in the AccountingCustomerParty which is not allowed in EN16931 invoices. Use Party/Contact instead.
Invoice Navigator automatically removes the disallowed `cac:BuyerContact` element from your Invoice. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, UBL-CR-264 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of UBL-CR-264 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-264
Auto-fix UBL-CR-264 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.