VerifactuCloud

Where the product stands today

We would rather you knew exactly what is tested and what is not.

Tested

  • Registration records built by our backend and accepted by AEAT: today against the live environment, and for months before that against pre-production.
  • The SHA-256 hash chain works end to end and is validated by AEAT's gateway.
  • The QR code is verified against the specification: a rendered code was scanned with a phone and AEAT's own verification page resolved the invoice.
  • We check daily that our chain matches AEAT's: the hash is recomputed from the values the agency returns, rather than our own record being compared with our own.
  • Chain state recovery from the AEAT after a loss of local state.
  • We invoice our own company with this system, with our own FNMT representative certificate, and since September 2026 against AEAT's live environment. What we sell you is what we use.
  • Transactions not subject to Spanish VAT: on 3 September 2026 AEAT accepted a record classified N2, checked against the transmitted XML envelope rather than against a summary.
  • Production runs on its own database, with encrypted backups off the cluster and a restore that was actually verified rather than merely a copy kept.
  • Before we activate a taxpayer we ask AEAT whether it already holds records for them, month by month back to October 2024, and we activate only if it answers that it holds none: one month left unanswered is enough to stop it. Checked against the live gateway on 17 September 2026. The check is automatic; the taxpayer's authorisation with AEAT is not, and without it nothing is filed.

Not yet

  • Cancellation records are implemented, but we have never transmitted one — to the live gateway or to the test one. It is the only path in the system we have not walked end to end with AEAT.
  • We have no production customers, and we are not going to invent any.
  • We do not issue corrective invoices. Today a wrong invoice is put right with a cancellation record, which is not the same thing.

When any of this changes, we will say so here, with the date.

VerifactuCloud is not certified, approved or endorsed by the Spanish tax agency. The regulation provides for no prior approval: it is the software vendor who files a declaration of responsibility stating that their system complies. Ours is signed. Nobody can sell you an AEAT seal, because none exists. Be wary of anyone who tells you otherwise.

Let's talk

We are in production and taking on customers. Tell us what you invoice with, what volume you handle and how you want to integrate it, and we will tell you what fits and what does not. If you are integrating the API yourself, you can sign up directly in the partner dashboard.