Describe the issue
XMLport for exporting credit memos to the Peppol BIS3 XML format was probably created as a copy of the invoice export, because it has the same structure of elements. But the XML file generated by this XMLport is not valid against Peppol UBL CreditNote scheme.
The XML element TaxPointDate is misplaced and should be moved rigth after the IssueDate element.
In the standard implementation of the providers, TaxPointDate value is empty and therefore it is not exported to the XML file and, therefore, the XML file without TaxPointDate is valid. But when the implementation of interface "PEPPOL Document Info Provider" is overridden and TaxPointDate has a value, the validation fails.
Expected behavior
The XML element TaxPointDate should be placed according to the XSD scheme, or as there is a definition on https://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-creditnote/tree/.
Steps to reproduce
A new implementation of the interface is needed and there should be variable TaxPointDate filled.
Additional context
No response
I will provide a fix for a bug
Describe the issue
XMLport for exporting credit memos to the Peppol BIS3 XML format was probably created as a copy of the invoice export, because it has the same structure of elements. But the XML file generated by this XMLport is not valid against Peppol UBL CreditNote scheme.
The XML element
TaxPointDateis misplaced and should be moved rigth after theIssueDateelement.In the standard implementation of the providers,
TaxPointDatevalue is empty and therefore it is not exported to the XML file and, therefore, the XML file withoutTaxPointDateis valid. But when the implementation ofinterface "PEPPOL Document Info Provider"is overridden andTaxPointDatehas a value, the validation fails.Expected behavior
The XML element
TaxPointDateshould be placed according to the XSD scheme, or as there is a definition on https://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-creditnote/tree/.Steps to reproduce
A new implementation of the interface is needed and there should be variable
TaxPointDatefilled.Additional context
No response
I will provide a fix for a bug