Clearance, Format Mandate, Five-Corner: KSeF, Germany, and Spain Compared
Three EU countries, three architectures for the same policy goal. If you invoice in more than one of them, you cannot treat e-invoicing as a PDF toggle. Here is what each model forces your stack to do.
Clearance, Format Mandate, Five-Corner: KSeF, Germany, and Spain Compared
ViDA (VAT in the Digital Age) is pushing member states toward continuous transaction controls: the tax authority sees structured invoices close to the moment they exist. Poland, Germany, and Spain all claim that direction. They did not pick the same machine.
If your software has one "send invoice" button that emails a PDF, you will fail in all three, for three different reasons.
The Three Machines
| Poland (KSeF) | Germany (UStG § 14) | Spain (Crea y Crece + Verifactu) | |
|---|---|---|---|
| Model | Centralised clearance | Decentralised format mandate | Hybrid five-corner, plus a separate software law |
| What the state sees at send time | The invoice. KSeF assigns a number or rejects. | Nothing. Audit later. | A UBL copy via the AEAT public solution, on every B2B flow |
| Legal invoice | The accepted FA(3) XML | EN 16931 structured file (XRechnung or ZUGFeRD EN 16931 / Extended) | Structured, signed Facturae / UBL / CII (plus Verifactu record if you are in SIF scope) |
| Delivery proof | UPO (state-signed) | Channel log, QES, EDI, or internal control | Platform acknowledgement plus 4-day status |
| Pipe | KSeF only (online, offline, offline24) | Email, Peppol, EDI, portal. Parties choose. | Accredited private platform or AEAT public platform, platforms must interconnect |
| Offline | Designed (three modes) | Not a clearance problem | Verifactu incident mode; TicketBAI assumes connectivity |
| B2B issuance live? | Yes, for VAT payers in scope | Receive duty live since 1 Jan 2025. Issuance 1 Jan 2027 above €800,000 Gesamtumsatz, 1 Jan 2028 for the rest | Verifactu: 1 Jan / 1 Jul 2027. Crea y Crece B2B: Oct 2027 / Oct 2028 from the ministerial order |
| Late-payment hook | Deemed receipt + UPO as dunning evidence | Format plus civil Verzug. No state payment feed. | Status includes effective payment date |
Spain is two laws. Verifactu (RD 1007/2023) governs billing software: hash chain, QR, SIF. Crea y Crece (Law 18/2022 and RD 238/2026) governs the B2B commercial invoice and its exchange. Treating them as one project is how Spanish rollouts miss a deadline.
What Each Model Forces in Software
Clearance (KSeF). The send path is a transaction with a remote authority. You need session handling, structured error codes, UPO storage, offline queues, and a KSeF number that later appears in the bank transfer title (art. 108g from 1 January 2027). "Email the customer a copy" is visualisation, not issuance. If KSeF is down and you are not in a legal offline mode, you have not invoiced.
Format mandate (Germany). The send path is whoever the buyer named. You need EN 16931 validation (schema and business rules, including BT-10), two syntaxes, ZUGFeRD PDF/A-3 without flattening, GoBD-stable archive of the structured record, and a channel switch (email / Peppol / EDI) per buyer. There is no UPO. Your evidence pack is the file plus the transmission log. Email is lawful and a weak authenticity channel.
Five-corner (Spain). The send path is a platform that must talk to the counterparty's platform and to the AEAT. You need accreditation or a connection to an accredited platform, electronic signature, Facturae and UBL, and a status machine with a 4-calendar-day SLA. The invoice is not done when it leaves you. It is done when acceptance, rejection, or payment has been reported.
ViDA Does Not Pick a Winner for You
ViDA's digital reporting and structured e-invoicing (working horizon 2030 for intra-EU, with national CTC regimes already ahead) rewards stacks that already emit EN 16931 and can report, not stacks that store PDFs. It does not require every member state to build a KSeF. Germany's July 2026 tax-crime action plan already points at real-time VAT reporting on top of the format mandate. Spain already reports payment dates. Poland already clears.
A multi-market operator therefore does not wait for a single EU API. You implement three adapters behind one invoice document:
- A canonical invoice (parties, lines, tax, payment means, references).
- A per-market validator (FA(3), KoSIT / XRechnung, Facturae / Verifactu).
- A per-market transport (KSeF session, Peppol or email, Spanish platform).
The product mistake is to start from the US workflow many receivables tools still sell: branded PDF, open tracking, reminder button, credit line. Open tracking is not UPO. A reminder button is not a requerimiento. A credit line is a bank. None of the three EU machines is a bank.
Plandesk keeps one invoice record and three transports. Poland goes to KSeF. Germany emits XRechnung or ZUGFeRD and sends on the buyer's channel. Spain signs, exchanges, and reports status. Aging and dunning read the legal artefact of that market, not an email pixel.
This material is information of a general nature and does not constitute legal or tax advice. For a specific situation, verify the current rules or consult a qualified adviser.