Italy Credit and Debit Note Rules: TD04, TD05, Article 26

Italy credit and debit note rules start with a practical distinction: a credit note (nota di credito) reduces or cancels an invoice and normally goes through SDI as TD04, while a debit note (nota di debito) increases the taxable amount and is generally issued as TD05. The main timing rule comes from Article 26 of DPR 633/1972. Its one-year limit applies to certain error and discount corrections, but not to cancellations, annulments, or failed payments tied to insolvency proceedings. One more trap matters for implementation teams: some reverse-charge corrections do not use TD04 at all, and instead reuse the original TD16 to TD19 document type with negative amounts.

If you are looking for a working answer rather than a legal memo, the fastest way to frame Italy credit and debit note rules is to ask what changed in the original transaction. Did the invoice need to be reduced or cancelled, did the amount need to increase, or was the original transaction part of a reverse-charge flow that has to be corrected inside the same document-type family?

Scenario	Typical document	Usual SDI treatment	Main compliance question
You need to reduce or cancel an invoice	Credit note	TD04	Does Article 26's one-year limit apply?
You need to increase the taxable amount or VAT	Debit note	TD05	Has the increase been issued and registered promptly?
The original transaction was reverse charge	Correction note with negative amounts	Reuse original TD16 to TD19 family	Should the correction stay in the original reverse-charge flow?

In day-to-day finance work, a nota di credito is the document you use when the commercial or VAT position must move downward. Typical triggers include a pricing error, a returned supply, a cancelled transaction, or non-payment in a qualifying insolvency scenario. A nota di debito does the opposite. It formalizes an upward adjustment, so it matters whenever the taxable base or VAT should have been higher than what appeared on the original invoice.

That distinction sounds straightforward, but the Italian rules become more technical once timing and SDI document logic enter the picture. The rest of this guide breaks the topic into the decisions that actually create VAT risk: whether the one-year limit applies, when a no-limit exception exists, which document type belongs in SDI, and why reverse-charge corrections follow a different path from ordinary domestic credit notes.

When the One-Year Limit Under Article 26 Applies

Article 26 of DPR 633/1972 is the rule finance teams usually end up searching for when they need to know whether an Italian credit note can still adjust VAT. In practice, the one-year limit matters when the correction is tied to a mistake in the original invoice or to a later discount or allowance that was not already built into the original contractual terms.

That means the one-year clock is most relevant in scenarios such as:

• the original invoice overstated the quantity
• the unit price was wrong
• a discount was agreed after the invoice, rather than being part of the initial contract
• the supplier needs to reduce the taxable amount because the original invoice did not reflect the commercial reality correctly

The operational question is not simply "Do I want to issue a credit note?" It is "Why am I reducing this invoice?" If the answer is that the original document was wrong, or that you are applying a later commercial reduction that falls inside Article 26's timing rule, the one-year limit becomes the first control point.

Once that term has passed, the business may still need to issue a commercial correction, but the VAT result changes. The note is treated outside the scope of VAT for the adjustment, so you may correct the taxable base without recovering VAT in the same way you could within the permitted term. For controllers and accountants, that is the difference that matters. Missing the timing rule is not just a paperwork problem. It changes the tax effect of the correction itself, and it can also change when an Italian B2B invoice is actually late and which payment-term rules still govern the balance once the underlying amount has been revised.

A practical way to decide is to separate invoice-error cases from transaction-unwinding cases. If you are fixing price, quantity, or a later non-contractual discount, you are usually in the one-year-limit territory. If the transaction was later cancelled, revoked, or became uncollectible through insolvency procedures, you may be dealing with one of the no-limit exceptions covered next.

Which Credit Note Cases Have No Time Limit

The one-year limit does not cover every reduction scenario. Italian practice draws an important line between correcting an invoice and unwinding the underlying transaction. Where the transaction is cancelled, annulled, revoked, rescinded, or otherwise withdrawn, the credit note is not treated like an ordinary late correction of a price or quantity error. Those are the cases where the time-limit analysis changes.

The same section of law also matters when the customer fails to pay because of unsuccessful insolvency or enforcement proceedings. That is why Italy credit note insolvency rules receive so much attention in specialist alerts. They are not a niche side issue. They determine when a supplier can reduce VAT after a debt has become commercially and legally compromised. For multinational finance teams, Bulgaria's bad debt VAT adjustment rules provide a useful contrast because they hinge on formal debt criteria plus recipient-side verification rather than Italy's Article 26 insolvency timing framework.

The key reform point is the 2021 change introduced by Decreto Sostegni-bis. Before that reform, suppliers often had to wait until insolvency proceedings had run their course before issuing the credit note needed for VAT recovery. Now the note can be issued at the beginning of formal insolvency proceedings, rather than at the end. For a finance team dealing with distressed receivables, that is a major timing difference.

This exception should still be applied carefully. A customer who is merely late in paying is not automatically an insolvency case. A commercial dispute, a promised future payment, or a routine aged receivable does not by itself put the supplier into the no-limit insolvency category. The question is whether the non-payment sits inside the type of formal proceeding or failed enforcement path that Article 26 recognizes.

That distinction matters for VAT reporting as well as document issuance. When a qualifying exception applies, the timing of the credit note affects the VAT period in which the adjustment is taken, or at the latest the annual VAT return. Teams that document the triggering event clearly, rather than relying on generic notes such as "customer unpaid," are much better placed to defend the treatment.

Which SDI Document Type to Use for Domestic Credit and Debit Notes

For ordinary domestic corrections, the SDI logic is usually straightforward. A credit note is normally transmitted through FatturaPA as TD04, while a debit note is generally transmitted as TD05. In both cases, the note should clearly reference the original invoice so that the correction can be traced through the tax record and the ERP workflow. If the original document also carried a virtual stamp rather than VAT, the correction review should verify whether the bollo treatment needs to change too, because Italy's imposta di bollo invoice rules depend on the EUR 77.47 threshold and the nature of the underlying transaction. Teams comparing international correction models may also want a narrower look at Vietnam's adjustment-versus-replacement e-invoice workflow, where the operational decision is framed around Article 19 notice, adjustment, and replacement paths rather than TD04 versus TD05.

This is where finance operations and implementation work meet. You are not only choosing the right legal label. You are also deciding how the correction will be classified in XML, posted in the accounting system, and matched back to the original invoice. If that foundation is wrong, downstream VAT reporting, reconciliation, and audit support become harder than they need to be.

Debit notes deserve special attention because they increase the taxable amount and related VAT. In the relevant adjustment scenarios, they function as mandatory correction documents: if the original taxable base was too low, the business needs a document that increases it, not a workaround in narrative text or an internal memo. The debit note should also be registered in the register of issued invoices, identified clearly as a debit note with the original invoice reference, and handled as a normal issued document rather than a separate informal adjustment record. Unlike the credit-note cases discussed under Article 26, this is not usually framed as a one-year-limit issue.

The document-type discipline matters because Italy runs e-invoicing at very large scale. According to the European Commission's 2024 Italy eInvoicing Country Sheet, Italy's Sistema di Interscambio processes some 2 billion B2B eInvoices per year. In a system of that size, small mapping errors become repeatable control failures, which is why teams handling domestic adjustments should understand Italy's broader FatturaPA and SDI compliance rules alongside the variation-note rules themselves.

If you are working with simplified variation documents, check the current FatturaPA technical specifications and Agenzia delle Entrate guidance rather than assuming the standard TD04 and TD05 logic answers every edge case. For most readers, though, the core domestic rule is the one that drives day-to-day compliance: TD04 for a credit note that reduces or cancels the invoice, TD05 for a debit note that increases it.

Why Some Reverse-Charge Corrections Do Not Use TD04

One of the most common implementation mistakes in this area is assuming that every Italian credit note belongs in TD04. That is not always true. When the original transaction sat in a reverse-charge flow, the correction may need to stay inside that original document-type family instead of being recast as a standard domestic credit note.

The key rule is straightforward: if the original reverse-charge transaction was reported through TD16, TD17, TD18, or TD19, the corrective document should generally reuse that same document type with negative amounts, rather than switching to TD04. That is the practical answer behind many searches for reverse charge credit note Italy.

Why does this matter? Because the correction is not just reducing a commercial invoice in the abstract. It is correcting a transaction that was already framed for SDI and VAT purposes as a specific kind of reverse-charge entry. Reusing the original TD16 to TD19 family preserves the logic of that original reporting path. Using TD04 instead may look intuitive if you are thinking only in terms of "credit note equals TD04," but it can break the consistency of the submission flow.

A useful decision sequence is:

1. Identify whether the original transaction was an ordinary domestic invoice or a reverse-charge transaction.
2. Confirm which document type was used for the original SDI reporting.
3. If the original flow was TD16, TD17, TD18, or TD19, evaluate the correction inside that same family using negative values.
4. Use TD04 only where you are genuinely dealing with a standard credit note scenario rather than a reverse-charge correction that belongs in the original structure.

This reverse-charge exception is one of the reasons the topic needs a dedicated English reference page. Many short advisories mention the rule in passing, but they do not explain it in operational terms. For teams building ERP logic or reviewing exceptions in shared services, the main lesson is simple: check the original document flow before you choose the correction code.

Registration Steps, Penalties, and a Compliance Checklist

Once you know whether the correction is a credit note or a debit note, the remaining risk is procedural. The note should point back to the original invoice, state the correction clearly, and be classified under the correct SDI document type before it is posted or transmitted. That sounds basic, but it is exactly where avoidable VAT exposure appears, especially when teams treat debit notes as informal adjustments instead of formal tax documents.

If your team needs a broader accounting refresher on what a debit note means in accounting, use that as background. In Italy, though, the operational question is narrower: has the taxable amount moved up or down, does Article 26's timing rule apply, and did the business choose the SDI code that matches the original scenario?

Penalty exposure is not theoretical. Omitted, late, or incorrect credit and debit notes can trigger a penalty equal to 70% of the VAT associated with the undocumented taxable amount, with a minimum of EUR 300. Where the violation does not affect VAT settlement, the penalty range is EUR 250 to EUR 2,000. Those figures are enough to justify a documented review step before a correction note is finalized.

For upward adjustments, late cases can be regularized through ravvedimento operoso. That does not remove the need to issue the right debit note, but it gives businesses a way to regularize the position when the taxable base and VAT should have been increased earlier.

Use this checklist before issuing or posting the note:

1. Confirm whether the event is an invoice error, a later discount, a cancellation, an insolvency case, or a reverse-charge correction.
2. Check whether Article 26's one-year limit applies, or whether an exception removes that limit.
3. Select the correct SDI route: TD04, TD05, or the original reverse-charge TD16 to TD19 family with negative amounts.
4. Reference the original invoice clearly and keep the support for the correction reason in your working papers or ERP notes.
5. Validate the VAT period impact so the adjustment lands in the correct return cycle.
6. Escalate edge cases that touch adjacent Italian VAT mechanics, including another Italy-specific VAT invoicing rule: split payment, because local invoicing rules often interact.

That checklist is the core takeaway. Italy's variation-note rules are manageable when teams classify the scenario correctly first, then let timing, document type, and VAT effect follow from that classification.