Engine Classification
Financial or legal field · Modification blocked by policy
Reason: SEPA creditor identifier is issued by your bank and cannot be automatically determined. Contact your bank if you need this identifier.
What is BR-DE-30?
BR-DE-30 is a fatal validation rule defined in the XRechnung (Germany) specification (DEU national rules). It validates the ID element under PayeeParty > PartyIdentification in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: XPath: /Invoice/cac:PayeeParty/cac:PartyIdentification/cbc:ID[@schemeID="SEPA"]
Why This Error Matters
Invoice will be rejected by XRechnung validation. Without creditor identifier, SEPA direct debit cannot be processed - banks require this to authorize automatic payment collection.
BR-DE-30 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Validator Behavior
- ·Causes invoice rejection
- ·Rejected by XRechnung endpoints
- ·Error returned: BR-DE-30
- ·Specification: XRechnung (Germany)
How to Fix It
Add creditor ID
PayeeParty/PartyIdentification/ID
Set scheme
schemeID="SEPA"
Before / After
<Invoice> <!-- Issue: German SEPA direct debit requires creditor identifier. --> </Invoice>
<Invoice> <!-- Issue resolved per XRechnung (Germany) --> </Invoice>
Technical Reference
XPath: /Invoice/cac:PayeeParty/cac:PartyIdentification/cbc:ID[@schemeID="SEPA"]Common Causes
- ·Direct debit selected but creditor ID field not populated
- ·Seller has not registered for SEPA direct debit creditor ID
- ·Creditor ID stored in banking system not integrated with invoicing
- ·ERP system does not have field for creditor identifier
- ·Payment method changed to direct debit without adding required fields
Seeing this in production? The API handles BR-DE-30 automatically. See the fix response →
Frequently Asked Questions
SEPA direct debit requires creditor identifier.
Add creditor ID (Gläubiger-Identifikationsnummer). This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
Yes, BR-DE-30 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.
BR-DE-30 involves a financial or legal field that cannot be auto-modified by policy. Invoice Navigator detects and flags this error immediately, but the correction must be made manually in your ERP or invoicing software.
Related Errors
Related Content
Last updated: 3 March 2026
Validate your invoice
Drop your XML here to check for BR-DE-30
Detect BR-DE-30 before submission
This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.