# VeriFactu and B2B electronic invoicing: differences, dates and which comes first > VeriFactu and B2B electronic invoicing are not synonyms. If “VeriFactu” is used as shorthand for the RRSIF/SIF timetable, current law on 17 October 2026 places RRSIF first: adaptation before 1 January 2027 for Corporate Income Tax taxpayers and before 1 July 2027 for the remaining covered taxpayers. B2B e-invoicing starts on 6 October 2027 for businesses above EUR 8 million and on 6 October 2028 for the rest. The Ministry has announced an intention to align pending RRSIF obligations toward October 2028, but that forecast still requires a legal amendment before it replaces the current timetable. Canonical: https://kairoseth.com/en/solutions/verifactu-vs-b2b-electronic-invoicing-spain-differences Product: [VeriFactu Software](https://kairoseth.com/products/kairoseth-fiscal) Primary query: VeriFactu vs B2B electronic invoicing Spain Intent: commercial-investigation-verifactu-b2b-electronic-invoicing-differences Published: 2026-10-07 Updated: 2026-10-17 Geographic scope: España Geographic context: This cluster directly depends on Spanish national regulation published in BOE and Spanish Tax Agency specifications/portals. No city variants are created because the differentiating value is national regulation. If a search uses “VeriFactu” as shorthand for the RRSIF/SIF timetable, the answer today is yes: under legislation published and in force on 17 October 2026, systems must be adapted to RRSIF before 1 January 2027 for Corporate Income Tax taxpayers and before 1 July 2027 for the remaining covered taxpayers. Mandatory B2B electronic invoicing, developed through Royal Decree 238/2026 and Order HAC/1028/2026, applies from 6 October 2027 for businesses above EUR 8 million in turnover and from 6 October 2028 for the rest. Under currently published law, the RRSIF timetable therefore comes first. However, on 5 October 2026 the Ministry of Finance published an official forecast to postpone pending RRSIF obligations until October 2028 and converge them with electronic invoicing. That forecast is official but does not replace the current dates until the corresponding legal amendment is approved. ## Two related frameworks: fiscal system records and electronic invoice circulation RRSIF/VERI*FACTU answers questions about how invoicing software must behave: generation of records, integrity, preservation, accessibility, readability, traceability and immutability, together with the relevant submission mode. Kairoseth Fiscal therefore centralizes preflight, identity, chaining, fiscal transport, state and regulatory presentation outside source systems. An ecommerce order or ERP row supplies commercial facts but does not decide sensitive fiscal logic itself. B2B electronic invoicing addresses another layer: how an electronic invoice is issued, transmitted, received and interconnected between businesses and professionals. Royal Decree 238/2026 modifies Spanish invoicing rules and defines a system involving private platforms and a public solution. It also introduces invoice-status/payment information and interoperability requirements. The two layers share data and may converge technically, but confusing them today can produce designs where an integration solves only fiscal records while being marketed incorrectly as a complete B2B exchange solution. ## Does VeriFactu take effect before mandatory B2B electronic invoicing? Under published law in force on 17 October 2026, yes, if “VeriFactu” is used as shorthand for the RRSIF/SIF adaptation timetable. Royal Decree-law 15/2025 set adaptation before 1 January 2027 for Corporate Income Tax taxpayers and before 1 July 2027 for the remaining covered taxpayers. The B2B timetable instead runs from the entry into force of Order HAC/1028/2026 on 6 October 2026: twelve months for businesses above EUR 8 million and twenty-four months for the rest, corresponding to 6 October 2027 and 6 October 2028. The answer has a second layer: on 5 October 2026 the Ministry of Finance announced its intention to postpone pending RRSIF obligations until October 2028 so they coincide with the electronic-invoicing timetable for SMEs and self-employed professionals. It is an important official forecast for planning, but it should not be presented as a consolidated new legal date until the amendment changing the current timetable is published. ## The current B2B timetable has a published legal trigger on 6 October 2026 Order HAC/1028/2026 was published on 5 October and entered into force on 6 October 2026. Its explanatory text states that entry into force starts the statutory countdown defined in Law 18/2022 and Royal Decree 238/2026. Final Provision Four of the Royal Decree separates two groups: twelve months for businesses that exceeded EUR 8 million in annual turnover during the previous year and twenty-four months for the remaining businesses and professionals. Under the regulation reviewed on 17 October 2026, this places effective dates on 6 October 2027 for the first group and 6 October 2028 for the rest. Private exchange platforms also have their own obligations taking effect after twelve months. These dates should always be rechecked before contractual or production decisions because later regulation may change them; unlike the 5 October RRSIF forecast, however, this timetable currently has a published legal mechanism that has started the countdown. ## The public B2B solution has its own technical model, forms, web services and states Order HAC/1028/2026 develops technical and functional elements of the public solution: semantic model and UBL/EN 16931 syntax, issuance and interconnection procedures, faithful-copy submission, validations, responses, rejection handling, recovery, queries, states and payment communication. The Spanish Tax Agency must publish service specifications and capacity details on its electronic office. The public solution must be available at least two months before its first effective application. This shows why adding a QR code or reusing a VeriFactu endpoint is not enough to claim electronic invoicing is solved. B2B exchange has its own lifecycle and state data. A well-separated architecture can reuse invoice identity, customer data, amounts, series and observability, but it must implement the appropriate exchange contract. Kairoseth should not confuse VERI*FACTU presentation with a B2B invoice transmitted under Royal Decree 238/2026. ## The Ministry has announced convergence, but the product should prepare for it without inventing it early On 5 October 2026 the Ministry of Finance published a forecast modification of deadlines for pending RRSIF obligations. The communication proposes alignment with the electronic-invoicing timetable through October 2028 and later movement toward greater convergence of scope and technical aspects, while preserving substantially equivalent guarantees of integrity, preservation, accessibility, readability, traceability and immutability. The Spanish Tax Agency links the communication from its SIF/VERI*FACTU portal. Technical strategy can take advantage of that announced direction: one catalog of installations, adapters, invoice identity, MappingProfile, observability and secret controls can feed different modules. But each regulatory output contract should remain isolated until a unified specification actually exists. A shared data core with separate adapters allows future convergence without duplicate systems while avoiding the premature claim that a VeriFactu integration automatically satisfies B2B exchange. ## Recommended architecture shares business facts rather than premature regulatory rules WooCommerce, PrestaShop, ERP, Excel and legacy software can produce a stable invoice representation containing identity, series/number, date, issuer/recipient, lines, taxes, currency and totals. Those facts are reusable. Organization and installation catalogs, isolated credentials, events, correlationId and support tooling can also be shared. Transport decisions, syntax, states and framework-specific requirements should not be merged prematurely. For Kairoseth, the pattern is source adapter → neutral model → specific regulatory modules. Kairoseth Fiscal continues handling RRSIF/VERI*FACTU. A future B2B electronic-invoicing layer can consume the same origin while maintaining its own interoperability, syntax and state contract. If the Ministry later materializes deeper convergence, both modules can share more components; if convergence changes direction, separation prevents rewriting source integrations. ## For businesses: plan one roadmap but keep two compliance checklists An SME can save effort by treating both changes as one invoicing-modernization program: inventory systems, improve data quality, document numbering, customers, series, corrective flows, integrations and observability. That work benefits both frameworks. It is also useful to know whether annual turnover exceeded EUR 8 million because the published B2B timetable distinguishes that group. For the rest, the current B2B date falls in October 2028, matching the announced horizon for future RRSIF alignment even though the two dates arise from different legal mechanisms. The checklists should remain separate: one proves SIF/VERI*FACTU readiness and another proves B2B electronic-invoicing readiness. Do not mark the second complete because a QR works, or the first complete because a UBL invoice was transmitted successfully. Before each go-live, review current regulation, Spanish Tax Agency specifications and the specific business scope. That discipline captures convergence benefits without losing traceability over which obligation has actually been tested. ## What a solution should not promise in October 2026 A solution should not claim that VeriFactu and electronic invoicing are the same obligation, that October 2028 is already a consolidated new RRSIF date, that a VeriFactu connector automatically converts invoices into compliant B2B exchanges or that passing a technical smoke test equals official certification. It should not hide the October 2027 B2B phase for businesses above EUR 8 million under the current timetable either. It can communicate verifiable facts: Royal Decree-law 15/2025 currently keeps RRSIF dates in January/July 2027; Order HAC/1028/2026 entered into force on 6 October 2026; Royal Decree 238/2026 defines twelve- and twenty-four-month B2B phases; the Ministry announced a forecast to align RRSIF toward October 2028; and decoupled architecture can prepare a business for both changes. Every claim should link to legal sources or product evidence and be rechecked when regulation changes. ## How to prepare for both changes without duplicating the project 1. Inventory systems and locate the real documentary identity of every invoice. 2. Separate RRSIF/VERI*FACTU requirements from B2B exchange requirements. 3. Normalize reusable commercial facts: series, date, parties, lines, taxes, currency and totals. 4. Complete VeriFactu readiness with preflight, idempotency, state, corrective flows and presentation. 5. Design the B2B layer separately: syntax, interconnection, copies, states and payments according to current specifications. 6. Share adapters, identity and observability where safe without merging regulatory contracts. 7. Review Spanish Tax Agency/BOE sources before each production gate and update the roadmap if announced convergence becomes law. ## Key points - RRSIF in force on 17 October 2026: adaptation before 1 January 2027 for Corporate Income Tax taxpayers and before 1 July 2027 for the remaining covered taxpayers. - Order HAC/1028/2026: entered into force 6 October 2026 and started the B2B countdown. - Royal Decree 238/2026: B2B application on 6 October 2027 for >EUR 8m and 6 October 2028 for the rest. - Ministry of Finance 5 October 2026: official forecast to postpone pending RRSIF obligations until October 2028, pending legal materialization. ## FAQ ### Are VeriFactu and B2B electronic invoicing the same thing? No. They are both related to invoicing and announced convergence exists, but today they have different legal frameworks, technical contracts and obligations. Prepare them together without treating them as identical. ### Will VeriFactu take effect before mandatory B2B electronic invoicing? Under published law in force on 17 October 2026, yes, if “VeriFactu” is used as shorthand for the RRSIF/SIF timetable: adaptation before 1 January 2027 for Corporate Income Tax taxpayers and before 1 July 2027 for the remaining covered taxpayers. B2B e-invoicing starts on 6 October 2027 for >EUR 8 million and 6 October 2028 for the rest. The Ministry has announced a future RRSIF alignment toward October 2028, but it still requires legal implementation. ### When does B2B electronic invoicing start under current Spanish regulation? Order HAC/1028/2026 entered into force on 6 October 2026. Royal Decree 238/2026 sets application 12 months later for businesses above EUR 8 million and 24 months later for the rest: 6 October 2027 and 6 October 2028, unless later regulation changes the timetable. ### Is October 2028 already the definitive new VeriFactu date? We do not treat it that way. The Ministry has communicated an official forecast to align toward October 2028, but Kairoseth waits for the legal instrument that materializes the change before treating it as consolidated regulation. ### Does my WooCommerce or ERP VeriFactu connector already solve B2B electronic invoicing? Not automatically. It can reuse invoice facts and identity, but B2B exchange requires its own syntax, transmission/interconnection, copy and state contract under Royal Decree 238/2026 and its specifications. ### Can both projects be prepared together? Yes. Share inventory, adapters, data quality, identity and observability while keeping regulatory modules and gates separate until convergence is formally defined. ## Sources - [BOE — Royal Decree-law 15/2025](https://www.boe.es/diario_boe/txt.php?id=BOE-A-2025-24446) — Boletín Oficial del Estado - [BOE — Royal Decree 238/2026](https://www.boe.es/eli/es/rd/2026/03/25/238/con) — Boletín Oficial del Estado - [BOE — Order HAC/1028/2026](https://boe.es/diario_boe/txt.php?id=BOE-A-2026-20587) — Boletín Oficial del Estado - [Ministry of Finance — RRSIF and e-invoicing alignment forecast](https://www.hacienda.gob.es/sgt/gabsehacienda/nota-informativa-verifactu.pdf) — Ministerio de Hacienda - [Spanish Tax Agency — invoicing and records](https://sede.agenciatributaria.gob.es/Sede/iva/facturacion-registro.html) — Agencia Estatal de Administración Tributaria - [Spanish Tax Agency — invoicing software systems and VERI*FACTU](https://sede.agenciatributaria.gob.es/Sede/iva/sistemas-informaticos-facturacion-verifactu.html) — Agencia Estatal de Administración Tributaria ## External resources - [Royal Decree-law 15/2025 in BOE](https://www.boe.es/diario_boe/txt.php?id=BOE-A-2025-24446): Rule keeping the current RRSIF adaptation dates in January and July 2027. - [Royal Decree 238/2026 in BOE](https://www.boe.es/eli/es/rd/2026/03/25/238/con): Consolidated text governing mandatory B2B electronic invoicing. - [Official Ministry forecast on convergence](https://www.hacienda.gob.es/sgt/gabsehacienda/nota-informativa-verifactu.pdf): 5 October 2026 note forecasting postponement of pending RRSIF obligations until October 2028. ## Next step - [Explore VeriFactu Software](https://kairoseth.com/products/kairoseth-fiscal) - [Custom request](https://kairoseth.com/custom-requests)