Reference
Markdown exportBT-24 Specification Identifier
An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms. This field identifies which invoicing specification/profile is being used (e.g., XRechnung, PEPPOL BIS).
BT-24 (Specification identifier / CustomizationID) names the specification the document conforms to. Mandatory under EN 16931. XRechnung 3.0 uses urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0; the XRechnung extension appends #conformant#urn:xeinkauf.de:kosit:extension:xrechnung_3.0. Legacy xoev-de 2.x identifiers and the Peppol BIS Billing identifier are not XRechnung 3.0 values.
BT-24 · EN 16931 / XRechnung 3.x
BT Reference Card
Key EN 16931 and XRechnung facts for this business term.
- BT code
BT-24- Name
- Specification Identifier
- Cardinality
- Mandatory (M)
- Business group
- BG-2 PROCESS CONTROL
- Data type
- Identifier
- Example value
urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0
Quick answer
An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms. This field identifies which invoicing specification/profile is being used (e.g., XRechnung, PEPPOL BIS).
Invoice basics
Core document identifiers, dates, process identifiers, and high-level invoice context.
Quick actions
In plain language
An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms. This field identifies which invoicing specification/profile is being used (e.g., XRechnung, PEPPOL BIS).
An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms. This field identifies which invoicing specification/profile is being used (e.g., XRechnung, PEPPOL BIS).
Critical for electronic invoice processing as it determines which validation rules, business logic, and technical requirements apply to the invoice. Systems use this identifier to select the appropriate processing pipeline and validation schema. Essential for interoperability between different e-invoicing networks and standards.
What you usually enter here
URN (Uniform Resource Name) format following the pattern: urn:cen.eu:en16931:2017#[compliant|conformant]#[specification-specific-identifier]
Typical valid values include: urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0, urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0#conformant#urn:xeinkauf.de:kosit:extension:xrechnung_3.0
Mandatory for all XRechnung invoices since version 1.0. Required by EN 16931-1 standard and essential for compliance with German e-invoicing regulations and PEPPOL network requirements.
What goes wrong often
Avoid values like: XRechnung, PEPPOL, EN16931, urn:custom:billing:1.0
Relevant rule codes: BR-01, BR-DE-21
Examples in context
Critical for electronic invoice processing as it determines which validation rules, business logic, and technical requirements apply to the invoice. Systems use this identifier to select the appropriate processing pipeline and validation schema. Essential for interoperability between different e-invoicing networks and standards.
Mandatory for all XRechnung invoices since version 1.0. Required by EN 16931-1 standard and essential for compliance with German e-invoicing regulations and PEPPOL network requirements.
Valid Examples
- urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0
- urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0#conformant#urn:xeinkauf.de:kosit:extension:xrechnung_3.0
Invalid Examples
- XRechnung
- PEPPOL
- EN16931
- urn:custom:billing:1.0
- urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_2.3
- urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0
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-24
Data Type:
identifier
Cardinality:
1..1
Requirement:
Mandatory
Max Length:
200 characters
Since Version:
XRechnung 1.0+
XML Implementation
/Invoice/cbc:CustomizationID/CrossIndustryInvoice/ExchangedDocumentContext/ram:GuidelineSpecifiedDocumentContextParameter/ram:IDValidation Rules
BR-01
BR-01
BR-DE-21
BR-DE-21
Next step
Check whether your XRechnung declares XRechnung 3.0 in BT-24
The free validator selects the rule set by the value in BT-24. With the XRechnung 3.0 identifier it applies the XRechnung rules. The plain EN 16931 identifier is checked only against the EN 16931 rules, not as XRechnung. A missing or other value matches no rule set, and the file is rejected. If you create the XRechnung from a PDF, the converter sets BT-24 to the XRechnung 3.0 identifier.
Free, no account needed. XML file up to 2 MB.
Why the standard cares about this field
Business Context
Critical for electronic invoice processing as it determines which validation rules, business logic, and technical requirements apply to the invoice. Systems use this identifier to select the appropriate processing pipeline and validation schema. Essential for interoperability between different e-invoicing networks and standards.
Legal Requirement
Mandatory for all XRechnung invoices since version 1.0. Required by EN 16931-1 standard and essential for compliance with German e-invoicing regulations and PEPPOL network requirements.
FAQ
What is the difference between XRechnung and PEPPOL specification identifiers?
XRechnung 3.0 uses "urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0"; invoices that use the XRechnung extension use "urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0#conformant#urn:xeinkauf.de:kosit:extension:xrechnung_3.0". Peppol BIS Billing 3.0 is a different CIUS with its own identifier, "urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0"; it is not an XRechnung BT-24 value. Both build on EN 16931-1 but apply different rules.
How do I choose the correct specification identifier for my invoice?
Use the identifier of the specification the recipient requires, not of the transport channel. German public buyers usually require the XRechnung identifier, also over Peppol (E-Rech-V § 4 also allows other EN 16931-compliant formats); other Peppol recipients usually need the Peppol BIS Billing identifier. Check the required specification with your recipient. Legacy identifiers such as "urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_2.3" belong to XRechnung 2.x and are not valid for XRechnung 3.0 invoices.
What happens if I use the wrong specification identifier?
Using an incorrect specification identifier will cause validation errors and invoice rejection. The receiving system relies on this field to apply the correct validation rules. Always verify the required specification with your invoice recipient before submission.
Are there regional variations of specification identifiers?
Yes, different countries and regions may have their own CIUS (Core Invoice Usage Specification) based on EN 16931-1. For example, Australia/New Zealand uses "urn:cen.eu:en16931:2017#conformant#urn:fdc:peppol.eu:2017:poacc:billing:international:aunz:3.0". Always use the specification required by your target market.
How does BT-24 relate to BT-23 (Business Process Type)?
BT-24 defines the technical specification and validation rules, while BT-23 defines the business process context. Both are mandatory in XRechnung 3.0.1+ and work together to ensure proper invoice processing. BT-24 tells the system “how to validate”, while BT-23 tells it “what business process this supports”.
Can I use custom specification identifiers?
No, you must use standardized specification identifiers that are recognized by the receiving systems. Custom identifiers will cause validation failures. Use only officially published identifiers from recognized standards bodies like CEN, PEPPOL, or national e-invoicing authorities.