What already exists
Everything on this site runs in the browser. There is no server that reads an invoice โ the parsing, the validation and the exports all happen on the page. That core currently reads:
- XRechnung (UBL and CII), ZUGFeRD 1.0 and 2.x, Factur-X 1.0 through 1.08 including the 2026 sub-line extension
- Peppol BIS Billing 3.0, and any other EN 16931 CIUS โ a CIUS is a narrowing of the norm, not a new syntax, so unfamiliar ones read the same
- FatturaPA including signed
.p7m, Facturae including.xsig, KSeF FA(2) and FA(3), RO e-Factura - The containers around them: ZIP, nested ZIP,
.emland.msg - Official receipts: the Polish UPO and the nine SdI message types, paired back to the invoice they belong to
- Bank statements โ MT940, camt.053, bank CSV โ and reconciliation against the invoices
It is TypeScript, has no runtime dependency on a server, and is covered by several thousand automated checks that run before every deploy.
What a licence would probably look like
- The parsing core as an npm package, source included, no telemetry, no network calls
- Updates as formats change โ that is most of the ongoing work; the formats move every year and the failures are silent when they move
- From โฌ990 per year for one product, more for redistribution
These numbers are a starting point for a conversation, not a price list. If the shape is wrong for you, that is exactly the sort of thing worth telling us.
What is not on offer
Being specific about this saves both sides a call:
- No hosted API. We do not run servers for invoice data, and that is a deliberate limit rather than a stage we have not reached yet.
- No Peppol access point. That needs infrastructure and accreditation we do not have and are not seeking.
- Not the official Schematron engine. We have tested it and it works in a browser, but redistributing the CEN and SaxonJS artefacts has licensing questions we have not resolved. Our validation is a documented subset, and the differences against the official engine are written down rather than glossed over.
If you would use this
Write to us and say which formats you actually receive, roughly how many invoices a month, and what you are embedding it into. A sentence or two is plenty โ we are counting real needs, not collecting leads. There is no form on this page and no tracking on this site, so an email is the only way we would ever know.
If nobody writes, we will take that as the answer and quietly remove this page. That seems fairer than leaving a page up that implies a product exists.