E-invoicing

Invoices that pass the actual rules.

Not a PDF that looks right — a document checked against the published EN 16931, Peppol and XRechnung rule sets before it is produced. You find out now, instead of from your customer's accounts team three weeks later.

Read the guide

What it does

Validates against the real rule sets. Two tiers: our own check on the fields the standard requires, then the published Schematron artefacts themselves — the same files an access point runs. Checking is free, stateless and does not count against your renders, so you can check every invoice before you send it.

Produces Factur-X. A PDF/A‑3 with factur-x.xml embedded: one file a person can read and a machine can parse. No network, no membership, no agreement with the recipient — you email it like any other PDF. That is why it is the format to start with.

Produces the XML on its own, as UBL or CII, for the profile you name — the file you hand to your access point.

Records what each document was held to. The rule sets are published artefacts that get revised. Every render keeps the profile and the exact ruleset versions it passed, so a year from now “was this compliant?” has an answer instead of a guess.

Profiles

ProfileRules runWhere it is used
factur_x_en16931 EN 16931 France and Germany, by agreement rather than mandate
peppol_bis_billing_3 EN 16931 + Peppol BIS Billing 3.0 Peppol — EU public sector, NHS England, and the UK for all VAT invoices from April 2029
xrechnung_ubl / xrechnung_cii EN 16931 + XRechnung 3.0 German public authorities. Defined in both syntaxes; ask which one they take

What it does not do

We do not transmit. Getting a document onto Peppol is the Access Point role — membership, certificates, accreditation, continuing obligations. We are not one and are not becoming one. We make the document correct; your access point, or your customer's, moves it. Factur-X needs no network at all.

“Peppol” is not “the EU”. Italy clears through SdI, France through its PDP model, Poland through KSeF. Those are national platforms, each a separate implementation rather than a profile, and we do not support them. Anyone promising “EU e-invoicing” on the back of a Peppol integration is overselling.

A US-only business has nothing here to comply with. EN 16931 is a VAT standard, and its rules test the tax scheme against the literal string VAT. The US has no VAT. We refuse to relabel a sales tax to make a document validate. For that business the PDF is the invoice — this page matters the day you invoice someone in Europe.

Start with a document you already have

Send it to the checker and read the list back. Every finding names the business term the standard uses, so you can look it up in EN 16931 rather than only in our docs.

Read the guide API reference