XML invoices generated by the plugin: format and limits

Getting startedwordpress2026-07-01

Goal

Understand what POP produces when it generates an XML invoice for an order, and what’s missing to send it to the SDI without an active transmission channel.

What the plugin generates

For every completed order, POP creates a FatturaPA XML file (FPR12 format by default, the standard format for invoices to private individuals; the format changes if the document is addressed to a business recipient). You can download the files individually from the Invoices tab, or select several and export them in bulk as a .zip archive.

What it does NOT do on its own

The XML file generated by the plugin alone is not digitally signed. The digital signature, if required by the chosen transmission channel, is applied by the channel itself (e.g. SdI via POP), not by the base XML generation.
The file is not automatically transmitted to the SDI unless you activate one of the transmission channels (SdI via POP, PEPPOL, KSeF, or an add-on such as Fatture in Cloud, Aruba, or SdI via PEC) — see choosing-an-invoicing-integration.

If you don’t activate any channel, it’s still possible to download the XML and transmit it yourself (e.g. via PEC, signing it with an external tool, following the guidelines of the Agenzia delle Entrate, Italy’s Revenue Agency).

Verify

After an order moves to processing or completed, in POP → Electronic Invoice - Settings > Invoices you should see the XML document associated with the order, ready to download.

Common errors

The downloaded XML is rejected by an intermediary/external software because it’s “not signed” — expected: base XML generation does not include the signature; you need to sign it externally or activate a transmission channel that handles signing.
The XML is missing for an order — check the order status: generation happens when it moves to “processing” or “completed”, see invoice-numbering-and-order-status.
You need to know where the XML/PDF files are physically stored on the server — see generated-files-storage.

To choose a channel that automatically sends the XML to SDI/PEPPOL/KSeF see choosing-an-invoicing-integration; for the XML payload contract on the API side see api/sdi.