Account
English

BR-50: A Payment account identifier shall be present if Credit transfer information is…

EN 16931 core rule · Error · UBL / CII

StandardEN 16931-1 (European e-invoicing semantic model)SeverityError: the invoice is rejectedSyntaxUBL, CIIBusiness terms
  • BG-17 Credit transfer
  • BT-84 Payment account identifier
Applies toEvery EN 16931 invoice: XRechnung, ZUGFeRD 2.x / Factur-X (profiles EN 16931, EXTENDED, XRECHNUNG), Peppol BIS Billing 3.0, and national CIUS such as the Dutch NLCIUS or the Italian/Spanish profiles.

Official rule text

[BR-50] A Payment account identifier (BT-84) shall be present if Credit transfer (BG-17) information is provided in the Invoice.

Why this error occurs

The value is present but does not match the required pattern: wrong date format, an IBAN with a wrong check digit, an e-mail address without a valid structure, a URL without scheme, or a text with forbidden characters.

How to fix it

Correct the value so it matches the format named in the rule: dates as YYYY-MM-DD in UBL and YYYYMMDD with format="102" in CII, IBANs without spaces and with a valid checksum, e-mail addresses with exactly one @, URLs starting with http:// or https://.

What the validator checks

Checked element (context):

UBL

cac:PaymentMeans[cbc:PaymentMeansCode='30' or cbc:PaymentMeansCode='58']/cac:PayeeFinancialAccount

Test (XPath):

normalize-space(cbc:ID) != ''

CII

//ram:SpecifiedTradeSettlementPaymentMeans[ram:TypeCode='30' or ram:TypeCode='58']/ram:PayeePartyCreditorFinancialAccount

Test (XPath):

(ram:IBANID) or (ram:ProprietaryID)

Check your invoice

Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.

Check your invoice →

Same check via API:

curl -F file=@invoice.xml https://einvoicechecker.com/v1/validate

Related rules

Frequently asked questions

What does BR-50 mean?

BR-50 is a en 16931 core rule: A Payment account identifier (BT-84) shall be present if Credit transfer (BG-17) information is provided in the Invoice.

Will my invoice be rejected because of BR-50?

Yes. BR-50 is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals) reject the invoice until it is fixed.

Which formats does BR-50 apply to?

Every EN 16931 invoice: XRechnung, ZUGFeRD 2.x / Factur-X (profiles EN 16931, EXTENDED, XRECHNUNG), Peppol BIS Billing 3.0, and national CIUS such as the Dutch NLCIUS or the Italian/Spanish profiles. Syntax: UBL and CII.

Source: EN 16931-1:2017 schematron (CEN TC434, via Peppol BIS 3.0.20). Catalogue generated from the official schematron on 2026-10-14.