Une identification de la spécification contenant l'ensemble complet des règles concernant le contenu sémantique, les cardinalités et les règles métier auxquelles les données contenues dans le document d'instance sont conformes. Ce champ identifie quelle spécification/profil de facturation est utilisé (par exemple, 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.
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.
/Invoice/cbc:CustomizationID/CrossIndustryInvoice/ExchangedDocumentContext/ram:GuidelineSpecifiedDocumentContextParameter/ram:IDurn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_2.3urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0urn:cen.eu:en16931:2017#conformant#urn:fdc:peppol.eu:2017:poacc:billing:international:aunz:3.0XRechnung✗ InvalidePEPPOL✗ InvalideEN16931✗ Invalideurn:custom:billing:1.0✗ InvalideXRechnung uses "urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0" for German public administration, while PEPPOL uses "urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0" for international B2B transactions. Both are based on EN 16931-1 but have different extensions and requirements.
For invoices to German public authorities, use the XRechnung identifier. For PEPPOL network transactions, use the PEPPOL BIS identifier. The choice depends on your recipient and the network through which the invoice will be transmitted. Check with your recipient or network provider for the required specification.
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.
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.
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".
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.
Notre convertisseur de factures alimenté par l’IA gère automatiquement toutes les exigences XRechnung, y compris la validation correcte des champs.