Compliant formats, Extracted, not OCR'd.

Factur-X, XRechnung and Peppol e-invoices carry their data as structured XML. When Cribble can read that XML, it does — before any AI touches the file — and every field comes back exact rather than guessed.

Get started
A bright laptop showing XRechnung XML extracted into exact invoice fields

Detection first

XML attachments and hybrid Factur-X PDFs are recognized on arrival and routed to a deterministic parser, so AI never gets a vote on a structured document we can open. The exception we'll name rather than hide: a Factur-X PDF whose embedded XML is compressed can't be opened yet, so it's read as a PDF instead — flagged as Factur-X, with confidence scores like any other extraction.

UBL and CII, both dialects

Peppol BIS and XRechnung-UBL on one side, Factur-X and XRechnung-CII on the other. Same clean output either way.

Ready for the mandates

Germany's B2B e-invoicing mandate is phasing in through 2028, with other EU countries close behind. Receiving compliant invoices correctly is table stakes, and Cribble does it from day one.

One inbox for both worlds

The awkward reality of the e-invoicing transition is that you'll receive both kinds for years: structured XML from big suppliers, PDFs and paper from everyone else. Most tools handle one or the other.

Cribble treats them as one stream. Structured formats are parsed exactly; everything else goes through AI extraction. You see one inbox, one review flow, one export — and a field parsed from XML arrives at full confidence because it was read, not guessed. Where a file has to fall back to AI, the confidence scores say so rather than pretending otherwise.