All free tools

Technical resource · English edition

Validate your FPR12 invoice XML locally

Check an ordinary FatturaPA XML file against the official Agenzia delle Entrate XSD before sending it to Italy’s Sistema di Interscambio (SdI). No invoice upload, email address or account is required.

What a passing result means

The file parsed as XML, conformed to the ordinary-invoice VFPR12 XSD version 1.2.3, and declared FPR12 in both the root attribute and transmission header. It does not mean the SdI will accept it, that a signature is cryptographically valid, or that the VAT treatment, totals, identities and legal obligations are correct. SdI applies further checks that this tool does not reproduce.

01 / local check

Choose the official schema and your XML

Invoice maximum 5 MiB; schema maximum 256 KiB. Plain XML only, not a signed .p7m envelope, ZIP or PDF. Neither selected file is uploaded or stored by this tool. The official schema must match our pinned 1.2.3 download fingerprint; a modified or different version is refused. Clear the selection to discard the invoice and result, or close the tab to discard the session.

Download the ordinary-invoice XSD directly from the Revenue Agency, then choose that unmodified file here. This website does not redistribute the Agency schema. This is the XSD itself, not the PDF specification numbered 1.9.1.

No schema selected.

No invoice selected.

02 / read the structure

Which fields are in an FPR12 XML?

The root FatturaElettronica uses namespace http://ivaservizi.agenziaentrate.gov.it/docs/xsd/fatture/v1.2 and versione="FPR12". It contains one header, one or more bodies and optionally an XML digital-signature element. Element order matters: the XSD uses sequences, not an unordered list.

Key FPR12 XML blocks and how their fields are used
Path / blockWhat it carries
Header/DatiTrasmissioneTransmitter’s IdPaese and IdCodice, ProgressivoInvio, FormatoTrasmissione=FPR12 and CodiceDestinatario. Optional transmitter contacts and PECDestinatario follow. The XSD constrains format and length but cannot establish that a routing code reaches your actual customer.
Header/CedentePrestatoreSupplier’s DatiAnagrafici, Sede and optional other address, professional register and contacts. The data include fiscal identifiers and RegimeFiscale; schema validity cannot confirm the identity or eligibility for that regime.
Header/CessionarioCommittenteBuyer’s identifying and address details. Optional fiscal representative and third-party issuer blocks are separate header elements and have prescribed positions.
Body/DatiGeneraliDatiGeneraliDocumento includes TipoDocumento, Divisa, Data and Numero; optional withholding, stamp duty, pension fund, total, description and related-document details depend on the transaction. ImportoTotaleDocumento is optional in this XSD, not an independently verified computed total.
Body/DatiBeniServiziOne or more DettaglioLinee entries and tax summary DatiRiepilogo with amounts, VAT rate and, when relevant, Natura. The XSD checks types, order and allowed codes, not whether the chosen VAT treatment or arithmetic is appropriate.
Body/DatiPagamento / AllegatiPayment terms/details and embedded attachments are optional blocks. Attachments can increase file size substantially; the 5 MiB cap here protects the browser, not a guarantee of SdI file acceptance.

03 / method & limits

How this check works

  1. The selected files stay in browser memory. The official XSD is checked against the supported download’s SHA-256 fingerprint before use. The invoice’s 5 MiB limit applies before reading; DTD and entity declarations are rejected before parsing.
  2. Browser WebAssembly compiles your verified Agency XSD. Its XMLDSig import is provided from this website’s licensed, DTD-free W3C schema copy in memory; parser network access and external entity loading are disabled. The validator checks the whole document and returns XSD diagnostics.
  3. Because the official ordinary schema supports both FPR12 and FPA12, this page additionally checks that both format indicators say FPR12. A simplified invoice FSM10 or public-administration invoice FPA12 is outside this tool’s scope.

Not covered: actual SdI transmission/acceptance, duplicate document numbers, fiscal/VAT registers or counterparty verification, business-rule error codes, semantic arithmetic, current tax treatment, authenticity or digital-signature cryptography. Files with external DTDs are deliberately not supported even if another XML system accepts them. No result is a legal or tax opinion.

For the end-to-end invoicing process, read our SdI and FatturaPA guide.

Official specification & schema sources

Source snapshot checked 10 November 2026. Agency technical specifications v1.9.1 are listed as usable from 15 May 2026; the ordinary invoice schema itself declares v1.2.3. The W3C signature schema’s optional structure is included, but no signature verification is performed.