Sales Pack - XInvoice

[yuri]

Tried validation on https://invoice-portal.de/en/xrechnung-validator/.

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.

[yuri]

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.

[ThomasB]

Maybe check this: https://en.e-rechnung-bund.de/e-invo...yer-reference/

https://xeinkauf.de/faq/xrechnung (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.

[yuri]

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

Quote:

"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?

[yuri]

There's a general EN 16931 standard that is extendable by design. Different countries have different standards upon that basic once. Usually, it's additional validation rules or more restrictive rules. The e-invoice should also contain the specification identifier.

I consider an international (Europe only for now) solution, not only German/France specific.

[shalmaxb]

As far as I understand, there are general European rules, complemented with some countrywise rules. The Link from peterberlin provides the german version, but there is an english verson for developers: https://en.e-rechnung-bund.de/e-invo...are-companies/
I am not able to judge all this, but perhaps it could help you yuri .

[yuri]

I have some questions which are important for the future implementation. Will appreciate if anybody with experience could answer.

1. Would we need the ability to export the same invoice in different formats? When one format is needed for a customer, another – for our company. For example, XRechnung and RO_CIUS.

2. Would we need the ability to export different invoices in different formats? For example, one invoice for Romanian customer in their regional format/standard, another invoice – in German format.

Thanks

[yuri]

One more project that may be useful https://github.com/easybill/zugferd-php.

[yuri]

There's some movement in Dompdf into supporting PDF/A. That's good news for us.

[yuri]

> EspoCRM is not suitable for generating invoices in Germany.

Maybe still suitable as it's not yet 2025.

[peterberlin]

Maybe the link will help:

https://www.e-rechnung-bund.de/faq/

https://www.e-rechnung-bund.de/faq/x...hen%20Rechnung.

According to the GOBD, EspoCRM is not suitable for generating invoices in Germany.
peter

[radek]

Hello,

in Czech Republic we have ISDOC format which is XML file that is usally sent alongside invoice (invoice.isdoc), or directly embeddedinto PDF as some PDF attachments.

Here is a github repo with code sample https://github.com/isdoc/isdoc.pdf

There is also documentation available, but it's in Czech https://isdoc.cz/6.0.2/doc/isdoc.html

Since we had to do multiple XML exports for various accounting software we also made a module for XML templates which work the same as PDF templates, but instead of printing to PDF it will save as XML file (while the same handlerbars and template helpers are available) - this could possibly be a good approach for this too, since clients may need to make small adjustments to the XML files. From my experience it's impossible to cover all types of clients, some are in OSS (one stop shop) some are "special vat payers or something" and XML templates do add a lot of flexibility to this, since you can use if statements, template helpers etc.

[item]

Hi,
maybe here we understand more (it's my case )

https://www.mustangproject.org/

At the right you see a sample PDF containing Factur-X/ZUGFeRD metadata generated with the Mustang library. If you open it in Adobe Acrobat Reader just click on the paperclip symbol to see the embedded ZUGFeRD XML structure. It has been created using the invoice class. Which you can also use to create a XRechnung.

So for dompdf.. maybe insert xml in a comment tag <!-- {{xml}} -->

Maybe.

[yuri]

Hi,

The question whether the PDF and XML have to be separate or somehow combined (XML in PDF?). Is there any implementation among other popular ERP/CRM systems?

EDIT. It looks that the "ZUGFeRD" defines combination of XML and PDF. The problem is implementation. We use Dompdf lib, not sure it does support it. It does not support PDF/A mode yet. Haven't yet researched deeply.

May be useful: https://github.com/atgp/factur-x

[hom]

Hello everyone,

I would also very much welcome an integration of the XML invoice in the EspoCRM sales pack.

As Bernhard has already written, this standard will be mandatory in Germany from 2025, and later probably throughout the EU. As this is intended to combat tax evasion, it can also be assumed that the xml invoice will remain. In contrast to some other digitization projects

As far as I can see, there are standards for Germany (X-Rechnung) and France (Factur-X). Both standards are included in the ZuGFerd standard 2.2. This may offer a good approach for implementation. The advantage of the ZuGFerd standard is that a PDF invoice with an integrated XML invoice is generated.

Why does it make sense to combine PDF and xml invoices?
The obligation to use XML invoices initially only applies to the B2B sector. Invoices to private individuals or amounts up to EUR 250 are not subject to the xml invoice obligation. The xml obligation also does not (yet) apply to cross-border invoices either.

However, as EspoCRM is intended to be flexible all areas can be covered with that. Here is the link to the ZuGFerd standard: https://www.ferd-net.de/standards/zu...2.2/index.html

So it would be great if the option for xml invoicing could be included in the sales pack. As invoicing from EspoCRM works excellent so far, it would almost be a disaster to use a different program here.
You are welcome to contact me for tests.
Regards
Holger