Verifactu statement of conformity with the Verifacti API

No AEAT certification: the producer self-certifies, also in a mixed architecture

The statement of conformity (declaración responsable) is the self-certification by which the producer of an invoicing system (SIF) declares that it complies with RD 1007/2023 and Orden HAC/1177/2024: the Spanish Tax Agency (AEAT) does not certify or register any software. If your software uses the Verifactu API, the architecture is mixed and each producer publishes its own: you, your SIF’s, citing Verifacti as an external component; Verifacti, its API’s. We give you Verifacti’s statement, its version by API and a template for yours.

Test environment and test NIF included
GET /verifactu/declaracion · no API key
curl https://api.verifacti.com/verifactu/declaracion
200 OK
{
  "url": "https://storage.googleapis.com/verifacti_non_sensitive_prod/declaracion/actual.pdf",
  "url_version": "https://storage.googleapis.com/…/declaracion/<versión>.pdf",
  "sistema_informatico": {
    "nombre": "bilbabit",
    "id": "A1",
    "version": "<versión vigente>"
  }
}

How to make the statement of conformity if you use the Verifactu API

  1. 1

    Download Verifacti’s statement

    As a PDF or with GET /verifactu/declaracion, and note the current API version.

  2. 2

    Fill in the template

    With your SIF’s details, citing Verifacti as an external component, with its version.

  3. 3

    Publish it in your software

    Visibly (for example, in the help section) and for whoever sells it. Update it with every version of your SIF.

What Verifacti gives you for your statement

  • Verifacti’s statement of conformity

    Public, as a PDF, to cite in yours.

  • The current version by API

    GET /verifactu/declaracion returns the PDF URL and the version, so your statement always cites the right one.

  • Word template

    With notes to complete your SIF’s statement; delete the notes when done.

  • VERI*FACTU mode only

    Verifacti’s statement says its component works only as VERI*FACTU, sending every record to the AEAT.

Mixed architecture: who does what

Your SIF is the main component and Verifacti the external one. Orden HAC/1177/2024 (art. 15) provides for a SIF with components from different producers; each one publishes its statement.
Split of tasks between your software and Verifacti
TaskYour SIF (main component)Verifacti (external component)
Statement of conformityPublishes its own and cites Verifacti with its versionPublishes its own (PDF and GET /verifactu/declaracion)
Sending each invoiceCalls the API when issuing, with correct dataGenerates the invoicing record and sends it to the AEAT with its certificate
Fingerprint and chaining—Computes the fingerprint and chains each record
QRPrints it on the invoice with the VERI*FACTU legendReturns it in the response, in Base64
Representation formEach taxpayer signs it before their first invoiceSubmits as a social collaborator; provides the forms and online signing

Which SIF identity the records carry

By default, each NIF’s invoicing records carry Verifacti’s identity in the SistemaInformatico block. If your software is the main component and you want yours to appear, set your system’s identity on the NIF with PUT /nifs/{entorno}/{nif}/sistema_informatico (or when registering it) and send your SIF’s version and multiple-taxpayers indicator with each invoice.

Changing the identity (or the producer) is a new SIF for the AEAT: the NIF starts a new chain of records. Details in the NIF management API documentation.

The statement belongs to Verifactu; TicketBAI has its guarantor software register

The statement of conformity belongs to Verifactu (RD 1007/2023). TicketBAI has no statement: the foral treasuries keep a guarantor software register, and Verifacti is registered in Álava, Bizkaia and Gipuzkoa.

Why Verifacti for Verifactu compliance

Built for developers

Public documentation with examples for every call, quick start guide, Postman collections, llms.txt and a free account with a test environment.

Typical integration: one to three developer days

Specialists in Spain

Common and foral territory: Verifactu, TicketBAI and SII with one provider.

TicketBAI guarantor software in Álava, Bizkaia and Gipuzkoa

Proven reliability

Hundreds of companies and software vendors in production with Verifacti. Data hosted in the EU and an SLA in the terms of use.

AEAT social collaborator

Statement of conformity: rules and dates

The obligation to certify the SIF with a statement of conformity is in RD 1007/2023 (art. 13), and its content in Orden HAC/1177/2024 (art. 15). For producers it has been in force since 29 July 2025; the postponement announced for taxpayers does not change it.

Producers and resellers of invoicing softwareSince 29 Jul 2025
RDL 15/2025 did not change this date.
In force
Corporate Income Tax payers1 Jan 2027
Published in the BOE, future date
Everyone else, including the self-employed1 Jul 2027
Published in the BOE, future date
Postponement of the pending obligationsOct 2028
The note does not specify the scope for businesses invoicing over €8M.
Announced, no rule published

This is not advice: each taxpayer determines what applies to them with their adviser.

Verifactu API pricing

From

€14.99

/month per NIF active in production, excl. VAT

See all prices
  • The price per NIF goes down with every tier.
  • Free test environment and test NIF.
  • Annual plan with a 10% discount, no setup fees.
  • Verifacti’s statement and the template are free.
  • Startup plan for companies under 12 months old, with under €100,000 in revenue and under €200,000 in funding.

Vendors who already integrated it

Koibox
«La integración con Verifactu fue muy sencilla y el soporte ha sido excelente. Siempre atentos y rápidos para resolver dudas. Muy contento con el servicio.»
Antonio TapiasCTO & Co-Founder, Koibox
Boxify
«Hemos integrado nuestro software en tiempo récord. La documentación es clara y sencilla, y los ejemplos variados y muy útiles. El equipo de soporte me ha ayudado con todas las dudas.»
Kike IsasiFounder, Boxify

Questions about the statement of conformity

More questions about the Verifactu API

Is there software certified or approved by the AEAT?

No. The AEAT does not certify or register software: each producer self-certifies with its statement of conformity.

If I use an API like Verifacti, do I need my own statement?

Yes. It is a mixed architecture: your SIF and Verifacti are components from different producers and each one publishes its own. In yours you cite Verifacti as an external component, with its version.

Where do I have to publish the statement?

In the system itself, visibly, for every version, for the user and for whoever sells it. In web software, for example in the help section.

Is there a model or example statement?

Yes. The AEAT publishes an example and Verifacti provides a Word template prepared for a mixed architecture.

With Verifactu postponed, do I have to publish it now?

The obligation for producers and resellers to offer compliant systems has been in force since 29 July 2025; the postponement announced for taxpayers does not change it. Verifactu deadlines.

Start integrating today

Try it for free with the test environment.

Test environment and test NIF includedSee pricing