01Validation for software teams

European e-invoicing validationfor your software.

Validate UBL and CII invoices against supported EN 16931-1:2017 and XRechnung 3.0 rules. Return structured diagnostics with rule IDs and source locations inside the workflow your product already uses.

Test an invoice Read integration docs

Inspection / invoice-0042.xmlUBL 2.1

Source

38<cac:LegalMonetaryTotal>

39 <cbc:LineExtensionAmount

40 currencyID="EUR">940.00</cbc:LineExtensionAmount>

41 <cbc:TaxExclusiveAmount

42 currencyID="EUR">950.00</cbc:TaxExclusiveAmount>

43</cac:LegalMonetaryTotal>

DiagnosticBlocking

BR-CO-10

Invoice line total mismatch

The stated line total must equal the sum of the invoice line net amounts.

Expected: 950.00 EUR
Received: 940.00 EUR

line 40 · BT-106 / BT-131

Profile: XRechnung 3.0Rules executed: 56

Specification: EN 16931-1:2017
German profile: XRechnung 3.0
Syntaxes: UBL 2.1 + CII
Runtime: Pure TypeScript

02Validation evidence register

Evidence with its scope attached.

These figures describe the current engine and test corpus. They do not claim complete KoSIT parity or replace an official recipient check.

Evidence	UBL	CII	Result	Scope note
Corpus documents exercised	45	41	86 total	Official XRechnung corpus
Corpus crashes	0	0	0	Parser stability only
European core rules	40	40	40	EN 16931-1:2017 subset
German additions	16	16	16	BR-DE profile rules

03Deployment architecture

The engine goes where the invoice already is.

Use the library inside a browser worker, server process or CI pipeline. Invoice bytes remain inside the execution context your team controls.

import { validateXml } from
'@stampbench/core';

const result = validateXml(xml, {
  profile: 'xrechnung'
});

console.log(result.valid);
console.log(result.violations);

Invoice XML

UBL or CII

@stampbench/core

Parse and validate

Your execution context

Browser · Worker · CI

ValidationResult

Structured findings

04Live browser inspection

Change the XML. Run the actual rules.

This preview calls the same validateXml and locateViolations functions used by the full playground.

Validation runs in this browser. The XML is not uploaded.

Payload editorUBL · 94 lines

<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>
  <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
  <cbc:ID>RE-2026-0042</cbc:ID>
  <cbc:IssueDate>2026-08-01</cbc:IssueDate>
  <cbc:DueDate>2026-08-31</cbc:DueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
  <cbc:BuyerReference>04011000-12345-67</cbc:BuyerReference>
  <cac:AccountingSupplierParty>
    <cac:Party>
      <cbc:EndpointID schemeID="EM">rechnung@beispiel-software.de</cbc:EndpointID>
      <cac:PostalAddress>
        <cbc:StreetName>Musterstraße 12</cbc:StreetName>
        <cbc:CityName>Berlin</cbc:CityName>
        <cbc:PostalZone>10115</cbc:PostalZone>
        <cac:Country><cbc:IdentificationCode>DE</cbc:IdentificationCode></cac:Country>
      </cac:PostalAddress>
      <cac:PartyTaxScheme>
        <cbc:CompanyID>DE123456789</cbc:CompanyID>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:PartyTaxScheme>
      <cac:PartyLegalEntity>
        <cbc:RegistrationName>Beispiel Software GmbH</cbc:RegistrationName>
      </cac:PartyLegalEntity>
      <cac:Contact>
        <cbc:Name>Anna Beispiel</cbc:Name>
        <cbc:Telephone>+49 30 1234567</cbc:Telephone>
        <cbc:ElectronicMail>buchhaltung@beispiel-software.de</cbc:ElectronicMail>
      </cac:Contact>
    </cac:Party>
  </cac:AccountingSupplierParty>
  <cac:AccountingCustomerParty>
    <cac:Party>
      <cac:PostalAddress>
        <cbc:StreetName>Amtsweg 1</cbc:StreetName>
        <cbc:CityName>Bonn</cbc:CityName>
        <cbc:PostalZone>53113</cbc:PostalZone>
        <cac:Country><cbc:IdentificationCode>DE</cbc:IdentificationCode></cac:Country>
      </cac:PostalAddress>
      <cac:PartyLegalEntity>
        <cbc:RegistrationName>Bundesamt für Beispielwesen</cbc:RegistrationName>
      </cac:PartyLegalEntity>
    </cac:Party>
  </cac:AccountingCustomerParty>
  <cac:PaymentMeans>
    <cbc:PaymentMeansCode>58</cbc:PaymentMeansCode>
    <cbc:PaymentID>RE-2026-0042</cbc:PaymentID>
    <cac:PayeeFinancialAccount>
      <cbc:ID>DE89370400440532013000</cbc:ID>
      <cbc:Name>Beispiel Software GmbH</cbc:Name>
      <cac:FinancialInstitutionBranch><cbc:ID>COBADEFFXXX</cbc:ID></cac:FinancialInstitutionBranch>
    </cac:PayeeFinancialAccount>
  </cac:PaymentMeans>
  <cac:PaymentTerms>
    <cbc:Note>Zahlbar innerhalb von 30 Tagen ohne Abzug.</cbc:Note>
  </cac:PaymentTerms>
  <cac:TaxTotal>
    <cbc:TaxAmount currencyID="EUR">180.50</cbc:TaxAmount>
    <cac:TaxSubtotal>
      <cbc:TaxableAmount currencyID="EUR">950.00</cbc:TaxableAmount>
      <cbc:TaxAmount currencyID="EUR">180.50</cbc:TaxAmount>
      <cac:TaxCategory>
        <cbc:ID>S</cbc:ID>
        <cbc:Percent>19</cbc:Percent>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:TaxCategory>
    </cac:TaxSubtotal>
  </cac:TaxTotal>
  <cac:LegalMonetaryTotal>
    <cbc:LineExtensionAmount currencyID="EUR">940.00</cbc:LineExtensionAmount>
    <cbc:TaxExclusiveAmount currencyID="EUR">950.00</cbc:TaxExclusiveAmount>
    <cbc:TaxInclusiveAmount currencyID="EUR">1130.50</cbc:TaxInclusiveAmount>
    <cbc:PayableAmount currencyID="EUR">1130.50</cbc:PayableAmount>
  </cac:LegalMonetaryTotal>
  <cac:InvoiceLine>
    <cbc:ID>1</cbc:ID>
    <cbc:InvoicedQuantity unitCode="HUR">10</cbc:InvoicedQuantity>
    <cbc:LineExtensionAmount currencyID="EUR">950.00</cbc:LineExtensionAmount>
    <cac:Item>
      <cbc:Description>Sprint 14</cbc:Description>
      <cbc:Name>Softwareentwicklung</cbc:Name>
      <cac:ClassifiedTaxCategory>
        <cbc:ID>S</cbc:ID>
        <cbc:Percent>19</cbc:Percent>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:ClassifiedTaxCategory>
    </cac:Item>
    <cac:Price>
      <cbc:PriceAmount currencyID="EUR">95.00</cbc:PriceAmount>
    </cac:Price>
  </cac:InvoiceLine>
</Invoice>

Diagnostics engine state2 errors

Profile: xrechnung
Rules: 56
Syntax: UBL
Ruleset: 2026-08.2

BR-CO-10error · line 72

Sum of line net amounts is 950.00 but BT-106 states 940.00.

BT-106 / BT-131exact locationexpected: 950.00received: 940

BR-CO-13error · line 73

Total without VAT (BT-109) should be 940.00 (BT-106 − BT-107 + BT-108) but is 950.00.

BT-109exact locationexpected: 940.00received: 950

IG-DE-W1warning · line 35

Buyer electronic address (BT-49) is missing — Peppol delivery and many workflow systems need it.

BT-49ancestor location

Open full playground

05Current capability ledger

What exists today.

A technical inventory written for architecture review, not a feature-card wall.

Syntax parsing: UBL 2.1 and UN/CEFACT CII are auto-detected from the XML document.
Semantic validation: 40 EN 16931 core rules or 56 rules with the German profile.
Source locations: Each finding can carry a line, column, XML path and stated location precision.
Deterministic repair: Arithmetic errors with one derivable answer can be repaired without inventing business data.
UBL generation: Structured invoice data can be computed and emitted as XRechnung 3.0 UBL.
CLI and CI: The same TypeScript engine can run in a process, test pipeline or browser worker.
Integration surfaces: Use the MIT library, command-line tool or browser worker inside an existing product workflow.
Ruleset versioning: Every validation result identifies the ruleset version and number of rules executed.

06Founding integration pilot

Put the validator inside one real workflow.

A fixed-scope engagement for software teams evaluating Stampbench against their own invoice path. The initial £3,000 price is being tested with early pilot customers.

Discuss a pilot

01: One staging workflow
Integrate the current validator into one defined invoice path in your product.
02: Representative documents
Exercise the integration against an agreed set of UBL or CII invoices from your workflow.
03: Structured diagnostics
Return supported rule IDs, business terms and source locations in a form your product can use.
04: Coverage handover
Document the implemented boundary, acceptance results and anything outside the supported ruleset.

The pilot covers one product and one integration path. It is engineering work and validation tooling, not certification, recipient approval or legal advice. Any continuing support is scoped separately after the pilot.

07Standards scope

Precise about the boundary.

The current engine targets EN 16931-1:2017 and XRechnung 3.0. A new 2026 edition of the European standard is entering migration, so support is described by exact ruleset rather than a timeless claim of full compliance.

Germany’s B2B e-invoicing transition uses different deadlines depending on turnover and transmission method. Stampbench validates invoice structure; it does not decide tax treatment or replace current authority guidance.

Read validation evidence German Finance Ministry guidance

Run the document

Inspect the invoice before your customer does.

Open browser playground Read evidence