Tungsten Automation Knowledge

Verify image for CII invoices (ZUGFeRD, Factur-X, XRechnung) differs from the original PDF

000045967 · Troubleshooting · Last Updated: Sep 11, 2026

ISSUE

For CII-based invoices (ZUGFeRD, Factur-X, XRechnung), the invoice image on the Verify screen differs from the originally provided PDF and may contain multiple pages.

CAUSE

For these formats, the Verify image is no longer the supplier's original embedded PDF. It is generated directly from the XML using that format's official visualization standard (for XRechnung, the official KoSIT stylesheet). The rendered image represents the full XML data as defined by that stylesheet; empty tags are omitted to avoid unnecessary noise.

The rendered image is built to contain every field present in the XML, while AP Essentials only extracts the fields defined in the field mapping. A field that isn't part of the mapping is still visible on the image, so it can still be manually roped and captured during verification if needed. 

The original PDF and XML are untouched and sent downstream exactly as received; the rendered image exists only for verification.

SOLUTION

The rendered image is a fuller, official representation of the XML, built directly from the format's own visualization standard, so it can be relied on as an accurate reflection of the invoice data. The legal invoice itself is never altered: the original PDF and XML continue unchanged through processing and downstream delivery.

REFERENCES

ZUGFeRD, Factur-X, and XRechnung Field Mapping

Applies to

ProductVersionBuildEnvironmentHardware
AP Essentials

Sections recovered from body HTML: issue, cause, solution, refs.

https://aio-eus-uat-cae-aif-app14-local.redglacier-35d7ee4f.eastus.azurecontainerapps.io/article/45967 | Article 000045967 | Printed Sep 30, 2026

Back to the article · use your browser's Print command, or save the PDF.