1) Technical validation (mandatory)
Checks embedded XML against ZUGFeRD/EN-16931 rules and structural mandatory fields. Outcome: formally valid/invalid plus rule findings.
This page explains how Canary checks ZUGFeRD, Factur-X and e-invoices, which data is compared, where automated comparison reaches its limits, and when AI+ adds additional value.
Canary clearly separates standards validation, data comparison and context analysis. This shows which finding comes from which method.
Checks embedded XML against ZUGFeRD/EN-16931 rules and structural mandatory fields. Outcome: formally valid/invalid plus rule findings.
Compares payment- and tax-relevant fields from PDF view with XML values (e.g. IBAN, amounts, tax rate, date, invoice number).
EU AI analyzes context and plausibility in the PDF, prioritizes candidates better and helps with ambiguities that pure numeric matching cannot solve reliably.
Automated matching is essential, but not trivial. Different layouts and text structures can represent the same values very differently.
In addition to the 3 core stages, Canary adds targeted extra checks when prerequisites are met.
Looks for contradictory statements in PDF context and marks potential candidate conflicts transparently instead of assigning values silently wrong.
Checks VAT IDs only when required IDs and country constellation are available. If the service is down, the status is clearly shown as "currently unavailable".
For robust decisions, use check results in this order: