VeriFactu slips again: what October 2028 means for your invoicing

On 5 October Spain's tax authority announced that VeriFactu moves to October 2028. It is the third delay. If you were racing to meet July 2027 you can stop racing — but you cannot stop watching it.

VeriFactu slips again: what October 2028 means for your invoicing

VeriFactu is the regime that requires invoicing software to produce signed, chained, tamper-evident records, created by Royal Decree 1007/2023. The underlying idea has not changed since the start: an invoice should not be editable or deletable without leaving a trace.

What keeps changing is when.

The calendar as it stands today

  • The original decree pointed at 2025 for software vendors.
  • A first postponement moved the obligation for companies to 1 January 2027 and for the self-employed to 1 July 2027.
  • On 5 October 2026 the tax authority announced a third delay: a single date in October 2028, replacing both of the above.

⚠️ One detail worth not skipping: until it is published in the BOE, the official date is still 1 July 2027. The new calendar has been announced, not approved. Planning around an announcement is reasonable; writing it into a contract is not.

Why they moved it

The stated reason is sensible and says a lot about the real problem: avoiding a situation where companies have to change invoicing systems twice in a short span. First for VeriFactu and then, shortly after, for mandatory business-to-business electronic invoicing. Collapsing both into one date saves an entire migration.

For a small company on an old ERP, that double migration was exactly the wall. We have watched it up close: a management system that works perfectly for day-to-day work and is suddenly the reason everything has to be replaced.

What has NOT been postponed

This is where people get confused. The delay affects when your software must comply. It does not touch any of this:

  • The ordinary invoicing rules. Sequential numbering, retention, the mandatory fields on every invoice. None of that moved.
  • SII for anyone already inside it.
  • Invoices to public bodies, which still go through FACe.
  • Business-to-business e-invoicing, which is coming regardless — and for which this 2028 date is effectively the starting gun.
A postponement is not an amnesty. It is time, and time is only worth something if it gets used.

What we would do with these two years

The temptation is to close the tab and come back in 2028. That is precisely what happened with the two previous dates, and the result was a queue of providers with no capacity left. What makes sense now, without rushing:

  • Ask your provider in writing whether their software will be adapted and whether the upgrade is included or billed separately. The answer to the second half tends to surprise people.
  • Tidy the data before the software. Duplicate customers, mistyped tax numbers and inherited invoice series are what actually makes a system change painful. That can be cleaned today and depends on no deadline at all.
  • Connect what you already have. If the quote, the invoice and the payment live in three places that do not talk to each other, 2028 will find you doing manual work you could have automated this year.

If you want us to look at how your invoicing is wired and what can be tidied now, tell us how you work. We do not sell invoicing software: our job is making the pieces you already have talk to each other.

Sources

  1. Royal Decree 1007/2023 — requirements for invoicing systems (BOE)
  2. Agencia Tributaria — invoicing systems and VeriFactu
  3. Infoautónomos — VeriFactu delayed again, now 2028
  4. Xataka — VeriFactu postponed to October 2028
Back to blog

Shall we talk aboutyour project?