EU e-invoicing compliance
Know exactly which e-invoice rules were checked.
Invogi's e-invoicing validation software reports deterministic control results on incoming invoices against an explicit technical profile and rule-set version. XRechnung, Peppol BIS, and EN 16931 invoices can be checked with the official reference validators, and KSeF invoices against the official FA(3) schema. Factur-X and ZUGFeRD technical validation is production-supported on Invoice Firewall for all five profiles. Technical validation results do not certify legal or tax compliance.
Profile status
Available validation profiles
Each profile names the validation scope and where it is available. Technical validation does not certify legal or tax compliance.
Available · Built-in subset and Invoice Firewall
EN 16931
Built-in required-field and totals checks on every invoice; the official CEN XSD and Schematron rules for UBL and CII on Invoice Firewall.
Available · Every plan and Invoice Firewall
XRechnung & ZUGFeRD
Declared XRechnung invoices use the official KoSIT validator; ZUGFeRD runtime checks cover PDF/A-3, XMP, attachments, and all five XML profiles.
Available · Invoice Firewall
Factur-X
Five official PDF/XML profiles run against pinned container, XSD, and Schematron validators.
Available · Invoice Firewall
Peppol BIS
Peppol BIS Billing 3.0 invoices checked with the official KoSIT validator and Peppol artefacts.
Available · Every plan
KSeF
Every KSeF FA(3) invoice validated against the Ministry of Finance's official FA(3) schema.
Not sure which profile applies to you?
Talk to us → or start with the EU baseline: EN 16931.
How validation works
A consistent result for every implemented rule
Where a rule is implemented, Invogi evaluates it deterministically and records the profile, rule-set version, result, and evidence. Coverage varies by profile and is stated above.
- Declared-profile routing — jurisdiction-specific rules run only for the profile an invoice declares or an API caller selects, never a guessed one.
- Arithmetic checks — totals, tax, and line-item math validated against the configured rule-set version.
- Required-field checks — mandatory elements for the profile confirmed present and correctly typed.
- Evidence attached to every validation result — deterministic checks, not an LLM black-box score.
National and EU e-invoicing mandate timelines are updated by regulators regularly. Confirm current deadlines with your own advisors before making a compliance decision based on this page.
See it on your own invoices
Start with invoice-risk analysis, then discuss your profile requirements.
Run the free AP Recovery Audit on a CSV/XLSX export, or contact us to confirm how the exact rules you need are covered before relying on compliance output.
FAQ
Common questions
Does Invogi provide legal or tax compliance certification?
No. Invogi validates invoices against a configured technical profile and rule-set version. It does not provide legal or tax advice or certify regulatory compliance.
What is EU e-invoicing compliance?
It means invoices are issued and received as structured, machine-readable documents that conform to a technical profile — such as EN16931 or a national implementation like XRechnung or KSeF — rather than as unstructured PDFs.
Which e-invoice rules does Invogi currently check?
Every structured invoice gets a built-in EN 16931 subset. Declared XRechnung invoices are checked with the official KoSIT validator on every plan, and KSeF FA(3) invoices against the official FA(3) schema. On Invoice Firewall, organizations can also validate Peppol BIS and plain UBL/CII invoices with the official Peppol and CEN artefacts. Factur-X and ZUGFeRD technical validation is production-supported on Invoice Firewall for all five profiles against the pinned container and XML rule sets.