Turn a Spanish Facturae 3.2 / 3.2.1 / 3.2.2 invoice into a PEPPOL BIS 3.0 UBL e-invoice — the format the PEPPOL network and the EN 16931 mandates across Europe expect. Signed .xsig files are accepted; parties, lines, IVA breakdown and totals are mapped automatically, and Spanish NIFs become PEPPOL endpoint identifiers. Free, no signup.
Drop the Facturae XML — any FACe-accepted version (3.2, 3.2.1, 3.2.2). A signed .xsig is XML too and converts fine; the XAdES signature itself is not carried over, because the UBL output is a new document.
2
Automatic EN 16931 mapping
Seller and buyer (including their AddressInSpain / OverseasAddress blocks), invoice lines with unit codes, the IVA breakdown per rate, payment details with IBAN, and the totals chain are mapped to their EN 16931 UBL equivalents. Spanish NIFs are emitted as PEPPOL endpoint IDs with the EAS 9920 scheme, so the output is routable on the network.
3
Download PEPPOL BIS 3.0 UBL
You get a UBL invoice with the PEPPOL BIS 3.0 CustomizationID, ready for any PEPPOL Access Point or EN 16931-based national mandate. Conversion caveats — like an IRPF retention that UBL cannot express — are reported so nothing disappears silently.
Why convert Facturae to UBL?
Facturae is Spain's national format: FACe and Spanish public administrations understand it, but the PEPPOL network and the EN 16931 mandates spreading across Europe (Germany, France, Belgium, Poland, Romania…) do not. If your billing system produces Facturae and a customer asks for a PEPPOL invoice — or a foreign marketplace, ERP or government portal only accepts EN 16931 — you need the same invoice re-expressed as UBL. Re-keying it is error-prone; the converter maps it field by field.
What carries over — and what cannot
Carried over: parties with tax IDs and addresses, invoice lines (quantities, unit codes, prices, discounts and charges), the IVA breakdown per rate, document totals, due date, IBAN and payment means, order and contract references.
IRPF withholdings have no EN 16931 equivalent. They are excluded from the UBL totals — the payable amount becomes the amount before retention — and the converter tells you so. Handle the retention outside the invoice.
The XAdES signature is not transferred: the UBL output is a new, unsigned document. PEPPOL transport does not use document signatures, so nothing is lost in practice.
Rectificativa metadata and batch data (corrective references, FileHeader batch wrapper, administrative centres) have no UBL home — corrective invoices convert as ordinary invoices with a notice, and multi-invoice batches (Modality L) must be converted one invoice at a time.
Validate the result, both ways
The converted UBL follows the PEPPOL BIS 3.0 rules — you can drop it into the free PEPPOL validator to see the rule-by-rule report before sending. And if the conversion complains about your source file, run the original through the Facturae validator to find the exact FE-R rule that's broken.
Facturae to UBL: FAQ
Why would I convert a Facturae invoice to UBL?
Facturae is only understood inside Spain (FACe and Spanish public administrations). The PEPPOL network and the EN 16931 mandates across Europe — Germany, France, Belgium, Romania and more — expect UBL or CII. If a customer, marketplace or foreign portal asks for a PEPPOL invoice and your system produces Facturae, converting is far safer than re-typing the invoice.
Can I upload a signed .xsig file?
Yes. A .xsig is Facturae XML with an embedded XAdES signature, and the converter reads it fine. The signature itself is not carried over — the UBL output is a new, unsigned document. PEPPOL does not use document-level signatures (integrity is handled by the transport network), so nothing is lost in practice.
What happens to IRPF withholdings?
EN 16931 has no concept of IRPF retention, so it cannot be expressed in a PEPPOL UBL invoice. The converter excludes the withholding from the UBL totals — the payable amount becomes the amount before retention — and reports a clear warning so you know it happened. Handle the retention outside the invoice, as most cross-border flows do.
Are all Facturae versions and batch files supported?
Versions 3.2, 3.2.1 and 3.2.2 — everything FACe accepts — are supported. Multi-invoice batch files (Modality L with more than one invoice) are rejected with a clear message: convert one invoice at a time. Corrective invoices (rectificativas) convert as ordinary invoices; the corrective metadata has no UBL equivalent and is dropped with a notice.
Is the converted UBL actually PEPPOL-compliant?
The output carries the PEPPOL BIS 3.0 CustomizationID, Spanish NIFs are mapped to endpoint identifiers with the EAS 9920 scheme, amounts are normalised to two decimals, and the totals chain is kept arithmetically consistent. You can verify any result in the free PEPPOL validator — same uploader, full rule-by-rule report.
Is the Facturae to UBL converter free?
Yes — upload the Facturae, download the PEPPOL UBL, no account needed for the free daily quota.