Skip to content
E-invoice to JSON
GitHub
Menu

What was tested

CI (.github/workflows/ci.yml) runs all of this on every push and pull request, and deploys the browser converter only when everything passes. The site build checks that every README section has a page and that no internal link or #fragment is broken (site/check.ts), and site/a11y.ts runs axe-core in the light and dark themes on the converter (every result tab) and the docs, checks that nothing scrolls sideways at 320 and 375 px, that keyboard focus is visible and that no page requests anything from another host but the fonts.

  • Detection (every fixture plus header-only cases): each of the 27 fixtures, envelopes, versions and profiles; every UBL and CII profile rule (Peppol, EHF extension, self-billing, XRechnung, NLCIUS, CIUS-RO/PT, HR-CIUS, OIOUBL 2/3, PINT, UBL.BE, EN 16931 2017/2026, BIS 2, Factur-X MINIMUM to EXTENDED, ZUGFeRD 2.0); probe edge cases (a 4,000-element UBLExtensions block, CDATA, a foreign-namespace CustomizationID, prefixed roots, whitespace in a namespace).
  • Parsers: field-by-field assertions on synthetic fixtures written for this suite (see test/fixtures/README.md): a full Peppol BIS 3 invoice, a credit note, a negative 380 invoice, XRechnung UBL and CII, Factur-X BASIC (381) and MINIMUM, and Svefaktura 1.0 invoice and credit. The real samples (ANAF, HR-CIUS, PINT, Factur-X PDF) must parse with no BR-CO warnings. Also tested: a malformed amount gives an error that names the element, and tampered totals give BR-CO warnings with the values left untouched.
  • Hostile input: DOCTYPE with internal entities and with an external DTD; file, entry, total-size, entry-count, payload-count and nesting limits; a ZIP whose header understates its size; a 64 MB PDF attachment bomb without a declared size (stopped at the limit); payload hashes equal across different wrappers.
  • Values: decimal parsing (trailing zeros kept, commas and exponents rejected), dates (format 102, date-times, invalid calendar dates) and XPath-compatible rounding.
  • Known-answer sweep: bun run sweep:fixtures checks every fixture against test/fixtures/expected.json. Run the same mode on a labelled sample of your own inbound files: a plain sweep only shows coverage, not whether the detected format is right.
  • Real-sample sweep (reported by the earlier version, detection only; not re-run for this repository): 6,427 files from the phive-rules validation suites, KoSIT XRechnung tests, Mustang (ZUGFeRD/Factur-X PDFs) and OCA’s FatturaPA tests. 4,840 invoices were detected across 27 format IDs and 1,543 non-invoices (orders, responses, catalogues, France CDAR status messages) were recognised as such. The 34 files left unknown are all non-invoices: Schematron rule files, HR-XML staffing messages and a deliberately invalid test file. One real Italian invoice had a space inside its namespace URI; detection now tolerates that.
Section titled “Related”

Open source (0BSD), built on the eu-einvoice-canonical library. No analytics and no cookies: the only outside requests are the fonts and the trusted lists or language models you switch on.