Reference
Markdown exportBT-23 Business Process Type Identifier
Identifies the business process that this invoice is part of, enabling proper handling and routing of electronic invoices
BT-23 (Business process type) identifies the procurement process the invoice belongs to, as a URN. Mandatory in XRechnung 3.x (BR-DE-16); optional in base EN 16931. The receiver uses it to select the right validation profile. Example: urn:fdc:peppol.eu:2017:poacc:billing:01:1.0.
BT-23 · EN 16931 / XRechnung 3.x
BT Reference Card
Canonical EN 16931 / XRechnung facts for this business term — citable from this anchor.
- BT code
BT-23- Name
- Business Process Type Identifier
- Cardinality
- Mandatory (M) — XRechnung; Optional (O) — EN 16931
- Business group
- BG-2 PROCESS CONTROL
- Data type
- Text
- Example value
urn:fdc:peppol.eu:2017:poacc:billing:01:1.0- Common error
- BR-DE-16: Business process type (BT-23) must be provided. The value must be a valid URN identifying the business process the receiver uses to apply validation rules.
- XRechnung note
- XRechnung 3.0+ promotes BT-23 from optional to mandatory (BR-DE-16) so that the receiver can pick the correct CIUS-specific rule pack. Free text is rejected; use a registered URN.
Quick answer
Identifies the business process that this invoice is part of, enabling proper handling and routing of electronic invoices
Invoice basics
Core document identifiers, dates, process identifiers, and high-level invoice context.
Quick actions
In plain language
Identifies the business process that this invoice is part of, enabling proper handling and routing of electronic invoices
Identifies the business process that this invoice is part of, enabling proper handling and routing of electronic invoices
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
What you usually enter here
URN (Uniform Resource Name) format with standard identifiers
Typical valid values include: urn:fdc:peppol.eu:2017:poacc:billing:01:1.0, urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0, urn:cen.eu:en16931:2017#conformant#urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
Mandatory since XRechnung 3.0.1 (2024) to align with PEPPOL BIS 3.0 requirements and ensure EN16931 compliance
What goes wrong often
Avoid values like: BASIC, DE-INVOICE, simple-billing,
Relevant rule codes: BR-DE-30, BR-61
Examples in context
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
Valid Examples
Use these points as the practical checks for this section.
- urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
- urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0
- urn:cen.eu:en16931:2017#conformant#urn:fdc:peppol.eu:2017:poacc:billing:01:1.0
Invalid Examples
Use these points as the practical checks for this section.
- BASIC
- DE-INVOICE
- simple-billing
XML mapping and field facts
Open the technical reference if you need XML paths, validator rule codes, legal wording, or schema-specific mapping details.
Field ID:
BT-23
Data Type:
text
Cardinality:
1..1
Requirement:
Mandatory
Max Length:
200 characters
Since Version:
XRechnung 3.0.1+
XML Implementation
/Invoice/cbc:ProfileID/CrossIndustryInvoice/ExchangedDocumentContext/ram:BusinessProcessSpecifiedDocumentContextParameter/ram:IDValidation Rules
BR-DE-30
Business Process Type Identifier (BT-23) must be provided
BR-61
Business Process Type Identifier must have a valid URN format
Why the standard cares about this field
Business Context
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
Legal Requirement
Mandatory since XRechnung 3.0.1 (2024) to align with PEPPOL BIS 3.0 requirements and ensure EN16931 compliance
FAQ
What is the Business Process Type Identifier used for?
It identifies the specific business process context for the invoice, enabling systems to apply the correct validation rules and processing logic.
Is BT-23 mandatory in XRechnung 3.0.1?
Yes, BT-23 became mandatory starting with XRechnung 3.0.1 to ensure compliance with PEPPOL BIS 3.0 standards.
Which identifier should I use for German public administration?
Use "urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0" for invoices to German public authorities.