Invora v1.4
Germany EN 16931 · BR-DE-2

How to Fix XRechnung Error BR-DE-2 (Seller Contact BG-6)

XRechnung 3.0 mandates seller contact point name (BT-41), telephone (BT-42), and electronic email (BT-43) inside BG-6.

Exact Fix

Include seller.contactName, seller.phone, and seller.email on every DE_XRECHNUNG_UBL or DE_XRECHNUNG_CII request.

Failing Payload
"seller": {
  "name": "Acme GmbH",
  "vatId": "DE123456789"
  // Missing contactName, phone, email -> BR-DE-2/5/6
}
Fixed Payload
"seller": {
  "name": "Acme GmbH",
  "vatId": "DE123456789",
  "contactName": "Finance Desk",
  "phone": "+49 30 5550199",
  "email": "billing@acme.de"
}
Verify Fix via Free Preflight API
curl -sS -X POST https://api.invora.dev/v1/einvoice/preflight -H "Content-Type: application/json" -d @invoice.json

Are BT-41 and BT-42 required for ZUGFeRD 2.2 too?

In ZUGFeRD 2.2 (EN 16931 profile) they are warnings, whereas XRechnung 3.0 treats them as blocking errors.