Hybrid Documents Are the New Normal. And Most AP Systems Still Can’t Handle Them.

AP teams are not losing time to bad software but they are losing time to a workflow built for a document world that no longer exists.

The assumption baked into most invoice processing setups is that an invoice arrives as a PDF. Something a human reads, approves, and hands off. That assumption has been quietly wrong for a few years now, and most finance operations did not notice until the format exceptions started creating real processing backlog.

The format shift that already happened

Factur-X and ZUGFeRD are live mandates. France’s first phase has taken effect this year. Germany extended its B2B e-invoicing requirement in January 2025. Italy has had FatturaPA running for years. These are not emerging edge cases from large enterprise trading partners, they are where the entire European invoicing infrastructure is heading.

What makes them structurally different is this: Factur-X and ZUGFeRD are technically identical since version 2.1. Both produce a PDF/A-3 file the finance team can read and approve normally, with a structured XML file embedded inside for automated ERP processing. One document, two processing requirements, running simultaneously.

AP systems built around PDF processing do not automatically extract the embedded XML. Pure XML pipelines cannot serve the reviewer who needs to read and sign off. Bridging that gap with manual workarounds, a separate queue, a conversion step, a colleague handling the exceptions, is how organizations absorb costs they are not measuring.

Why dropping an AI layer on top does not hold

The reflex right now is to add an AI model to the workflow and let it absorb format variation. It performs in controlled conditions. At production volume, it drifts. Confidence scores shift. Outputs that looked reliable in month one need human review by month three.

In AP, almost right is expensive. A misread line item does not surface as a system error, it surfaces as a reconciliation problem two weeks later, after someone already approved it.

Prompt drift is real. Model deprecation is a planning risk. A capture layer built entirely on a model you do not control introduces governance gaps easy to ignore until a compliance requirement makes them unavoidable. The teams running clean operations at volume use deterministic classification as the foundation and invoke AI selectively, where document quality or format variation actually requires it. Structured output feeds the ERP. That is the boundary.

IRISXtract consolidates paper invoices, standard PDFs, and structured formats including ZUGFeRD, XRechnung, Factur-X, and FatturaPA into one processing workflow. Hybrid invoices are handled as a single document: the XML layer extracted for automated ERP processing, the PDF preserved for human review and archival. Output is validated against business rules and regulatory requirements before anything reaches the ERP.

No separate queue for XML files. No manual conversion step eating time the AP team does not have. The Solution Pack Accounts Payable (SPAP) runs as an add-on to existing ERP infrastructure through standardized connectors, nothing rebuilt, no parallel migration.

If your current setup is treating hybrid invoices as exceptions, they are already becoming the standard volume.

See how it works in your environment — request a free demo

EInvoicing #AccountsPayable #DocumentAutomation #IRISXtract #DigitalTransformation #InvoiceProcessing #IRISaCanonCompany