add official XRechnung schema #91
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
add official XRechnung schema from XRechnung Bundle 3.0.2 - https://xeinkauf.de/dokumente/ The filenames were prefixed with the drafthorse standard and include paths adapted accordingly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
add official XRechnung schema from XRechnung Bundle 3.0.2 - https://xeinkauf.de/dokumente/
The filenames were prefixed with the drafthorse standard and include paths adapted accordingly.
I left the filenames unaltered (to keep changes from official download as little as possible and future compatibility) but it might make sense to simply use "XRECHNUNG".
Schema name currently is "FACTUR-X_XRECHNUNG_CrossIndustryInvoice_100pD16B".
I tested with guideline "urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0" and it seems to work. (Not that I really know what I'm doing here).
Should fix #54