A tool by {siteLink} — not a product of the Mustangproject.
Drag in the Mustangproject report — and the validated invoice with it. A Mustang report names its findings only by path and does not carry the document; only together do they give a view in which every finding stands at its place.
.xml — the order does not matterThese findings could not be placed anywhere in the document. Each one gives the reason. That is deliberate: a finding that points at the schema instead of a node belongs nowhere, but it must not be hidden.
This page runs in the browser without installation. The report and the invoice are read in the browser and not sent.
⚠️ What this page loads from outside is set in config.js. As delivered, the folder loads nothing: the fonts and the rule catalogue lie inside it. A single file without config.js loads the fonts from Google Fonts and the rule catalogue from {site}; nothing from the report is sent.
⚠️ This single file loads data from {site} but sends nothing from the report there. German and French with their rule catalogues, the code lists, Kits A and S, the fonts and the manual come from there; English and its rule catalogue are inside the file. Without a connection it shows English. Whoever wants no outbound call at all uses the app as a folder.
⚠️ Without the rule catalogue there are no plain-language explanations. If it cannot be loaded, the view shows the validator's own messages — complete, but in its own language. The eInvoice Validation Explorer for Mustang for WordPress gives the explanations.