E-invoicing by country

E-invoicing in Spain: mandates, formats, sending and receiving

Dynafis combines invoice validation, recipient capability, country profiles and evidence for Spain. The permitted route is determined per legal entity, transaction and environment; FACe is only one part of the overall process.

What applies in this country?

Spain uses separate rails: FACe/Facturae for B2G, SII for relevant taxpayers, VERI*FACTU for applicable software and tax scope, and a future B2B route that is not production-enabled yet. FACe/Facturae, SII, VERI*FACTU and the future B2B route are distinct rails. Dynafis does not activate future B2B production without final technical rules and provider evidence; Peppol remains cross-border or voluntary.

Who is affected?

The profile distinguishes B2B, B2G, B2C and cross-border. Scope also depends on establishment, tax registration, recipient type, public procurement and cross-border context.

Networks and portals

Relevant networks and portals include FACe, SII, VERI*FACTU and Peppol. Dynafis validates Facturae, XAdES, SII records and VERI*FACTU records and the addressing schemes 9920 as separate concerns.

Networks and portals
  • FACe
  • SII
  • VERI*FACTU
  • Peppol
Formats and profiles
  • Facturae
  • XAdES
  • SII records
  • VERI*FACTU records
Identifiers
  • 9920
What Dynafis supports today

Dynafis supports the available sub-routes and exposes missing national rails as blockers. Partial coverage is never presented as complete country compliance.

Coverage boundaries

The support status describes Dynafis technical coverage, not a blanket legal or tax approval. National reporting, fiscalization, archive or signature duties may apply in addition to invoice exchange.

Sending process
  1. 01

    Determine legal entity, transaction type and recipient country

  2. 02

    Validate recipient ID, scheme and document profile

  3. 03

    Freeze the canonical invoice and run the country preflight

  4. 04

    Execute the permitted exchange, clearance and reporting rails

  5. 05

    Reconcile provider statuses, receipts and evidence

Receiving process
  1. 01

    Retrieve from Peppol, the national platform or a partner connector

  2. 02

    Store the legal original separately from the transport artifact

  3. 03

    Validate profile, sender, totals and correction references

  4. 04

    Assign the document to the correct legal entity in the shared inbox

Corrections and status
  1. 01

    Reference the original and profile version unambiguously

  2. 02

    Choose credit note, correction, replacement or cancellation only when supported

  3. 03

    Reconcile status history, reporting and evidence together

For accountants and multi-client work

For accountants and multi-client work

Accounting firms configure Spain per client and legal entity. Credentials, provider accounts, documents and production approvals never inherit between clients; month-end checks remain traceable per legal entity.

For accountants and multi-client work
FAQ
Is e-invoicing mandatory in Spain?

Spain uses separate rails: FACe/Facturae for B2G, SII for relevant taxpayers, VERI*FACTU for applicable software and tax scope, and a future B2B route that is not production-enabled yet. The exact scope must be assessed for the legal entity and transaction.

Is Peppol sufficient for Spain?

Not automatically. Peppol may be an exchange rail, but it replaces national clearance, reporting or fiscalization such as FACe, SII, VERI*FACTU and Peppol only when the active country profile explicitly permits it.

What does Dynafis support for Spain today?

Dynafis supports the available sub-routes and exposes missing national rails as blockers. Partial coverage is never presented as complete country compliance.

Sources and review status

Reviewed: · es-multi-rail-2026.07.29