Skip to main content

BR-FX-EN-04 Delivery date or service period required (Factur-X / ZUGFeRD)

BR-FX-EN-04 is a rule of the Factur-X 1.09 / ZUGFeRD 2.5 Schematron for the BASIC and EN 16931 profiles. It applies when the seller or invoicer and the buyer or invoicee both have a German postal address and the invoice is not a down payment invoice (type code 386). The invoice must then contain the actual delivery date (BT-72), an invoicing period (BG-14) or a period on every invoice line (BG-26). Without BT-72, the delivery block must also hold data; the rule text asks for at least the deliver-to country (BT-80). The Schematron reports it as a warning.

Problem Description

WARNING

Factur-X / ZUGFeRD rule (FNFE-MPE and FeRD, BR-FX)

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-FX-EN-04 Factur-X / ZUGFeRD profile rule

Reported in stage 3: National rules (CIUS).

Level warning: on its own, the invoice is still accepted.

ZUGFeRD and Factur-X validators report this rule, not the XRechnung configuration.

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-FX-EN-04: Factur-X / ZUGFeRD profile rule, 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

KoSIT does not run this rule; a ZUGFeRD or Factur-X validator does. For strict ZUGFeRD and Factur-X output, Invoice-Converter.com goes further than the warning: the review step reports the missing date or period, and the file is not created until you add it. That is a product rule, not a requirement of the standard.

Solution

Add the actual delivery date (BT-72) when you know it. For services, add the invoicing period (BG-14, BT-73 and BT-74) or a period on each line (BG-26). If you give only a period, also add the deliver-to country (BT-80). Take the dates from the source documents; do not reuse the invoice date as a stand-in.

Quick actions

Valid Examples

  • BT-72 = 2026-10-15
  • BG-14 = 2026-09-01 to 2026-09-30 with BT-80 = DE

Invalid Examples

  • No BT-72, no BG-14 and no BG-26 on a domestic German invoice
  • BG-14 given, but no BT-80 and no other delivery data

Code Examples

Valid XML
<ram:ApplicableHeaderTradeDelivery>
  <ram:ActualDeliverySupplyChainEvent>
    <ram:OccurrenceDateTime>
      <udt:DateTimeString format="102">20261015</udt:DateTimeString>
    </ram:OccurrenceDateTime>
  </ram:ActualDeliverySupplyChainEvent>
</ram:ApplicableHeaderTradeDelivery>
Invalid XML
<ram:ApplicableHeaderTradeDelivery/>

Affected Fields

Validation Tools