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

Invoice Navigator automatically fixes this issue by correcting the `cac:PayeeFinancialAccount` element in your Invoice (BR-DE-25-b). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

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

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

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

Many instances of BR-DE-25-b 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-b`:Payment code 59 (direct debit) must not include Credit Transfer (BG-17) or...

Payment code 59 (direct debit) must not include Credit Transfer (BG-17) or Card Payment (BG-18) sections. Only Direct Debit Mandate (BG-19) should be present for SEPA direct debit payments.

Severity

Fatal

Rule set

XRechnung (Germany)

Country

DEU

Fix type

AUTO-FIX

Confidence

80%

Engine Classification

Ensure payment card information is present for card payment means codes

Confidence: 80% · Applied automatically in pipeline

What is BR-DE-25-b?

BR-DE-25-b is a fatal validation rule defined in the XRechnung (Germany) specification (DEU national rules). It validates the PrimaryAccountNumberID element under CardAccount in the UBL invoice XML.

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.

Target path: //cac:PaymentMeans[cbc:PaymentMeansCode='48' or cbc:PaymentMeansCode='54' or cbc:PaymentMeansCode='55']/cac:CardAccount/cbc:PrimaryAccountNumberID

Get API Access Test This Error ↓

Why This Error Matters

Invoice rejected. Conflicting payment methods cause processing errors. Direct debit requires only the mandate information.

BR-DE-25-b 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.

Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.

Validator Behavior

·Causes invoice rejection
·Rejected by XRechnung endpoints
·Error returned: BR-DE-25-b
·Specification: XRechnung (Germany)

Before / After

Failing XML

<cac:PaymentMeans>
  <cac:PayeeFinancialAccount>INVALID_CODE</cac:PayeeFinancialAccount>
</cac:PaymentMeans>

Corrected XML

<cac:PaymentMeans>
  <cac:PayeeFinancialAccount>VALID_CODE</cac:PayeeFinancialAccount>
</cac:PaymentMeans>

Technical Reference

XPath

//cac:PaymentMeans[cbc:PaymentMeansCode='48' or cbc:PaymentMeansCode='54' or cbc:PaymentMeansCode='55']/cac:CardAccount/cbc:PrimaryAccountNumberID

SpecXRechnung (Germany)

Operationset_default

StrategyEnsure payment card information is present for card payment means codes

Common Causes

·Direct debit payment has transfer or card details
·PaymentMeansCode 59 with BG-17 or BG-18 present
·Mixed payment types in single payment instruction
·Transfer/card sections not removed for direct debit
·Template exports all payment sections regardless of type

Seeing this in production? The API handles BR-DE-25-b 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-b 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-b:Payment code 59 (direct debit) must not include Credit Transfer (BG-17) or...