BR-DE-1fatal

How to fix BR-DE-1

Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16) enthalten.

XRechnung rule from the KoSIT XRechnung 3.0 schematron (German CIUS of EN 16931). It applies only to invoices whose specification identifier (BT-24) is XRechnung. Such files are checked against EN 16931 and the KoSIT XRechnung rules instead of the full Peppol BIS rule set. Check your file with the XRechnung validator.

What this rule checks

EN 16931 makes the PAYMENT INSTRUCTIONS group (BG-16) optional, but XRechnung requires it. The invoice must contain at least one cac:PaymentMeans (CII: ram:SpecifiedTradeSettlementPaymentMeans) with a Payment means type code (BT-81). Depending on the code, BR-DE-23 to BR-DE-25 then require the matching details: an account (BG-17) for credit transfer, card data (BG-18) for card payment, or a mandate (BG-19) for direct debit.

Referenced business terms

This rule references the following EN 16931 business term. Click through for the full definition, the UBL XPath and the cardinality.

How to fix it

Add a cac:PaymentMeans block with cbc:PaymentMeansCode (e.g. 58 for SEPA credit transfer, 30 for credit transfer) and the payee account in cac:PayeeFinancialAccount. In CII, add ram:SpecifiedTradeSettlementPaymentMeans under ram:ApplicableHeaderTradeSettlement.

Common causes

  • The invoice only states payment details in free text (cbc:Note or payment terms).
  • The generator omits cac:PaymentMeans for invoices that are already paid or paid by other means.
  • cac:PaymentMeans was placed after cac:TaxTotal or inside the wrong parent, so it is not found at document level.
  • In CII, the payment means is missing under ram:ApplicableHeaderTradeSettlement.

Example: before (broken)

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <!-- ... header, parties ... -->
  <!-- cac:PaymentMeans is missing -->
  <cac:PaymentTerms>
    <cbc:Note>Zahlbar innerhalb von 30 Tagen</cbc:Note>
  </cac:PaymentTerms>
</Invoice>

Example: after (fixed)

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <!-- ... header, parties ... -->
  <cac:PaymentMeans>
    <cbc:PaymentMeansCode>58</cbc:PaymentMeansCode>
    <cac:PayeeFinancialAccount>
      <cbc:ID>DE75512108001245126199</cbc:ID>
      <cbc:Name>Muster GmbH</cbc:Name>
    </cac:PayeeFinancialAccount>
  </cac:PaymentMeans>
  <cac:PaymentTerms>
    <cbc:Note>Zahlbar innerhalb von 30 Tagen</cbc:Note>
  </cac:PaymentTerms>
</Invoice>

Related rules

Validate your invoice

Upload your corrected invoice to check it passes BR-DE-1 and all other EN 16931 and XRechnung (BR-DE) rules. Free, instant, no signup.