01
Invoice data
Issuer, recipient, identifiers, addresses, lines, tax, references, payments and mandatory content.
Technical readiness for B2B e-invoicing
Assessment and architecture for adapting ERP, SaaS and internal processes to structured invoice exchange between businesses in Spain.
Regulatory review
- Position
- Royal decree published; public-solution technical order pending
- Application
- 12 or 24 months from the future order taking effect
- Formats
- CII, UBL, EDIFACT and Facturae under the EN16931 model
Context
Royal Decree 238/2026 defines the system, but effective application starts from a future technical order for the public solution. This period can be used to fix data, states and integration boundaries without inventing a closed date.
01
Readiness assessment
Before selecting a platform, check whether data and process can support the new exchange.
02
System map
ERP, invoicing, CRM, procurement, treasury, document repositories and private platforms involved in the flow.
03
Actual scope
Affected B2B operations, exceptions, territories and decisions requiring tax or legal validation.
02
Exchange architecture
The design must support structured formats and retain traceability between the business document and every transmission.
01
Model and formats
Canonical EN16931 model and controlled transformations across CII, UBL, EDIFACT, Facturae and, where appropriate, Peppol BIS.
02
Signing and transport
Advanced signature on private platforms, authentication, entry points, faithful copy to the public solution and delivery evidence.
03
Interoperability
Integration contracts, semantic validation, versioning, errors and compatibility between private platforms and the public solution.
03
Status, payment and reconciliation
The system does not stop after issue. It needs to record commercial acceptance or rejection, full payment and, where used, partial status or assignment. Those events must reconcile with ERP, CRM and treasury.
Specific reporting obligations and periods depend on the business and application rules. Implementation should keep them configurable rather than embed an unvalidated tax interpretation in code.
- Stable identifier across invoice, copies and status messages.
- Transformation traceability without losing the original.
- Idempotent retries and an incident queue.
- Reconciliation of acceptance, rejection, collection and payment.
- Operational audit and alerts for pending status.
04
What can move before the technical order
- Clean and document the fiscal data model.
- Inventory formats, platforms, customers and suppliers.
- Separate generation, representation, signing and transport.
- Design status handling and payment reconciliation.
- Create versioned adapters and synthetic contract data.
- Reserve final public-solution integration for definitive specifications.
Assessment outcome
Readiness should end in concrete decisions and tests, not a generic presentation about the regulation.
- 01System, owner and entry-point map.
- 02Field and data-quality matrix by format.
- 03Design for status, errors, retries and reconciliation.
- 04Backlog separating stable work from future-order dependencies.
Common questions
Short answers about scope, evidence and implementation boundaries.
Is there a calendar date applying to every business?+
No. Royal Decree 238/2026 links effective application to a future order for the public solution. From that order taking effect, the periods are 12 months for businesses above EUR 8 million in turnover and 24 months for the rest.
Will the public solution be mandatory?+
The royal decree permits private platforms but establishes interoperability and submission of a faithful UBL copy to the public solution under its rules.
Is generating a PDF enough?+
No. The regulated electronic invoice is a structured message following EN16931 and an admitted syntax. PDF may serve transition or readability purposes but does not replace the message.
Should implementation wait for the technical order?+
The final connection should wait for definitive detail, but data, architecture, status, format and integration-contract work can start now. Those areas usually account for most of the effort.
Official source
The schedule is expressed relatively because it still depends on a future order. This page will be updated when that order is published.
- Royal Decree 238/2026
BOE · Spanish legal text on mandatory e-invoicing between businesses and professionals
Initial technical review
Use the regulatory wait to reduce technical uncertainty.
With an anonymised invoice sample, system map and payment process I can separate useful preparation from decisions that still depend on the order.
- Do not send certificates, tax IDs, invoices or secrets through this form.
- Tax and legal applicability must be validated with your adviser.
- A human reply, normally within one business day.