FAQ

PEDIF receives the PDF document through the agreed input channel, matches it to an approved layout, captures the agreed fields, and checks the generated target output against defined rules. The result is then passed to the configured downstream process or made available for review if anything is unclear.

Yes. A useful starting point is a test with representative documents. The test assesses the layout, data quality, required fields, target format, and potential exceptions. It indicates suitability, but does not replace a full implementation or legal review.

For a new layout, sample documents, relevant fields, validation rules, the target format, and the handoff method are agreed. This results in an approved processing configuration or fingerprint for the agreed scope.

Protection depends on the agreed operating model and the approved technical and organizational measures. Before use, the data location, access rights, encryption, deletion, subprocessors, and data processing arrangements should be reviewed against the current evidence. Further information is available at: https://www.pedif.digital/en/security.

Recurring, text-based PDF documents with a stable structure are the most reliable. Whether scans or image files can be processed depends on the approved workflow and the recognition steps used. Suitability is assessed in advance using sample documents.

Separate processing for multiple tenants, legal entities, or business units can be included in a project. Whether and how this is implemented depends on roles, data spaces, routing rules, and the agreed operating model.

That depends on the input channel and the configured separation and routing logic. One or more documents per message can only be processed automatically if assignment, file separation, and exception handling are clearly defined.

Scans and image-based PDFs require additional image or OCR recognition and depend more heavily on readability and quality. Whether they are included in the approved scope is assessed using real examples.

Each relevant layout variant must be recognizable and assignable to the correct workflow. Recurring variants can be approved separately; new or changed layouts are treated as exceptions until they have been reviewed and, if necessary, configured.

A fingerprint describes the recurring characteristics of a document layout and the rules used to recognize and process relevant fields. It is followed by data validation and, where necessary, exception handling.

With hybrid formats such as ZUGFeRD or Factur-X, a visible PDF representation can remain part of the target format. With purely structured formats such as XRechnung, the XML file is the primary output. The representation produced depends on the selected target format and workflow.

Typically, the use case, documents, fields, target format, interfaces, and exceptions are agreed first. This is followed by testing, configuration, business review of the results, approval, and a controlled go-live.

Representative examples of the standard layout and relevant special cases are required, such as multi-page documents, discounts, credit notes, or different line-item tables. The number and selection are determined by the document variety and desired scope; there is no universal minimum quantity for every case.

Cross-border workflows can generally be assessed. However, the target format, mandatory fields, tax logic, transmission method, and local requirements differ by country and recipient. Business and legal assessment must be carried out separately.

Yes, provided the required format can be technically described, aligned from a business perspective, and approved for the target workflow. Mapping, validation, and the interface are defined for each implementation.

Processing time depends on the document type, input channel, validation, exception rate, and operating model. Binding response or processing times apply only if they have been agreed in writing for the specific service.

PEDIF is provided according to the agreed operating model. Whether cloud-based, customer-specific, or local deployment options are available must be confirmed technically and contractually for the specific use case.

The recipient, target format, and transmission method are determined through agreed attributes and routing rules, such as a partner ID, customer number, document content, or input channel. Unclear or conflicting information is not forwarded automatically, but treated as a review case.

A ZUGFeRD or Factur-X invoice is a PDF/A-3 file with embedded structured XML data. You can check whether an XML file is included by viewing the attachments in a PDF viewer. The file should also be checked against the required profile using a suitable validator.