Fiscalization in Spain (VeriFactu)¶
In addition to German fiscal law, DiKAS also supports Spanish fiscal law. In Spain there is no TSE and no DSFinV-K export — instead, VeriFactu applies: every invoice is chained tamper-proof and registered with the tax authority AEAT. DiKAS handles this automatically in the background; this page explains what's behind it and what looks different on the receipt.
Who is this page for?
For businesses in Spain. The chapters TSE & Tax Authority, DATEV Export, and Kassenmeldung — Cash Register Notification to the Tax Authority apply only to Germany and have no relevance in Spain.
What Is VeriFactu?¶
VeriFactu is the Spanish system for verifiable invoices (Real Decreto 1007/2023): POS software must tamper-proof chain every invoice with a hash chain and transmit it to the AEAT, or make it verifiable. It's the Spanish counterpart to the German TSE — just without dedicated hardware.
DiKAS follows one path:
| Path | Description |
|---|---|
| Native VeriFactu path | DiKAS signs and transmits on its own (XAdES signature, mTLS with an AEAT certificate), without an intermediary service |
It works fail-closed: if an invoice cannot be registered properly, this is logged and retried later — no transaction is lost.
Why fiskaly is gone
Until 13 Aug 2026 this page listed fiskaly SIGN ES as a second, selectable path. That is
no longer true: Spain runs exclusively on the native in-house path, and the software refuses
any other setting at startup — so that a stale configuration value cannot silently divert an
installation to a paid third-party service. If you find Fiscal:Es:Backend=fiskaly in an old
guide: remove the value.
What's on the Receipt?¶
Spanish receipts from DiKAS automatically include the required information:
- The notice "VERI*FACTU" or "Factura verificable en la sede electrónica de la AEAT"
- The QR tributario (approx. 30–40 mm) — guests and auditors can use it to verify the invoice directly on the AEAT website
- Sequential invoice numbers per series
Factura Simplificada and Full Invoice¶
In Spain, a normal POS receipt is a factura simplificada (simplified invoice). It's permitted up to:
| Limit | Applies to |
|---|---|
| €400 | in general |
| €3,000 | hospitality and retail, among others |
Above that (or if the guest requests it, e.g. for input tax deduction), a full invoice with the customer's details is required — in DiKAS via Customer Invoices.
Voids and Corrections (Facturas Rectificativas)¶
Unlike in Germany, a correction in Spain is registered as a factura rectificativa — a separate correction invoice referencing the original. DiKAS automatically classifies these correctly (sale F1/F2, correction R1/R5). Nothing changes for you at the POS: void as usual — the correct classification happens in the background.
The Invoice for the Recipient: Facturae¶
The VeriFactu record is the report to the AEAT — it never reaches your customer. The invoice for the recipient is a separate document. In Spain that format is Facturae: mandatory towards public authorities (B2G via FACe) and, under the Crea y Crece act, in future between businesses too.
For every customer invoice DiKAS produces:
| Format | For | Download |
|---|---|---|
| Facturae 3.2.2 | Spain — also carries IRPF withholding and recargo de equivalencia | Invoice → XML (Facturae) |
| EN 16931 (UBL) | Recipients and platforms that require UBL | Invoice → XML (UBL) |
| ZUGFeRD/XRechnung (CII) | Germany | Invoice → XML |
Not yet suitable for FACe
The generated Facturae is unsigned. To submit it to FACe (public sector), Spain requires an XAdES signature inside the document; that arrives with the qualified certificate. For passing it to a business customer the document is already usable.
A full invoice needs the customer's tax number
A factura completa must identify the recipient. If the customer record has no NIF/CIF (or VAT ID), neither the AEAT report nor the Facturae can be produced in full — the receipt is held back rather than reported incompletely. A factura simplificada (receipt) does not need it.
Setup¶
The fiscal country is an instance setting (Fiscal:Country), not a toggle in the interface: Spanish customers run on a Spanish DiKAS instance, and registration with the AEAT (taxpayer, signature access) is set up during provisioning. As the operator, you don't need to configure anything for this.
VeriFactu obligation timeline
The VeriFactu obligation takes effect in stages starting 2027 (corporate taxpayers first, other businesses follow). DiKAS is prepared for this — businesses can already opt to work in VeriFactu mode voluntarily beforehand. Clarify binding deadlines with your tax advisor (gestoría).
Payment Methods in Spain¶
- Cash and card payment (Stripe Terminal, SumUp, SoftPOS) work the same as everywhere — see Payment Methods and Hardware.
- Bizum and Redsys terminals are in preparation, but not usable yet.
Next Steps¶
→ Payment Methods — checkout with card and SoftPOS
→ Customer Invoices — full invoices with customer details
→ Hardware — receipt printers, terminals, and accessories