UBL-CR-680:A UBL invoice should not include the PaymentMeans/PayerFinancialAccount
Fix: 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. Upload your invoice to fix this automatically.
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.
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.
The invoice may pass transmission, but this non-compliance can cause problems during tax audits or buyer-side processing.
Target path: //cac:PaymentMeans/cac:PayerFinancialAccount
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 that can cause issues at the receiving end — tax audits, ERP processing, or VAT reconciliation mismatches.
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
How to Fix It
Locate the disallowed element
Open your invoice XML and find cac:PayerFinancialAccount at //cac:PaymentMeans/cac:PayerFinancialAccount. This element is not permitted in the target e-invoice profile and triggers UBL-CR-680.
Remove cac:PayerFinancialAccount
Delete the entire cac:PayerFinancialAccount block and its child elements. 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.
Re-validate your invoice
Upload the corrected invoice to confirm UBL-CR-680 is resolved. If your software consistently adds this element, contact your vendor about their e-invoice export settings.
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Required block is missing --> <!-- <cac:PayerFinancialAccount> ... </cac:PayerFinancialAccount> -->
<!-- Add the required block --> <cac:PayerFinancialAccount> <!-- child elements --> </cac:PayerFinancialAccount>
Technical Reference
//cac:PaymentMeans/cac:PayerFinancialAccountCommon 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 →
Frequently Asked Questions
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.
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.
UBL-CR-680 is a warning that may not always cause rejection, but indicates a compliance issue.
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.
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for UBL-CR-680
Auto-fix UBL-CR-680 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.