Account
English
DeutschFrançaisPolskiNederlands
CheckerXRechnungZUGFeRDFactur-XPeppolUBLKSeFAPIPricingAccount

DE-R-019: The element "Payment account identifier" should contain a valid IBAN if code 58 SEPA…

Peppol national rule · Warning · UBL

StandardPeppol BIS Billing 3.0 country rules (NL, DE, IT, SE, DK, NO, GR, IS)CountryGermanySeverityWarning: the invoice is accepted but should be correctedSyntaxUBLBusiness terms
  • BT-81 Payment means type code
  • BT-84 Payment account identifier
Applies toOnly when the seller (or for some rules the buyer) is in the named country: the rule is triggered by the country code of the party. Dutch rules implement NLCIUS, German rules the XRechnung requirements inside Peppol.

Official rule text

[DE-R-019] The element "Payment account identifier" (BT-84) should contain a valid IBAN if code 58 SEPA is provided in "Payment means type code" (BT-81).

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

(/ubl-invoice:Invoice/cac:PaymentMeans[cbc:PaymentMeansCode = (30,58)] | /ubl-creditnote:CreditNote/cac:PaymentMeans[cbc:PaymentMeansCode = (30,58)])[$supplierCountryIsDE and $customerCountryIsDE]

Test (XPath):

not(cbc:PaymentMeansCode = '58') or                     matches(normalize-space(replace(cac:PayeeFinancialAccount/cbc:ID, '([ \n\r\t\s])', '')), '^[A-Z]{2}[0-9]{2}[a-zA-Z0-9]{0,30}$') and                     xs:integer(string-join(for $cp in string-to-codepoints(concat(substring(normalize-space(replace(cac:PayeeFinancialAccount/cbc:ID, '([ \n\r\t\s])', '')),5),upper-case(substring(normalize-space(replace(cac:PayeeFinancialAccount/cbc:ID, '([ \n\r\t\s])', '')),1,2)),substring(normalize-space(replace(cac:PayeeFinancialAccount/cbc:ID, '([ \n\r\t\s])', '')),3,2))) return  (if($cp > 64) then string($cp - 55) else  string($cp - 48)),'')) mod 97 = 1

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 DE-R-019 mean?

DE-R-019 is a peppol national rule: The element "Payment account identifier" (BT-84) should contain a valid IBAN if code 58 SEPA is provided in "Payment means type code" (BT-81).

Will my invoice be rejected because of DE-R-019?

No. DE-R-019 is a warning: the invoice is accepted but the recipient sees the notice. Fix it anyway, warnings often become errors in later rule versions.

Which formats does DE-R-019 apply to?

Only when the seller (or for some rules the buyer) is in the named country: the rule is triggered by the country code of the party. Dutch rules implement NLCIUS, German rules the XRechnung requirements inside Peppol. Syntax: UBL.

Source: Peppol BIS Billing 3.0.20 national rules (November 2025). Catalogue generated from the official rule sets on 2026-10-15.