SummandLive demo, free and Pro.
The first two sections run the real @sweberdev/summand build in your browser: the XML Schema check, the XPath and Schematron engine with the official CEN and KoSIT rules, the PDF reader and the Leitweg-ID check. The Pro section shows output of the real Pro packages for a few sample invoices.
Your invoice never leaves your browser. Nothing is uploaded or stored.
Summand checks invoices technically against EN 16931 and XRechnung. It is not tax advice.
Validate
Check an e-invoice against the official rulesEN 16931 and XRechnung.
Drop an XRechnung or ZUGFeRD / Factur-X file, or pick a sample. Summand finds the syntax and profile, checks the XML Schema, applies the matching rule sets and lists every finding with rule, line and XPath.
Loading Summand and the rule sets…
Leitweg-ID
Check the address of a German public buyerISO 7064 check digits.
German public authorities are addressed by a Leitweg-ID in the buyer reference (BT-10). A typo means the invoice is rejected. Summand checks the structure and the two check digits.
Loading Summand and the rule sets…
Pro
Read, show and process invoices in bulkSummand Pro.
Summand Pro turns invoices into typed data, renders them for people, watches your inbox folder and hands valid invoices to DATEV. Below is real output of summand-view and summand-inbox for the sample invoices.
summand-view: the invoice with errors as readable HTML, with its validation report
The ZUGFeRD sample in German
summand-inbox on a folder of six files
$ npx summand-inbox incoming --html report.html --audit-log audit.jsonl
ok incoming/2026-10/lieferant-471102.pdf
ok incoming/2026-10/mustermann-18383.xml
ok incoming/2026-10/mustermann-18383_cii.xml duplicate of incoming/2026-10/mustermann-18383.xml
FAIL incoming/2026-10/mustermann-18383_resent.xml 1 error(s), 1 warning(s) duplicate of incoming/2026-10/mustermann-18383.xml
ERR incoming/2026-10/scan-0815.pdf The PDF contains no embedded invoice XML. A ZUGFeRD / Factur-X invoice must embed the XML (for example factur-x.xml); a plain PDF is not an e-invoice.
ok incoming/2026-10/stadtwerke-2026-10.xml
6 file(s): 4 valid, 1 invalid, 1 unreadable, 2 duplicate(s), 1 warning(s)summand-read: one typed object for UBL and CII
import { readInvoice } from "@weber-development/summand-read"
const invoice = readInvoice(bytes) // UBL, CII or ZUGFeRD PDF
invoice.seller.vatId // "DE 123456789" BT-31
invoice.buyerReference // "04011000-12349-88" BT-10
invoice.totals.payable // "233.00" BT-115
invoice.payment.creditTransfers // [{ accountId: "DE79…", bic: "DRESDEFFXXX" }]
invoice.lines.map((l) => [l.item.name, l.quantity, l.unit, l.netAmount])Two lines of the audit log: each line carries the SHA-256 of the file and a chain value over the line before
{
"time": "2026-10-05T20:05:23.662Z",
"file": "incoming/2026-10/lieferant-471102.pdf",
"sha256": "05b5a382db8fdc60d1e9ec31fef7fb09c91d68413b9187f7ca116aed116ed1d0",
"size": 37897,
"status": "valid",
"errors": 0,
"warnings": 0,
"errorIds": [],
"number": "471102",
"issueDate": "2024-11-15",
"seller": "Lieferant GmbH",
"sellerVatId": "DE123456789",
"payableAmount": "529.87",
"currency": "EUR",
"ruleSets": [
"EN 16931 validation artefacts (UN/CEFACT CII) 1.3.16"
],
"chain": "911520726f5c04de09bbc52354d0392db48b288e8c264f5ab05e655fe5028f7b"
}
{
"time": "2026-10-05T20:05:23.762Z",
"file": "incoming/2026-10/mustermann-18383.xml",
"sha256": "8ed131cc276bb37d160ffc243dee9eade601de9ed04392ab38eac5ce26e9ac77",
"size": 6839,
"status": "valid",
"errors": 0,
"warnings": 0,
"errorIds": [],
"number": "18383",
"issueDate": "2020-11-27",
"seller": "Mustermann GmbH",
"sellerVatId": "DE 123456789",
"payableAmount": "233.00",
"currency": "EUR",
"ruleSets": [
"EN 16931 validation artefacts (UBL) 1.3.16",
"XRechnung Schematron (UBL), XRechnung 3.0 2.6.0"
],
"chain": "34984313b72ecb517a540adda3a0bf9aa2ce4143c358ce11232bd9eae28209bf"
}summand-inbox watch: checks each file as it arrives and sorts it into valid/, invalid/ and duplicate/
$ npx summand-inbox watch incoming --move --audit-log audit.jsonl
Watching incoming for .xml and .pdf files. Stop with Ctrl+C.
ok lieferant-471102.pdf -> valid/lieferant-471102.pdf
ok mustermann-18383.xml -> valid/mustermann-18383.xml
ok mustermann-18383_cii.xml duplicate of mustermann-18383.xml -> duplicate/mustermann-18383_cii.xml
FAIL mustermann-18383_resent.xml 1 error(s), 1 warning(s) duplicate of mustermann-18383.xml -> duplicate/mustermann-18383_resent.xml
ERR scan-0815.pdf The PDF contains no embedded invoice XML. A ZUGFeRD / Factur-X invoice must embed the XML (for example factur-x.xml); a plain PDF is not an e-invoice. -> invalid/scan-0815.pdf
ok stadtwerke-2026-10.xml -> valid/stadtwerke-2026-10.xml
^C
Stopped. 6 file(s): 4 valid, 1 invalid, 1 unreadable, 2 duplicate(s), 1 warning(s)DATEV export of the valid invoices: one booking per VAT rate, ready for your tax advisor to import
$ npx summand-inbox incoming --datev buchungsstapel.csv --beraternummer 1001 --mandantennummer 1 --kontenrahmen SKR03
# buchungsstapel-2024.csv (Windows-1252, first 14 of 125 columns shown)
"EXTF";700;21;"Buchungsstapel";13;20261006074054605;;"SU";"Summand Pro";;1001;1;20240101;4;20241115;20241115;"Eingangsrechnungen";;1;0;0;"EUR";;;;;"03";;;;
Umsatz (ohne Soll/Haben-Kz);Soll/Haben-Kennzeichen;WKZ Umsatz;Kurs;Basis-Umsatz;WKZ Basis-Umsatz;Konto;Gegenkonto (ohne BU-Schlüssel);BU-Schlüssel;Belegdatum;Belegfeld 1;Belegfeld 2;Skonto;Buchungstext;…
294,25;"H";"EUR";;;;70000;4900;"8";1511;"471102";;;"Lieferant GmbH";…
235,62;"H";"EUR";;;;70000;4900;"9";1511;"471102";;;"Lieferant GmbH";…The HTML report of the same run
Free 2.0
Pick rule set versions and validate whole foldersSummand, free.
Summand 2.0 builds on the 1.1 line: one ruleSets option decides which official rules run and in which version, and validateMany checks whole folders of invoices in parallel. The 2.0 release itself makes result messages a stable contract and requires Node.js 22.
One option for rule sets and versions
ruleSets replaces the old xrechnung switch. You choose EN 16931 and XRechnung, and can pin the older XRechnung 2.5.0 to reproduce a verdict that was given under it. The result lists the versions that really ran.
Node.js
import { validateInvoice } from "@sweberdev/summand";
const result = validateInvoice(xml, { ruleSets: ["en16931", "xrechnung@2.5.0"] });
// CLI: summand validate --rule-sets en16931,xrechnung@2.5.0 invoice.xmlOutput for a UBL invoice whose amount due was changed to 1.00 (valid, ran, then each error)
valid: false
ran: en16931-ubl@1.3.16, xrechnung-ubl@2.5.0
BR-CO-16 error en16931-ublSee exactly which rules are bundled
summand rules lists every bundled rule set with version, rule count, licence and source, and shows which version is the default. Your stored verdicts can name the rules that produced them.
Terminal
npx @sweberdev/summand rulesOutput
Rule set Version Rules Licence Publisher Source Used
en16931-ubl 1.3.16 979 EUPL-1.2 CEN/TC 434 (ConnectingEurope) https://github.com/ConnectingEurope/eInvoicing-EN16931 default
en16931-cii 1.3.16 806 EUPL-1.2 CEN/TC 434 (ConnectingEurope) https://github.com/ConnectingEurope/eInvoicing-EN16931 default
xrechnung-ubl v2.6.0 56 Apache-2.0 Koordinierungsstelle für IT-Standards (KoSIT) https://github.com/itplr-kosit/xrechnung-schematron default
xrechnung-cii v2.6.0 52 Apache-2.0 Koordinierungsstelle für IT-Standards (KoSIT) https://github.com/itplr-kosit/xrechnung-schematron default
xrechnung-ubl v2.5.0 55 Apache-2.0 Koordinierungsstelle für IT-Standards (KoSIT) https://github.com/itplr-kosit/xrechnung-schematron on request (@2.5.0)
xrechnung-cii v2.5.0 49 Apache-2.0 Koordinierungsstelle für IT-Standards (KoSIT) https://github.com/itplr-kosit/xrechnung-schematron on request (@2.5.0)Validate folders with a worker pool
validateMany spreads files over worker threads and returns results in input order. A file that cannot be read becomes a SUM-BATCH error entry, never a crash, so an unreadable file never looks like a valid one.
Node.js (batch.mjs)
import { validateMany } from "@sweberdev/summand/batch";
for await (const { index, name, result, error } of validateMany(files, { lang: "de" })) {
if (error) console.log(index, name, error.code);
else console.log(index, name, result.valid ? "valid" : `${result.errors.length} error(s)`);
}Output for four invoices and one missing file
0 inv/rechnung-1.xml valid
1 inv/rechnung-2.xml valid
2 inv/rechnung-3.xml valid
3 inv/falsch.xml 1 error(s)
4 inv/fehlt.xml SUM-BATCHStable rule codes in every message
Every error, warning and info carries a stable id, a severity and the rule set it came from, in English or German. 2.0 documents these fields as the contract, so you can build filters and reports on them.
Terminal
npx @sweberdev/summand validate --lang de invoice.xmlOutput for the same changed invoice
UNGÜLTIG falsch.xml XRechnung 3.0 1 Fehler, 0 Warnung(en)
Fehler BR-CO-16 (Zeile 88): Fälliger Zahlungsbetrag (BT-115) = Gesamtbetrag der Rechnung mit Umsatzsteuer (BT-112) - Gezahlter Betrag (BT-113) + Rundungsbetrag (BT-114).Upgrading from 1.x: replace the xrechnung option with ruleSets, and use Node.js 22 or newer. Peppol rules and the Factur-X EXTENDED Schematron are not bundled.
Read the docsPro 3.0.0
A workbench for received invoicesSummand Pro.
Pro 3.0.0 adds a browser workbench to the validation service: named users register received invoices, check and approve them with the four-eyes rule, and export them with an evidence bundle. The approval workflow is stable from this version. Nothing from 2.x was removed.
Register, check, approve, export
The workbench keeps documents and a hash-chained log in a data folder. Reviewers check, approvers approve, admins export, and the person behind each step comes from the sign-in, not from a typed name. Everyone gets only the buttons their role and the four-eyes rule allow.
Start it with a users file
docker run -d -p 8080:8080 -v summand-data:/data \
-v ./users.json:/etc/summand/users.json:ro \
-e SUMMAND_WORKBENCH_DIR=/data \
-e SUMMAND_USERS_FILE=/etc/summand/users.json \
ghcr.io/weber-development/summand-server:3
# users.json
[
{ "name": "Anna", "role": "reviewer", "tokenSha256": "<sha-256 of her token>" },
{ "name": "Bernd", "role": "approver", "tokenSha256": "<sha-256 of his token>" },
{ "name": "Chris", "role": "admin", "tokenSha256": "<sha-256 of his token>" }
]The whole path, recorded
Recorded from a real run of the server with the KoSIT sample invoice, three users and the HTTP API that the page uses. The reviewer cannot approve; the approver can only approve what somebody else checked.
Recorded output
$ curl -s -H "Authorization: Bearer $ANNA_TOKEN" -H "Content-Type: application/xml" --data-binary @rechnung-4711.xml localhost:8080/v1/documents | jq ".document | {id, state, invoice, receivedBy}"
{
"id": "8ed131cc276b",
"state": "received",
"invoice": {
"status": "valid",
"errors": 0,
"warnings": 0,
"number": "18383",
"issueDate": "2020-11-27",
"seller": "Mustermann GmbH",
"sellerVatId": "DE 123456789",
"payableAmount": "233.00",
"currency": "EUR"
},
"receivedBy": "Anna"
}
$ curl -s -X POST -H "Authorization: Bearer $ANNA_TOKEN" -d "{}" localhost:8080/v1/documents/$ID/approve | jq .error
{
"code": "forbidden",
"message": "The role \"reviewer\" may not do this (approve)."
}
$ curl -s -X POST -H "Authorization: Bearer $ANNA_TOKEN" -d "{}" localhost:8080/v1/documents/$ID/check | jq ".document | {state, checkedBy}"
{
"state": "checked",
"checkedBy": "Anna"
}
$ curl -s -X POST -H "Authorization: Bearer $BERND_TOKEN" -d "{}" localhost:8080/v1/documents/$ID/approve | jq ".document | {state, approvedBy}"
{
"state": "approved",
"approvedBy": "Bernd"
}
$ curl -s -X POST -H "Authorization: Bearer $CHRIS_TOKEN" -d "{\"reference\":\"BU-2026-118\"}" localhost:8080/v1/documents/$ID/export | jq ".document | {state, exportedBy}"
{
"state": "exported",
"exportedBy": "Chris"
}
$ curl -s -H "Authorization: Bearer $CHRIS_TOKEN" localhost:8080/v1/documents/$ID/evidence -o evidence-4711.zip && unzip -Z1 evidence-4711.zip
manifest.json
README.md
verify.mjs
index.jsonl
documents/8ed131cc276bb37d/original.bin
documents/8ed131cc276bb37d/validation.json
documents/8ed131cc276bb37d/events.jsonl
$ curl -s -H "Authorization: Bearer $CHRIS_TOKEN" localhost:8080/v1/workflow/verify | jq -c ".events | {ok, records}"
{"ok":true,"records":4}Evidence bundle on export
Marking an invoice as exported archives the original with its validation result and the full event history. The ZIP can be checked by a third party with the included script, or with summand-inbox archive verify-bundle. It is unsigned.
Verify the log and a bundle
curl -s -H "Authorization: Bearer $ADMIN_TOKEN" localhost:8080/v1/workflow/verify | jq .events
unzip evidence-4711.zip -d evidence && node evidence/verify.mjs evidenceOne page, two languages
The page at /app is plain HTML in German and English with a strict content security policy. We checked it with axe-core in headless Chromium (sign-in, list and detail view, no violations). We did not test with a screen reader.
Open it
http://localhost:8080/appThe demo cannot show the page itself: it needs your own Docker host and users. Not verified: browsers other than Chromium, a screen reader, load, several server processes on one data folder. The text files inside the evidence bundle are in German. The archive and the evidence bundle are not reviewed by a tax advisor and not a certified GoBD system.
Read the docsPro 2.1.0
Run it as a serviceSummand Pro.
Pro 2.1.0 adds an HTTP validation service for stacks that are not Node.js, and sending, notifying and evidence export for the inbox. The inbox additions are beta.
Validation service for any stack
A Docker image that validates XRechnung, ZUGFeRD and Factur-X over HTTP. PHP, Python, Java, C# or a shell script only need an HTTP client, and no invoice is stored.
Start it and validate
docker run --rm -p 8080:8080 ghcr.io/weber-development/summand-server:2
curl -s --data-binary @invoice.xml -H 'Content-Type: application/xml' \
'http://localhost:8080/v1/validate?lang=en' | jq '{valid, errors: [.errors[] | {id, severity, message}]}'Embed the service in your own server
Use the same service from Node.js with an optional API key and a body size limit, or mount its handler in your own node:http server.
createServer
import { createServer } from "@weber-development/summand-server";
const app = createServer({ apiKey: process.env.SUMMAND_API_KEY, maxBodyBytes: 10 * 1024 * 1024 });
const { url } = await app.listen(8080, "0.0.0.0");
process.on("SIGTERM", () => void app.close());Send invoices by e-mailBeta
Validates the e-invoice first, then mails the XML or ZUGFeRD PDF to the buyer over SMTP. An invoice that fails the check is not sent unless you force it.
summand-inbox send
summand-inbox send invoice-4711.xml \
--to buyer@customer.example \
--from invoices@seller.example \
--smtp-url smtp://smtp.seller.example:587 \
--smtp-user-env SUMMAND_SMTP_USER \
--smtp-password-env SUMMAND_SMTP_PASSWORDSigned webhooks and deadline mailsBeta
Tell your ERP or your team when an invoice is approved, rejected or overdue. Webhooks are signed with HMAC-SHA-256 and retried, and secrets stay in environment variables.
notify.json
{
"version": 1,
"events": ["approved", "rejected", "deadline-overdue"],
"webhooks": [
{
"name": "erp",
"url": "https://erp.example.com/hooks/summand",
"secretEnv": "SUMMAND_WEBHOOK_SECRET",
"retries": 3
}
]
}Evidence bundle from the archiveBeta
Exports a ZIP with the original invoice, its validation result, workflow events and a SHA-256 manifest. The recipient can check it with a command or a standalone script.
Export and verify
summand-inbox archive export 3fa9c1d20b77a1e4 --out evidence-4711.zip
summand-inbox archive verify-bundle evidence-4711.zip \
--manifest-sha256 <the value you were sent> \
--anchor <the chain head you were sent>The demo cannot show these: the service needs your own Docker host, and mail and webhooks need your own servers. The inbox additions are only tested against local test servers, not real mail or webhook services. The archive is not reviewed for tax purposes.
Read the docsNext step
Validate invoices where they arriveMIT licensed.
Install @sweberdev/summand and call validateInvoice in your upload route, your mail handler or your CI. The getting started guide takes five minutes.