How do I fix UBL-CR-680?

This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is UBL-CR-680 a critical error?

UBL-CR-680 is a warning that may not always cause rejection, but indicates a compliance issue.

Can UBL-CR-680 be automatically fixed?

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

warningEN16931

`UBL-CR-680`:A UBL invoice should not include the PaymentMeans/PayerFinancialAccount

This UBL element should not be present in an EN16931 invoice. It is allowed in full UBL 2.1 but not in the EN16931 subset.

Severity

Warning

Rule set

EN16931

Country

All EU

Fix type

AUTO-FIX

Confidence

95%

Engine Classification

Remove disallowed PayerFinancialAccount from PaymentMeans

Confidence: 95% · Applied automatically in pipeline

What is UBL-CR-680?

UBL-CR-680 is a warning validation rule defined in the EN16931 specification. It validates the PayerFinancialAccount element in the UBL invoice XML.

This is a soft validation failure. The invoice may pass initial transmission, but non-compliant values in this field can cause problems during tax audits, buyer-side processing, or downstream VAT reconciliation.

Target path: //cac:PaymentMeans/cac:PayerFinancialAccount

Get API Access

Why This Error Matters

Invoice will be rejected by EN16931 validators. These conformance rules prohibit UBL attributes and elements not in the EN16931 e-invoicing profile. Remove the disallowed attribute or restructure the element.

UBL-CR-680 is a soft failure. The invoice may pass initial validation, but the non-compliant field can cause issues at the receiving end — tax authorities may flag it during audits, buyer ERP systems may fail to process it, or VAT reconciliation may produce mismatches. Fixing warnings before they accumulate prevents larger compliance gaps.

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

·Generates validation warning
·Fails EN 16931 business rule validation
·Error returned: UBL-CR-680
·Specification: EN16931

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before

<!-- Required block is missing -->
<!-- <cac:PayerFinancialAccount> ... </cac:PayerFinancialAccount> -->

After

<!-- Add the required block -->
<cac:PayerFinancialAccount>
  <!-- child elements -->
</cac:PayerFinancialAccount>

Technical Reference

XPath//cac:PaymentMeans/cac:PayerFinancialAccount

SpecEN16931

Operationremove

StrategyRemove disallowed PayerFinancialAccount from PaymentMeans

Common Causes

·PaymentMeans contains PayerFinancialAccount element
·cac:PayerFinancialAccount not in EN16931 credit transfer
·Payer account only allowed in BG-19 direct debit
·Credit transfer should not include debtor account
·ERP exports payer account in wrong payment context

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

Handle UBL-CR-680 Automatically in Your Pipeline

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

Get API Access View API Documentation

UBL-CR-680:A UBL invoice should not include the PaymentMeans/PayerFinancialAccount