For prospects
Marketing deck
The overview: what Beleggo does and for whom — from freelancer to software vendor. Ends at the free tool.
XRechnung · ZUGFeRD · Peppol
No upload. No account. No cloud.
You must receive them since 2025 and send them from 2027 — and an invoice that breaks EN 16931 may be rejected by the recipient. Without a proper invoice, the input-VAT deduction is at risk. Check and create XRechnung, ZUGFeRD and Peppol here: free, in the browser, no upload.
Free · no account
Unlimited · no daily cap
Sending mandatory from 2027/2028
Real XML, validated locally against EN 16931 — no black box.
Play the tourThe solution
The same engine — local, no server, no JVM — from the free browser tool to an embedded licence. What becomes possible for you:
Batch-validate whole client folders, watch folders, multi-seat licensing — and readiness reports on the practice’s letterhead, recording what a client’s software was tested against. No data-processing agreement needed and no professional-secrecy question, because the documents never leave the building.
See status and scope →Open, check, repair, create and convert — free in your browser, no account, no upload. Beleggo Pro: unlimited templates, PDF branding with your logo and a payment QR, offline licence. No data egress, no subscription, predictable.
Try it free →A CLI for batch runs and CI pipelines, and an MCP server as a deterministic guardrail for AI pipelines: the AI writes, Beleggo checks.
Embed the same engine inside your product — npm package, WASM, web component or binary. Close to the only JS/browser engine that validates without a JVM and without upload.
Beleggo under your brand: your own branding, your own legal pages, your customer relationship. One static bundle per partner — no infrastructure of your own.
Proof, not promises
Other online checkers upload your invoice to a server and delete it "after 24 hours" or "after 7 days". With us it never arrives there — no data-processing agreement, and for tax firms no question of professional secrecy. That is not a promise — it is checkable:
Conformance
Our engine is checked against 340 real test invoices and returns the same verdict as the official validators — the same rule base (KoSIT v1.6.2) that also underpins the Service-BW endpoint and the government routers.
Cross-checked with
1,781 checks per invoice: 1,749 rules from the official Schematron, 21 mandatory particulars under § 14 UStG, 5 VAT risk rules, 6 attachment checks.
Ruleset status: EN 16931 2026-01-31 · XRechnung 3.0.2 (Schematron 2.5.0) · Peppol BIS 3.0.20 · NLCIUS 2.0.3.13 · CIUS-RO 1.0.9 · HR-CIUS 1.0.3 · CIUS-PT 2.1.1
340 samples checked against the official validators · 0 open disagreements — matrix public.
Receiving has been mandatory since 2025 — and a PDF by email is not an e-invoice. Open XRechnung, ZUGFeRD and Peppol files, view them in plain language and check validity before you book them.
Sending becomes mandatory from 2027/2028. Create an EN 16931-valid invoice in under a minute — and check it before it goes out.
Auto-repair
Three rings: deterministic fixes with no AI, concrete correction proposals to confirm, and AI only for the rest — the data only you or an agent can know. All local, nothing uploaded.
# Ring 1 — deterministic, no AI$ beleggo fix DK-074.cii.xml --validate● 1 fix: reordered <rsm:ExchangedDocument> validity: invalid → valid# Ring 2 — proposed, you confirm$ beleggo validate DK-067.ubl.xml --explain✗ BR-CL-04: currency code must be ISO 4217 value: "EU" suggestion: EUR# Ring 3 — AI fills the rest (still local)$ beleggo-mcp · repair_plan3 auto-fixed · 1 to confirm · 1 needs inputWatch
Check, repair, simulate the recipient, VAT, batches, creating and PDF import — eleven chapters, each explained first and then demonstrated live.
Recorded in the real studio — nothing staged.
Capabilities
Open, check, repair, create, convert — all locally in your browser, nothing uploaded.
XRechnung (UBL & CII), ZUGFeRD / Factur-X and Peppol BIS 3 — checked across five layers: XML schema, EN 16931, format, country CIUS and the PDF/A-3 container.
Cross-checked against the official KoSIT test invoices and the official KoSIT validator jar — proven in CI, not just claimed.
Safe structural repairs plus value-preserving normalisations (whitespace, escaping, date format) — with a before/after diff. The original is kept; amounts, VAT and IBAN are never changed automatically.
Correct any field directly, re-validate instantly, and download the corrected XML — or the repaired ZUGFeRD PDF.
Click an error and instantly see which field of the invoice it means. The cryptic rule codes are mapped onto the document.
UBL ↔ CII ↔ ZUGFeRD PDF — locally, re-validated after conversion. Convert a rejected UBL to CII without uploading it.
We check the PDF/A-3 container and reconcile the visible page against the embedded XML — catching mismatched totals or IBANs that XML-only checkers miss.
Check before you send whether the invoice will pass a public authority — including the Leitweg-ID with its check digits (which the standard rules don’t verify).
1,749 validation rules explained in plain language and linked from every result — no more guessing what BR-DE-15 or BR-CO-10 mean. All 215 XRechnung and Peppol rules are written out, in German, English and French.
The same rule is named differently in each syntax. Every rule page shows both paths together — which is exactly why checking a CII file against the UBL rules gives you a wall of errors that mean nothing.
When the totals disagree we name the amount, what the other figures make, and the difference — instead of just “BR-CO-15”. We never change amounts automatically.
An invoice that has gone out is not edited but reversed. One click opens it as a credit note (381) or corrected invoice (384), carries every entry across and fills in the reference to the original (BT-25).
Batch in the terminal, an MCP server for AI agents and a desktop app — the same engine, no server, no JVM.
All of it without installing anything — open an invoice and see straight away what fails.
For businesses
Since 2025 businesses must be able to receive e-invoices; sending follows in 2027/2028. Beleggo covers opening, checking, creating and converting — today.
Invoices never leave your machine. No cloud, no account, no server. Because no data is transmitted, no data-processing agreement (Art. 28 GDPR) arises — GDPR-friendly by design.
Unlike SaaS portals that bill monthly per user, or consulting test packages priced in the four figures: validation is free and unlimited, and Pro is a one-time payment. Predictable, not recurring.
The same verdict as the official KoSIT validator — the same rule base that also underpins the Service-BW endpoint and the government routers. Guaranteed in CI.
A CLI for batch runs and CI pipelines, an MCP server for AI agents (free and local — elsewhere a paid enterprise feature), a desktop app — the same engine as the browser, no JVM, no server hops.
The rule sets (KoSIT, XRechnung, Peppol) are bundled and automatically monitored against the official sources — nothing silently breaks in the background.
Before and after the invoice
Beforehand, the master data decides whether a valid invoice can exist at all. Afterwards it has to reach the books, the recipient and the archive. Four terminal commands, all local.
Every other command judges a document. This one judges the partner records documents are built from: who has no electronic address, whose VAT id is invalid, who is filed twice. From an ERP export, from the invoices you already have — or from both, which also shows where the master record and the invoices disagree.
beleggo stammdaten invoices/ --records vendors.csv --profile sap-bpFindings, not clearance: whether a VAT id is actually registered is a confirmation from the tax authority — an online step this deliberately does not take.
A Belegtransfer package (ZIP with document.xml) for DATEV Unternehmen online, or a real EXTF booking batch with one row per invoice per VAT rate. The consultant and client numbers, fiscal year and account length are asked for, never guessed. The batch stays uncommitted.
beleggo datev invoices/ --format dxso --out documents.zipBoth formats follow DATEV’s published format descriptions and have not yet been verified against a live DATEV import. Import into a test client first.
The validated UBL invoice in its Peppol envelope (SBDH), plus a manifest — exactly what an Access Point accepts for submission. Every header value comes from the document itself; a missing one gets the invoice refused and named rather than quietly filled in.
beleggo peppol-pack invoices/ --out outboundBeleggo is not an Access Point and transmits nothing. The package goes to the service provider you contract with.
The structured records of a folder as a set in which every entry links over the one before it. Change a document, a field or the ordering and the root changes — a single value you write down. Later the set checks itself and names every discrepancy. Optionally also as a Datenträgerüberlassung in the Beschreibungsstandard.
beleggo archive invoices/ --out holdings-2025Not an archive: the set is what an archive ingests, plus the proof it was checked. Software cannot be certified under GoBD (Rz. 179), and nothing here claims it.
Beleggo Pro
Checking and creating stay free. Pro unlocks the extras that make professional day-to-day smoother — as a one-time payment instead of a monthly fee, with a licence verified offline, without a server.
Branding only affects the PDF — the XML’s EN 16931 validity is untouched.
Integration & customization
You don't just want to use the checking, creation or conversion — you want it embedded in your ERP, portal or invoicing workflow, or a variant tailored to you? We bring the same engine into your environment and adapt it.
Embed & integrate
Drop the engine into your website, portal or workflow — as a web component, via the CLI or the MCP server. Local, no server hops.
Customize & white-label
Your own branding, tailored validation profiles, additional rules or formats — shaped around your use case.
On-premise & automation
Batch processing, CI pipelines and operation inside your own infrastructure, so invoice data never leaves the building.
Guidance & support
From the first integration to ongoing operation — with a named contact instead of a ticket queue.
Your contact
Questions about e-invoicing, integration or Pro? You write directly to the person behind Beleggo — no call centre, no queue.
Still unsure?
The same rule base as the official KoSIT validator — cross-checked in our CI.
See conformance →Nowhere. Everything runs locally in your browser — no upload, no account, no cloud.
See security →Checking and creating are free. Pro is a one-time payment, not a subscription.
See Pro →Receiving since 2025, sending from 2027/2028 — depending on turnover. The deadlines guide explains.
See the deadlines →FAQ
Validation runs entirely in your browser via Saxon-JS. We read the structured XML (from the PDF for ZUGFeRD) and check it against EN 16931 and the German business rules (BR-DE). Nothing is uploaded — your invoice never leaves your machine.
No. Everything runs locally — no upload, no account, no cloud. That is GDPR-friendly by design, because the invoice data never leaves your device — no data-processing agreement arises. Beleggo even works offline.
Yes. Our engine is cross-checked against the official KoSIT test invoices and the official KoSIT validator jar, and returns the same verdict — guaranteed in our CI. It is the same rule base that also underpins the Service-BW endpoint and the government routers.
XRechnung as UBL and CII, ZUGFeRD / Factur-X (XML inside the PDF) and Peppol BIS 3. You can convert between UBL, CII and ZUGFeRD PDF — locally, and re-validated after conversion.
Yes. The auto-fixer resolves structural errors and value-preserving details (stray whitespace, unescaped characters, a missing date qualifier) in one click — with a before/after diff. The original is kept; amounts, VAT and IBAN are never changed automatically. Anything else you can correct yourself in the editor with live validation.
Beleggo is not an archive. It creates and checks audit-ready e-invoices per EN 16931; the GoBD-compliant, tamper-proof retention (§ 147 AO, typically 8–10 years) is handled by your DMS or archiving system. Export the unchanged original as XML or ZUGFeRD PDF for that. The data stored in your browser (seller profile, customers) is not a substitute for an archive.
The B2G preflight checks your invoice against the XRechnung rules for public authorities — even if the file started in another format — and lists the mandatory fields still missing. The Leitweg-ID is validated including its check digits.
Yes. There is a CLI for batch runs and CI pipelines, plus an MCP server that lets AI agents validate, fix and create invoices — all with the same engine, locally, no JVM.
Checking and creating are free and usable without an account. Pro is a one-time payment (no subscription) and unlocks unlimited saved invoices plus PDF branding — your own logo, accent colour, a payment QR and a note on the PDF. The licence is verified offline.
XRechnung is pure XML (the German CIUS of EN 16931); ZUGFeRD / Factur-X is a hybrid: a readable PDF with embedded XML. Beleggo checks and creates both — and for the hybrid it even reconciles the visible page against the embedded XML. See the guides for more.
Only published, checkable facts — every claim with a source and a date checked.
The validation rules in plain language — linked straight from any check result.