eDocPrintPro PDF/A – Version 3.29.0 – supports the e-billing standard ZUGFeRD 2.0 / EN 16931 / Factur-X 1.0

The eDocPrintPro version 3.29.0 now also supports the current e-billing standards – ZUGFeRD 2.0 / EN 16931 and Factur-X 1.0. These are based on PDF/A-3 where the billing records are embedded as an XML file in the PDF as a file attachment.


  • Selection of e-billing standards – ZUGFeRD 2.0 / EN 16931 / Factur-X 1.0
  • Selection of a profile supported by the standard (MINIMUM, BASIC WL, BASIC, EN 16931, EXTENDED)
  • Use predefined (path, name) XML / select XML via file dialog
  • Automatically delete XML after embedding in PDF (Yes/No)

Requirement: A XML file valid according to the selected standard and profile must already be ready before printing. The XML file is not extracted from the print data.

Download – eDocPrintPro PDF/A & ZUGFeRD

GhostScript 9.27 Setup

PDF2PDFA and the e-invoice standard ZUGFeRD 2.0 / EN 16931 / Factur-X 1.0

ZUGFeRD 2.0 / EN 16931 / Factur-X:

Important prerequisites for the acceptance of electronic invoices are above all the use of a standardized data format and the legal framework conditions, which can be used by boh the sender and the recipient.

In June 2017, the EU created a standard format for electronic invoices, the European standard EN 16931. The aim of this EU standard: Electronic invoice exchange is to be standardized and legally guaranteed throughout Europe.

The previous ZUGFeRD standard 1.0 had to be adapted to the new standard. ZUGFeRD 2.0 (published on March 11, 2019) was developed as part of a Franco-German collaboration, in close coordination with the French Standard Factur-X 1.0 and is technically identical to this. Using ZUGFeRD 2.0, electronic invoices can be created, that comply with EU standard EN 16931 and EU Directive 2014/55/EU. Details about the electronic invoice can also be found on the pages of the European Commission. ZUGFeRD 2.0 also uses the global standard UN/CEFACT XML in the form of Cross Industry Invoice. This could even give ZUGFeRD 2.0 a worldwide perspective.

The new ZUGFeRD version 2.0, like version 1.0, combines a PDF/A-3 invoice file (visual representation of the invoice data as a digital format instead of the classic paper invoice) with an invoice file in XML format embedded in the PDF/A-3 document.

ZUGFeRD 2.0 profiles:

Several profiles are planned for ZUGFeRD 2.0 and Factur-X. The «EN 16931» profile replaces the ZUGFeRD 1.0 «Comfort» profile and complies fully with the EU standard, which however only defines the core elements of an invoice. With the «Extended» profile, additional information can be recorded in an electronic invoice, for example by industry or according to legal requirements. In addition, «Basic» and «Basic WL» have defined two more profiles for smaller suppliers.

ZUGFeRD is suitable for organizations of all sizes and, thanks to EN-16931 compliance, has an expanded, international significance. The profile «EN 16931» is recognized by all European administrations. Since November 2018, electronic invoices have been required in Business to Government (B2G) traffic in the EU.

With version 1.2.0 of the PDF2PDFA converter component, ZUGFeRD 2.0 and Factur-X documents can now be generated from a PDF and the corresponding XML.

Download – Demo & Test Application – PDF2PDFA Converter >>>

PDFmdx – Read position data via group / subgroup fields

In addition to document fields, PDFmdx can also read position data. Position data is lists or tables with rows and columns. These are typically found on invoices to cite several items in the document. We use the term “sliding group / subgroup. One or more columns (= fields) in on or more rows, on one or more pages, are searched and read in a vertically defined area.

From the PDFmdx version 3.5.0 there is a 2-stage structure where in addition to the groups a subgroup level is also possible. One or more subgroup datasets can be recognized and read out for a group dataset. There are documents with 2-stage position data, eg. in the case of textiles or clothing where an item (number, description) can also have a “sub-level” with sizes or color specifications. The item itself is simply listed and in the level below there are the quantities / prices for individual characteristics.

Two-level readout of position data:

  • “Document/Group/Subgroup” fields define the detection level.

  • An area defined by 2 red horizontal boundary lines will be scanned on all pages of the document for the group (red boxes) and subgroup (green boxes) records.

  • The specified conditions are used to identify and read out the group (G) and subgroup (U) data records.

  • Along with the lowest-level records, the information of the group and document fields is also available.

For tests and as a starting point for your own tests, we have created two example templates with PDF test files. The *.pmdx templates only need to be imported into the PDFmdx Editor via drag&drop and the output path may need to be adjusted. For processing, it is then necessary to create a job with input and error folders in the PDFmdx processor and to select the two test templates for the job.

Download – PDFmdx – Templates and examples for two-level reading of position data >>>
Download – PDFmdx Template Editor & Processor >>>

PDFmdx version 3.5.3 available

New features PDFmdx version 3.5.3:

  • Field / Area OCR / Invert area / Always execute OCR:

Normally for PDFmdx processing, PDF files are used as input, which already contain text – either “normal” PDF or scanned PDF which have received an additional text layer via a previous OCR process (eg. via AutoOCR or FileConverterPro).

PDFmdx also has an integrated OCR function to determine the text in the areas of the positioned fields from the image information.

With the general PDFmdx OCR settings it is possible to specify how the texts from the PDF are to be obtained – “Original”, “OCR” or “SmartOCR”. With “Original” the text is always taken from the PDF, with “OCR” the text is always obtained via a PDFmdx OCR process, even if a text already exists in the PDF. With the “SmartOCR” setting, the PDFmdx OCR function is only executed if there is no text in the PDF, otherwise the existing text in the PDF is taken. These settings generally apply to the entire template and all associated layouts.

In this context, there are now 2 new functions that allow to recognize white text on a black background.

Individual areas with white text on a black background can not be recognized via an automatic OCR process, because before the OCR process the area would have to be inverted in order to be recognized. This can only be done interactively by selecting the area manually.

In the PDFmdx Editor it is now possible to activate the option “Invert Area” in the field configuration. In this case, the field area is inverted for the OCR processing. This creates black text on a white background which can be recognized by the OCR.

There is another new field function “Execute OCR always” with which the general setting “SmartOCR” can be overridden. OCR recognition is then always executed for this field, even if an underlying text already exists.


  • PDFmdx Editor – find condition, call layout: There is now a search function to search in the conditions for a (partial) string forward and backward. A line in the conditions can thus be jumped to directly. The linked layout can then be called directly from the condition line. This feature makes it easy to work with a large number of conditions.

  • The web service functions have been revised. In the web service example the metadata can now also be downloaded as XML.
  • For the metadata XML, the new variables JobID, JobName, JobDescription and ProcessID have been added.

Download – PDFmdx Template Editor & Processor >>>

PDFPrint-FM version 1.3.0 – Start print processing via *.rd file trigger

With the PDFPrint-FM version 1.3.0, there is now also the possibility to trigger the start of the print processing not only via the PDF files to be printed, but via a “*.rd” file.

If a file with the extension “*.rd” is copied to a monitored folder or if it is available at a certain time, all PDF files for this event in the folder will be printed. This makes it possible to specify the exact time at which the printout of the PDFs should start and trigger it externally.

Download – PDFPrint-FM –  Folder Monitoring – Prints PDF´s >>>

FileConverterPro (FCpro) – DropConvert MultiOS Client for MS-Windows, MacOS, Linux available

FileConverterPro (FCpro) is a web service application to convert a wide range of document formats to PDF, PDF/A-1, PDF/A-3 or ZUGFeRD. It is also possible to convert entire document stacks, hierarchical document structures, email (MSG, EML) and ZIP containers into a complete PDF.

With the DropConvert MultiOS Client, there is now also a free FCpro Client application for Linux and MacOS besides MS-Windows.

It can be used to easily convert documents and scans with or without OCR into searchable PDF and PDF/A documents via a graphical user interface using drag&drop.

The DropConvert MultiOS Client communicates with a FCpro server via REST web service and was completely developed in JavaScript, independent of platform based on the ELECTRON framework.

Functions FCpro DropConvert MultiOS:

  • Converts Office, CAD and Image files to PDF, PDF/A and ZUGFeRD.
  • Conversion of container formats (eg. ZIP, MSG, EML) into a complete PDF.
  • Also generates searchable PDF via OCR from scans.
  • Communication with the FCpro server via REST/https – web service.
  • Destination folder presettable.
  • Insert files via Drag&Drop.
  • Selection of a conversion profile stored on the FCpro server.
  • Automatic or manual start of processing.

Userinterface – MS-Windows:

Userinterface – Ubuntu Linux:

Userinterface – macOS Mojave:

Download – FCpro DropConvert MultiOS Setup for MS-Windows >>>
Download – FCpro DropConvert MultiOS Setup for LINUX (deb) >>>
Download – FCpro DropConvert MultiOS Setup for LINUX (AppImage) >>>
Download – FCpro DropConvert MultiOS Setup for MacOS (dmg) >>>

PDFmdx Version 3.5.0 available

Innovations PDFmdx Version 3.5.0:

  • Subgroups – additional hierarchy for moving groups: A sliding group is used, for example, to recognize invoice items that occur several times in a document or on a page and to be able to form several data records from this. However, there are documents where these records require a further hierarchy level, if there are multiple sub-records under one heading, e.g. to differentiate different characteristics of an article according to color or size. This can be done either as a list or in the form of a matrix. In order to be able to recognize and read out such additional characteristics it is now possible to form “subgroups” for a moving group.

There are now 3 field levels – the “Document fields”, the “Group fields” and the “Subgroup fields”. Subgroup records are defined by conditions such as the group records. The output also provides the information of the document and the group for subgroup records.

For the output, you can configure whether – all data records are output, or whether the group or document records are to be suppressed. The fields of the higher levels are also available in the group/subgroup dataset. To identify the data record level, the variable %RECORD_LEVEL% can be used with the values (D)ocument, (G)roup, (S)ubgroup.

The fields of the different levels are displayed in different colors in the PDFmdx Editor – document fields “Blue”, group fields “Red” and subgroup fields “Green”.

The working/search area for the moving group/subgroup is represented in the PDFmdx Editor by 2 horizontal red lines, which can be positioned vertically in the preview. The search for data records takes place only within the specified range.

  • MS-SQL Database Support for Metadata / Log & Error Log Function: In addition to exporting the metadata to an XLSX/CSV/XML file, there is now also the option to write the records into MS-SQL database tables. The read-out variables are written as documents/groups/subgroup data sets with configurable fields and contents, the log table with a fixed structure.

MS-SQL Export Functions:

    • Configuration – MS-SQL Server / Database.
    • Create / delete SQL tables / delete data from the tables.
    • Create / delete SQL columns in the selected table.
    • For each template, the SQL export can be activated and the SQL table can be selected. Fields (variables) or fixed text can be assigned to any SQL column.
    • Enable SQL – Logging / Error Log. The name of the log table is configurable.
    • The SQL log contains the following information: PROCESS_ID, computer name (WsName), user name (UserName), template (Template), layout, status (OK, ERROR), error code (ErrorCode), error message as text (ErrorMessage), information about the input/output file (InputPath, InputFileName, InputFolder, OutputPath, OutputFileName, OutputFolder), start/end of processing (StartTime, EndTime), processing time (ProcessingTime).

PDFmdx error codes in the log:

    • 0 = Successful processing.
    • 1 = No pages remaining in the PDF.
    • 2 = Configured stationery could not be found.
    • 3 = Missing license.
    • 4 = Error loading text plugin.
    • 5 = Error writing the PDF file.
    • 6 = No matching template/layout found for the specified criteria.
    • 7 = Error writing printer (PCF) configuration file.
    • 8 = Processing error.
    • 9 = Error creating the output folder.
    • 10 = Error creating the output file.
    • 11 = Error when overlaying/underlaying the stationery.
    • 12 = Error while signing.
    • 13 = Error when sending emails.
    • 14 = Error writing metadata.
    • 15 = Error generating the XML file.

  • PDFmdx Editor – Test Functions: The test feature in PDFmdx Editor and PDFmdx Processing are now based on the same component. This ensures that the result of the “Test” in the PDFmdx Editor, for the recognition, the splitting and the reading, yields the same result as for the processing by the PDFmdx Processor.

In a PDFmdx template you can configure if and how a layout should be identified by conditions. In the “Test” function in the PDFmdx Editor, the conditions are checked, the recognized layout is identified and the fields specified in the layout are read out. On the test mask there is now a checkbox to ignore the layout recognition/criteria. The fields are then read out and displayed only via the manually selected layout.

  • Field substring from the end: The substring field function is now not only possible from the beginning of a field, but also from the end (switchable).

  • New OCR version, several recognition languages: The field OCR function for fields has been updated and is now based on Tesseract Version 4.0. As a result, it is now possible to recognize multiple languages.

  • Default values for fields – layout related: In addition to the function to give a general value, there is now also a function to assign an individual default value for a field for each layout. A variable is assigned the default value if the field was not positioned on a layout or if the field was positioned but nothing can be read because the area is empty (=blank). This allows the layout recognition of a variable to assign a fixed value – eg. a customer number that can not be read directly from the document.
  • New “Composite” field type: The “Composite” type allows you to create combined fields, that consist of several other fields or text. Such composite fields are available for output (folder, filename, metadata), but not for conditions. These fields can be composed of variables of the documents, groups and subgroups.

  • Option – No remaining pages – Do not move document to the error folder: When splitting, deleting pages (cover pages) and deleting blank pages, it may happen that the remaining document no longer has any remaining pages left for processing. This option determines whether the “remaining document” is to be retained and moved to the error folder, or whether such a document is not preserved and the process is only logged in the error log.

  • Export of additional formats, selectable for – “Successful / Error / Both”: It is now also possible to convert PDF files, that have been moved to the error folder, into other formats (eg. TXT) to carry out further evaluations.

Download – PDFmdx Template Editor & Processor >>>

eDocPrintPro free / PDF/A & ZUGFeRD Version 3.28.4 available

eDocPrintPro version 3.28.4 is now based on the latest GhostScript version 9.27. This GhostScript update is required due to a known security vulnerability.

Download – eDocPrintPro free Version

Download – eDocPrintPro PDF/A & ZUGFeRD

GhostScript 9.27 Setup

PDFPrint-CS-FM – Hotfolder / Folder Monitoring for the PDFPrint-CS PDF Print Service

PDFPrint-CS-FM is a free add-on application for the PDFPrint-CS PDF print service to monitor one or more inbox folders and to remotely print all existing or newly added PDF files via web service.

The functions are fully in line with the PDFPrint-FM application, but the expression is not “local” but “remote” via HTTPS via the SOAP web service interface


Download – PDFPrint-CS-FM – Ordnerüberwachung für PDFPrint-CS >>>

FileConverterPro 1.0.88 – JPEG – automatically adapt DPI to the A4 page format

The current mobile phone cameras produce JPEG images with very high resolutions. The “DPI” in the JPEG file are set to 72 x 72dpi for display on the screen. This results in a calculated page format of over one meter due to the high resolution of the cameras. If such a JPEG file is converted to PDF then the 72dpi and the 3000-4000 pixels result in a PDF page size of e.g. 140 x 100cm. If such images are e.g. sent as attachments by email and the MSG/EML email file is converted to a PDF, one gets a PDF file containing e.g. all pages A4 format, but the JPEG attachment has a much larger page format.

To prevent this and get an approximately uniform page format when converting JPEG photos, there is now a new option to automatically adjust the “DPI” during conversion. An adjustable tolerance (from 10 to a maximum of 20%) is also taken into account, whereby the automatic adjustment only takes place if the DPI setting in the JPEG exceeds the page format “A4 + tolerance”.


Download – FileConverterPro (FCpro) (~600MB ) >>>