Invoicing software compatible with Verifactu, through an API
Start with a few NIFs and scale without rebuilding anything.
Verifacti is an API that lets invoicing software vendors make their program compatible with Verifactu and TicketBAI: your software sends each invoice in JSON and gets the QR code instantly, and Verifacti generates, chains and submits the record to the Spanish Tax Agency (AEAT) or the foral treasury. The obligation to sell adapted software has been in force since 29 July 2025; the announced postponement affects taxpayers, not vendors.
- AEAT social collaborator
- TicketBAI guarantor software
Looking for an invoicing program for your business? See which requirements it must meet.
Dates that affect your software and your customers
Yours first: the obligation of invoicing software vendors has been in force since 29 July 2025, and the postponement announced for taxpayers does not change it.
| Who | Date | Status | Rule |
|---|---|---|---|
| Producers and resellers of invoicing software RDL 15/2025 did not change this date. | Since 29 Jul 2025 | In force | RD 1007/2023 · Orden HAC/1177/2024 |
| Corporate Income Tax payers | 1 Jan 2027 | Published in the BOE, future date | RDL 15/2025 |
| Everyone else, including the self-employed | 1 Jul 2027 | Published in the BOE, future date | RDL 15/2025 |
| Postponement of the pending obligations The note does not specify the scope for businesses invoicing over €8M. | Oct 2028 | Announced, no rule published | Nota de Hacienda, 5 oct 2026 |
| TicketBAI in Álava: foral taxpayers Phased from 1 April 2022; all other taxpayers since 1 December 2022. | Since 1 Dec 2022 | In force | NF 13/2021 y DF 48/2021 · FAQ 1.9 · calendario |
| Batuz in Bizkaia (TicketBAI and LROE): all taxpayers Companies that are not SMEs since 1 January 2024; everyone else in windows on 1 July 2024, 1 January 2025, 1 July 2025 and 1 January 2026. | Since 1 Jan 2026 | In force | NF 8/2023 · Batuz |
| TicketBAI in Gipuzkoa: foral taxpayers Phased by activity from 1 July 2022. | Since 1 Jun 2023 | In force | NF 3/2020 · DF 32/2020 |
| B2B e-invoicing: all other businesses and professionals Invoice statuses optional until 6 October 2029 for individuals and pass-through entities up to €8M. | 6 Oct 2028 | Published in the BOE, future date | RD 238/2026 · Orden HAC/1028/2026 |
This is not advice: each taxpayer determines what applies to them with their adviser.
The APIs for your software
NIFs in common territory submit with the Verifactu API; those taxed in Álava, Bizkaia or Gipuzkoa, with the TicketBAI API. That is the criterion of the regulation; each API is a separate submission integration on the same NIF management.
One NIF management for all your customers
You integrate the NIF management API once: registering, activating and removing NIFs, representation and webhooks. Each regulation then adds its own submission integration, close to the target administration’s API.
Each NIF has its own API key and uses the API of its obligation: TicketBAI in Álava, Bizkaia and Gipuzkoa; in common territory, the SII if the NIF is in the SII and Verifactu otherwise. That is the criterion of the regulation, not a recommendation for your case.
You register your customers’ NIFs through the API (several at once), activate them, each with its own API key, manage their representation form and get the results by webhook.
With the NIF’s sistema_informatico field, your Verifactu records carry your software’s identity as the invoicing system (SIF).
Why Verifacti
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 daysSpecialists in Spain
Common and foral territory: Verifactu, TicketBAI and SII with one provider.
TicketBAI guarantor software in Álava, Bizkaia and GipuzkoaProven 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; every invoice is validated before submission and errors come back with a codeDoes the per-NIF cost eat your margin?
You only pay for each NIF active in production. If you meet its requirements, there is the Startup plan; if not, the public tariff goes down with every tier of NIFs, and for high volume there is custom per-NIF pricing.
See the tariff on Pricing.
What an invoicing software vendor needs
| Requirement | How Verifacti covers it |
|---|---|
| Many customers or users | NIF registration through the API (POST /nifs, several at once), activation, deactivation and one API key per NIF (documentation). |
| Records that carry your software as the SIF | sistema_informatico field of the NIF: Verifactu records carry your system’s identity instead of Verifacti’s (when you change it, the NIF starts a new chain). |
| QR code on the invoice instantly | The API response includes the QR code in Base64 (Verifactu API and TicketBAI API). |
| Few rejections | Every invoice is validated before submission against the AEAT and foral treasury rules, and errors come back with a stable code (public catalogue: Verifactu, TicketBAI and SII). |
| No certificates from your customers | Verifacti is an AEAT social collaborator and submits with its own certificate once the representation form is signed, online too for individuals. |
| Customers in common territory and in the Basque Country | Verifactu API and TicketBAI API on the same NIF management; guarantor software in Álava, Bizkaia and Gipuzkoa. |
| Knowing what happened to each invoice | Webhooks per NIF with the answer from the AEAT or the foral treasury, signed with a secret (HMAC-SHA256). |
| A per-NIF cost you can pass on | Price per NIF active in production; free test NIF and test environment; custom pricing for volume. |
| Test before paying | Free account with the Verifactu and TicketBAI test environments; the Verifactu test NIF is created when you sign up and support provides the TicketBAI one. |
| Data in the EU | Data hosted in the EU. |
What our customers say

«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.»
«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.»
“Verifacti’s SaaS platform is intuitive and reliable, and their team’s deep expertise and prompt, crystal-clear answers helped us reach our goals on time. They’re not only highly knowledgeable and professional but also a genuine pleasure to work with.”
“Verifacti made Veri*factu compliance surprisingly straightforward. Their API is clean, well-documented, and their support team responds with real solutions — not generic replies. For any SaaS serving Spanish businesses, Verifacti is the partner you want.”Integrations with your ecosystem
Pricing
Tax compliance for all your users, at a per-NIF cost that fits your fee: public tariff of the Verifactu API and the TicketBAI API per NIF active in production, VAT excluded, and custom pricing for volume. The E-invoicing API has no price yet.
From
€14.99
per month for the first NIF active in production, VAT excluded
See all pricing- The price per NIF goes down with every tier.
- Free test environment and test NIF.
- Annual plan with a 10% discount, no setup fees.
- Up to 3,000 invoicing records per month per NIF.
- Startup plan for companies under 12 months old, with under €100,000 in revenue and under €200,000 in funding.
- Monthly plan with no lock-in.
Questions from invoicing software vendors
If I make invoicing software, does the Verifactu postponement affect me?
Who signs the statement of conformity if I use an external API?
Do my customers need a digital certificate?
Do I have to generate the XML or calculate the hash myself?
Is there a plan to start with a few NIFs?
Keep reading
Try the API in the test environment
Create the free account and send your first invoices to the test environment with the test NIF.