Italy DDT Guide: Deferred Invoicing Explained

An Italy DDT guide has to start with one core idea: a DDT, or Documento di Trasporto, is the transport document used to evidence the movement of goods, and that evidence is what makes deferred invoicing possible. When a supplier makes multiple deliveries in the same month and each shipment is backed by its own DDT, those deliveries can usually be rolled into one fattura differita. In practice, that later invoice is commonly reported as TD24 in FatturaPA, issued by the 15th day of the following month, and linked back to the relevant DDT numbers.

That matters because the DDT is not the invoice itself. It does not replace the tax document that will later pass through Italy's e-invoicing system. Instead, it proves that the goods physically moved, on a specific date, between identifiable parties. In other words, the DDT sits between logistics and invoicing. It gives the supplier documentary support for shipping now and invoicing later.

For international teams, the closest comparison is often a delivery note. That comparison is useful, but incomplete. In Italy, the DDT has a tighter connection to invoicing deadlines and document references than a generic shipment note in many other markets. If you need a broader cross-market baseline, see how delivery notes work in broader shipment and receiving workflows. The Italian workflow adds a specific legal and operational consequence: the DDT can support a later consolidated invoice rather than forcing an invoice at the moment the goods leave.

This is why the DDT matters well beyond transport paperwork. Once the deferred invoice reaches finance, the DDT numbers, delivery dates, supplier details, and customer details become the reference points for validation and reconciliation. A team that treats the DDT as a warehouse document only will miss the fact that it is also the starting record in a longer document chain.

The mandatory fields that make a DDT usable

The legal label matters less than the practical test: can this DDT prove what moved, when it moved, and between whom? If the answer is unclear, the document becomes much harder to rely on later when a deferred invoice cites it.

For readers specifically checking Italy DDT mandatory fields, the baseline list is straightforward. At a minimum, readers should expect an Italian DDT to include:

• Issue date
• A unique progressive number
• Sender details
• Buyer or recipient details
• Carrier details, when the carrier is different from the sender
• A clear description of the goods
• Quantity and nature of the goods
• The person responsible for transport

Those fields are not just formalities under the DDT framework linked to DPR 472/1996. Each one supports a later control. The date establishes when the delivery happened. The progressive number gives the shipment a traceable identifier. The sender and recipient details tie the delivery to the parties that will later appear on the invoice. The goods description and quantity make it possible to check whether the later invoice matches what was actually dispatched.

In practice, many businesses also include the reason for transport, delivery terms, or internal order references. Those details are often what make the document operationally useful, especially when the shipment is later reviewed by AP or by an ERP workflow rather than by the logistics team that created it.

This is where generic "delivery note requirements" can mislead foreign teams. A sparse delivery note might be enough to help a driver and receiver confirm a shipment, but it may not be enough to support deferred invoicing cleanly. If the document does not clearly identify the counterparties, the goods, and the shipment reference, the later invoice will have a weaker documentary chain. That is also why many teams align their internal checks with the compliance expectations associated with the Agenzia delle Entrate, even when the day-to-day issue is operational rather than purely tax-driven.

---

How multiple DDTs become one deferred invoice

The operational logic is straightforward once you separate shipment evidence from invoicing. A supplier ships goods several times during a month. Each delivery is documented with its own DDT. Instead of raising a separate invoice for every dispatch, the supplier can issue one fattura differita that consolidates those deliveries, provided the underlying DDT trail is in place.

That deferred invoice must not float free from the shipment records. It should reference the relevant DDT numbers and dates so the relationship between the goods movement and the invoice can be verified later. This is the practical core of the Italian deferred-invoice workflow: the DDT is the delivery evidence, while the invoice is the fiscal document that summarizes the billable result of those deliveries.

A simple workflow walkthrough looks like this:

1. Goods are dispatched and each shipment gets its own DDT.
2. The supplier retains the DDT references, dates, and party details for the period being billed.
3. One deferred invoice is issued for the eligible deliveries, citing the relevant DDTs.
4. The invoice is transmitted through the normal Italian e-invoicing channel and later checked against the supporting delivery trail.

In electronic invoicing terms, the standard code most readers will encounter is TD24. That is the document type normally used in FatturaPA for the standard deferred invoice flow, so when teams ask about the Italy TD24 deferred invoice process they are usually asking how DDT-backed deliveries are represented in the e-invoicing system. The invoice still moves through SDI, just like other Italian e-invoices. If you need a more technical breakdown of how TD24 deferred invoices move through Italy's FatturaPA and SDI system, that article expands on the message format side of the process.

For AP teams and ERP implementers, the important point is that the DDT and the invoice do different jobs. The DDT answers, "What shipment happened, and when?" The deferred invoice answers, "What is now being billed?" Good controls depend on keeping those roles distinct while preserving the links between them. That is why missing DDT numbers, missing delivery dates, or unclear customer references create real downstream friction even when the invoice itself looks complete.

When an immediate invoice is required, and where TD25 fits

Not every later-issued invoice qualifies as a deferred invoice. The DDT-based workflow depends on having proper delivery evidence that supports consolidation. If that documentary support is missing, businesses should be careful about assuming they can simply invoice later and call the result deferred.

That is the practical divide between fattura immediata and fattura differita. A fattura immediata is the immediate invoice route, generally used when the supplier is invoicing the transaction directly rather than relying on a DDT-backed series of deliveries. In the workflow described in the brief research, if there is no usable DDT trail, the business should expect the immediate-invoice timing rules to apply instead of the deferred-invoice logic, including the usual expectation that the invoice is issued within 12 days rather than rolled into a later monthly consolidation.

Readers should also separate TD24 from TD25. TD24 is the standard code that most teams associate with the normal deferred-invoice process backed by DDT references. TD25 is a different deferred-invoice variant, commonly discussed for triangular operations. The important point for most finance teams is not to memorize code tables in the abstract, but to ask the right operational question first: what kind of transaction happened, and what delivery evidence supports it?

For a quick comparison:

• Immediate invoice: used when the business is invoicing directly without relying on a later DDT-backed consolidation
• Deferred invoice: used when the business is consolidating deliveries that were already evidenced by DDTs
• TD24: standard code for the usual deferred-invoice flow
• TD25: special deferred-invoice variant for narrower scenarios such as triangular operations

That question prevents a common mistake. Teams sometimes focus on the invoice date alone and ignore whether the underlying shipment documentation actually supports the intended code and timing. In Italy, the correct workflow starts with the movement of goods and the documents that evidence it. Only then does the business decide whether the case fits the standard deferred-invoice route or whether an immediate invoice or another document type is the better fit.

---

Retention rules and the shift to digital DDTs

Once a DDT supports invoicing, it becomes part of the recordkeeping story, not just the transport story. Italian businesses therefore need to think about retention and accessibility, not only creation. The research behind this article points to a 10-year retention expectation, with the wider goal of keeping DDTs and related invoice evidence available for inspection and traceable over time.

That is where Article 2220 of the Italian Civil Code and DPR 633/1972 matter in practical terms. Finance teams need to preserve the documentary trail that links shipment evidence to the later invoice. If a company can no longer retrieve the DDT that supports a deferred invoice, it loses part of the proof chain that explains why the invoice was issued in that form and on that timeline.

The next shift is digitization. Italy still operates in a mixed environment where paper, PDF, email, PEC, and structured exchange can coexist, but the direction of travel is clear. For teams planning Italy DDT digitization, the pressure now comes from several directions at once. Peppol and AgID are pushing stricter validation logic for structured transport documents. e-CMR is relevant because electronic consignment workflows are expanding in cross-border road transport, including Italy's 2024 adoption for international use. The EU eFTI Regulation adds more momentum by requiring electronic freight transport information workflows by July 2027.

That trend is no longer theoretical. According to AgID's notice on Italian Peppol DDT validation controls, from February 26, 2024, DDTs that do not comply with the Italian Peppol business rules are subject to blocking controls and discarded by schematron validation. For document teams, that means digitization is not just about speed. It is about getting references, formats, and validation rules right early enough that the document can move through downstream processes without manual rescue work.

Why AP teams and ERP workflows care about DDT references

The DDT becomes most valuable when the invoice arrives and someone has to prove that the billed goods were actually delivered in the way the supplier claims. That is why AP teams, controllers, and ERP implementers should treat DDT references as structured operational data rather than as passive attachments.

At a minimum, the DDT number and delivery date help connect the supplier invoice to a real shipment event. The sender and recipient details help confirm that the commercial counterparties on the invoice align with the delivery evidence. The goods description and quantities help explain why an invoice amount looks the way it does, especially when one deferred invoice covers several dispatches. When those references are absent, inconsistent, or buried in unsearchable files, exception handling becomes slower and disputes are harder to resolve.

This is where the article's workflow lens matters. A generic tax explainer may stop at the legal definition of the DDT. In practice, the more important question for finance operations is what happens next. The later invoice has to be validated. The delivery evidence may need to be matched to goods receipts or shipment records. Reconciliation becomes more reliable when the document trail is complete. If you want a broader view of why delivery references matter in invoice matching and reconciliation controls, that guide shows the same control logic from the AP side.

A useful implementation priority list is short:

• Capture DDT numbers and delivery dates consistently
• Preserve the supporting documents for the full retention period
• Align logistics, invoicing, and AP records around the same identifiers
• Flag missing or conflicting references before the invoice is posted

That approach turns the DDT from a local shipping form into a dependable part of the wider invoice-validation chain.