errorformatUBL 2.1

UBL-CR-154:A UBL invoice should not include the AccountingSupplierParty Party...

Fix: Invoice Navigator automatically removes the disallowed `cbc:BuildingName` element from your Invoice. Upload your invoice to fix this automatically.

Your invoice contains a BuildingName element in the supplier postal address which is not allowed in EN16931 invoices. This element must be removed.

Severity
Fatal
Rule set
UBL 2.1
Country
All EU
Fix type
AUTO-FIX
Confidence
95%
Category
structural

Engine Classification

Remove disallowed UBL element per EN16931 specification

Confidence: 95% · Applied automatically in pipeline

What is UBL-CR-154?

UBL-CR-154 is a fatal validation rule defined in the UBL 2.1 specification. It validates the BuildingName element under Party > PostalAddress 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:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:BuildingName

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-154 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-154
  • ·Specification: UBL 2.1

How to Fix It

1.

Locate the disallowed element

Open your invoice XML and find cbc:BuildingName at /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:BuildingName. This element is not permitted in the target e-invoice profile and triggers UBL-CR-154.

2.

Remove cbc:BuildingName

Delete the entire cbc:BuildingName block and its child elements. Invoice Navigator automatically removes the disallowed `cbc:BuildingName` element from your Invoice.

3.

Re-validate your invoice

Upload the corrected invoice to confirm UBL-CR-154 is resolved. If your software consistently adds this element, contact your vendor about their e-invoice export settings.

Before / After

Failing XML
<cac:PostalAddress>
  <cbc:BuildingName>value</cbc:BuildingName>
</cac:PostalAddress>
Corrected XML
<cac:PostalAddress>
  <!-- cbc:BuildingName removed for EN 16931 compliance -->
</cac:PostalAddress>

Technical Reference

XPath/Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:BuildingName
SpecUBL 2.1
Operationremove
StrategyRemove disallowed UBL element per EN16931 specification

Common Causes

  • ·Source ERP exports full UBL 2.1 supplier address fields instead of EN16931 subset
  • ·Generic UBL template includes optional address elements not needed for e-invoicing
  • ·Conversion from another format added unsupported supplier address elements
  • ·Manual XML editing introduced non-standard supplier party elements
  • ·Invoice software not configured for EN16931 compliance on supplier data

Seeing this in production? The API handles UBL-CR-154 automatically. See the fix response →

Frequently Asked Questions

Your invoice contains a BuildingName element in the supplier postal address which is not allowed in EN16931 invoices. This element must be removed.

Invoice Navigator automatically removes the disallowed `cbc:BuildingName` element from your Invoice. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Yes, UBL-CR-154 is a critical error that will cause invoice rejection. It must be fixed before submission.

Many instances of UBL-CR-154 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

Share this guide:

Validate your invoice

Drop your XML here to check for UBL-CR-154

Auto-fix UBL-CR-154 in seconds

Upload your invoice and we fix this error automatically. Financial fields are never touched.