No announcement yet.

Sales Pack - XInvoice

  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Another questions regarding German invoices. XRechnung has a rule BR-DE-15 "For German suppliers, the element “Buyer reference“ (BT-10) shall be provided".


    "BT-10 Buyer reference: The Leitweg-ID is an identifier developed to address public entities in Germany and may be used within XRechnung. KoSIT does not provide any Leitweg-ID from German public authorities. Public authorities themselves should provide the Leitweg-ID to the issuers of electronic invoices."

    But, if XRechnung becomes mandatory not only for B2G but for B2B, how the Leitweg-ID can be provided/obtained?​​


    • #17
      Maybe check this: (german only, used translator)

      How is the routing ID (Leitweg ID) used to address XRechnung in B2B?

      When using XRechnung in B2B, no routing ID (Leitweg ID) is required for addressing XRechnung invoices. In the “Buyer reference (BT-10)” element, any other suitable identifier can be used for internal routing purposes. The “Buyer reference (BT-10)” element is merely a text field and does not use any schema definitions.


      • #18
        Thanks for pointing out information.

        > When using XRechnung in B2B, no routing ID is required to address XRechnung.

        But the standard tells that the field is mandatory. I understand, it will be up to the invoice issuer (Espo user) to specify some arbitrary value.


        • #19
          Tried validation on

          While XRechnung 2.3 requires the Buyer Reference, the 3.0 version allows to omit it.

          Checked the 3.0.1 specs (in German), it stipulates that some rules are applied only for B2G.

          Click image for larger version

Name:	image.png
Views:	117
Size:	14.9 KB
ID:	106924


          • #20
            Hello devs & community, is it possible to integrate the ZUGFeRD 2.X ( current Version at time of writing: ) Standard into EspoCRM? A new Law in Germany describes how an E-Invoice has to look in the future ( (transitional period beginn: 1.1.25 end: 1.1.28) ), it


            • #21

              yuri Thanks for putting my post in the correct place.

              As it looks for now:

              B2G -> XRechnung works 100%, perhabs ZUGFeRD will work too but without warrenty
              B2B -> ZUGFeRD: easy readable by humans AND has the XML Data integrated

              i think we should look at the following projects:

              Project horstoeko/zugferd

              This package provides only support for CII - not UBL

              Supported profiles
              • EN16931 Minimum
              • EN16931 Basic
              • EN16931 Basic WL
              • EN16931 Comfort
              • EN16931 Extended
              • EN16931 XRechnung 1.x
              • EN16931 XRechnung 2.x
              • EN16931 XRechnung 3.x

              Project horstoeko/ubl

              read and write xml files containing electronic invoice data in the UBL format


              Project horstoeko/orderx

              read and write xml files containing electronic orders data in all Profiles ( )


              direct Download for Zugpferd:

              Edit: format
              Last edited by user_4711; 06-12-2024, 01:35 PM.


              • #22
                XRechnung is already almost implemented.

                horstoeko/zugferd is not an option for us. We already use the PDF printing functionality based on dompdf which currently does not support PDF/A. Once they support it, we will be able to combine the current PDFs with the XRechnung XML. They plan to support it but no any timelines.


              • #23
                please take a look again at this place: we can use our created pdf documents and merge them with the xml data.

                ZUGFeRD vs XRechnung:

                File format:

                ZUGFeRD is a so-called hybrid format (PDF/A-3), consisting of a visible PDF part in which a machine-readable XML part is embedded. In contrast, the XRechnung is a pure XML file.


                The specification of a syntax ensures a uniform technical implementation of the e-invoice in the EU. The XML schemas UBL (=Universal Business Language) and CII (=Cross Industry Invoice) are considered permissible syntaxes. While ZUGFeRD can only be implemented in CII syntax, the XRechnung can be implemented in both syntaxes.

                Target group:

                The B2G sector, i.e. the sending of invoices to German authorities or the federal administration, was specified as the target or user group of the XRechnung invoice format. At the same time, ZUGFeRD emerged as the currently most widely used and therefore most accepted invoice exchange format between companies (B2B sector).
                Advantages and disadvantages:

                The X-Invoice was developed (specifically) for the B2G sector, while the ZUGFeRD format was specifically tailored to the needs of the business world. The latter format also covers the requirements of public administration from version 2.1.1 (Latest Version 2.2)
                Last edited by user_4711; 06-12-2024, 02:56 PM. Reason: additional Information: ZUGFeRD vs XRechnung


                • #24
                  Originally posted by user_4711i View Post

                  sounds great, but i only found this discussion about PDF/X PDF/A Support in dompdf

                  @user_4711​ Look here:
                  Last edited by ThomasB; 06-12-2024, 03:11 PM.


                  • user_4711
                    user_4711 commented
                    Editing a comment
                    thank you! i'll keep an eye on it, too.

                  • item
                    item commented
                    Editing a comment
                    i have "like" on github.. maybe the PR will be merged

                • #25
                  Yet another problem to solve is generating CII. Currently we only have UBL implementation.