Attestwire › Rule reference › BR-50

BR-50 Credit transfer details must include the account identifier

noun · EN 16931 · fatal · BG-17 / BT-84

For a sample invoice, the library reports: The invoice supplies credit transfer information (BG-17) — a payment account name (BT-85) — but no payment account identifier (BT-84). BT-84 is the only part of the group that actually receives money; the name and the BIC describe the account, they do not identify it.

Business term

BG-17 / BT-84

Severity

fatal

The fix

Set payment.iban to the receiving account. If you did not mean to give credit transfer details, remove payment.accountName and payment.bic as well — a half-filled BG-17 is worse than none, because it looks answered.

A passing value

"payment": { "meansCode": "58", "iban": "DE02120300000000202051", "accountName": "Acme GmbH" }

What the library returns

The full error returned by @attestwire/en16931. It includes the rule ID, affected field and suggested correction. Developers can use this object in their application:

{
  "rule": "BR-50",
  "field": [
    "BG-17",
    "BT-84"
  ],
  "severity": "fatal",
  "message": "The invoice supplies credit transfer information (BG-17) — a payment account name (BT-85) — but no payment account identifier (BT-84). BT-84 is the only part of the group that actually receives money; the name and the BIC describe the account, they do not identify it. A payer's system reads BT-84 and nothing else.",
  "fix": "Set payment.iban to the receiving account. If you did not mean to give credit transfer details, remove payment.accountName and payment.bic as well — a half-filled BG-17 is worse than none, because it looks answered.",
  "example": "\"payment\": { \"meansCode\": \"58\", \"iban\": \"DE02120300000000202051\", \"accountName\": \"Acme GmbH\" }",
  "xpath": "/ubl:Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:ID",
  "docsUrl": "https://attestwire.com/rules/BR-50"
}

xpath is always a UBL path. On a CII invoice, look for the matching CII field instead.