UBL-CR-430: Remove Name from the financial institution of the payment service provider

The short answer

UBL-CR-430 is a warning raised when cbc:Name appears in the financial institution of the payment service provider (cac:PaymentMeans/cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cac:FinancialInstitution). EN 16931 has no business term for it, so remove the element. EN 16931 identifies the payment service provider by its identifier alone, cac:FinancialInstitutionBranch/cbc:ID (BT-86).

The warning on its own does not make the document invalid, though other rules still check what is there. Removing the element keeps the XML inside the EN 16931 model, which is what a receiver maps the invoice from.

What the rule checks

The rule checks one thing: whether cac:PaymentMeans/cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cac:FinancialInstitution/cbc:Name exists. Its value is not read.

It runs once against the whole document, so it is reported once however many times the document has the element, and the finding points at the document root rather than at the element: look for cac:PaymentMeans/cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cac:FinancialInstitution/cbc:Name in the XML.

The element sits inside cac:FinancialInstitution, which UBL-CR-664 reports wherever it appears, so a document with it reports both.

How an integration ends up here

Possible causes, from the shape of the rule rather than from measured usage:

• The source system holds the value, and the mapping writes it because UBL 2.1 has a place for it.
• A general UBL 2.1 library writes every element and attribute it has a value for, whether or not EN 16931 uses it.
• A mapping built for another UBL-based document, such as an order, a despatch advice or a national profile, is reused for Peppol BIS Billing.

How to fix it

1. Stop writing cac:PaymentMeans/cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cac:FinancialInstitution/cbc:Name.
2. EN 16931 identifies the payment service provider by its identifier alone, cac:FinancialInstitutionBranch/cbc:ID (BT-86).
3. Remove the enclosing cac:FinancialInstitution too: UBL-CR-664 reports it wherever it appears.

Validate your corrected invoice

Before and after

These are fragments, not complete documents. The complete synthetic documents they come from are linked below.

Fragment of the invoice with the warning: Name in the financial institution of the payment service provider

<cac:FinancialInstitutionBranch>
  <cbc:ID>EXAMPLE-BRANCH</cbc:ID>
  <cac:FinancialInstitution>
    <cbc:ID>EXAMPLE-1</cbc:ID>
    <cbc:Name>Example</cbc:Name>
  </cac:FinancialInstitution>
</cac:FinancialInstitutionBranch>

Fragment of the corrected invoice: the same lines without FinancialInstitution

<cac:FinancialInstitutionBranch>
  <cbc:ID>EXAMPLE-BRANCH</cbc:ID>
</cac:FinancialInstitutionBranch>

The invoice with the warning has <cbc:Name>Example</cbc:Name> in the financial institution of the payment service provider, and the corrected invoice is the same document without cac:FinancialInstitution. It reports this warning and UBL-CR-664, and is valid on every layer.

Where it applies

• Applies to UBL Invoice and CreditNote alike; the recorded example is an invoice.
• The warning comes from the EN 16931 layer's rules for the UBL syntax. In the recorded example the schema layer passes: the element is valid UBL 2.1 and is only outside the EN 16931 model.

Related rules

• UBL-CR-664 reports FinancialInstitution, which encloses this element
• UBL-CR-431: Address in the financial institution of the payment service provider
• Browse every rule in the reference
• Background: Understanding EN 16931 validation errors

Scope and source

Written for Peppol BIS Billing 3.0.21 (May 2026), EN 16931 1.3.16, as applied to UBL 2.1 Invoice and CreditNote documents. Other profiles, syntaxes and releases can define this identifier differently. Guidance version 2026-09-29.1: source checked 2026-09-29, explanation last updated 2026-09-29.

The official definition of UBL-CR-430 carries the normative wording and test. This page is our explanation of it, not a copy.

Guidance does not change the engine verdict. Fixing this finding does not mean the document passes every layer, and validation does not certify legal or tax compliance or transmit a document over Peppol.