50.1 Processing Mode and File Types (XML, PDF, XML from PDF)
50.1.1 Overview ¶
E-invoices arrive in two file forms: as plain XML (XRechnung) or as a PDF with embedded XML (ZUGFeRD/Factur-X). A profile’s processing mode (see chapter 8.7) defines which form the profile processes and which file the tasks refer to. This chapter explains the connections.
50.1.2 What the mode actually controls ¶
| Effect |
Details |
| File selection in the monitored folders |
“Process XML file” mode: only .xml files; the two PDF modes: only .pdf files. Other file types are ignored. |
| Reference file of the tasks |
“Process PDF file” mode: rename/move/print/… act on the PDF. The two other modes: the tasks act on the XML (in “XML from PDF” mode on the extracted XML file). The file tasks show the reference file in their name (“Rename PDF file” or “Rename XML file”). |
| Extraction (“XML from PDF” mode only) |
The embedded XML is automatically extracted to a temporary folder - no configuration needed. To store the XML file permanently, use the Save XML file task (see chapter 9). |
| Invoice data |
Read from the XML in all modes - in PDF mode from the embedded XML |
50.1.3 Which mode for what? ¶
| Situation |
Recommended mode |
| Invoice intake as XRechnung XML (e.g. via Peppol or email) |
Process XML file |
| Invoice intake as ZUGFeRD PDF; the PDF is to be filed, printed, forwarded |
Process PDF file |
| A follow-up system (accounting, archive) expects XML files, but ZUGFeRD PDFs are delivered |
Extract XML from PDF file and process it |
50.1.4 Mixed intake ¶
If both XML and PDF invoices arrive in one inbox, set up two profiles on the same folder - one per mode. This is exactly how the two demo profiles are built (see chapter 50.3). Since each profile only considers “its” file extension, the profiles do not interfere with each other.