Surpress warnings: Validation-Warnung UBL-CR-646 A UBL invoice should not include the InvoiceLine SubInvoiceLine

itplr-kosit / validator-configuration-xrechnung

Configuration for validating documents against the German XRechnung standard using the KoSIT validation tool

https://xeinkauf.de/xrechnung/

Apache License 2.0

62 stars 17 forks source link

Surpress warnings: Validation-Warnung UBL-CR-646 A UBL invoice should not include the InvoiceLine SubInvoiceLine #36

Closed landrix closed 3 years ago

landrix commented 4 years ago

Warum wird diese Warnung ausgegeben? Nach Spezifikation ist das Dokument korrekt.

Sie können das zum Beispiel auch in der mitgelieferten Testsuite des aktuellen Releases mit der Datei 04.02a-INVOICE_ubl.xml nachprüfen.

landrix commented 4 years ago

Hi, is german language not welcome?

Why is this warning being given? According to the specification, the document is correct.

You can check this, for example, in the test suite supplied with the current release using the 04.02a-INVOICE_ubl.xml file.

rkottmann commented 4 years ago

German language is welcome and English is preferred for the international community.

Your question indicates, that you validated an Extension XRechnung document.

We (XRechnung Schematron Rules) allow SubInvoiceLines. However, the CEN Schematron rules https://github.com/ConnectingEurope/eInvoicing-EN16931/ (not maintained by us, but used in the configuration) disencourage use of SubinvoiceLines . That`s why you get warning from the CEN rules but an all is god from XRechnung Schematron rules.

Depending on your business case etc. you might just disregard the warning.

Does this answer your question?

landrix commented 4 years ago

can i suppress this warning for our customers? currently i validate an invoice like this:

java -jar validator\validationtool-1.4.0-java8-standalone.jar -s validator-configuration-200\scenarios.xml -h XRechnung-UBL-200.xml

rkottmann commented 3 years ago

No without changing the source code of the report generator, you can not fully supress the warning. In future releases we will add this feature though. But I can't give you a timeline right now.