errorUBL 2.1

UBL-CR-519:A UBL invoice should not include the InvoiceLine FreeOfChargeIndicator

Your invoice contains an InvoiceLine FreeOfChargeIndicator element 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-519?

UBL-CR-519 is a fatal validation rule defined in the UBL 2.1 specification. It validates the FreeOfChargeIndicator element under InvoiceLine in the UBL invoice XML.

When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

Target path: /Invoice/cac:InvoiceLine/cbc:FreeOfChargeIndicator

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-519 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

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

Before / After

Failing XML
<Invoice>
  <cbc:FreeOfChargeIndicator>value</cbc:FreeOfChargeIndicator>
</Invoice>
Corrected XML
<Invoice>
  <!-- cbc:FreeOfChargeIndicator removed for EN 16931 compliance -->
</Invoice>

Technical Reference

XPath/Invoice/cac:InvoiceLine/cbc:FreeOfChargeIndicator
SpecUBL 2.1
Operationremove
StrategyRemove disallowed UBL element per EN16931 specification

Common Causes

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

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

See Also

Last updated: 27 February 2026

Share this guide:

Handle UBL-CR-519 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.