Verifactu API FAQ

Answers to the most common questions when integrating Verifactu with the Verifacti Verifactu API: how to create invoices and corrective invoices, the QR code, AEAT errors, webhooks, going to production and the statement of conformity. What the rules say about who it applies to and from when is on the Verifactu page. The full API reference is in the documentation.

Common Verifactu questions

8 questions

What are the deadlines for Verifactu compliance?

RDL 15/2025, of 2 December (BOE of 3 December 2025), extended these deadlines. We outline the deadlines published in the BOE below, which the AEAT explains here.
1. Deadlines for own-use software
If your invoicing software is for your own use (for issuing your own invoices), then your deadline would be:
  • January 1, 2027 if you are subject to corporate tax.
  • July 1, 2027 for others (mainly freelancers/self-employed)
These dates are published in the BOE. In addition, the Ministry of Finance has announced a postponement to October 2028 (information note of October 5, 2026), with no rule published yet.
2. Deadlines for software producers or vendors
If you are a software producer or vendor, your software must have been adapted to Verifactu since July 29, 2025. The AEAT has insisted that all software sold today must be adapted. This deadline has not changed and can be confirmed in the AEAT's own FAQ.
Exception: software already sold with a multi-year maintenance contract—the deadline is extended to the 2027 deadlines (see above).
All the dates, with their status, in When Verifactu comes into force.

When must I send invoices to the AEAT?

The AEAT's expectation is that invoices are submitted in real time; it is not possible to send invoices at the end of the day or of any time period.

Why is early adoption of Verifactu recommended?

Incentives for software manufacturers, vendors, and distributors
  • Legal obligation - Since July 29, 2025, only invoicing software adapted to Verifactu can be sold in Spain. Selling non-adapted software exposes the SIF to very significant penalties. This legal obligation has not changed with the postponement of December 2, 2025 (RDL 15/2025), which only affects individual taxpayers with their own software, nor with the postponement to October 2028 announced by the Ministry of Finance with no rule published. All the dates, with their status, in When Verifactu comes into force.
  • Competitive advantage - Successive AEAT announcements and their media coverage have had the effect of ensuring awareness of the regulation among taxpayers. Software customers will likely place greater value during 2027 on software solutions that solve the Verifactu challenge. Any software offering from now on that does not incorporate Verifactu will be at a competitive disadvantage compared to those that can ensure regulatory compliance.
For companies that issue invoices
Adapting before the mandatory date lets you test the integration and solve issues without deadline pressure.

What is the difference between an invoicing record and an invoice?

An invoicing record and an invoice are not the same thing.
Invoicing records are the XMLs generated by Verifacti from the calls made to the API. For each call made to the Tax Agency, there is one XML (invoicing record).
An invoice can have one or more invoicing records.
  • Initially, when a new invoice is created, there would be a single record for that invoice.
  • If subsequent calls related to the same invoice are made later (for example, a call to the amendment endpoint), there would be more than one record for the same invoice.

Must tickets, receipts, and simplified invoices be reported to the AEAT?

In the eyes of the Tax Authority, a purchase ticket is equivalent to a simplified invoice, and simplified invoices must be reported through the Verifactu system. In other words, all tickets must be reported through the Verifactu system as simplified invoices.
See the simplified invoice example.

Is it possible to send invoices for the same NIF with different SIFs?

When using Verifacti, all invoices from different series are consolidated into a single chain, so effectively there is always a single SIF. This architecture is described in the developer FAQ here (page 10).

What is NO VERI*FACTU mode and why is it not covered by the API?

The tax authority offers two paths to comply with the Verifactu system: VERI*FACTU mode and NO VERI*FACTU mode.
  • VERI*FACTU mode consists of sending invoicing records to the tax authority in real time.
  • In NO VERI*FACTU mode, records must still be generated in real time, but they are not sent to the AEAT—they are retained by the invoicing software.
NO VERI*FACTU mode is not covered by the API due to the zero demand we have received for this way of complying with the regulation. Here are some of the drawbacks of NO VERI*FACTU mode:
  1. Storage obligation: In NO VERI*FACTU mode, the taxpayer does not send invoices to the tax authority in real time, which creates an obligation to store the invoicing records. This means that the invoicing software must be prepared to send all the taxpayer's tax information upon request by the Tax Agency.
  2. Additional requirements: choosing this path implies additional technical requirements such as the need for an event log.
  3. Preferred mode: the AEAT presents VERI*FACTU as the preferred mode.
In VERI*FACTU mode, there is no obligation to store the invoicing records sent to the Tax Agency, neither for the invoicing software nor for the taxpayer, since those records have already been previously submitted. The tax authority is clear on this point: the obligation to store invoicing records only exists in NO VERI*FACTU mode.
👉 Watch short video: Verifactu vs NO VERI*FACTU, and the obligation to store the XML invoicing records
More in VERI*FACTU and NO VERI*FACTU modes.

Is the Verifactu system mandatory for companies already enrolled in the Immediate Information Supply (SII) system?

No, companies enrolled in the Immediate Information Supply (SII - Suministro Inmediato de Información) system are not required to adapt to the Verifactu system.
For an official and specific confirmation for your case, we recommend consulting directly with the Tax Agency (AEAT) via email at verifactu@correo.aeat.es.

How the API works

15 questions

How does the Verifacti API work?

The Verifacti API for Verifactu is designed to facilitate the submission of tax information to the Tax Agency, providing an accessible solution for invoicing software developers. Instead of integrating directly with the tax authority's API, developers can make their requests to the Verifacti API, thus avoiding technological complexities and technical barriers.
👉 Watch short video: how our API works (Part 1) - Explanation and first steps
Ease and speed
The Verifacti API is designed to offer a simple and quick integration thanks to:
  • Clear and concise documentation, with examples and Postman collections.
  • Use of JSON as the communication format.
  • No need to handle the wait between submissions imposed by the AEAT: Verifacti queues the records and respects its flow control.
  • Elimination of the need for your own certificates, using Verifacti's representation certificates.
  • Dedicated technical support, especially during the integration phase.
The Verifacti API workflow follows this scheme:
  1. When a new invoice is issued in the invoicing software, a request is sent to the Verifacti API using a specific API key for the issuing company (taxpayer NIF). The invoice data is sent in JSON format.
  2. The Verifacti API responds immediately with a QR code in Base64 format, ready to be included in the invoice and delivered to the recipient.
  3. The Verifacti API immediately generates the invoicing record (XML file) complying with all requirements (immediacy, chaining, format, unalterability, integrity, traceability, etc.).
  4. In the following seconds/minutes, Verifacti sends the information to the tax authority's API, which issues a response XML.
  5. The AEAT response must be confirmed to verify whether the invoice was accepted or requires corrections: this can be done via webhook or by making a subsequent call to the record status endpoint.
Prior validation and AEAT errors
The endpoints and the structure of the calls follow those of the AEAT API. Each invoice is validated before it is sent, and any error comes back with a code (code catalogue). When the AEAT rejects a record, its response comes through as is, with the AEAT's code and message.

What steps should I follow to integrate with the Verifacti API and ensure regulatory compliance?

We have an essential resource that is a must-read for the steps needed for a successful integration: quick start guide.

Who is responsible for generating the hash, the chaining, and the XML?

The Verifacti API is responsible for generating the Invoicing Record (XML) and everything included in and dependent on it: hash and chaining.
The software integrating with Verifacti only needs to ensure that requests are made with the issuer's unique API key and the JSON with the invoicing operation data to our API.
From your call onward, we take care of the rest:
  • We generate the XML.
  • We return the QR code so you can attach it to the invoice.
  • We submit the XML to the AEAT with our own digital certificate.
  • We provide you the AEAT response via webhooks or through the record status endpoint.

What is the traceability requirement and how does the Verifacti API comply with it?

The traceability requirement demanded by Verifactu refers to the mandatory chaining of invoicing records (XML). Each new XML generated must reference the previous XML, thus creating a chain that allows you to jump from one XML to another until reaching the first in the chain.
The record chain therefore constitutes a chaining of all invoicing records (XMLs) generated and sent by an invoicing information system in chronological order of creation, regardless of whether the records refer to invoice creation or other operations (such as cancellation or amendment), and regardless also of the numbers and series of the invoices issued.
When working with the Verifacti API, traceability is ensured by the API itself, which generates the XML files from user calls. Thus, when a call is made to the Create Invoice endpoint and a 200 status code is received, it can be assumed that Verifacti has generated the XML file from the call data and that it is correctly chained to the previous one.
Traceability should not be confused with the invoicing regulation requirement that establishes the mandatory sequential numbering of invoices within the same series. This sequentiality requirement is a requirement that Verifactu does not enforce (it does not return an error when sequentiality is not met) and has nothing to do with traceability.

Why does it take a few minutes for my invoice to reach the AEAT?

In the case of Verifactu, the tax authority has imposed limits on the quantity and timing of requests that can be made to the AEAT, and so the API returns the QR immediately and the invoicing record reaches the tax authority afterwards, usually within one or two minutes. This is correct and is the way the AEAT has chosen to manage requests to its API.
In TicketBAI, the response immediately returns the TicketBAI code (tbai) and the QR to print on the invoice; the submission to the foral treasury also happens afterwards.

What capabilities and features does the API offer?

These are some capabilities and features of the API:
  • QR code generation
  • XML generation (including chaining and hash)
  • Certificate management
  • Retry logic if the AEAT API is down
  • Batch transmission
  • TicketBAI API compliance included in the price
  • Each invoice is validated before it is sent, and any error comes back with a code
  • Invoice recipient verification to avoid AEAT errors
  • NIF management API for programmatic registration and deregistration of users
  • Webhooks to receive AEAT responses
  • Automated representation management system via API
  • Serverless architecture based on containers, enabling automatic scaling based on load
  • Simple and clear API documentation

Can I integrate Verifacti with my programming language and tech stack?

Verifacti can be integrated with any tech stack. The only technical requirement is that your stack is capable of making calls to a cloud REST API. This is very common and widely supported in any modern language or framework (and also in older ones).
If you don't know how to do it, you'll easily find resources on the web, ChatGPT, or YouTube with tutorials explaining how to make calls to a REST API from practically any technology. It is a standard, completely safe, and common procedure in software integration.
Additionally, we have clients who have successfully integrated Verifacti from a multitude of languages, frameworks, and ERPs. Among them, notable examples include:
  • Programming languages: Python, Java, C#, Visual Basic .NET, PHP, Ruby on Rails, Go, Rust, Kotlin, Swift, Objective-C, C++, Perl.
  • JavaScript environments and frameworks: Node.js, Express, NestJS, React, Angular, Vue.js, Next.js, Nuxt.js, Svelte.
  • Backend frameworks and stacks: Django, Flask, Spring Boot, Laravel, Symfony, CodeIgniter, ASP.NET Core, Grails.
  • Enterprise integration environments / ERPs: Odoo (custom modules), Dolibarr, SAP, Microsoft Dynamics, Sage, Zoho, Oracle NetSuite.
  • Invoicing and accounting systems: Holded, A3 Software, Factusol, ContaPlus.
  • Automation and integrations: Zapier, Integromat (Make), n8n.
  • Databases and connectors: MySQL, PostgreSQL, SQL Server, MongoDB, Firebase, Redis.
  • Other common environments: WordPress (with plugins), Magento, Shopify, WooCommerce, Prestashop.
In summary, it doesn't matter if you work with classic or modern technologies: Verifacti is compatible with any tech stack.

How does Verifacti guarantee traceability if a single company (same CIF) uses the system to invoice from multiple locations or POS terminals with different invoice series?

For companies with multiple stores or POS terminals and different invoice series, if they use an external component like Verifacti to chain all their invoices, all these locations are considered a single Independent Invoicing Software (SIF).
The AEAT argues that the SIF definition refers to the smallest independent invoicing software. Given the architecture of our solution, the invoicing from different stores is not independent of each other, so they form a single SIF and a single chain.
This method is fully valid and compliant with the regulation, offering an alternative to other models that, while also correct, are not the only way to operate.

Is it possible to send invoices to the AEAT through the Verifacti API using Excel or Google Sheets?

Verifacti does not offer a direct plugin for Excel or Google Sheets. However, from Google Sheets it is possible to make calls to external APIs, which would be necessary to interact with the Verifacti API and send invoices to the AEAT.

Do you have Postman collections?

Yes. In the API documentation you will find the Postman collections to download.

How does the Idempotency-Key header work and when should I use it?

The optional Idempotency-Key header lets you retry a submission without the risk of duplicating it, for example after a timeout or a dropped connection. It is accepted by /verifactu/create, /verifactu/create_bulk, /verifactu/modify and /verifactu/cancel, in TicketBAI by /ticketbai/create, /ticketbai/modify and /ticketbai/cancel, and in the SII by /sii/create, /sii/create_bulk, /sii/modify and /sii/cancel.
Generate a unique key per operation (a printable ASCII string of 1 to 255 characters; a UUID works) and store it with the invoice before sending it. This is how it works:
  • Same body, same key: the API returns the status code and body of the first response, with the Idempotent-Replayed: true header, and does not create a new record.
  • Responses that are stored: 2xx and 4xx. A 400 is replayed too, so if you fix the data, use a new key. 5xx responses are not stored: the retry is processed again and all the data is validated again, including the issue date.
  • Duration: 24 hours from the first response. Retries do not extend it; after that, the request is processed as new.
  • Scope: the key is tied to the issuing NIF, not to the API key, so it keeps working after a key rotation. A request rejected at authentication (401) does not use it.
  • Errors: the same key with a different body or on another endpoint returns 422; if the first request is still in progress, the retry returns 409 and you just need to try again in a few seconds.
If you lost the response and more than 24 hours have passed, first check whether the invoice was registered: how to know whether an invoice was registered without its uuid. Full details in the API documentation.

What data from the Verifacti API responses should I store in my database?

For effective tracking of invoices sent through the API, we recommend storing the following fields in your database:
  • From the Create Invoice response: the uuid, the Base64 string of the QR, and the hash.
  • From the Invoice Status response: fecha_expedicion (issue date) and the current status of the invoice. Additionally, for error tracking and debugging, it is very useful to store the estado (status) and mensaje_error (error message) obtained from this query.
  • From the Download XML response: xml_req (request XML) and xml_res (response XML) for auditing and reference purposes.

Are the endpoint URLs different for test and production environments?

The endpoint URLs do not change—they are the same for both test and production environments. What determines which environment is used is the API key being used.
Each API key has an associated environment: test or production.
  • In the test environment, the company API key starts with vf_test_
  • In the production environment, the company API key starts with vf_prod_

Do I have to include the SIF identifier in my calls to Verifacti?

By default, no. Verifacti generates the XML sent to the AEAT and fills in the SistemaInformatico block with its own identity.
If you want Verifactu records to carry your software's identity, set it per NIF (the sistema_informatico field of POST /nifs or PUT /nifs/{entorno}/{nif}/sistema_informatico) and send sistema_informatico.version and sistema_informatico.indicador_multiples_ot in every request. See What SistemaInformatico data appears in the records Verifacti sends to the AEAT?

What SSL/TLS versions does the Verifacti API support?

The Verifacti API supports TLS 1.2 and above. It is not compatible with SSLv3.

New invoice

16 questions

How should I manage invoice numbering with Verifactu to ensure sequential and correct ordering of invoices within the same series?

Invoicing regulations require that invoices be issued with consecutive numbering within the same series.
Number assignment
The correct practice is to assign the invoice number only after it has been successfully sent to our API and a 200 (OK) status code has been received in response. The 200 status confirms that the invoicing record has been created, and regardless of whether the AEAT accepts or rejects the invoice for any reason, the number has been correctly assigned.
That said, if invoices are issued slightly out of order with a difference of a few minutes, this is not usually considered a serious problem.
Handling AEAT invoice rejection
Once a 200 response has been obtained from the Verifacti API, if the AEAT subsequently rejects the invoice, the number would still be correctly used and should not be "released" for another invoice. In this context, the invoicing record has been created and submitted to the AEAT, and therefore the number is used by the invoice with errors. The AEAT rejection must be resolved through a corrective invoice that references precisely that erroneously issued invoice.
Incidents
In incident situations such as an internet outage, invoice generation may be interrupted even while sales continue to occur (see incidents section). Ideally, when the connection is restored, invoices should be sent in the order of the original transactions.
Do not confuse sequentiality with traceability
This requirement for sequential invoice numbering within the same series established by invoicing regulations (which Verifactu ignores) should not be confused with the chaining or traceability requirement that Verifactu does establish, which affects the invoicing records (XMLs) that the Verifacti API is responsible for generating. It is therefore Verifacti that guarantees this XML traceability requirement.
Verifactu accepts non-sequential invoices
It is important to clarify that Verifactu accepts submissions of invoices with non-consecutive numbering without errors. Therefore, it should not be assumed that because invoices were accepted without errors, the sequentiality requirement has been properly met. Complying with Verifactu does not exempt you from the sequential numbering obligation of invoicing regulations.

How should I fill in the issue date and operation date fields when creating invoices, and what is the impact on numbering and taxation?

There are two date fields in the Verifacti API:
  • fecha_expedicion (issue date): mandatory field, this is the invoice issue date which must be the current date.
  • fecha_operacion (operation date): optional field, in case you want to issue an invoice for a transaction that occurred on a past date, this field should be used.
Key points to keep in mind:
  • The fecha_operacion field does not directly affect the sequential numbering of invoices.
  • Sequentiality is governed by the issue date.
  • Numbering must be consecutive and uninterrupted based on this issue/registration date.
  • The fecha_operacion field simply indicates when the delivery of goods or provision of services took place. It can be earlier than the issue date.
  • The operation date determines which settlement period (month or quarter) the VAT should be attributed to, even if the invoice is issued later (always within the regulatory deadlines).

How can I include the invoice creation time in the call?

There is a field in the invoicing record (XML) that specifies the exact time of the invoicing record generation (FechaHoraHusoGenRegistro). This field is completed by the Verifacti API and does not require any data in the user's API call.
This is the time the system uses for time control: the call to the Tax Agency (or delegated software) must be made within a maximum of 240 seconds (4 minutes) after this record generation time, according to the regulation.

What is the maximum length of the series field?

The combination of the series and invoice number must not exceed 60 characters.

Why are there only 12 lines in invoices?

One of the Verifactu system requirements when creating a new invoice is to include a breakdown by VAT type, which in the Verifactu API is called lines.
It is important to clarify that the tax authority does not use this breakdown to obtain information about the products or services sold. Its purpose is exclusively to reflect different VAT types in cases where the same invoice includes multiple VAT types.
Therefore, in situations where the entire invoice has a single VAT type, only a single line will be necessary.

How should the invoice breakdown lines be grouped by tax rate and tax regime key?

The breakdown lines in the invoice summary must be grouped by both tax rate and tax regime key.
If there are different combinations of these two criteria, a separate breakdown line must be generated for each one, even if the tax rate is the same but the tax regime key differs.

Example: Several VAT rates.

How do I manage self-invoices or invoices issued by third parties in Verifactu?

Verifactu does contemplate invoices issued by third parties or by the recipient (self-invoices). In the API, this is done using the emitida_por_tercero_o_destinatario field. These invoices can and must be sent just like all others.
Some important clarifications regarding this type of invoice:
  • For calculating Verifacti API costs, in this type of invoice, the taxpayer (VAT payer) must be registered as a NIF, even if they are not a user of the invoicing software.
  • In the JSON, the taxpayer's data will not appear, because that data is communicated through the NIF API key.
  • In the case of an invoice issued by a third party, it is necessary to indicate who the third party is in the specific fields nombre_tercero and nif_tercero.

Example: Issued by a third party.

How do I include IRPF (income tax) withholdings?

Invoices that include IRPF (income tax) withholding, such as payments to freelancers, must exclude the IRPF component when reported to the Tax Agency through Verifactu. This means that the total invoice amount in the hands of the final recipient will be different from the total invoice amount in Verifactu. When viewing an invoice on the AEAT website (through the QR), the AEAT itself explains that the data shown there does not include withholdings.

Example: Disbursements and withholding.

How can I reflect a discount on an invoice?

In Verifactu, there is no specific "discount" field: you must reflect it by adjusting the invoice amounts. You can do this by subtracting the discount directly from the taxable base of the line(s) (sending the already net base) or by adding an additional line with a negative amount (same VAT key as the affected line), so that the total amount is correct; if the discount is after issuance, then a corrective invoice/credit note is appropriate.

How do I include disbursements (suplidos)?

The tax authority establishes that disbursements (suplidos) do not have to be mandatorily included in invoices sent through the Verifactu system. However, they can be voluntarily included through an additional line with 0% VAT.

Example: Disbursements and withholding.

Does the Verifacti API support the Special Travel Agency Regime (REAV)?

Yes, the Verifacti API supports the Special Travel Agency Regime (REAV - Régimen Especial de las Agencias de Viajes). To register invoices under the Special Travel Agency Regime (REAV), use the clave_regimen parameter with the value 05.
You can find more information in the API documentation.

Does the Verifacti API support the Special Used Goods Regime (REBU)?

Yes, the Verifacti API supports the Special Used Goods Regime (REBU - Régimen Especial de Bienes Usados). To register invoices under the Special Used Goods Regime (REBU), you should use the clave_regimen with the value 03.
You can find more information in the API documentation.

Example: REBU (used goods).

How is the Equivalence Surcharge (Recargo de Equivalencia) managed when sending invoices to the Verifacti API?

The Equivalence Surcharge (Recargo de Equivalencia), if applicable, must be indicated in the invoice lines, specifying both the percentage and the corresponding amount. This aligns with the tax breakdown structure in the invoice lines.

Example: Equivalence surcharge.

How are invoices issued in foreign currency reported?

All invoices must be reported in EUR.

Is there a limit on the number of series for a single NIF?

You can use as many series as you want within the same NIF.

Is it necessary to verify the acceptance of the previous invoice by the Tax Agency before making a new call to the Verifacti API?

No, it is not necessary to verify that the previous invoice has been accepted by the Tax Agency.
In fact, in many contexts, it is not desirable to wait, since the AEAT response could take minutes.
The only requirement is that the invoicing record associated with the previous invoice has been correctly generated, which in practice means that the previous Verifacti API call returned a 200 status code.

Recipient and NIF validation

4 questions

How do I enter the tax details (NIF, DNI) of domestic or foreign invoice recipients?

When issuing an F1-type invoice, it is necessary to identify the recipient. Two cases are distinguished here:
When the recipient is a Spanish individual (freelancer or not), a Spanish entity with a valid NIF, or a foreigner with a NIE.
* In this case, the "nif" and "nombre" (name) fields must be provided, where "nombre" corresponds to the first and last names for individuals and the company name for entities.
  • For individuals, the name must be sufficiently similar to the one appearing on the DNI (national ID).
When the recipient is not a Spanish individual, a Spanish entity with a valid NIF, nor holds a NIE.
* In this case, the "nombre" (name) and "id_otro" (other ID) fields must be used to identify the recipient.
  • A specific case within this general case is that of EU companies with a valid VIES VAT number.
  • To identify foreign or non-resident clients, the passport or, in general, the field 06 (other supporting document) in the API can be used. In these cases, the AEAT does not validate said document.
If an invoice is issued with a recipient error, it will be necessary to issue a corrective invoice by substitution.

How do I validate the tax details of domestic and foreign invoice clients and recipients to avoid errors?

Verifacti provides several resources to help validate invoice recipient data, thus minimizing errors.
1. Default invoice recipient validation
In the Create New Invoice call, there is a validar_destinatario field that is set to true by default.
  • If the nif field is included, we validate by default that it is registered with the AEAT, since if it is not, the AEAT will reject the submission. This requires an additional call on our side, so if you are sure that the recipients' NIFs are registered, you can disable this validation by setting this field to false. This will make the call faster.
  • Similarly, if the id_otro field is included with id_type equal to 02, we validate by default that the VAT is in the VIES registry. You can disable this validation by setting this field to false.
2. Specific validation endpoints
There are also specific endpoints for selective use outside the invoice creation process. These endpoints require an activated paid subscription.
  • The Validate NIF at the AEAT endpoint allows performing the above validation through an endpoint.
  • The Validate VAT in VIES endpoint allows validating that an intra-EU VAT number is in the VIES registry. Note that this endpoint uses an EU API that fails quite often.

How do I proceed if the client's DNI/NIE data is missing or incorrect on an invoice?

If the client's DNI/NIE data is incorrect or missing, and the legal conditions allow it, you can convert the invoice into a simplified invoice.
To do this, resend the invoice marking the tipo_factura as F2 and omitting the NIF and client name. If you want to issue a full invoice (type F1), it is mandatory to include the correct recipient data.

Can I mark the client as 'NOT registered' if I don't have their correct DNI data?

If the name associated with a client's DNI is found to be incorrect, it is essential to obtain and record the exact name.
The Tax Agency (AEAT) requires that the recipient's name be correct. It is not permitted to mark a person as NOT registered if they are actually in the registry, as the problem lies in the inaccuracy of the data (the name) and not in the lack of DNI registration.

QR code

10 questions

What is the QR code and how do I obtain it?

The QR code in the Verifactu system is an encoded URL, unique for each invoice, located on the Tax Agency website. This URL allows verifying whether the invoice has been received by the tax authority through the Verifactu system. The tax authority expects all invoices issued by taxpayers subject to the Verifactu system to include this QR. Thus, any recipient of an invoice with a QR can easily access the URL from their mobile device and verify that the invoice has been reported to the Tax Agency.
The QR is generated from the following 5 invoice fields:
  1. Issuer NIF
  2. Series
  3. Number
  4. Date
  5. Amount
When a new invoice call is made to the Verifacti API, the synchronous immediate response includes the QR in Base64 image format.
👉 Watch short video: QR code in Verifactu, what it is and how it is generated
More in Verifactu QR code.

Can I recover the QR code of an invoice if I didn't save it in my database?

If you didn't save the QR in your database, you can make an additional call to the record status endpoint to recover it. To do this, you need to have saved the UUID of the request with which you created the invoice. Remember that with Verifactu, it is only necessary to include the QR on the invoice; it is not necessary to include or store the hash, unless you offer non-Verifactu services.

Do I need to include the hash on the invoice to comply with Verifactu?

With Verifactu, it is not necessary to include the hash on the invoice—the QR is sufficient. The hash must be included in the XML sent to the tax authority. The generation of that XML (with the hash) and its submission to the tax authority are Verifacti's responsibility.
In TicketBAI, the invoice carries the TicketBAI code and the QR, both returned by the API; the hash is not printed.

How do I convert the QR to attach it to my invoice?

There are libraries and functions in all tech stacks to convert the Base64 encoded QR image returned by the API into an image that can be attached to the invoice.

How do I convert the QR to attach it to my invoice if I use Stripe?

For the specific case of SaaS companies that use Stripe for subscriptions, the flow can be:
  1. The invoice.payment_succeeded event arrives, which contains the invoice object.
  2. Make a call to our API and collect the QR.
  3. The invoice object contains the Stripe PDF at invoice.invoice_pdf. Download it, attach the QR, and upload it to an S3.
  4. Show the client your own PDF, not the Stripe one.
Regarding the PDF, you can do two things:
  1. Use a library, but it is still costly to handle all cases correctly.
  2. Use the Stripe PDF itself and simply modify it. This is really easy and fast.

Can I generate the QR myself?

QR generation is straightforward. Although the Verifacti API provides the QR immediately when generating a new invoice, many users prefer to generate it themselves and add it to the invoice, since QR generation libraries exist in almost every programming language.

What is the expected length of QR codes in the Verifacti API response?

QR codes are returned as a Base64-encoded image, resulting in a considerably long character string (exceeding 3,000 characters), not a short URL as one might expect.

Is it mandatory to add text next to the QR code on Verifactu invoices?

Yes, it is mandatory to include descriptive text next to the QR code on the invoice PDF. Phrases such as VERI*FACTU or Factura verificable en la sede electrónica de la AEAT (Invoice verifiable at the AEAT electronic office) can be used.
More in Verifactu QR code.

What margin specifications do the QR codes generated by the Verifacti API have and do they comply with AEAT regulations?

The QR code size must follow the ISO/IEC 18004 standard. This standard establishes a minimum of 4 module margins. The QR codes generated by Verifacti have 6 module margins, thus complying with the specification.

Is it recommended to save the QR in case I need to reprint it?

Yes, it is recommended to save the QR for the following reasons:
  1. Ease of reprinting: Having the QR saved allows you to quickly and easily reprint the document in case of loss or damage of the original.
  2. Authenticity verification: The QR can be used to verify the document's authenticity at any time.
  3. Regulatory compliance: Keeping the QR ensures that Verifactu and TicketBAI regulations are met, as these systems may require QR presentation during audits or reviews.
Additionally, it is suggested to store the QR in a safe and accessible place, such as a digital cloud file, to prevent its loss.

Cancellation and modification

5 questions

How can I cancel, modify, or amend an invoice with the Verifacti API?

Yes, it is possible to modify and cancel invoices in Verifactu and with the Verifacti API.
To modify or cancel an already generated invoice, it is necessary to make additional calls to the AEAT through additional invoicing records.
The possible paths to follow include:
  • Corrective invoices with the Create Invoice endpoint (for most cases)
  • Credit notes with the Create Invoice endpoint (for full returns)
  • Cancel invoice endpoint (for very restricted cases where the invoice was issued in error)
  • Amend invoice endpoint (for very restricted cases where the change does not include fields with fiscal impact)
Confusion with the unalterability requirement
It is common to hear that under the Verifactu system, invoices cannot be modified. This perception is incorrect. The unalterability required by Verifactu refers to the invoicing records (XMLs generated by Verifacti), not the invoices themselves. Invoicing records are the XMLs that Verifacti generates from the calls made to the API. For each call made to the Tax Agency, there is one XML (invoicing record) and these cannot be modified after creation.

When and how should corrective invoices and credit notes be used?

Corrective invoices
  • Whenever you want to modify any aspect of an invoice (accepted, partially accepted, or rejected) that involves a change in fiscally relevant data (such as recipient, amount, tax rate, etc.), you must always use a corrective invoice.
  • Corrective invoices are types R1, R2, R3, R4, or R5.
  • Corrective invoices are new invoices with a different series from the original, and with their own QR.
  • These additional invoices must be delivered to the recipient.
  • When you issue a corrective invoice (including F3), you reference the original invoice. However, the AEAT does not appear to verify whether the original invoice was previously sent or anything of the sort.
You can perfectly issue a corrective invoice referencing an invoice that was never sent through the Verifactu system and it will not cause any issue with the AEAT API.
Credit note
  • The only exception is when you issue an invoice for goods that are subsequently returned in full. In that case, it is sufficient to issue a normal "negative" invoice. This is an ordinary invoice with a negative total amount that can go in the same series.
  • It would be a standard F1 invoice.
  • The fact that a negative F1 can be issued is made very clear in the AEAT examples, which can be found at the following link.
  • These additional invoices must be delivered to the recipient.
  • Credit notes do not require their own series; they can go in the same series as the original invoice.

When and how should the amendment and cancellation endpoints be used?

These endpoints exist in the Verifacti API because they also exist in the AEAT's own API. While the naming invites their use for all types of operations, the AEAT establishes very restricted use.
Cancellation endpoint
* Only for invoices that should never have been issued (issued in error).
  • Important: if an invoice is cancelled, that number cannot be reused—you must skip to the next one, otherwise Verifactu will report a duplicate invoice error.
Amendment endpoint
* When the corrected field has no fiscal implications, such as the description field.

How do I manage the change or conversion of a simplified invoice to a standard one?

  • In simplified invoices (type F2), recipient data cannot be added.
  • Standard invoices (type F1) do include recipient data.
  • You could first generate a simplified invoice and "convert" it to a standard one by adding the recipient data. Many of our users refer to this as an "Exchange invoice". In this situation, a new substitution invoice type F3 must be issued.

Does Verifacti offer tax advice for complex invoice cases (e.g., corrective invoices, disbursements)?

Verifacti does not provide detailed tax advice for complex invoicing cases (such as simplified invoice returns, corrective invoices with disbursements, or the use of R1 and R5). Our documentation and examples cover the most common scenarios.
For specific or unclear situations, we recommend consulting a tax advisor or the AEAT directly through verifactu@correo.aeat.es, who usually provide a quick response.

Errors and incidents

13 questions

What types of errors can occur when sending invoices and how do I handle them?

Below is a high-level overview of the types of errors that can prevent your invoice from being considered valid and correct by the Tax Agency (AEAT).
Something very important to understand regarding error handling is that under the Verifactu regulation, an invoice cannot be created (nor delivered to its recipient) if the Invoicing Record (XML) has not been previously generated, which requires a successful call to the Verifacti API. This is a red line for the AEAT, which accepts late XML submission but does not accept the non-creation of the XML.
1. Status code 500 response from the Verifacti API and Incidents
  • A 500 status code response from the Verifacti API implies that some kind of incident is preventing correct API calls. An example would be the Verifacti API being down.
  • The way to handle this situation would be similar to handling incidents such as internet or power outages, situations in which it becomes impossible to contact the Verifacti API.
  • In any of these situations, even if transactions and sales continue to occur, no invoice should be delivered to the buyer of the goods or services, since the AEAT makes clear that it is not possible to issue invoices without generating an invoicing record (XML), i.e., without having previously called the Verifacti API correctly.
2. Status code 429 response from the Verifacti API
  • You have exceeded the requests-per-minute limit of your API key.
  • Retry later at a lower rate.
3. Status code 400 response from the Verifacti API
  • The 400 response status code indicates instant validation errors from the Verifacti API that generally occur due to format or syntax failures in the request. A missing or invalid API key returns 401.
  • If a 400 status code is received, the invoice cannot be considered generated, as the invoicing record has not been generated and the QR for attaching to the invoice has not been returned.
  • If a 400 status code response is received, the submission must be corrected by reviewing and fixing the request structure and data format (e.g., ensuring dates follow the DD-MM-YYYY format).
4. Incorrecto or Aceptado con errores status of the invoicing record by the AEAT
  • When a 200 status code response is received, which comes with the QR for attaching to the invoice, the invoicing record (XML) has already been correctly generated by the Verifacti API for submission to the AEAT and the invoice can be considered generated.
  • At this point, the process of submitting the invoicing record to the AEAT begins, and the record status will be "Pending".
  • Once the submission is complete, a process that can take a few minutes, the AEAT issues a response XML indicating whether they accepted the invoicing record.
  • The record status should be checked through two possible paths: webhooks (recommended) or the record status endpoint.
  • The record status can also be viewed on the verifacti.com web interface, within each NIF's panel, in the "Records" menu.
  • AEAT errors occur due to failures in the fiscal content of the record (e.g., incorrect NIF/CIF).
  • When the record does not have the "Correct" status, then the invoice has been created but is not fiscally valid despite having received Verifacti's initial OK.
  • In this case, the invoice must be rectified. This involves issuing a Corrective Invoice to correct the invoice through an additional invoicing record. In exceptional cases, an amendment record can be issued.
5. Errors due to regulatory non-compliance outside Verifactu
Complying with Verifactu does not guarantee compliance with all invoicing regulations or accounting or tax rules. It is common to encounter situations where the Verifactu system accepts invoices with elements that are incorrect from the perspective of invoicing regulations. Therefore, it should not be assumed that a "correct" AEAT response to a call to its API through Verifacti equates to full regulatory approval.
Some examples of invoice errors that are nevertheless accepted by Verifactu (and by the Verifacti API) include:
  • Verifactu accepts without errors invoices that violate the sequential invoice numbering requirement within the same series established by invoicing regulations. Verifactu will not return an error if we send invoices in non-sequential order, despite this being incorrect and subject to penalties.
  • Verifactu accepts without errors invoices where the issue date is earlier than the date of the 200 status code response from the Verifacti API, which is the exact moment the invoicing record was created. This is incorrect, as the AEAT establishes that the issue date must coincide with the moment of the invoicing record (XML) creation.
More in the guide to Verifactu errors.

Why does the Verifacti API allow the submission of erroneous invoices and not prevent it through validation systems?

Regarding the errors that Verifacti detects and prevents, we must distinguish between two different types of errors:
Detection of errors in the invoicing record
* The Verifacti API has a validation system that prevents some of the most typical errors in invoicing records. When detected, the creation of the invoicing record is prevented, the submission to the AEAT is avoided, and the need for a subsequent corrective invoice is eliminated.
  • While the Verifacti API detects many errors, it is not possible to detect all of them, and therefore records may encounter AEAT errors once submitted to the tax authority.
Detection of errors according to invoicing or tax regulations
* Verifactu accepts without errors invoices that have errors according to various current regulations, such as invoices with non-sequential numbering or invoices with an issue date earlier than the invoicing record creation date.
  • The Verifacti API does not perform any validation in these situations. The reason is that it would be risky to add validations that the tax authority itself does not enforce, as the tolerance for certain errors may have reasons unknown to us, and therefore that tolerance must be preserved in the Verifacti API as well.

How should I handle incidents such as internet outages, Verifacti API outages with code 500, AEAT outages, or power cuts?

Below we explain how to deal with different types of incidents.
AEAT outage: we handle it
In the event of a tax authority API outage (something that has already happened, in production too), Verifacti will take care of retrying submissions until the AEAT API is operational again. Verifacti users therefore do not need to worry about this eventuality, which is covered by our API.
Other incidents: retry calls and provisional sale receipt or delayed invoice issuance (B2B only)
Any of the following 3 situations make it impossible to call the Verifacti API:
  • Power outage
  • Internet outage
  • Verifacti API outage
The AEAT addresses this topic in a FAQ on their website, with a response that can be misleading. There, the AEAT says that late submission of the Invoicing Record (the XML with the invoice data) is accepted and that you can "continue invoicing." However, that AEAT FAQ assumes the ability to generate the XML on-premise, which is very uncommon. Therefore, the AEAT approves delaying the XML submission, but does not approve delaying the XML creation to a moment after the invoice issuance.
In inquiries we have made to the AEAT, they have confirmed that it is not possible under any circumstances to issue an invoice without prior XML generation. For those software that use our API, this means that creating invoices without being able to call our API is not a possibility.
The AEAT has communicated to us in inquiries that given this situation, the issuance of a provisional sale receipt would be acceptable. That is, you can continue selling (and collecting payment, for example with the POS terminal if necessary), you just need to ensure that you do not deliver an invoice to the client. Instead, you should deliver an alternative document that includes the data that would be on the invoice, but that clarifies it is not the invoice, and indicates a channel for obtaining the invoice later for those who wish to do so.
Once the incident is resolved and the ability to make calls to the Verifacti API is restored, all pending invoice generation calls must be made:
  • Calls should be made in the same order as the transactions took place, although not achieving this would not be a serious problem.
  • The incidencia field must be sent with the value S.
  • Consider marking the operation date field with the transaction date if more than one day has elapsed.
It is also worth clarifying that in the case of a B2B transaction, it is possible to delay the invoice issuance. In this case, the invoice can be issued subsequently, before the 16th of the month following the transaction. This is another admissible solution.

What types of 400 status code errors can the Verifacti API return and how can I fix them?

Below we show some typical errors detected by the Verifacti API that generate an immediate 400 status code response. We show you the errors and give you information to fix them:
  • Authorization Header: the correct format is Authorization: Bearer [your_API_key]. Note: if the API key is missing or invalid, the response is not 400 but 401.
  • Date Format (fecha_expedicion): Verify that the date is in the DD-MM-YYYY format (day and month with two digits). For example, 22-02-2025.
  • id_otro field: This field must be a JSON object directly, not a text string containing a JSON.
  • Decimal Separator in Amounts: Use the period ( . ) as the decimal separator for all amounts (e.g., 320.00) with a maximum of 2 decimal places.
  • Boolean Values (true/false): Make sure boolean values are true or false (lowercase and without quotes), not text strings like "True".
  • Handling serie and numero: If series and number information is combined in the numero field, the serie field must be explicitly sent as an empty string ("").
  • Misplaced line fields: Fields like impuesto, clave_regimen, and calificacion_operacion are line-level fields and must be included within the invoice items, not at the header level.
We strongly recommend reviewing our official documentation and detailed examples to ensure a correct implementation.

What possible errors can the AEAT find in my invoices and how should I handle them?

Below we delve into the errors the AEAT can find in the invoicing records (XML) received from the Verifacti API and how to handle them:
Possible errors
* There are many possible errors the AEAT can find in an invoicing record, the most typical being format errors or the erroneous combination (contrary to documentation) of values from different fields.
Error handling
* If the invoice has been delivered to the client, even if the AEAT has rejected the invoicing record, the invoice is considered generated, and therefore its numbering is "occupied" and another invoice with that numbering should not be issued again.
  • The path recommended by the AEAT for resolving these situations is issuing corrective invoices, which require a different series from the originals. More information about corrective invoices in the examples section.
  • The situation would therefore be resolved through additional invoicing record(s), without modifying the original invoicing record, thus respecting the integrity and unalterability requirement of invoicing records.
  • Only in cases where the invoice was not delivered to the end client and the invoice should never have been issued or was issued in error could the invoice cancellation endpoint be used.
More in the guide to Verifactu errors.

How can I know if the AEAT accepts my invoice without errors or if the AEAT finds errors?

A successful integration must include a mechanism to listen for the AEAT response to submitted requests to confirm there are no errors.
This will allow you to:
  • Confirm that the request was processed correctly.
  • Detect and correct Tax Agency errors in time.
This can be done:

How does resending corrected or rejected invoices after an AEAT error affect the hash?

The hash is applied to invoicing records, not to individual invoices.
Verifacti is responsible for chaining these records sequentially at the time of their generation, regardless of whether the associated invoice is subsequently accepted or rejected by the system.
The final status of an invoice is determined after its submission, so the chaining sequence is not affected by resending corrected or previously rejected invoices.

How does resending corrected or rejected invoices after an AEAT error affect the numbering?

If the invoicing record has been sent to the AEAT, even if the AEAT has rejected the invoicing record, the invoice is considered generated, its numbering is "occupied" and another invoice with that numbering should not be issued again.

Why does the Verifacti API return a 'Duplicate' status for an invoice?

The Duplicate status and its associated details are responses that come directly from the Tax Agency (AEAT), they are not generated by the Verifacti API. This means that the AEAT has already previously received and processed a record with the same data.

How do I handle the "duplicate invoice" error?

For a duplicate invoice, it is not necessary to issue a corrective invoice. The AEAT will simply ignore it.

Is it possible to use the same series and invoice number in different fiscal years without Verifactu considering it a duplicate?

Yes, it is possible to use the same series and invoice number in different fiscal years.
Verifactu and the AEAT API only consider an invoice as a duplicate if the series, number, and issue date match.

How are responses associated with invoices sent in batches and how are validation errors handled?

When creating invoices in batches, responses are returned in the same order in which the invoices were sent. If any invoice is rejected due to a validation error, an error message will be returned specifying the index of the invoice within the batch that failed. To test batch invoice submissions, an active subscription is required.

I lost the response to a submission and I don't have the uuid. How do I know whether the invoice was registered?

Look the invoice up with POST /verifactu/status, sending serie, numero and fecha_expedicion (and fecha_operacion if you sent it). The API queries the AEAT and returns the record with its uuid, status and hash.
  • If it is found, the invoice is already registered: do not send it again.
  • If it returns "Factura no encontrada", it may not have reached the AEAT yet: records are submitted asynchronously, usually within a few minutes. Wait a few minutes and query again before resending it.
  • If the query returns 502, the AEAT did not respond: try again later.
If less than 24 hours have passed since the submission and you kept the Idempotency-Key, you can also repeat the same request with the same key and body: you will get the original response, with the uuid, without creating a new record.
In TicketBAI, POST /ticketbai/status accepts the same fields.

Webhooks

3 questions

Is it possible to track the status or history of webhook deliveries from the Verifacti graphical interface?

Currently, it is not possible to view the status or history of webhook deliveries in the Verifacti graphical interface. The webhook will attempt to send the message to your configured endpoint immediately after the invoice is sent to the AEAT, which usually happens one or two minutes after your request.

Why is the number of calls to my webhook fewer than the number of invoices I sent?

According to AEAT specifications, invoicing records must be packaged and sent in groups, not individually.
Verifacti groups multiple records into a single submission to the AEAT. Each time such a submission is made, your webhook is notified with the information of all records included in that package.
Therefore, the number of webhook calls corresponds to the number of packaged submissions made to the AEAT, not to the individual number of processed invoices.

Does Verifacti retry webhooks if my endpoint is unavailable or fails?

Yes, Verifacti webhooks are retried automatically if your endpoint does not respond with a 2xx code within the 10-second timeout. The current policy is:
  • Up to 3 retries (4 attempts in total).
  • Increasing waits of 1 minute, 6 minutes, and 30 minutes.
  • 4xx errors are considered permanent and are not retried.
Each notification includes the X-Webhook-Id header, which is stable across retries, so you can use it as an idempotency key to avoid processing the same notification twice.
If an endpoint fails repeatedly, we automatically deactivate the webhook and notify you by email. There is no automatic reactivation: you must reactivate it manually from your panel once the problem is fixed; reactivating it resets the failure counters.
Even so, as a best practice to ensure data consistency, we recommend periodically checking whether you have records in Pending status older than a certain threshold and using the record status query endpoint to obtain the updated document information.

Invoice listing

3 questions

How can I get a list of invoices for a specific day using the API?

The Verifacti API invoice listing endpoint queries the AEAT API directly. Currently, the AEAT API does not allow getting a list of invoices for a single day. To perform the query, it is necessary to specify a date range.

Do I need to make 12 calls to the invoice listing endpoint to get data for a full year?

Yes, to get invoices for a full year, you must make 12 calls to the invoice listing endpoint, setting the periodo parameter for each month (from 1 to 12). This is an AEAT API restriction.

Can I query the number of the last issued invoice to create the next one?

There is no way to query the Tax Agency for the last issued invoice. The last issued invoice must be obtained from the software's own database. It is possible to list invoices through the list invoices endpoint, which forwards the request directly to the AEAT, but you cannot make a call that returns only the last one.

Going to production

3 questions

When we start registering our users, what should we do with previous old invoices?

It is not necessary to include previous old invoices from the same tax period or from the same series.

When can I start sending invoices to the AEAT production environment?

The Verifactu production environment has been enabled since April 2025. It is already possible to send real invoices to the AEAT.

How can I run tests if my company is already set up in production mode?

To run tests, you must create the company in test mode. The same company can exist in test and production mode simultaneously, each with its own different API key.

Certification and statement of conformity

7 questions

What is the responsible declaration (declaración responsable)?

The responsible declaration (declaración responsable) is a self-certification in which the SIF confirms that it complies with the regulation. The "certification" requirement established by the Anti-Fraud Law (from which Verifactu originates) is satisfied with this "self-certification" that each invoicing software must publish, and that the AEAT can require in case of an inspection.
To comply with Verifactu, there are no external certification or AEAT verification requirements. Simply, each invoicing software must incorporate this document, regulated in Chapter IV of the Ministerial Order (Orden Ministerial).
In a mixed architecture case such as using an API like Verifacti, both the invoicing software and Verifacti itself must have their responsible declaration. Ours is available:
There is a complete section in the AEAT FAQ about this document and its requirements. Here we only highlight two very important aspects of this document:
  1. Placement of the responsible declaration - It must be visible to the software users and, in the case of commercialization, also to buyers. It is suggested that it be accessible in the help section of web-based software.
  1. Software numbering - The responsible declaration must refer to the corresponding software number. Each provider must have a declaration for each software numbering created after the entry into force of Verifactu. Only the current declaration, corresponding to the software numbering in use, should be available, although in case of an inspection, the AEAT could request all previous ones.
👉 Watch short video: Responsible declaration part 1, certification, where to include it, versions and other questions
More about the statement of conformity.

How do I create my responsible declaration (declaración responsable)?

The AEAT has published an example of a responsible declaration in PDF.
We have adapted this example for our users. You can download it here:
  • We provide an editable Word document.
  • We include informational notes for the more complex sections.
  • We add a section to explain the role of the Verifacti API.
Key information for filling out the document:
  1. Section titles are in bold and larger font.
  2. Replace the example responses with your own data.
  3. Delete the informational notes when completing the document.
It is mandatory to mention Verifacti as an external component. We have included a specific section for mixed architectures with an external component. You must state our current software version, which can change: GET /verifactu/declaracion returns it along with our statement.
👉 Watch short video: Responsible declaration part 2: guide to easily completing the responsible declaration
More about the statement of conformity.

Is it necessary to certify or homologate my software?

There is no list of AEAT-approved software for Verifactu. The certification obligation established by the anti-fraud law is resolved through self-certification, i.e., a responsible declaration (see related FAQ). Although some providers and invoicing software claim to be approved by the AEAT, such approval does not exist. It is a commercial strategy based on an inaccurate and even misleading claim.
In TicketBAI, the Basque foral treasuries' system, there is a register of "software garante" (guarantor software): the vendor declares that its software complies and registers it with each foral treasury. We also cover TicketBAI and we are registered as "software garante" in all three territories: Álava, Bizkaia and Gipuzkoa. We include the list of guarantor software in Bizkaia as an example.
More about the statement of conformity.

Is Verifacti AEAT-approved software?

There is no list of AEAT-approved software for Verifactu. The certification obligation established by the anti-fraud law is resolved through self-certification, i.e., a responsible declaration (see related FAQ). Although some providers and invoicing software claim to be approved by the AEAT, such approval does not exist. It is a commercial strategy based on an inaccurate and even misleading claim.
Verifacti has signed a specific social collaboration agreement with the AEAT (agreement 017) that allows us to use our own certificate to submit tax information to the AEAT on behalf of our clients. See list of entities with agreement here (we appear as Bilbabit SL).
In TicketBAI, the Basque foral treasuries' system, there is a register of "software garante" (guarantor software): the vendor declares that its software complies and registers it with each foral treasury. We also cover TicketBAI and we are registered as "software garante" in all three territories: Álava, Bizkaia and Gipuzkoa. We include the list of guarantor software in Bizkaia as an example.
More about the statement of conformity.

What SistemaInformatico data appears in the records Verifacti sends to the AEAT?

By default, records carry Verifacti's identification as the invoicing system, the same one stated in our responsible declaration: NombreRazon BILBABIT SL, NIF B75777847, NombreSistemaInformatico bilbabit, IdSistemaInformatico A1 and the declared version.
If your software issues the invoices and calls our API, you can make the records carry its identity. The note on the SistemaInformatico block in the annex of Orden HAC/1177/2024 says that, when the system is made of components from several producers, the data of the producer of the main component is recorded, and in an API integration that component is usually your software. It is set for each Verifactu NIF:
  • When creating the NIF, with the sistema_informatico field of POST /nifs, or later with PUT /nifs/{entorno}/{nif}/sistema_informatico: the producer's company name and NIF, the system name, IdSistemaInformatico (exactly 2 characters, uppercase letters or digits), TipoUsoPosibleSoloVerifactu and TipoUsoPosibleMultiOT.
  • In every request to create, modify or cancel an invoice, your software sends sistema_informatico.version and sistema_informatico.indicador_multiples_ot, which it computes for each of your users (AEAT developer FAQ 4). While the NIF uses Verifacti's identity they are ignored, so deploy sending them first and switch the NIFs afterwards.
  • For the AEAT, switching identity means a new billing system: the NIF gets a new installation number and the next record starts a new chain. Records already sent don't change, and any still pending are sent with the identity they were generated with.
  • Your responsible declaration must state that you use our component and its version.
About the rest of the block:
  • NumeroInstalacion is assigned by Verifacti: it distinguishes each NIF registered in Verifacti and each identity change, and is never repeated.
  • With Verifacti's identity, TipoUsoPosibleSoloVerifactu, TipoUsoPosibleMultiOT and IndicadorMultiplesOT are always S. With your identity, the first two are the ones you set and the third is the one you send with each request.
In the test environment, NIFs with Verifacti's identity use the test identification (NombreSistemaInformatico NombreSistemaInformatico, IdSistemaInformatico 77, version 1.0.03), which is why their test XML does not match the production one.

What is the installation number that appears in the responsible declaration and how do I manage it?

See the specific AEAT FAQ on this topic.

What is the Information System Identification that appears in the responsible declaration and how do I manage it?

Data storage and export

1 question

What are the data storage obligations with Verifactu?

In VERI*FACTU mode, there is no obligation to store the invoicing records sent to the Tax Agency, neither for the invoicing software nor for the taxpayer, since those records have already been previously submitted. The tax authority is clear on this point: the obligation to store invoicing records only exists in NO VERI*FACTU mode.
By invoicing record, the tax authority means the XML files that Verifacti generates from the calls received, and which are submitted to the AEAT. These are, therefore, the XML request files to the tax authority and the tax authority's response files. In VERI*FACTU mode, there is no obligation to store these files.
That said, Verifacti provides endpoints to download the invoicing records for those users who wish to keep them.
Export XMLs endpoint
Download XML endpoint
Additionally, Verifacti keeps this information while the NIF is active in production and for 30 calendar days after it is deactivated.
The above should not be confused with the obligation to store invoices derived from the Invoicing Regulation (Reglamento de Facturación) or other tax or accounting regulations. Any obligation that the software or its users (the taxpayers) had before the appearance of the Verifactu system remains in force. There are therefore storage obligations regarding invoices, as was already the case before the Verifactu regulation.
👉 Watch short video: Verifactu vs NO VERI*FACTU, and the obligation to store the XML invoicing records

Start integrating today

Try it for free with the test environment.

Test environment and test NIF includedSee pricing