BR-61: what it means and how to fix it
When the payment means is a credit transfer (codes 30 and 58), the payment account identifier must be present.
| Rule | BR-61 |
|---|---|
| Standard | EN 16931-1, the European standard for electronic invoices |
| Severity | Error (the invoice is not conformant) |
| Concerns | BT-84: Payment account identifier (IBAN) |
How to fix it
Add the IBAN of the account to be paid, or change the payment means code.
Where the field is in the XML
| Term | CII (XRechnung-CII, ZUGFeRD, Factur-X) | UBL (XRechnung-UBL, Peppol) |
|---|---|---|
| BT-84 Payment account identifier (IBAN) | ram:SpecifiedTradeSettlementPaymentMeans/ram:PayeePartyCreditorFinancialAccount/ram:IBANID | cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:ID |
From your code
curl -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/xml" \
--data-binary @invoice.xml "https://agent-data-tools.revmesh2074.workers.dev/einvoice/validate"The answer lists every broken rule with its number, the field, a message with the figures from your file and the fix. E-invoice API: validate, convert to JSON, and create XRechnung or ZUGFeRD XML from JSON.
Questions
What does BR-61 mean?
When the payment means is a credit transfer (codes 30 and 58), the payment account identifier must be present. It is a rule of EN 16931-1, the European standard for electronic invoices.
How do I fix BR-61?
Add the IBAN of the account to be paid, or change the payment means code.
Is BR-61 an error or a warning?
An error: a validator reports the invoice as not conformant, and a recipient that validates incoming e-invoices can reject it.
Related rules
- BR-DE-19: With payment means code 58 (SEPA credit transfer) the payment account should be a correct IBAN.
Rule numbers are those of EN 16931-1; the explanation is ours. Not tax or legal advice.