Kairoseth/Kairoseth Fiscal/VeriFactu/VeriFactu 2028: what Spain announced and what remains legally effective today.
VERIFACTU 2028 · ANNOUNCEMENT VS LAWUpdated 2026 guide

VeriFactu 2028: what Spain announced and what remains legally effective today.

On 5 October 2026 Spain's Ministry of Finance announced a plan to move pending invoicing-software obligations to October 2028. It is important for planning, but it must not be confused with a regulatory amendment already published in the Official Gazette.

The correct way to read the timetable is to keep two references separate: what the Ministry has announced for 2028 and the 2027 dates that remain legally effective until the corresponding amendment is published.

View VeriFactu SoftwareReview my case
VERIFACTU GUIDE

What is known and what still requires a regulatory change.

The announcement changes reasonable planning, but it does not justify removing the currently published legal dates from the calendar.

The Ministry announces October 2028

The 5 October note plans to move pending Royal Decree 1007/2023 obligations to October 2028 to align them with electronic invoicing for SMEs and self-employed professionals.

2027 remains the current legal reference

Until an amendment is published, the legally effective timetable still uses 1 January 2027 and 1 July 2027 depending on taxpayer type.

VeriFactu has not disappeared

The communication describes a delay and convergence. It also says core technical guarantees are expected to remain substantially equivalent.

Electronic invoicing and VeriFactu remain distinct frameworks

B2B electronic invoicing has its own implementing rules. The announced intention is to align timetables and later pursue convergence of scope and certain technical elements.

Technical preparation still has value

Mapping data, stabilizing numbering, testing integrations, and documenting errors and retries prevents the extra time from becoming another last-minute migration.

Final go-live checks must use official sources

Before production activation, check the Ministry, AEAT and BOE again. A planning announcement does not replace the regulation eventually published.

STEP BY STEP

How to plan while the announcement and current law coexist.

Separate legal compliance, technical readiness and the go-live decision.

01

Keep the current legal calendar visible

Do not remove 2027 from compliance controls until a published rule changes those dates.

02

Use 2028 as the announced planning horizon

Use the expected extra time to organize systems, data, integrations and tests without treating the amendment as completed.

03

Prepare without enabling production by default

Diagnosis, mapping and TEST can advance under control; production should remain a separate gate.

04

Revalidate when the BOE changes

When the amendment is published, update dates, documentation, content and go-live planning from the new legal text.

ANNOUNCED ≠ IN FORCE

Plan around October 2028, but comply with the rule that is actually in force.

As of 15 October 2026, the Ministry has communicated a planned delay. A regulatory amendment is still the step that turns that plan into a new legally applicable timetable.

FAQ

Frequently asked questions.

Short answers grounded in official sources.

Has VeriFactu legally moved to October 2028 already?

On 5 October 2026 the Ministry of Finance published a planned change to move pending obligations under Royal Decree 1007/2023 to October 2028. The communication itself describes a future regulatory change. Until that change is approved and published, the announced timetable and the legally effective timetable must be kept separate.

Which dates remain legally effective until the law changes?

Current rules retain 1 January 2027 for the group linked to Corporate Income Tax and 1 July 2027 for the remaining taxpayers covered by article 3.1, subject to the scope applicable to each case.

Why does the Ministry want VeriFactu to move to October 2028?

The announcement says the goal is to align pending invoicing-software obligations with electronic invoicing for SMEs and self-employed professionals and then pursue greater regulatory and technical convergence.

Does the announcement remove technical requirements for invoicing systems?

No. The Ministry states that integrity, preservation, accessibility, readability, traceability and immutability guarantees are expected to remain substantially equivalent to the current implementing framework.

Should businesses keep preparing their software?

Yes. The calendar can change, while system inventory, numbering and data reviews, integration design, preflight testing and recovery documentation still reduce risk. Production activation must always follow the rules in force at that time.

KEEP EXPLORING

Canonical VeriFactu guides.

Each guide owns a distinct intent to avoid duplication and make the path from question to solution clear.

OFFICIAL SOURCES

Always check the current official version.

This guide summarizes official rules and documentation; it does not replace tax advice or checking the exact scope that applies to each organization.

TRUST & CONTROL

Authority stays explicit as the platform grows.

Kairoseth separates identity, organization scope, product roles and product capabilities. A login route, browser state or AI response never becomes an authorization boundary by itself.

KAIROSETH PLATFORMCONTROL PLANE
Identity
Shared account
Verified
Organization
Tenant scope
Required
Product
RBAC assignment
Explicit
Sensitive actions
Policy gate
Controlled
01

Organization scope

Customer resources and access are resolved inside an active organization context rather than treated as global account state.

02

Product-scoped roles

Owner, Admin and Member authority is assigned per product. Organization membership alone does not automatically grant every product.

03

Server authority

Sensitive access, policy and capability decisions remain authoritative on the server instead of trusting client UI state or model output.

04

Controlled execution

Capabilities that can act are introduced behind explicit grants, staged gates and audit rather than implied autonomy.

Public trust evidence

Review the customer-facing policies that define privacy, security reporting, acceptable use and the current legal operating framework.

SOFTWARE VERIFACTU

Want to prepare for VeriFactu without depending on the calendar staying unchanged?

Kairoseth Fiscal separates diagnosis, integration, TEST and activation so technical readiness remains useful even when deadlines change.

View VeriFactu for my softwareERP / CRM