Identifies the business process that this invoice is part of, enabling proper handling and routing of electronic invoices
BT-23 became mandatory with XRechnung 3.0.1 to ensure compatibility with PEPPOL BIS 3.0. Without this identifier, invoices will be rejected.
Critical for XRechnung 3.0.1+ compliance, this field ensures invoices are processed correctly within the European e-invoicing ecosystem and enables interoperability between different systems
Mandatory since XRechnung 3.0.1 (2024) to align with PEPPOL BIS 3.0 requirements and ensure EN16931 compliance
/Invoice/cbc:ProfileIDFull UBL context:
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
<cbc:ProfileID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:ProfileID>
<cbc:ID>INV-2025-001</cbc:ID>
<cbc:IssueDate>2025-01-27</cbc:IssueDate>
<!-- Other elements -->
</Invoice>/CrossIndustryInvoice/ExchangedDocumentContext/ram:BusinessProcessSpecifiedDocumentContextParameter/ram:IDurn:fdc:peppol.eu:2017:poacc:billing:01:1.0urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0urn:cen.eu:en16931:2017#conformant#urn:fdc:peppol.eu:2017:poacc:billing:01:1.0BASIC✗ InvalidDE-INVOICE✗ Invalidsimple-billing✗ InvalidIt identifies the specific business process context for the invoice, enabling systems to apply the correct validation rules and processing logic.
Yes, BT-23 became mandatory starting with XRechnung 3.0.1 to ensure compliance with PEPPOL BIS 3.0 standards.
Use "urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0" for invoices to German public authorities.
Our AI-powered Invoice Converter automatically handles all XRechnung requirements, including proper field validation.