Mandatory B2B E-Invoicing in Spain: What to Do

Mandatory B2B E-Invoicing in Spain: What to Do

· by Panayot Dimkov

Mandatory electronic invoicing between businesses in Spain has become one of those conversations where everyone has a different date in mind. The confusion has a concrete cause: it is not one obligation, it is two, with different timetables and different purposes, and they sound alike.

In brief: the B2B electronic invoice under the Crea y Crece law requires companies and the self-employed to issue and receive invoices in a structured format. Its regulation is already in the official gazette, and the expected dates are 1 October 2027 for businesses with a volume of operations above 8 million euros and 1 October 2028 for everyone else. Verifactu is a different rule: it requires your invoicing software to be tamper-proof for the tax authority, and it applies earlier, in January or July 2027. Complying with one does not mean complying with the other.

This article separates the two, explains what applies to you today and why this change is the best opportunity you will get to automate invoicing. If the cost side is what interests you, we have a separate article on automating supplier invoices.

1The difference between Verifactu and e-invoicing

VerifactuB2B e-invoice
Legal basis Royal Decree 1007/2023, implementing the Anti-Fraud Act Crea y Crece Act and Royal Decree 238/2026
What it governs The program you issue with: it must chain records, prevent their modification and add a verification code The structured format and the exchange of the invoice between companies
Who you answer to The Spanish tax authority The other company, with invoice statuses and a copy to the Spanish tax authority
Status January and July 2027 October 2027 and 2028 (expected)

The practical consequence of this table matters: you can be perfectly up to date with Verifactu and still be unable to issue a structured electronic invoice when the other obligation arrives. They are two projects, even though they touch the same document.

2Where Verifactu fits

Verifactu does not change the invoice format: it requires the program you issue invoices with to chain its records, prevent them from being altered without a trace and print a QR code that lets the invoice be checked. Royal Decree-Law 15/2025, the rule's second postponement, pushed the obligation back to 1 January 2027 for Corporate Income Tax payers and 1 July 2027 for everyone else. As it arrives before B2B e-invoicing, it is usually the first front.

If you invoice from a spreadsheet, a text document or a program nobody maintains, that is the problem to solve first, before thinking about automating anything. It is not a question of efficiency, it is compliance.

3Mandatory B2B e-invoicing: dates and requirements

The Crea y Crece Act requires all businesses and professionals to issue, send and receive electronic invoices in transactions with one another. The missing regulation, Royal Decree 238/2026, was published in the official gazette on 31 March 2026 and specifies what those invoices must be: a structured file that follows the European standard EN 16931, in UBL, CII, EDIFACT or Facturae. A PDF sent by email does not comply.

The deadlines do not run from the royal decree but from the entry into force of the ministerial order governing the Spanish tax authority's public invoicing solution: twelve months for businesses whose volume of operations exceeded eight million euros in the previous year and twenty-four months for everyone else. The draft order sets that entry into force at 1 October 2026, which is where 1 October 2027 and 1 October 2028 come from. Until the order is published in the official gazette these are expected dates: if it comes into force later, both move back by the same amount, so confirm them before you finalise a plan.

To issue and receive invoices you can use a private platform or the free public solution the Spanish tax authority is preparing. Either way, a copy of every invoice reaches the tax authority.

There is a second component that gets discussed less and carries real operational implications: the obligation to report the status of received invoices, meaning their acceptance or rejection and their full actual payment, each with its date and within a maximum of four working days. That turns invoice reception into a process with obligations of its own, not just an inbox where documents land.

That detail generates the most work and almost nobody is looking at it. Reporting statuses by hand, invoice by invoice, is exactly the kind of repetitive task worth automating from day one.

4Why this is the best moment to automate

Adapting purely to comply means doing half the work and keeping the worse half. Here are the concrete reasons; if you want to put figures on them, we explain how to calculate the ROI of automating a process.

01
You are touching the process anyway
The cost of analysis and internal coordination is already being paid. Using it to redesign the whole circuit carries a far smaller marginal cost than running two separate projects.
02
Structured data changes everything
A structured invoice arrives with labelled data. No AI interpretation, no OCR templates to maintain. Automating reception becomes simpler and cheaper at a stroke.
03
Status reporting demands a workflow
If acceptance, rejection and payment must be reported for every invoice, that circuit needs rules and traceability. Building it by hand guarantees failure as soon as volume grows.
04
Traceability is no longer optional
Both rules push towards complete records of what happened to each document. An automated process produces that trail by design; a manual one produces it through discipline, which fails.

5Where to start, in order

  • Check your issuing software. If it cannot demonstrate compliance, that is the absolute priority and everything else waits.
  • Inventory how invoices come in and go out. How many channels, how many formats, how many suppliers. It is the basis of every later decision.
  • Separate issuing from receiving. They are two projects with different rules and different difficulty. Merging them into one scope usually ends badly.
  • Design for coexistence. For a good while you will receive structured invoices and PDFs at the same time. The flow must accept both inputs without duplicating work.
  • Leave status reporting ready even if it is not yet enforceable. Allowing for it in the design is cheaper than bolting it on later.

For the current state of the rules and the technical requirements, the reference is the electronic office of the Spanish tax authority, the Agencia Tributaria. This article is informative and does not replace tax advice: deadlines have changed several times and should be checked with your adviser before making decisions.

RegulationInvoicingAutomation

Frequently asked questions

What is the difference between Verifactu and mandatory e-invoicing?

They are two separate obligations that often get confused. Verifactu requires the software you issue invoices with to be tamper-proof and traceable for the tax authority. The e-invoice under the Crea y Crece law governs the format and the exchange of that invoice with the other company. They can be met separately and have different timetables.

When will B2B e-invoicing become mandatory?

Royal Decree 238/2026 already sets out the rules, but the deadlines run from the entry into force of the ministerial order on the Spanish tax authority's public solution: twelve months for businesses with a volume of operations above eight million euros and twenty-four months for everyone else. With the date in the draft order, that would mean 1 October 2027 and 1 October 2028. Check the official gazette before planning.

Is a PDF sent by email an electronic invoice?

Not for the purposes of this obligation. The B2B e-invoice is a structured file that follows the European standard EN 16931, in UBL, CII, EDIFACT or Facturae, which software can read without having to interpret it. A PDF is a document designed to be read by a person and does not comply.

What happens if I do not adapt?

Under Verifactu, Article 201 bis of the General Tax Act sets a fine of 50,000 euros per financial year for holding non-compliant invoicing systems, with higher amounts for those who produce or market such software. With B2B e-invoicing, the most immediate effect is commercial: your business customers will also be required to receive invoices in a structured format, and if you cannot issue them, it becomes a barrier.

Can I use the change as an opportunity to automate?

It is the best moment to do it. You are going to touch the invoicing process anyway, and a structured invoice is far easier to automate than a PDF: the data arrives labelled and does not need interpreting. Adapting purely to comply wastes half the work.

In short

These are two obligations, not one. Verifactu has published dates — January and July 2027 — and affects the software you issue with; business-to-business electronic invoicing now has its regulation, with expected dates in October 2027 and October 2028, and affects the format and the exchange. Confusing them leads companies to believe they are compliant when only half the job is done.

And there is a real opportunity in the middle. You are going to redesign the invoicing circuit anyway: doing it with compliance as the only goal leaves on the table the part that actually saves work. That is how we approach our AI process automation service.

Adapting your invoicing?

Tell us how you issue and receive invoices today and with which systems. We analyse the full circuit and propose a scope that meets the rules and removes manual work along the way.

Request a process analysis