Skip to main content

BR-DE-11 Deliver-to post code must be provided when a delivery address is used

Under the XRechnung standard specification, whenever a distinct delivery address (BG-15 / DELIVER TO ADDRESS) is included on the invoice, the deliver-to postal code (BT-78) must be explicitly provided. Automated logistics and public procurement inventory management systems rely on exact postal codes to route deliveries and reconcile receipt vouchers.

Problem Description

ERROR

German XRechnung rule (KoSIT, BR-DE) · XRechnung 3.0

Interactive pipeline

Click a stage to see what it checks, or type a rule ID to light up the stage that reports it.

Try:

BR-DE-11 XRechnung rule (Germany)

Reported in stage 3: National rules (CIUS).

Level error: the report recommends rejecting the invoice.

Stage 3 · What it checks

  • The specification identifier in BT-24 selects the rule set, for example XRechnung 3.0 or Peppol BIS Billing 3.0.
  • XRechnung adds the German BR-DE rules: buyer reference (BT-10), seller contact, payment instructions.
  • Peppol adds PEPPOL-EN16931 and country rules. XRechnung applies some PEPPOL-EN16931 rules too.

Example codes

Typical fix

Fill the fields the rule set requires in your master data, such as the Leitweg-ID in BT-10 or the seller contact.

A validator checks an e-invoice in stages. First the file must be well-formed XML that matches the UBL or CII schema (XSD). Then the EN 16931 business rules run: BR core rules, BR-CO calculations, BR-CL code lists, BR-DEC decimals and VAT-category rules such as BR-S. Next come the national or network rules that BT-24 selects: BR-DE for XRechnung, PEPPOL-EN16931 for Peppol BIS Billing. The report lists every failed rule: one error means reject, warnings alone still mean accept. BR-DE-11: XRechnung rule (Germany), reported in the stage “National rules (CIUS)”. Rule sets: KoSIT validator 1.6.3 with the XRechnung configuration of 31 Aug 2026 (EN 16931 artefacts 1.3.16), Peppol BIS Billing 3.0.21.

Context and Significance

Rule BR-DE-11 is checked alongside BR-DE-10: both city and postal code are mandatory whenever the delivery address block BG-15 is populated.

Solution

In your ERP shipping or sales order configuration, ensure the ship-to location includes the postal code. In UBL 2.1 syntax, populate <cbc:PostalZone> within <cac:Delivery><cac:DeliveryLocation><cac:Address>. In UN/CEFACT CII syntax, populate <ram:PostcodeCode> within <ram:ApplicableHeaderTradeDelivery><ram:ShipToTradeParty><ram:PostalTradeAddress>. If physical delivery address details are not applicable, omit the delivery address container completely.

Quick actions

Valid Examples

  • Deliver-to address with BT-78 = "80331" and BT-77 = "München"
  • Deliver-to address with BT-78 = "70173" and BT-77 = "Stuttgart"

Invalid Examples

  • Delivery address (cac:Delivery/cac:DeliveryLocation/cac:Address) contains street and city but omits cbc:PostalZone
  • Postal code left as empty string while other address elements are populated

Code Examples

Valid XML
<cac:Delivery>
  <cac:DeliveryLocation>
    <cac:Address>
      <cbc:StreetName>Lagerweg 12</cbc:StreetName>
      <cbc:CityName>Stuttgart</cbc:CityName>
      <cbc:PostalZone>70173</cbc:PostalZone>
      <cac:Country><cbc:IdentificationCode>DE</cbc:IdentificationCode></cac:Country>
    </cac:Address>
  </cac:DeliveryLocation>
</cac:Delivery>
Invalid XML
<cac:Delivery>
  <cac:DeliveryLocation>
    <cac:Address>
      <cbc:StreetName>Lagerweg 12</cbc:StreetName>
      <cbc:CityName>Stuttgart</cbc:CityName>
      <cac:Country><cbc:IdentificationCode>DE</cbc:IdentificationCode></cac:Country>
    </cac:Address>
  </cac:DeliveryLocation>
</cac:Delivery>

Affected Fields

Validation Tools