warningEN16931
UBL-CR-310:A UBL invoice should not include the TaxRepresentativeParty PostalAddress BlockName
Your invoice contains a PostalAddress BlockName element in the TaxRepresentativeParty which is not allowed in EN16931 invoices. This element must be removed.
We can fix this automatically
AUTO-FIXAuto-fix: Remove the disallowed element from the invoice XML. No data loss occurs because EN16931 explicitly prohibits this element.
No manual changes needed
Upload and Fix NowWhy 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.
Common Causes
- Source ERP exports full UBL 2.1 delivery/party fields instead of EN16931 subset
- Generic UBL template includes optional delivery elements not needed for e-invoicing
- Conversion from another format added unsupported delivery elements
- Manual XML editing introduced non-standard elements
- Invoice software not configured for EN16931 compliance
Frequently Asked Questions
Your invoice contains a PostalAddress BlockName element in the TaxRepresentativeParty which is not allowed in EN16931 invoices. This element must be removed.
Your invoice contains a PostalAddress BlockName element in the TaxRepresentativeParty which is not allowed in EN16931 invoices. This element must be removed. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
UBL-CR-310 is a warning that may not always cause rejection, but it indicates a potential compliance issue that should be addressed.
Many instances of UBL-CR-310 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues.
See Also
Last updated: 16 January 2026
Share this guide: