How do I fix BR-DE-1?

This requires user input to resolve. Review the relevant cbc: and cac: elements in your Invoice XML and provide the correct value. (BR-DE-1). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is BR-DE-1 a critical error?

Yes, BR-DE-1 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can BR-DE-1 be automatically fixed?

Many instances of BR-DE-1 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

errorDEUXRechnung (Germany)

`BR-DE-1`:Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16)...

German XRechnung requires Payment Instructions (BG-16). You must specify how the invoice should be paid.

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: Payment Means Code, Payment Account (IBAN)

What is BR-DE-1?

BR-DE-1 is a fatal validation rule defined in the XRechnung (Germany) specification (DEU national rules). It checks whether eine rechnung (invoice) muss angaben zu "payment instructions" (bg-16)....

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.

Get API Access Test This Error ↓

Why This Error Matters

Invoice rejected. German invoices must include payment information for processing.

BR-DE-1 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-1
·Specification: XRechnung (Germany)

Before / After

Failing XML

<Invoice>
  <!-- Issue: Payment means type code is required for German invoices -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per XRechnung (Germany) -->
</Invoice>

Technical Reference

SpecXRechnung (Germany)

StrategyRequires user input: Payment method and details (bank account, payment terms). Cannot auto-generate payment instructions.

Common Causes

·XRechnung invoice missing payment instructions
·BG-16 Payment Instructions group not present
·German invoice without payment method details
·PaymentMeans section not exported
·Template missing payment instructions for Germany

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

Related Errors

BR-DE-01

Invalid Leitweg-ID Format

BR-DE-02

Payment terms text recommended

BR-DE-2

Die Gruppe "SELLER CONTACT" (BG-6) muss übermittelt werden.

Last updated: 27 February 2026

Share this guide:

Handle BR-DE-1 Automatically in Your Pipeline

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

Get API Access View API Documentation

BR-DE-1:Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16)...