How to verify a report someone sent you
A verification link shows a report that this service produced. Four checks tell you how far you can rely on it.
1. Signature
The page checks the Ed25519 signature with the public key published at /.well-known/rulestamp-report-key.txt. A valid signature means this service issued exactly this report digest at the time shown. A PDF or JSON file someone edited cannot carry a valid signature for a changed digest.
2. File digest
Choose your copy of the invoice on the verification page. If its SHA-256 equals the file digest in the report, you hold exactly the bytes that were checked.
3. Content digest
Mail gateways and access points sometimes re-format XML: line endings, indentation, namespace prefixes. The content digest is computed from the parsed XML, so it still matches when only the formatting changed. If it differs too, your invoice is a different invoice.
4. Re-run
The page can run the same rules on your file in the browser. With the same engine version the report digest must be identical. After a rule update the engine version changes and the digest is expected to differ; the page tells you when that is the case.
What a report does not tell you
- Whether the seller or buyer exist, or whether bank details belong to them.
- Whether the invoice was sent, received or paid.
- Full XML Schema validity and national rules outside Peppol.
If a link is used to make a fraudulent invoice look approved, use the report-abuse address on the page. Open the verification page.