Italy Stamp Duty on Invoices: Imposta di Bollo Guide

In Italy, a EUR 2 stamp duty can apply to an invoice when the relevant amount is outside VAT and exceeds EUR 77.47. That is the core rule behind Italy stamp duty on invoices. On electronic invoices, the duty is not handled with a physical revenue stamp. It is flagged digitally in FatturaPA, then settled on a quarterly basis through Agenzia delle Entrate's workflow, either in the portal or via F24.

For most readers, the first decision is straightforward: if an invoice is fully subject to VAT, imposta di bollo is usually not due. The issue arises when the invoice contains supplies that are exempt, excluded, non-taxable, or otherwise outside ordinary VAT charging. If the relevant non-VAT amount goes over EUR 77.47, the invoice may need the EUR 2 duty. In everyday usage, many businesses still refer to this as a marca da bollo requirement even when the invoice is electronic. That is why Italy invoice stamp duty is less like a percentage tax and more like a document-level compliance requirement tied to how the invoice is classified.

This is also why quick rules can be misleading. An invoice total above EUR 77.47 does not automatically mean bollo applies, and a small VAT line does not automatically remove the issue. You need to look at which part of the invoice is outside VAT, whether that portion crosses the threshold, and how the invoice is represented in the Italian e-invoicing flow. For accountants, AP teams, and foreign businesses, the real question is not "What is imposta di bollo?" but "Does this specific invoice require it, and how will that show up in the data and settlement process?" The answer depends on four operational checks: the VAT treatment, the threshold calculation, the FatturaPA data, and the quarterly settlement trail.

The EUR 77.47 Threshold and the VAT-versus-Bollo Rule

The fastest way to understand Italy's stamp-duty logic is this: VAT and bollo are usually alternative. In practice, bollo tends to appear where the invoice is not carrying VAT in the ordinary way. That is why the rule shows up so often on VAT-exempt or otherwise non-VAT documents, including the familiar case of stamp duty on Italian forfettario invoices.

The EUR 77.47 test applies to the part of the invoice that falls into the non-VAT bucket. If the whole invoice is outside VAT and the taxable relevance for stamp duty exceeds that amount, the EUR 2 duty is usually due. If the invoice mixes VAT and non-VAT items, the review is more precise: you do not look only at the grand total. You look at whether the non-VAT portion exceeds EUR 77.47.

Consider a mixed invoice with EUR 40 of services subject to VAT and EUR 90 of charges that are exempt from VAT. The invoice total is EUR 130, but the point is not the total. The key fact is that the exempt portion is EUR 90, which is above the Italy EUR 77.47 invoice threshold. That is the kind of invoice where a team should stop and assess whether bollo is due rather than assuming the VAT line settles the question.

This is where invoice coding matters. The absence of VAT can reflect different legal reasons, and those reasons shape the invoice fields that should accompany the document. In Italian e-invoicing, that often means checking the relevant Natura codes and confirming that the tax treatment and the bollo treatment tell the same story. If the tax coding says the invoice, or part of it, sits outside VAT, bollo may be the next compliance question.

Forfettario invoices are the example most non-Italian readers encounter first because many guides focus almost entirely on freelancers. That example is useful, but too narrow. The same logic also matters for exempt financial services, medical or educational services, and other invoices where VAT is not charged in the usual way. That broader view is what finance teams need if they review varied supplier documents rather than a single taxpayer regime.

If your team already works with other Italy-specific VAT edge cases, it helps to compare bollo with another Italian invoice scenario where VAT treatment changes the XML fields. Both situations show why a quick glance at the invoice total is not enough. You need to understand what kind of tax treatment the document is actually reflecting.

How Bollo Appears in FatturaPA and Electronic Invoices

On an electronic invoice, the duty is not handled with a paper stamp attached to the document. It is represented digitally inside FatturaPA XML. That distinction matters because the compliance signal becomes part of the structured invoice data that moves through the Sistema di Interscambio (SDI) and into downstream accounting or extraction workflows.

In practical terms, the invoice uses the Bollo virtuale indication in the DatiBollo area to show that stamp duty applies, together with the EUR 2 amount. A finance team reading the invoice in plain PDF form may only notice a line saying that bollo is due or recharged. A team working from XML, however, can validate that the document includes the corresponding structured flag instead of relying only on narrative text.

That is useful on both sides of the workflow. For the issuer, the presence of the DatiBollo information helps show that the invoice was classified as a qualifying non-VAT document when it was generated. For the receiving side, the bollo fields give AP or accounting reviewers a concrete signal that the invoice may be exempt, excluded, or otherwise outside ordinary VAT charging. That signal should match the rest of the tax data rather than sit in isolation.

This is also why stamp duty belongs in a data-model discussion, not just a tax memo. A workflow that extracts Italian invoices should be able to distinguish a normal VAT invoice from one carrying a bollo obligation, capture the EUR 2 amount where relevant, and preserve the surrounding tax context. If a document shows bollo in its human-readable content but the XML tells a different story, that inconsistency deserves review.

Readers who need the wider context for how FatturaPA XML and SDI work in Italy's e-invoicing system can compare the stamp-duty flag with the broader transport and validation flow. For this topic, the key point is narrower: once bollo applies, it should be visible in the structured e-invoice data in a way that finance systems and reviewers can actually test.

Lists A and B, Quarterly Settlement, and How Payment Works

Once an electronic invoice is transmitted, the bollo question moves from invoice preparation into quarter-end settlement. Agenzia delle Entrate aggregates the relevant e-invoice data inside Fatture e Corrispettivi, where taxpayers can review the invoices considered relevant for stamp duty and settle the amount due for the quarter.

The most useful distinction is between List A and List B. List A reflects invoices already identified by the agency based on the transmitted data. List B is the control layer for invoices the agency believes may still require bollo even though the invoice did not indicate that the duty was not due. According to Agenzia delle Entrate's e-invoice stamp duty guidance, List B includes electronic invoices with amounts exceeding EUR 77.47, certain non-VAT Natura codes, and no indication that stamp duty is not due.

That point matters because a missing bollo flag does not necessarily end the story. If the invoice data suggests the threshold and tax-treatment conditions are present, the quarter-end review can still surface it. For accounting teams, that means stamp duty is not only an invoice-issuance issue. It is also a reconciliation issue between what the document says, what the structured data shows, and what the portal lists for settlement.

The payment itself is handled on a quarterly schedule. The amount due is surfaced in the portal after quarter end, and taxpayers can settle it through the portal or by filing an F24. In other words, Italy e-invoice stamp duty is operationally tied to two moments: getting the invoice classification right when the document is issued, and then confirming the quarter-end amount is paid through the correct channel.

For international businesses and shared-service teams, this is where process design matters. If you only review the invoice body and never reconcile it against the portal output, omitted bollo can remain invisible until the quarterly cycle. A better control is to compare the invoice's non-VAT treatment, bollo indicator, and quarter-end portal view so that exceptions are caught before they become a repeated compliance issue.

Who Owes the Duty and What AP Teams Should Validate

The legal responsibility for imposta di bollo on invoices in Italy sits with the supplier that issues the invoice. That remains true even when the EUR 2 amount is passed through to the customer as a separate charge. From a process perspective, that distinction matters: recharging the cost is a commercial choice, but liability for applying the duty correctly begins with the issuer.

For issuing teams, the review should be disciplined rather than informal. Before an invoice goes out, confirm the VAT treatment first. Then check whether the relevant non-VAT amount exceeds EUR 77.47, whether the invoice should show bollo, and whether the electronic document includes the matching structured indication when it is sent through SDI. If the invoice falls into a regime or exemption where bollo is common, that should trigger an explicit validation step rather than reliance on memory.

For AP reviewers, bollo can be a useful signal rather than just an extra EUR 2 line. It may indicate that the supplier treated the invoice as exempt, excluded, or otherwise outside ordinary VAT. That means the bollo treatment should line up with the rest of the tax coding, supplier status, and document context. If those pieces do not fit together, the team should investigate the tax treatment instead of assuming the invoice is compliant because the duty was mentioned.

A practical checklist looks like this:

• Confirm why VAT is absent or limited on the invoice.
• Check whether the relevant non-VAT amount exceeds EUR 77.47.
• Verify that bollo is shown consistently in the visible invoice and, for electronic invoices, in the XML data.
• Make sure the supplier's quarter-end process will capture the amount due if they are the liable party.
• Escalate inconsistencies instead of manually "patching" the invoice with a casual surcharge.

When an issued document is inconsistent, the right response may be a correction workflow rather than a quick annotation. That is one reason it helps to know when an Italian invoice needs a correcting credit or debit note. For finance teams handling live invoice operations, stamp duty is not a niche footnote. It is a small amount with outsized value as a compliance signal inside the broader invoice review process.