Spain (SIGN ES)

SIGN ES at a glance

	Details
Regulation	Verifactu and SII (National), TicketBAI (Basque Region), and NaTicket (Navarre Region)
What it requires	XML invoice generation, cryptographic signing and chaining, real-time submission to tax authorities, QR generation
API architecture	Specialized API — purpose-built for Spain, uses the Management API for org setup
Integration effort	2-4 weeks from scratch
Key feature	One API covering fiscalization systems (TicketBAI, Verifactu, NaTicket) and e-reporting (SII) through a single integration

Verifactu, TicketBAI, NaTicket, and SII — all in one API

The complexity of Spain’s fiscal framework comes from the coexistence of common territory and foral territories, which creates multiple concurrent compliance systems. Software vendors commercializing products in Spain must ensure compliance with each applicable system. SIGN ES handles all of them through a single API:

• Verifactu — applies nationally across Spain under Royal Decree 1007/2023. It does not apply to companies located in the Basque Region or Navarre.
• TicketBAI — applies in the three Basque Country provinces: Araba, Bizkaia, and Gipuzkoa. Each territory has its own tax authority.
• NaTicket — applies in the foral territory of Navarre.
• SII — national VAT reporting system operated by the Spanish Tax Agency (AEAT).

SIGN ES abstracts all of these behind a single API surface. You specify which regulation applies per taxpayer, and SIGN ES handles the rest.

💡One integration across Spain

You do not need a separate integration per regulation. SIGN ES routes each compliant invoice flow to the correct tax authority based on the taxpayer’s fiscal territory and obligations.

Key concepts

Signers

A signer represents the signing device and contains the certificate used to sign invoices and receipts. Since fiskaly is a social collaborator of the Spanish Tax Agency, we can provide the signing certificate without the taxpayer needing to supply their own certificate.

Clients

A client represents a POS terminal, invoicing device, application, or similar issuing system. Each client is connected to a signer. Clients have two states: ENABLED and DISABLED (setting a client to DISABLED is irreversible).

Invoices

Invoices are the core transaction model in SIGN ES. There are six types:

1. Simplified invoice — issuer info only, up to EUR 400 (or EUR 3,000 for special cases such as retail, restaurants, and parking). Most common for B2C receipts and tickets.
2. Complete invoice — issuer and recipient info. Most common for B2B.
3. Correcting invoice — fixes an error on a previously issued invoice. The correction can be made by substitution or by differences.
4. Enrichment invoice — adds recipient data to a previously issued invoice.
5. External invoice — imports pre-integration invoices for correction reference and is not submitted to the tax authority.
6. Remedy invoice — remedies incorrect information, mostly due to integration errors, that does not legally require a correction.

All invoice types except the external invoice are cryptographically signed, chained by referencing the previous invoice hash, and submitted in real time to the relevant tax authority. External invoices are reference records only: they do not generate XML and are not transmitted.

Integration effort

Scenario	Duration	Notes
New integration	2-6 weeks	Full flow: Management API org setup, certificates, signers, clients, invoice signing, and submission
Adding Verifactu to existing TicketBAI	~1 week	Same API, different regulation flag per taxpayer
Already on Unified API (FR/IT)	2-4 weeks	Different API architecture — SIGN ES uses Management API, not the Unified pattern

Are you already a customer of SIGN DE?

See the guide specifically designed for SIGN DE customers. It can simplify your integration effort considerably: For SIGN DE customers.

Getting started

1. Create your organization

   Register on fiskaly HUB and create a managed organization for each taxpayer via the Management API, or use HUB directly.

2. Set up certificates

   Create the required electronic certificate. Talk to our team if you prefer to use an existing one. See electronic certificate and device certificate.

3. Create signers and clients

   Create one signer (signing certificate) and one client (POS terminal) per terminal, POS device, application, or other device used to issue invoices.

4. Create invoices

   Create your first invoice. SIGN ES generates the XML, signs it, chains it to the previous invoice, and submits it to the tax authority. The response includes the signed invoice and its transmission status.

5. Generate QR codes

   Each invoice must include an identifier code and a QR code on the printed/displayed receipt. See invoice compliance.

Documentation

Introduction

Overview of Spanish fiscal regulations and SIGN ES

Integration Process

End-to-end integration walkthrough

Invoice Compliance

Invoice format, QR codes, identifier codes, and placement rules

Connection Loss

Handling connectivity issues during real-time submission

Glossary

Key terms for Spanish fiscal compliance

For SIGN DE Customers

Migration guide: what changes when coming from SIGN DE