All explained rules

BR-61: A transfer with no account to transfer to. How to fix it

The invoice states a credit transfer as the payment means (BT-81) but gives no account (BT-84).

Error: the invoice is refusedFrom the European norm EN 16931

The rule, in its own words

If the Payment means type code (BT-81) means SEPA credit transfer, Local credit transfer or Non-SEPA international credit transfer, the Payment account identifier (BT-84) shall be present.

Fields involved: BT-81, BT-84

What the rule checks

The rule checks a condition: if the payment means is a credit transfer, an account identifier must be present too. For other payment means, such as direct debit or card, the rule does not apply.

Why files fail it

  • The payment means was set but no bank details are held in the master data.
  • The IBAN is in the PDF layout but not in the structured data.
  • A transfer was chosen as the payment means when payment is actually by direct debit. In that case it is the payment means that is wrong, not the account.

How to fix it

  1. Add the IBAN. The field is "Payment account identifier" (BT-84) in the standard.
  2. If the payment means is wrong, correct that instead: a direct debit does not require an account identifier here.
  3. Then check BR-DE-19 as well: the IBAN also has to be arithmetically sound.

Check your file

Upload your invoice. It runs through the same official validator that applies this rule, and you see immediately whether it passes now.

Check an invoice

or drop it here

XRechnung XML, or a ZUGFeRD / Factur-X PDF. Up to 10 MB.

  • Run against the official EN 16931 and XRechnung rules
  • Your file is deleted the moment the result appears
  • No sign-up, and a result in seconds

What to do next

An invoice with errors will be rejected. Build a compliant one from the PDF you already have, or enter the details yourself. Either way you get a file that passes.