Which e-invoice formats and signed envelopes can this viewer open?
The viewer decodes five distinct XML syntaxes (UN/CEFACT CII, OASIS UBL 2.1, Polish KSeF, Italian FatturaPA, and Spanish Facturae) alongside hybrid PDF/A-3 containers and signed envelopes. Most European B2G and B2B exchanges follow the semantic data model established by Directive 2014/55/EU on Electronic Invoicing.
Because ZUGFeRD 1.0 predates EN 16931 and uses legacy XML tags, the parser excludes version 1.0 and supports ZUGFeRD 2.x and Factur-X profiles instead. It displays document type codes 380 for invoices and 381 for credit notes, plus payment code 58 for SEPA transfers. Suppliers creating hybrid documents can use our hybrid ZUGFeRD and Factur-X PDF/A-3 creator locally.
| E-invoice format | File extensions accepted | Underlying syntax | Special local handling |
|---|---|---|---|
| XRechnung | .xml |
CII or UBL 2.1 | Checks German BR-DE rules |
| Peppol BIS Billing 3.0 | .xml |
UBL 2.1 | Checks document codes 380 and 381 |
| ZUGFeRD 2.x / Factur-X | .pdf, .xml |
CII inside PDF/A-3 | Extracts embedded XML attachment |
| Polish KSeF FA(2) / FA(3) | .xml |
National <Faktura> XML |
Checks 10-digit NIP checksums |
| Italian FatturaPA | .xml, .xml.p7m |
FPR12, FPA12, FSM10 |
Unwraps CAdES .p7m envelope |
| Spanish Facturae | .xml, .xsig |
Facturae 3.2 to 3.2.2 | Strips XAdES signature wrapper |
Extracting embedded XML from hybrid PDFs and signed national files
Many accounts-payable teams receive hybrid PDFs or cryptographically wrapped files that standard text editors cannot read cleanly. The browser worker unpacks those containers locally so you can inspect both the human-readable layout and the underlying XML payload.
Inspecting EmbeddedFiles and AF arrays inside ZUGFeRD and Factur-X PDFs
When you drop a PDF, the reader inspects both the PDF EmbeddedFiles name tree and the catalog’s AF (Associated Files) array using @cantoo/pdf-lib. It scans up to 20 tree levels for standard attachment names including factur-x.xml, zugferd-invoice.xml, xrechnung.xml, and order-x.xml.
Under the FNFE-MPE Factur-X Hybrid Standard, the embedded XML carries the authoritative machine-readable invoice data while the PDF pages provide the visual layer. Clicking Download the XML saves that extracted attachment cleanly to disk, while any extra files attached to the PDF are listed at the bottom of the invoice card.
Unwrapping CAdES .p7m and XAdES .xsig signature containers
Italian Sistema di Interscambio (SdI) invoices frequently arrive as binary CAdES-BES .xml.p7m envelopes, while Spanish public-sector invoices often use XAdES .xsig wrappers. The parser strips the ASN.1 or XML signature envelope in memory so you can read line items, VAT rates, and IBANs immediately, then click Download unwrapped XML.
For specialized national workflows, Polish finance teams can also inspect Polish FA(2) and FA(3) filings in the KSeF XML viewer with dedicated NIP and schema metadata panels.
Checking EN 16931 required fields, VAT math, and XRechnung rules
Visualizing an XML file is only half the workflow when accounts-payable systems reject files for broken totals or missing buyer codes. The Checks banner runs deterministic EN 16931 business rules automatically the moment a file opens.
Line-level arithmetic and 0.01 rounding tolerance checks
The validator evaluates BR-CO-10 through BR-CO-14 by summing line net amounts, document-level allowances, charges, tax-exclusive totals, and VAT category breakdowns. It applies a 0.01 rounding tolerance (1 cent) to prevent false positives from standard two-decimal rounding differences on multi-line supplier invoices.
Catching missing buyer references and VAT category errors
Required-field rules (BR-01 through BR-27) flag missing invoice numbers, invalid calendar dates, non-ISO three-letter currency codes, negative line prices, or missing seller and buyer country codes. When the file declares an XRechnung or Peppol specification identifier, additional national rules such as German buyer references (Leitweg-ID) under the KoSIT XRechnung Specification are checked as well, helping teams resolve rejections before re-submission.
Tip: If an incoming German supplier invoice fails
BR-DEchecks, ask the vendor to regenerate it using corrected buyer reference codes or author compliant German XML bills with the XRechnung generator.
Does a readable PDF export replace the original XML invoice?
A readable PDF generated from an XML e-invoice is an inspection copy only and does not replace the legal XML original. Under German and EU tax-auditing rules, businesses must archive the original structured XML (or original hybrid PDF/A-3) in machine-readable form to preserve audit integrity.
Archiving original XML files for statutory tax compliance
Whether the file is a Peppol UBL document conforming to the OpenPeppol BIS Billing 3.0 Specification or a signed national XML, store the unaltered source file in your accounting archive. Use Save as PDF and Full preview for internal approvals, expense reviews, or human sign-off.
Statutory archiving rules differ across EU member states, so treat these checks as operational guidance rather than certified tax or legal advice. For formal compliance sign-off, always confirm archiving obligations with a qualified accountant or tax authority and run the invoice through your national portal’s official validator.
Local Web Worker parsing with zero invoice uploads
Invoices contain sensitive supplier pricing, customer addresses, and bank IBANs that should never transit third-party servers. Every step, from reading .xml and .pdf bytes to rendering the printable PDF, executes inside your browser tab with 0 bytes sent over the network, just as when you unwrap Italian SdI invoices without server uploads. You can also click Full preview to inspect the rendered PDF pages before saving.