Validation build: the evidence log is live; the pricing example is simulated and places no cover. What that means

RiskRouter

For finance teams, and the software that issues and receives invoices

When a tax audit or a customer questions an invoice, show the copy you kept is the one you issued.

Years after it was issued, an invoice is checked by a tax inspector, contested by a customer, or set beside a supplier’s copy that reads differently. The question is whether the copy in your archive is the one that existed at the time.

Try it in two minutes Talk about a pilot
When it is tested
A VAT audit; a customer or supplier disputing an amount or a date; an investigation into altered or duplicated invoices.
What you will be asked for
That the authenticity of origin, the integrity of content and the legibility of each invoice are ensured from issue to the end of its storage period, for example by business controls that create a reliable audit trail between an invoice and a supply (VAT Directive 2006/112/EC, Article 233(1)); that copies of invoices issued and received are stored (Article 244), for a period each Member State sets (Article 247(1)).
What goes wrong today
Archives are migrated, PDFs are regenerated from the accounting system, and e-invoicing formats change. A regenerated invoice may be correct and still not be the one issued, and nobody can show which.
What changes
Each invoice is sealed when it is issued or received: a fingerprint of the file exactly as sent, with its number and date. The invoice stays in your archive; only a salted fingerprint reaches us. Numbered in a chain, a series can be shown to be complete: an invoice sealed and later left out shows as a gap.

Sealing shows that a record existed unchanged from a given moment; whether your records are enough is yours to judge. A seal is not an electronic signature or an e-invoicing format, and replaces neither. What the VAT Directive asks · Showing nothing is missing

Try it in two minutes

  1. Choose a real file of your own: an invoice you issued, as a PDF or an XML e-invoice. It is read in your browser and never uploaded.
  2. Seal it on Seal a file. A free sandbox key is issued on the page; only a salted fingerprint reaches the log.
  3. Make a copy, change one character in it, and check both against the receipt at Check. The copy fails; the original passes.

From your own systems it is one API call per record. Integrate · Other industries