errorformatUBL 2.1

UBL-CR-616:A UBL invoice should not include the InvoiceLine Item AdditionalItemProperty...

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

UBL 2.1 Invoice schema does not include `cac:Item/cac:AdditionalItemProperty/cac:ItemPropertyGroup`. This element must be removed for EN 16931 compliance.

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-616?

UBL-CR-616 is a fatal validation rule defined in the UBL 2.1 specification. It validates the ItemPropertyGroup element under Item > AdditionalItemProperty 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:InvoiceLine/cac:Item/cac:AdditionalItemProperty/cac:ItemPropertyGroup

Why This Error Matters

Invoice will be rejected by EN16931 validators. These conformance rules prohibit UBL elements that are not part of the EN16931 e-invoicing profile. Remove the disallowed element.

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

How to Fix It

1.

Locate the disallowed element

Open your invoice XML and find cac:ItemPropertyGroup at /Invoice/cac:InvoiceLine/cac:Item/cac:AdditionalItemProperty/cac:ItemPropertyGroup. This element is not permitted in the target e-invoice profile and triggers UBL-CR-616.

2.

Remove cac:ItemPropertyGroup

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

3.

Re-validate your invoice

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

Before / After

Failing XML
<cac:AdditionalItemProperty>
  <cac:ItemPropertyGroup>value</cac:ItemPropertyGroup>
</cac:AdditionalItemProperty>
Corrected XML
<cac:AdditionalItemProperty>
  <!-- cac:ItemPropertyGroup removed for EN 16931 compliance -->
</cac:AdditionalItemProperty>

Technical Reference

XPath/Invoice/cac:InvoiceLine/cac:Item/cac:AdditionalItemProperty/cac:ItemPropertyGroup
SpecUBL 2.1
Operationremove
StrategyRemove disallowed UBL element per EN16931 specification

Common Causes

  • ·Invoice line item property contains ItemPropertyGroup
  • ·AdditionalItemProperty ItemPropertyGroup not permitted
  • ·Property grouping not in EN16931 profile
  • ·Flat property list required, no grouping
  • ·ERP exports hierarchical property structures

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

Frequently Asked Questions

UBL 2.1 Invoice schema does not include `cac:Item/cac:AdditionalItemProperty/cac:ItemPropertyGroup`. This element must be removed for EN 16931 compliance.

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

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

Many instances of UBL-CR-616 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

Last updated: 14 April 2026

Share this guide:

Validate your invoice

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

Auto-fix UBL-CR-616 in seconds

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