A client's documents never leave the building.

Clients as folders

A name and a folder per client in the desktop app. One click checks the whole folder, every check dates the client, and the journal records who it was for.

Several watched folders

Watch all your client inboxes at once, subfolders included. New files are checked automatically, optionally sorted into valid/ and invalid/ and logged.

A stock-take per client

The folder as a population rather than a list of verdicts: what is an e-invoice at all, where the structured original is missing, how the findings fall across the BMF error classes, which suppliers to call first, and how much input VAT is at risk per currency.

A package to hand over

One dated folder per client: the stock-take, the supplier call list, the journal, the draft process documentation and the sealed document set — all from one run, so the parts cannot describe different documents.

beleggo bundle client-a/2025/ --out handover/client-a --client "Client A" --report

A readiness report on the client’s software

Hand the client a folder of invoices, have their software judge each one, put the verdicts in a two-column CSV — and get the dated sheet naming the defects that software did not catch. The reference is the Beleggo engine under the rulesets pinned in this build; both are printed on the report.

beleggo readiness corpus/ --verdicts verdicts.csv --out report.pdf --brand practice.json

On the practice’s letterhead

Name, website, logo and logo position from a JSON file beside your documents — or set in the desktop app, with a preview. The report, the process documentation and the check report all come off the same paper.

"Check your invoice on our website."

Your own validator, under your name, on your website. The client drops their file in and has a verdict immediately — no account, no upload, and without you ever seeing the document. That is precisely the offer a competitor with a server upload cannot make.

The client creates a valid invoice themselves

For the clients with no ERP who are not going to buy one: fill in the form, download a valid XRechnung or ZUGFeRD PDF, with validity shown as they type. It saves the client the software purchase and you the phone call.

A dated record per client

What a client’s software checked and what it found — detected, missed, wrongly accepted, false alarm, no verdict. On your letterhead, with the date, kit version, content hash and every ruleset version. Identical input, identical report.

Test invoices carrying the client’s own details

Instead of "Example Ltd", a data kit carrying the client’s real company details. They test their own inbound processing against documents that resemble their actual traffic — not against examples any import can tell are examples.

The whole document folder, gone through once

A stock-take and a batch run over a client’s complete inbound: what is an e-invoice at all, which suppliers are still sending the wrong thing, which documents have to be rejected, how much input VAT is at risk. A service with a result that can be billed.

Process documentation and the evidence

The e-invoicing chapter as a draft on your letterhead, plus the journal and the sealed document set that evidence the checking happened. Two billable deliverables out of the same data, in an evening rather than a project.