From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: XRechnung
Date: Fri, 10 Nov 2023 18:47:22 +0100 [thread overview]
Message-ID: <bd8537f2-02ec-4486-bc60-5444141948e8@fiee.net> (raw)
In-Reply-To: <300cb0c2-b374-c6fc-7c13-f0237d07810c@gmx.es>
Am 10.11.23 um 18:07 schrieb Pablo Rodriguez via ntg-context:
> On 11/10/23 11:29, Henning Hraban Ramm wrote:
>> Am 10.11.23 um 09:37 schrieb juh+ntg-context--- via ntg-context:
>>> Hi,
>>>
>>> does anyone produce the XML-based invoice called XRechnung with ConTeXt?
>>> I don't know if XRechnung is the european name or only used in Germany?
>>
>> In German it’s ZUGFeRD, the international name is Factur-X:
>> https://www.pdf-tools.com/pdf-knowledge/zugferd-standard-electronic-invoices/
>
> According to https://www.ferd-net.de/standards/zugferd/, they may even
> be two different things (but I haven’t checked it).
Yes, sorry, XRechnung is the German federal version of EN-16931 for
invoicing public contractees, while Factur-X (F) = ZUGFeRD (D)
apparently is a different implementation of the same standard, stemming
more from industry standards, that _can_ include XRechnung.
Yet another mishmash of norms and standards where probably every
implementor only supports a part (just an experienced guess).
>> I always wanted to implement it, but never actually tried.
>> It’s based on PDF/A, and I’m not sure about the proper workflow to get that.
>
> Someone told some time ago that https://github.com/speedata/publisher
> implements ZugFeRD. Again, no idea how or to which extent.
I remember talking to someone at a DANTE meeting about an implementation
for LaTeX, but I can’t find it on CTAN.
> https://zugferd.github.io/ provides more info. Version 2 of ZUGFeRD
> seems to be Factur-X (according to them).
>
> If you allow me the pun (as a foreigner and non-native speaker), the
> name seems to be too near to something like »Zug-Pferd« (I know it is
> nonsense in German, but ZUGFeRD seems the name for an act or a
> regulation [which German-speaking countries love to do]).
The acronym is not accidental for sure. Somone probably neighed for joy.
(Zugpferd = cart horse, draft horse, fig. also top seller)
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-11-10 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 8:37 [NTG-context] XRechnung juh+ntg-context--- via ntg-context
2023-11-10 10:29 ` [NTG-context] XRechnung Henning Hraban Ramm
2023-11-10 17:07 ` Pablo Rodriguez via ntg-context
2023-11-10 17:47 ` Henning Hraban Ramm [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd8537f2-02ec-4486-bc60-5444141948e8@fiee.net \
--to=texml@fiee.net \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).