Order-X (specification and sample download) is for orders what Factur-X is for invoices: a UN/CEFACT XML file embedded in a PDF/A-3 file, with the PDF repeating on a visual level the data that is stored in the XML.


The main differences to Factur-X are

  • the process: Order-X foresees a reply, e.g. the acceptance or rejection of the order or a order change request
  • the XML standard. While Factur-X uses the UN/CEFACT Cross Industry Invoice (CII), Order-X of course uses the UN/CEFACT Cross Industry Order (CIO)
  • the XML standard version: For EN16931 compliance Factur-X has to stay with the 2016b-Version of CII while Order-X uses a 2020 version of CIO
  • the usual formal differences: Apart from a different filename of the embedded file (order-x.xml), the RDF data, the root node from the 2020 CIO (rsm:SCRDMCCBDACIOMessageStructure) and of course the typecode (220) are different from Factur-X. Just like back in ZUGFeRD 1, the profiles are Basic, Comfort and Extended with typecodes (=guideline IDs) being urn:order-x.eu:1p0:basic, urn:order-x.eu:1p0:comfort and urn:order-x.eu:1p0:extended. However, there are only minor differencies in the elements and attributes, e.g. “BilledQuantity” being “RequestedQuantity”.



It’s relatively safe to assume the EN16931 codelists can be used.


  • the Factur-X pythonlibrary also supports Order-X