Italian Fattura IVA

WooCommerce Italian VAT invoices need tax-field workflow proof, not just a PDF receipt.

If your WooCommerce store sells to Italian customers or Italian B2B buyers, invoice setup has to cover IVA totals, Codice Fiscale, Partita IVA, SDI or PEC readiness, reverse charge, invoice numbering, refunds, customer downloads, and accountant export before launch.

What an Italy-ready WooCommerce invoice plugin must store

Italian invoice workflows break when checkout cannot capture company and tax identifiers, invoice numbers are tied to WooCommerce order IDs, refunds overwrite the original PDF, or accountant exports miss invoice document evidence.

Before buying an invoice plugin, confirm that every field below is structured order data that can move into invoice PDFs, emails, My Account downloads, refund corrections, credit notes, and exports.

Italian VAT invoice field checklist

Seller legal name, address, Partita IVA, tax regime details, and contact details that match bookkeeping records
Customer legal name, billing address, country, Codice Fiscale, Partita IVA or EU VAT number, plus optional PO/reference data
Unique invoice number, invoice date, supply date, payment method, currency, net amount, IVA rate, IVA amount, and gross total
SDI code or PEC email readiness for Italian B2B/B2G workflows, even when the WooCommerce checkout still starts with a PDF invoice
Reverse-charge wording for eligible EU B2B invoices when VAT accounting shifts to the buyer
Credit-note or nota di credito relationship for refunds, corrections, cancellations, and retained original invoice PDFs

Where Italian invoice workflows break

ScenarioWeak setupBetter invoice workflow
Italian B2C orderWooCommerce sends a receipt-like email and the store owner manually creates invoice evidence later.Generate a final invoice after payment with IVA breakdown, dedicated invoice number, customer details, PDF delivery, and retained evidence.
Italian B2B orderPartita IVA, Codice Fiscale, SDI or PEC values are typed into order notes and never reach the invoice PDF or export.Capture tax identifiers as structured checkout fields, store them on the order, print them on the invoice, and include them in accountant export.
Refund or correctionThe original PDF is edited or replaced after a refund, making it hard to prove what was issued first.Keep the original invoice, issue a linked credit note/nota di credito with its own sequence, and expose both documents to the customer and accountant.
Monthly accountant handoffThe accountant receives WooCommerce orders without invoice numbers, tax IDs, IVA totals, PDF links, payment status, or credit-note references.Export invoice numbers, IVA/VAT fields, payment method, PDF URLs, refund links, and customer/company data in one accountant-ready file.

Questions to ask before choosing a plugin

1Can the plugin collect Codice Fiscale, Partita IVA, SDI and PEC fields before checkout is completed?
2Can invoice numbers use a dedicated sequence instead of WooCommerce order IDs?
3Can the PDF template show seller identity, customer identity, IVA totals, payment method, due date, and reverse-charge wording?
4Can customers download invoices and credit notes from My Account without support manually resending PDFs?
5Can refunds create a linked credit note/nota di credito while preserving the original invoice PDF?
6Can the accountant export include invoice numbers, IVA totals, tax identifiers, payment status, PDF links, and correction relationships?

FAQ

Does an Italian WooCommerce store need more than a PDF invoice template?

Usually yes if the store needs structured IVA fields, Codice Fiscale or Partita IVA capture, SDI/PEC readiness, retained PDFs, refund corrections, customer downloads, or accountant exports.

Should Italian invoice numbers reuse WooCommerce order IDs?

A dedicated invoice sequence is safer because WooCommerce order IDs include pending, failed, cancelled, draft, and test orders. A sequence such as IT-2026-000184 is easier to audit and export.

How should SDI or PEC fields fit a WooCommerce invoice workflow?

They should be captured as structured checkout/order fields, validated enough to avoid empty accounting handoff, printed or exported where needed, and retained with the invoice record rather than left in free-text notes.

How does Lattice Invoices fit this Italian IVA workflow?

Lattice Invoices is being shaped for EU WooCommerce stores that need structured tax fields, predictable invoice numbers, PDF delivery, credit notes, customer downloads, and accountant exports instead of a PDF-only receipt workflow.