Hello everyone,
Have any of you already implemented a workflow to receive an e-invoice (Factur-X / ZUGFeRD) at the end?
The way I imagine the workflow would look like this:
Input (PDF) => Smart Form (recognize and extract/provide variables) => Data Output (store static XML template, with reference to the variables) => OUTPUT (e.g. ZUGFeRD - with specification of the generated XML file) => Script (delete the temporary XML file)
Since I'm not very familiar with XML, I'm wondering how I can write the article items, which are always different in every invoice, into this static XML template.
In the XML template, the item ITEM/article items should be dynamic and expand itself if necessary.
Does anyone have an idea or has this already been implemented?
Many thanks in advance.
Translated with DeepL.com (free version)
Workflow => Factur-X / ZUGFeRD
- 10 Views
- Last Post yesterday
Hi Tobias,
in the manual side you can see more info too about https://help.scanshare.com/home/output-formats/outputprofile-pdf/
About how the options works in our process: In general the user just need to provide the Invoice XML since ZUGFeRD is a PDF/A document with embedded the electronic invoice XML file (in the German / France format). So that path points to a valid government XML electronic invoice which needs to be embedded into the PDF before it gets certified as ZUGFeRD. Normally you may find those XML exported by ERP systems or delivered by electronic mailing.
To check the PDF you can use Adobe Acrobat with the Preflight tool and use the ZUGFeRD validation profile (recent Acrobat versions) or use one of the German tool provided for that such as this one: https://www.zugferd-community.net/en/open_community/validation.
About the modification dynamic of the XML since Scanshare is flexible as always 
, if you wish to create that XML you may create any workflow extracting the data in the best way (Smart Form, Smart OCR, Zone OCR, Barcode or any other way) for the target document(s) and outputting to a XML file, which is then used in the PDF output profile, however it is up to you to make sure the XML respects the e-invoice specification to produce a valid ZUGFeRD PDF.
So for modify the XML you can use a simple script that read the standard XML as template, modify it with your %VARIABLE% and after that save the modified XML inside the Invoice XML path setted into output profile setting. However it is one of the way but another one can be a sample data export that create a valid XML and modify the data specified with your %VARIABLE% too.
I hope is clear but for specific case like your, we suggest always contact your Dealer/NOC first and in case of they contact the Scanshare support too for some quick tips 
Best regards,
Luca
