How do I fix BR-DE-25-a?

This requires user input to resolve. Provide the correct value for `cac:PaymentMandate` (BG-19). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is BR-DE-25-a a critical error?

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

Can BR-DE-25-a be automatically fixed?

Many instances of BR-DE-25-a 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-25-a`:When payment is by direct debit (SEPA), the mandate reference identifier is...

When payment is by direct debit (SEPA), the mandate reference identifier is required. This is the unique reference number that identifies the mandate agreement between the buyer and seller for automatic payment collection.

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: Mandate Reference ID

What is BR-DE-25-a?

BR-DE-25-a is a fatal validation rule defined in the XRechnung (Germany) specification (DEU national rules). It checks whether when payment is by direct debit (sepa), the mandate reference identifier is....

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 will be rejected by XRechnung validation. German public sector recipients require complete SEPA direct debit information for automated payment processing.

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

Before / After

Failing XML

<cac:PaymentMeans>
  <cac:PaymentMandate>INVALID_CODE</cac:PaymentMandate>
</cac:PaymentMeans>

Corrected XML

<cac:PaymentMeans>
  <cac:PaymentMandate>VALID_CODE</cac:PaymentMandate>
</cac:PaymentMeans>

Technical Reference

SpecXRechnung (Germany)

StrategyRequires user input: SEPA mandate reference identifier. User must provide the unique mandate ID from their direct debit agreement. Cannot derive - must come from contractual documentation.

Common Causes

·Direct debit payment selected but mandate field left empty
·ERP system does not capture SEPA mandate information
·Mandate reference stored in separate system not linked to invoicing
·Manual invoice creation without access to mandate database
·Payment method changed to direct debit after invoice created

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

Related Errors

BR-DE-01

Invalid Leitweg-ID Format

BR-DE-02

Payment terms text recommended

BR-DE-1

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

Last updated: 27 February 2026

Share this guide:

Handle BR-DE-25-a 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-25-a:When payment is by direct debit (SEPA), the mandate reference identifier is...