Zeppol / Guides

Spain e-invoicing for Shopify: the Crea y Crece mandate explained

Last updated 26 August 2026 · dates and requirements checked against primary sources on 26 August 2026

Spain spent three and a half years with a B2B e-invoicing law and no working deadline. That ended in March 2026, when Royal Decree 238/2026 finally gave the Crea y Crece law its implementing rules. The obligation now lands in two waves — 1 October 2027 for large businesses and 1 October 2028 for everyone else. If you sell B2B from Shopify into Spain, this is the second mandate wave to plan for, right behind Germany's.

The short version

How Spain got here

Ley 18/2022 — the ley de creación y crecimiento de empresas, universally called Crea y Crece — was passed in September 2022. It said that every business and self-employed professional in Spain must exchange electronic invoices with other businesses. What it did not say was how, in what format, or from when: all of that was left to a reglamento that took years to arrive.

That is why Spain sat on so many "upcoming mandate" lists with dates that kept moving. The regulation was published in the Boletín Oficial del Estado on 31 March 2026 as Royal Decree 238/2026, and the deadlines below are counted from the Ministerial Order that brings the system into operation. That order is itself still a draft: it went out for public consultation in spring 2026 and had not been published in the BOE when this page was checked, so 1 October 2026 is the planned start of the clock rather than a settled one.

The deadlines

Note the asymmetry that catches people out: from October 2027 a large Spanish buyer is obliged to receive structured invoices. Suppliers who cannot send one become the awkward exception a year before their own deadline bites — which is the same commercial pressure that made the Dutch market adopt e-invoicing without ever being told to.

Who is in scope

The mandate covers domestic Spanish B2B transactions — where the recipient is a business or professional established in Spain. Foreign companies with a Spanish permanent establishment are included. Consumer sales are out. So are simplified invoices (the Spanish factura simplificada, unless qualified), regulated energy operators and IATA clearing-house settlements.

If you sell from a Shopify store based outside Spain and have no establishment there, the Spanish obligation does not attach to you directly. It still reaches you through your customers: a Spanish business rebuilding its accounts-payable process around structured invoices will not want to keep a manual exception open for your PDF.

Spain is not a Peppol mandate — and that matters

This is the part most guides skate over. Belgium, the Netherlands and much of northern Europe route e-invoices over Peppol, using the four-corner model. Spain built something else: a hybrid of a public solution operated by the tax authority AEAT and certified private platforms that must interconnect with one another over AS2 or AS4, hold ISO/IEC 27001 certification, and support all permitted syntaxes. Where two private platforms are not yet directly connected, the public solution acts as the fallback route.

The good news is that the content travels well. UBL and CII are both syntaxes of EN 16931, the same European standard behind XRechnung and Peppol BIS. A store that can already produce a valid EN 16931 invoice has solved the hard half; Spain changes the envelope and the route, not the semantics.

The permitted formats

One line in the decree is worth more than the table to a merchant already set up for Europe: between private exchange platforms, a Peppol BIS message is expressly valid, because it is UBL conforming to EN 16931. Peppol is not the Spanish mandate, but the file you would send over Peppol is not a foreign object to it.

Practical reading: standardise on UBL. It is the only one of the four that works on every route, and it is the same format you would already be producing for Peppol countries and for EU B2B invoicing generally. Facturae is familiar to Spanish accountants, but building your store's pipeline around it would leave you unable to reach the public solution.

The four-day status reporting duty

Spain's mandate does not end when the invoice is delivered. The recipient has to report back what happened to it, within four calendar days (weekends and public holidays excluded):

• Commercial acceptance or rejection, with the date.
• Full effective payment, with the actual payment date.

Partial acceptance, partial payment and assignment for collection can be reported optionally. The policy intent is late-payment enforcement — Crea y Crece is, at heart, a law about businesses paying each other on time, and this is the reporting that makes payment behaviour visible.

For a merchant, the consequence is architectural rather than legal: an e-invoice acquires a lifecycle. Sent, delivered, accepted or rejected, paid. Anything that treats invoicing as "generate a file and email it" will not survive contact with this.

Veri*Factu is a different law — don't merge them

Search for Spanish invoicing and you will hit Veri*Factu within a minute, usually described as though it were the same mandate. It is not.

Veri*Factu has slipped more than once — it was originally set for 2026 and was postponed by a year in December 2025 — which is part of why the two get muddled. A Spanish business can be in scope of both at once, and they are satisfied by different things.

The Spanish VAT details that break invoices

A structured e-invoice is validated on arrival, so arithmetic that passes unnoticed on a PDF gets rejected here. Spain has a standard rate of 21%, a reduced 10% and a super-reduced 4% — a store with a mixed basket has to get the split right per line, not per order. Whether your Shopify prices include or exclude tax determines how net and VAT are derived, and rounding at the wrong step leaves you a cent out, which is enough to fail validation. And selling to a VAT-registered business in another EU country is normally reverse charge: 0% VAT, the buyer's number validated against VIES, and the right legal wording on the invoice. Reaching the network is the easy half; the numbers have to be right.

What this means for a Shopify store

Shopify sells well and invoices thinly. Its order confirmation is not an e-invoice — it cannot emit EN 16931-valid UBL, it has no notion of a Spanish tax identifier or an invoice status, and it cannot reach the public solution or a certified private platform. Serving Spanish B2B buyers properly needs a layer that:

• captures company name and NIF/VAT number on B2B orders,
• produces EN 16931-valid UBL, with the VAT worked out per line,
• transmits it over an approved route — public solution or certified platform,
• and tracks the invoice lifecycle back, because Spain asks for statuses.

If you already sell into Germany you are not starting from zero. Both mandates sit on the same European standard, and ViDA pushes the rest of the EU the same way around 2030. The countries differ in routing and reporting; the invoice underneath is largely the same object.

Spain is one of several member states with a date rather than a live mandate. The EU e-invoicing mandate table shows who is already live, who has a date, and who has nothing yet.

Where Zeppol fits, and where it does not

Worth saying before the signup box, because it decides whether the rest of this page is any use to you. Zeppol is not a route into the Spanish mandate, and the reason is the route rather than the format. Spain admits UBL, and Royal Decree 238/2026 goes further than that: on private exchange platforms a Peppol BIS message counts, precisely because it is UBL conforming to EN 16931. The document Zeppol builds is the right kind of document.

What Zeppol is not is a certified Spanish platform. The exchange has to run through the AEAT public solution or a certified private platform, and such a platform has to interconnect with the others over AS2 or AS4, hold ISO/IEC 27001, and carry the status reporting back within four working days. Holding a Peppol access point does not make you one of those, and the status lifecycle is a second obligation on top of the invoice. For your Spanish domestic obligation you need a Spanish platform.

What Zeppol does is the part that travels. If you sell from Spain into Germany, Belgium or the Nordics, your buyer's country decides the invoice, and that is an EN 16931 document over Peppol — which is exactly what Zeppol produces. Your Spanish domestic obligation needs a Spanish platform, and you will need both.

Frequently asked questions

This guide is general information for Shopify merchants, not legal or tax advice. Rules, mandates and thresholds vary by country and change over time — Spain's have moved more than once — so confirm your obligations with a qualified tax adviser.