errorDEUXRechnung (Germany)

BR-DE-3:Das Element "Seller city" (BT-37) muss übermittelt werden.

German XRechnung requires Seller City (BT-37). The seller's city must be specified.

Severity
Fatal
Rule set
XRechnung (Germany)
Country
DEU
Fix type
INPUT REQUIRED

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Seller City (BT-37)

What is BR-DE-3?

BR-DE-3 is a fatal validation rule defined in the XRechnung (Germany) specification (DEU national rules). It checks whether das element "seller city" (bt-37) muss übermittelt werden..

When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

Why This Error Matters

Invoice rejected. Complete seller address is mandatory for German invoices.

BR-DE-3 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

Validator Behavior

  • ·Causes invoice rejection
  • ·Rejected by XRechnung endpoints
  • ·Error returned: BR-DE-3
  • ·Specification: XRechnung (Germany)

Before / After

Failing XML
<Invoice>
  <!-- Issue: XRechnung requires Seller city (BT-37) -->
</Invoice>
Corrected XML
<Invoice>
  <!-- Issue resolved per XRechnung (Germany) -->
</Invoice>

Technical Reference

SpecXRechnung (Germany)
StrategyRequires user input: Seller city name. Cannot auto-derive from other address fields.

Common Causes

  • ·Seller address missing city for XRechnung
  • ·BT-37 Seller city not transmitted
  • ·German invoice requires seller city in address
  • ·AccountingSupplierParty/PostalAddress/CityName empty
  • ·Partial seller address without city name

Seeing this in production? The API handles BR-DE-3 automatically. See the fix response →

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle BR-DE-3 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.