X-Rechnung Add-on

[apardods]

• Added de-xrechnung-v3 addon.
• Added eu-en16931-v2017 addon that handles universal normalization and validation required for compliance.
• Added iso and untdid "catalogues" used for storing universally available extensions.
• Removed Payment UNTDID references, now supported by catalogues.

[codecov]

Codecov Report

Attention: Patch coverage is 91.54676% with 47 lines in your changes missing coverage. Please review.

Project coverage is 80.27%. Comparing base (1b4a1e7) to head (219651d).
Report is 32 commits behind head on main.

Files with missing lines	Patch %	Lines
addons/de/xrechnung/instructions.go	86.15%	6 Missing and 3 partials ⚠️
bill/charges.go	65.21%	7 Missing and 1 partial ⚠️
bill/discounts.go	68.18%	6 Missing and 1 partial ⚠️
org/inbox.go	87.87%	3 Missing and 1 partial ⚠️
addons/de/xrechnung/invoices.go	89.65%	2 Missing and 1 partial ⚠️
addons/eu/en16931/bill.go	93.02%	2 Missing and 1 partial ⚠️
tax/regime_def.go	82.35%	2 Missing and 1 partial ⚠️
tax/tax.go	82.35%	2 Missing and 1 partial ⚠️
addons/eu/en16931/scenarios.go	0.00%	2 Missing ⚠️
bill/invoice.go	33.33%	0 Missing and 2 partials ⚠️
... and 2 more

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #393      +/-   ##
==========================================
+ Coverage   79.04%   80.27%   +1.22%     
==========================================
  Files         220      232      +12     
  Lines       10811    11251     +440     
==========================================
+ Hits         8546     9032     +486     
+ Misses       1910     1857      -53     
- Partials      355      362       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[samlown]

Its going in the right direction, but lot's of changes required. Please do closely look at the other example addons to make sure everything is as similar as possible. Take special note of the usage of validation.Skip for example also, this is important.

[cavalle]

Beautiful! Totally feels like the right way to separate the extensions, scenarios, validations and normalisations derived from EN16931 from those derived from each specific CIUS/Extension.