ERP and Verifactu: tax compliance for your ERP, through an API

One API per regulation on the same NIF management, for all your customers.

If you make an ERP, the obligation to offer a system adapted to Verifactu has been in force since 29 July 2025 (RD 1007/2023), even if your customers’ dates are postponed. With Verifacti, your ERP sends each invoice in JSON to the Verifactu API, the TicketBAI API or the SII API depending on where each customer is taxed, gets the QR code instantly for Verifactu and TicketBAI, and gets ready for B2B e-invoicing (API coming soon).

Test environment and test NIF included
Read the documentation
  • AEAT social collaborator
  • TicketBAI guarantor software

Dates that affect your ERP 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.

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
SII: large companies (over €6M), REDEME and VAT groupsSince 1 Jul 2017
Since 1 January 2025, also holders of hydrocarbon tax warehouses (RIVA, art. 71.3).
In force
B2B e-invoicing: turnover over €8M6 Oct 2027
Published in the BOE, future date
B2B e-invoicing: all other businesses and professionals6 Oct 2028
Invoice statuses optional until 6 October 2029 for individuals and pass-through entities up to €8M.
Published in the BOE, future date

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

One NIF management, one integration per regulation

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, manage their representation form, activate them and get the results by webhook.

Why Verifacti

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; every invoice is validated before submission and errors come back with a code

Specialists in Spain

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

TicketBAI guarantor software in Álava, Bizkaia and Gipuzkoa

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

Is your ERP old or installed on premises?

It does not matter: each invoice is an HTTP call with JSON. If your ERP can make an HTTPS request, it can send to Verifacti. The documentation has examples for every call in cURL, Python, JavaScript, Node.js, PHP, Go, Java, C# and Visual Basic 6.

There are step-by-step tutorials in PHP, Python, C#, Delphi and Visual Basic.

What an ERP vendor needs

Requirements of an ERP vendor and how Verifacti covers them
RequirementHow Verifacti covers it
Many customersNIF registration, activation and removal through the API, and webhooks (documentation).
Customers in common territory, foral territories and the SIIVerifactu API, TicketBAI API and SII API on the same NIF management.
Instant QR codeThe synchronous Verifactu and TicketBAI response includes the QR code in Base64.
Prior validationEvery 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).
Statement of conformityMixed architecture: your ERP is the main component and Verifacti publishes its statement of conformity as the external component.
ModalityVERI*FACTU only: the API does not cover the NO VERI*FACTU modality (modalities).
A cost you can pass onPrice per NIF active in production; custom pricing for volume.

Software vendors already using 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
Xolo
“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.”
Sebastien RequiemCTO, Xolo
Mekavo
“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.”
Mehrdad MadadiFounder & Lead Developer, Mekavo

Pricing

Public tariff of the Verifactu API and the TicketBAI API: you pay per NIF active in production, VAT excluded. Custom per-NIF pricing is available for volume.

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.
  • SII with custom pricing based on invoice volume.
  • E-invoicing API: no price yet.

Questions from ERP vendors

If I make invoicing software, does the Verifactu postponement affect me the same way as my customers?

No. Your obligation to offer adapted software has been in force since 29 July 2025; the announced postponement affects taxpayers. See Verifactu deadlines.

What is the statement of conformity and who signs it if my ERP uses an external API?

Each vendor publishes its own. With Verifacti there is a mixed architecture: you declare your ERP and Verifacti publishes its own as the external component. See statement of conformity.

Do my customers need a digital certificate?

Not to submit: Verifacti is an AEAT social collaborator and submits with its own certificate once each NIF’s representation form is signed.

Can I register NIFs in bulk and receive webhooks?

Yes, with the NIF management API.

Does the API cover the NO VERI*FACTU modality?

No. The Verifactu API only covers the VERI*FACTU modality. See VERI*FACTU and NO VERI*FACTU modalities.

Try the API with your ERP in the test environment

Create the free account and send your first invoices from your ERP to the test environment.

Test environment and test NIF includedRead the documentation