Free tool · runs in your browser

Sample e-invoices,
rendered as you build them.

Pick a ready-made sample or build your own. Watch a real EN 16931 invoice take shape — with live well-formedness & business-rule checks — then export pretty-printed Peppol BIS 3.0, XRechnung or Factur-X XML, or a PDF. Nothing is uploaded.

1InvoiceEN 16931 header

Invoice number

Issue date

Due date

Type

Currency

Buyer ref

Order reference (BT-13)

Contract (BT-12)

Project (BT-11)

Sales order ref (BT-14)

Tax point date (BT-7)

Invoice note (BT-22)

2Seller

Name (BT-27)

VAT ID (BT-31)

Country (BT-40)

Street (BT-35)

City (BT-37)

Post code (BT-38)

Trading name (BT-28)

Legal registration ID (BT-30)

Contact name (BT-41)

Email (BT-43)

Phone (BT-42)

3Buyer

Name (BT-44)

VAT ID (BT-48)

Country (BT-55)

Street (BT-50)

City (BT-52)

Post code (BT-53)

Legal registration ID (BT-47)

Contact name (BT-56)

Email (BT-58)

Phone (BT-57)

Delivery date (BT-72)

Deliver-to name (BT-70)

Deliver-to street (BT-75)

City (BT-77)

Country (BT-80)

4PaymentBG-16

Means (BT-81)

IBAN (BT-84)

BIC (BT-86)

Account name (BT-85)

Payment terms (BT-20)

Payment reference (BT-83)

5Lines

DescriptionQtyUnit priceVAT%

6Allowances & chargesBG-20 / BG-21 · optional

TypeReasonAmountVAT%

peppol-bis-invoice.xml

Format: Peppol BIS 3.0 · UBL

Checks cover XML well-formedness and a curated set of EN 16931 business rules (BR-*). Output follows the EN 16931 structure with consistent calculations. It is not a full XSD + Schematron validation — the Peppol endpoint scheme is inferred from country, and profile-specific rules still need checking. Full Schematron validation of real invoices is work we do.

Sample e-invoices,rendered as you build them.

From test data to production compliance

Sample e-invoices,
rendered as you build them.