TppPDFMetaData.ParseZUGFeRDFile & XRechnung 3.0
Hello everyone,
I have question regarding the method TppPDFMetaData.ParseZUGFeRDFile.
The code in this function currently looks for the XML node
However when using XRechnung 3.0 this node does not seem to exist. The XML starts with the lines:
Since version 23.00 ReportBuilder still generates a PDF with attachment, because of the added Pokémon exception handling in TppPDFMetaData.AddZUGFeRDMetaInfo.
However the PDF will not have any metadata and not regarded als valid PDF by validation tools.
Are there plans to extend the function TppPDFMetaData.ParseZUGFeRDFile?
Best regards
David
I have question regarding the method TppPDFMetaData.ParseZUGFeRDFile.
The code in this function currently looks for the XML node
However when using XRechnung 3.0 this node does not seem to exist. The XML starts with the lines:
<?xml version="1.0" encoding="UTF-8"?> <ubl:Invoice xmlns:ubl="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <cbc:CustomizationID xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID> <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>Therefore the function raises an exception.
Since version 23.00 ReportBuilder still generates a PDF with attachment, because of the added Pokémon exception handling in TppPDFMetaData.AddZUGFeRDMetaInfo.

However the PDF will not have any metadata and not regarded als valid PDF by validation tools.
Are there plans to extend the function TppPDFMetaData.ParseZUGFeRDFile?
Best regards
David
Comments
ZUGFeRD and XRechnung are two distinct electronic invoicing methods. ZUGFeRD combines a visual PDF with an attached XML invoice, where XRechnung consists solely of an XML invoice.
For a ZUGFeRD XML invoice to be valid, it must meet the CII specifications (version 1.x) or EN 16931 specifications (version 2.x). Although the XRechnung format is compatible with ZUGFeRD, it does not necessarily fulfill all its specifications.
Specifically, your XML invoice appears to be missing the (ZUGFeRD) required "GuidelineSpecifiedDocumentContextParameter" node, which is causing the exception.
To successfully attach an XRechnung XML invoice to a ZUGFeRD PDF, the XRechnung XML must be updated to comply with the ZUGFeRD 2.3 specifications, incorporating the XRechnung profile.
For further details, please refer to the following link:
https://www.ferd-net.de/en/downloads/publications/details/zugferd-23-english
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com