Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EN16931 Validation artefacts v.1.3.13 #104

Open
SemikolonDEV opened this issue Nov 18, 2024 · 6 comments
Open

EN16931 Validation artefacts v.1.3.13 #104

SemikolonDEV opened this issue Nov 18, 2024 · 6 comments
Assignees

Comments

@SemikolonDEV
Copy link

Please provide EN16931 Validation artefacts v.1.3.13 (https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.13)

@bdewein bdewein self-assigned this Nov 20, 2024
@bdewein
Copy link
Collaborator

bdewein commented Nov 20, 2024

@SemikolonDEV the implementation of version 1.3.13 is planned for the next Bugfix Release (no set date, yet, probably around February)

@melo0187
Copy link

melo0187 commented Dec 5, 2024

@bdewein the effective date for EN16931 Validation artefacts v.1.3.13 is 15th of November 2024.
Does this make KoSIT validation using its latest validator-configuration non-compliant?

@phax
Copy link
Collaborator

phax commented Dec 5, 2024

@melo0187 to the best of my knowledge the EN 16931 validation artefacts don't provide a "use from" or "use until" date. This should be stated in the release: https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.13

But e.g. Peppol provides "not before" dates with their validation artefacts.

@melo0187
Copy link

melo0187 commented Dec 5, 2024

@phax thank you for replying!

I was just wondering, because in the EN 16931 release schedule it states:

Effective date: the date when compliant implementations of EN 16931 shall have the new version in operation.

This would mean that all implementations that do not yet use version 1.3.13 of the artifacts by their effective date would no longer be considered compliant with the standard 🤔

@phax
Copy link
Collaborator

phax commented Dec 5, 2024

Ah thanks - I wasn't aware of that list. The table indeed seems to be relevant. Leading it to the XRechnung authors to respond on the details.

@phax
Copy link
Collaborator

phax commented Dec 6, 2024

As the intent of the EN website is not 100% clear, reaching out to the EC will be necessary, to make sure that a joint understanding is reached.
In previous releases, it also deemed to be useful to not always use the latest version, due to breaking changes (and the EC not using semantic versioning for their rules).

So please stay tuned - it may take some time until an agreement is reached (especially due to the year-end season coming up)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants