errorcountryDEUXRechnung (Germany)

BR-DE-23-b:Payment code 30 or 58 (bank transfer) must not include Card Payment (BG-18)...

Fix: Invoice Navigator automatically fixes this issue by correcting the `cac:CardAccount` element in your Invoice (BR-DE-23-b). Upload your invoice to fix this automatically.

Payment code 30 or 58 (bank transfer) must not include Card Payment (BG-18) or Direct Debit (BG-19) sections. Only Credit Transfer should be present.

Severity
Fatal
Rule set
XRechnung (Germany)
Country
DEU
Fix type
AUTO-FIX
Confidence
80%
Category
structural

Engine Classification

Ensure mandate reference is present for SEPA direct debit (code 59)

Confidence: 80% · Applied automatically in pipeline

What is BR-DE-23-b?

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

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

Target path: //cac:PaymentMeans[cbc:PaymentMeansCode='59']/cac:PaymentMandate/cbc:ID

Why This Error Matters

Invoice rejected. Conflicting payment methods cause processing errors.

BR-DE-23-b is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

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-23-b
  • ·Specification: XRechnung (Germany)

How to Fix It

1.

Find the missing or empty field

Check cbc:ID at //cac:PaymentMeans[cbc:PaymentMeansCode='59']/cac:PaymentMandate/cbc:ID. This field is required but is either missing or empty.

2.

Set the required value

Invoice Navigator automatically fixes this issue by correcting the `cac:CardAccount` element in your Invoice (BR-DE-23-b).

3.

Re-validate your invoice

Upload the corrected invoice to confirm BR-DE-23-b is resolved.

Before / After

Failing XML
<cac:PaymentMeans>
  <cac:CardAccount>INVALID_CODE</cac:CardAccount>
</cac:PaymentMeans>
Corrected XML
<cac:PaymentMeans>
  <cac:CardAccount>VALID_CODE</cac:CardAccount>
</cac:PaymentMeans>

Technical Reference

XPath//cac:PaymentMeans[cbc:PaymentMeansCode='59']/cac:PaymentMandate/cbc:ID
SpecXRechnung (Germany)
Operationset_default
StrategyEnsure mandate reference is present for SEPA direct debit (code 59)

Common Causes

  • ·Credit transfer payment has card or mandate details
  • ·PaymentMeansCode 30/58 with BG-18 or BG-19 present
  • ·Mixed payment types in single payment instruction
  • ·Card/mandate sections not removed for bank transfer
  • ·Template exports all payment sections regardless of type

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

Frequently Asked Questions

Payment code 30 or 58 (bank transfer) must not include Card Payment (BG-18) or Direct Debit (BG-19) sections. Only Credit Transfer should be present.

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

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

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

Related Errors

Related Content

Last updated: 14 April 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-DE-23-b

Auto-fix BR-DE-23-b in seconds

Upload your invoice and we fix this error automatically. Financial fields are never touched.