Spain is the hardest European jurisdiction to summarise accurately, because three separate obligations run in parallel and are constantly conflated — by vendors, by project plans, and by the businesses subject to them.
Separating them is most of the work.
Three obligations, not one
| Obligation | What it does | Status |
|---|---|---|
| Public-sector invoicing | Structured invoices to public bodies through a national entry point | In force for years |
| Ledger reporting | Near-real-time submission of registered invoice data by larger taxpayers | In force |
| Billing-software requirements | Integrity, traceability and non-alterability requirements on invoicing software | Staged, with dates in national law |
| Business-to-business invoicing | Structured invoices between businesses | Statute in force; timetable depends on an implementing regulation |
Only the last of those is what people mean by "the Spanish mandate", and it is the one that has not started.
The statute that is in force and the obligation that is not
The business-to-business obligation was created by a statute concerned with business growth and late payment, not primarily with tax. That origin explains a feature that surprises people: alongside the invoicing requirement sits an obligation to report the payment status of invoices, because the policy purpose was to make late payment visible.
The statute is law. Its application, however, was made conditional on an implementing regulation, and the compliance periods run from the publication of that regulation rather than from the statute. A business that reads "in force since" and starts a project against that date has misread a document.
- 2015-01-15Structured invoicing to public bodies through the national entry point.in force
- 2017-07-01Near-real-time ledger reporting for taxpayers above the applicable thresholds.in force
- 2026-01-01Billing-software requirements begin to apply, on the staged basis set in national law.in force
- 2027-01-01Business-to-business invoicing for larger businesses, counted from publication of the implementing regulation.proposed
The last entry is deliberately labelled proposed. Its date is a function of a regulation that had not been published when this article was written; the official gazette and the revenue agency, linked below, are authoritative.
What the payment-status obligation adds
Most national mandates ask you to issue a document. Spain's asks you to say what happened to it afterwards: whether it was paid, and when.
That is a materially different integration. Invoice issue is a sales process; payment status is a treasury and receivables process, usually owned by different people and served by different systems. A project scoped as "we need to send structured invoices" will not have touched the system that knows when cash arrived.
If you take one thing from this article, take that. It is the Spanish equivalent of the French payment-reporting element, and it is missed for the same reason: it is not part of the invoice.
The billing-software regime is a separate problem
The requirements imposed on invoicing software — that records cannot be altered, that they are chained, that they are traceable — are about the integrity of the system that produces invoices, not about the format of what it emits.
Two practical points:
- It can catch businesses that will never be caught by the business-to-business invoicing obligation, because it is about the software rather than about the counterparty.
- It is satisfied by the software, which means the decision is largely made when you choose or upgrade a system, not when you design an invoicing flow. See in the ERP, in a platform, or both.
Why the three keep getting confused
The confusion is not carelessness. The three obligations overlap in subject matter, arrive from different legal instruments, and are administered by bodies with different remits, so a business hears about each from a different direction and assumes it is hearing about the same thing again.
It helps to separate them by what each one is for.
The business-to-business invoicing obligation is about the document between the parties: its form, and the fact that it has to be structured rather than a PDF. Its counterparty is your customer.
The ledger reporting regime is about data going to the administration on a short clock, derived from the books rather than from the document. Its counterparty is the tax administration, and it exists whether or not any invoicing mandate applies to you.
The public sector route is about who you are invoicing: a contracting authority, through the entry point the public sector operates, under rules that predate both of the others.
An entity can be subject to all three, to any two, or to one. Which combination applies is a scope question answered per entity, and the practical error is not misunderstanding any single regime — it is scoping a project against one of them and assuming the resulting architecture covers the others. It does not: the channels differ, the payloads differ and the deadlines differ, and a plan built on the invoicing obligation alone will be complete and wrong.
What to do while the timetable is unsettled
The temptation is to wait. That is defensible for the parts that depend on the regulation, and indefensible for the parts that do not.
Work that is safe to do now, because no version of the regulation will make it wasted:
- Establish scope. Which of your entities is established in Spain for VAT purposes. Nothing else can be answered until this is written down.
- Fix master data. Tax identifiers with their schemes, complete addresses, tax categories on every line. Required by every possible version of the rules, and the longest lead time you have. Start with master data for e-invoicing.
- Design the receiving side. Every staged mandate in Europe has begun with an obligation to receive. Spain will not be the exception, and the receiving process is independent of the format. See redesigning accounts payable.
- Separate the payment-status flow. Identify now which system knows when an invoice was paid, because that answer is often uncomfortable.
Work that is not safe to do now: committing to a format, buying a connection, or writing a date into a board paper without the word proposed beside it. The general point about reading dates is in what is actually obligatory, and Spain is the case that proves it.
