Stampbench

OUR STANDARDS / PLAINLY EXPLAINED

You make the invoice.
We check the careful bits.

You should not need to learn a rulebook to bill a customer. Stampbench checks the details, totals and digital format in the background, then explains anything that needs attention in ordinary language.

WHAT GETS CHECKED

A second pair of eyes for every invoice.

01

The important details are there.

Stampbench checks the customer, invoice number, dates, payment details and the other information the chosen invoice needs.

02

The numbers add up.

Line totals, tax and the amount due are calculated together, so the PDF and the digital invoice carry the same figures.

03

Your work stays private.

The free workbench checks the invoice in your browser. Your invoice content is not uploaded just to create or check it.

THE NAMES YOU MAY SEE

Standards without the homework.

EN 16931

The shared European model for what a digital invoice needs to contain.

XRechnung

The German e-invoice rules used by public authorities and many businesses.

UBL + CII

Two file languages accounting systems use. Stampbench handles the technical choice for you.

If a customer asks for a structured or compliant invoice, choose where you are based and Stampbench selects the suitable setup. You can still review it before downloading.

EVIDENCE, NOT A SLOGAN

Checked, tested and honest about the limits.

394automated tests across the product
86official test documents exercised
0crashes in that official corpus
Read the technical evidence and current limits

The suite covers the core library, command-line tool and web application. We also run 45 UBL and 41 CII documents from the official XRechnung test corpus through the engine. Eighty-three are accepted and three are deliberately published as open compatibility questions.

Stampbench implements a documented subset of the full ruleset. It does not claim SOC 2, ISO 27001 certification or complete KoSIT parity today. Passing a check is useful evidence, not legal advice or a guarantee that every recipient will accept a document.

Developers and auditors can inspect the exact rule coverage, versions and response metadata in the technical documentation.