Konvertējiet CII XML vai Factur-X PDF uz PEPPOL UBL — Bezmaksas tiešsaistes rīks
Augšupielādējiet UN/CEFACT CII XML rēķinu vai Factur-X / ZUGFeRD PDF — konvertors izvilks iegulto CII, kartēs katru EN 16931 lauku un atgriezīs tīru PEPPOL BIS 3.0 UBL XML.
Augšupielādējiet jēlu UN/CEFACT CII XML failu vai Factur-X / ZUGFeRD 2.x PDF/A-3. Konvertors automātiski atklāj formātu.
2
Kartēt CII uz UBL
Katrs CII elements tiek kartēts uz tā EN 16931 UBL ekvivalentu: puses, PVN sadalījums, naudas kopsummas, rēķinu rindas.
3
Lejupielādēt PEPPOL UBL
Saņemiet PEPPOL BIS 3.0 UBL XML failu ar pareizu CustomizationID, gatavu sūtīšanai caur jebkuru PEPPOL Access Point.
Kad konvertēt CII uz UBL
PEPPOL Access Points, kas saņem Factur-X
Franču un vācu piegādātāji arvien biežāk sūta Factur-X PDF arī starptautiskiem pircējiem.
Migrācija no ZUGFeRD uz PEPPOL
Vācijas uzņēmumi, kas pieņem PEPPOL pārrobežu rēķinu izrakstīšanai, bieži glabā ZUGFeRD 2.x / Factur-X PDF arhīvu.
SAP, DATEV un ERP integrācija
Daudzas ES ERP sistēmas dabiski uzņem tikai UBL. Piegādātāji, kas sūta CII vai Factur-X, var tikt normalizēti uz UBL.
Audits un caurspīdīgums
CII XML ir izsmalcināts un grūti lasāms. PEPPOL UBL izmanto pazīstamākos cbc:/cac: elementus.
Kas tiek kartēts no CII uz UBL?
Galvenes lauki, pārdevēja un pircēja puses, maksājuma līdzekļi, dokumenta līmeņa atlaides un izmaksas, PVN sadalījums, monetārie kopsummas un visas rēķinu vai kredītrēķinu rindas.
Kuri CII profili tiek pieņemti?
Visi pieci Factur-X / ZUGFeRD profili tiek pieņemti kā ievade: MINIMUM, BASIC-WL, BASIC, EN 16931 (COMFORT) un EXTENDED.
CII uz PEPPOL UBL: BUJ
Can I upload a Factur-X PDF directly?
Yes. The converter detects PDFs via the %PDF magic bytes and extracts the embedded CII XML automatically. You do not need to manually unpack the PDF or save the XML attachment separately. Drop the Factur-X / ZUGFeRD 2.x PDF and you get back PEPPOL UBL.
Which Factur-X profiles can I convert?
All five profiles are accepted as input: MINIMUM, BASIC-WL, BASIC, EN 16931 (COMFORT) and EXTENDED. The output is always PEPPOL BIS 3.0 UBL. Note that MINIMUM and BASIC-WL CII files do not contain invoice lines, so the resulting UBL will also have no lines — only document-level totals.
Does the output pass PEPPOL BIS 3 validation?
The output carries the correct PEPPOL CustomizationID and ProfileID. Whether it passes the full PEPPOL BIS 3 schematron depends on the source data — if the original CII invoice was EN 16931-compliant with all PEPPOL-required fields (seller endpoint, scheme IDs, etc.), the output will validate. For files with missing PEPPOL-specific fields, run the output through our PEPPOL BIS 3 Validator to identify what to fix.
How are CII dates and amounts handled?
CII uses date format 102 (YYYYMMDD) — the converter reformats these to ISO YYYY-MM-DD as required by UBL. Amounts are passed through with their original precision; currencyID attributes are preserved on every monetary element. The document currency code is copied from CII InvoiceCurrencyCode to UBL cbc:DocumentCurrencyCode.
What happens with credit notes (TypeCode 381)?
Credit notes are detected from CII TypeCode 381 and converted to UBL CreditNote documents (root element ubl:CreditNote, lines as cac:CreditNoteLine, quantities as cbc:CreditedQuantity). The billing reference structure is preserved if present in the source CII.
What is the reverse direction?
See our UBL to Factur-X converter — same field mappings in reverse, producing a Factur-X EN 16931 hybrid PDF from PEPPOL UBL. Together the two converters let you move freely between the PEPPOL ecosystem and the Factur-X / ZUGFeRD ecosystem.