FatturaPA Document Types: The TD Codes

FatturaPA specification version 1.4 lists 20 document-type codes for the TipoDocumento element, TD01 to TD06 and TD16 to TD29, and the one a file declares decides which rules SdI applies to it. TD01 is an ordinary invoice, TD04 a credit note, TD05 a debit note. The others cover advances, professional fee notes, the documents a buyer issues for purchases from abroad, and a set of special cases. A wrong code is not a cosmetic error. It changes which checks the file has to pass.

This page is for the accountant or integration lead who has to map an accounting system's document types to Italy's, or who is reading a rejection. It lists every code the specification lists and the rules that tie a code to who the seller and buyer are. It does not say which code a particular sale needs, because that is a question of Italian VAT law. The wider file is described in FatturaPA XML Format.

What are all the codes?

Twenty, as of specification 1.4 (31 January 2025) and schema 1.2.3. The Italian names are the Agency's, the English glosses are ours.

The list has gaps on purpose. There is no TD07 to TD15 in the ordinary schema, and the simplified invoice has its own schema, which this page does not cover. Two codes arrived recently. TD28 came with specification 1.3.2 on 1 October 2022, and TD29 with 1.4 on 31 January 2025.

Which code does an ordinary sale take?

TD01 for an invoice, and TD04 or TD05 for a document that adjusts one. These three cover most of what a trading company issues.

• TD01, an invoice, is the default.
• TD04, a credit note, reduces or cancels a previous invoice. The block DatiFattureCollegate in the body is where a document names the invoice it links to.
• TD05, a debit note, adds to it.
• TD02 and TD03 are advance payments, on an invoice and on a professional fee note.
• TD06, the professional fee note (parcella), is the document a professional issues for fees.

The code a credit note carries matters for a reason that is easy to miss. SdI rejects a second document from the same seller with the same year and number as one it has already accepted, as a duplicate (error 00404). The exception is the credit note: two such documents are allowed only when one of them is a TD04. A credit note sent as TD01 with the original invoice's number is therefore a duplicate by the rule, and is rejected.

What do TD16 to TD19 mean?

They are documents the buyer issues, to complete the record of a purchase where the buyer accounts for the VAT. The Agency's names say "integration" (integrazione) or "self-invoice" (autofattura). The distinction is in who writes the document: not the seller, but the buyer, in its own name.

• TD16: integration of a domestic reverse-charge invoice (reverse charge interno).
• TD17: integration or self-invoice for services bought from abroad.
• TD18: integration for intra-Community purchases of goods.
• TD19: integration or self-invoice for purchases of goods under article 17, paragraph 2, of Presidential Decree 633/72.

For a seller outside Italy these are the codes that matter most, because they describe what the Italian customer does with a foreign supplier's invoice, not what the supplier sends. The companion page Invoicing an Italian Customer From Outside Italy puts them in that setting. The page you are reading stays with the codes themselves.

What rules tie a code to the parties?

SdI checks the seller and the buyer against the code, and rejects a mismatch. The Agency's list of checks, version 2.0, gives these rules for the codes:

These rules explain rejections that look unrelated to document types. A TD17 file whose seller block carries an Italian VAT number fails 00473, because a document for services bought from abroad cannot have an Italian seller. A TD16 file with the same VAT number on both sides fails 00471. A TD21 self-invoice with a zero-rate line fails 00474.

Which mistakes get a file rejected?

Four patterns, all visible in the checks list.

1. Everything sent as TD01. A system whose export template emits one type for every document breaks the credit note rule above, and cannot produce the documents TD16 to TD19 at all.
2. The buyer's VAT identifier missing on a type that needs it (00475). A buyer identified only by fiscal code is not enough for those types.
3. The seller's country code wrong for the type (00473), most often from copying the Italian buyer's data into the seller block of a TD17.
4. A code outside the list. The schema is a closed list, and any other value fails the format check with 00200.

Mapping the codes before the first send, with the finance team and an Italian tax adviser, is cheaper than reading the rejections afterwards.

What is still open?

Three things, as of 31 October 2026.

• Which code a transaction needs. The specification names the codes. It does not decide them. That depends on Italian VAT law and on the facts.
• The simplified invoice. It has its own schema and its own codes, which we have not read.
• Later changes. The list grew in 2020, 2022 and 2025. Check the Agency's page before you hard-code it.

What to do next

1. List the document types your system issues and map each to a code from the table.
2. Check the party rules for any type from TD16 upward before you build it.
3. Read the other three pages in this set: FatturaPA XML Format, What Is an SDI Code? and Invoicing an Italian Customer From Outside Italy.
4. To talk through e-invoicing across several countries, book a demo. The developer documentation, the tutorials and the GoRoute API show how documents are sent.

Related reading

• E-invoicing in Italy, the country page.
• FatturaPA XML Format: Structure, File Name and Signature
• What Is an SDI Code? The Codice Destinatario Explained
• Invoicing an Italian Customer From Outside Italy
• San Marino e-invoicing, the background to TD28.

Sources, all read on 31 October 2026: Agenzia delle Entrate, FatturaPA specification version 1.4 (31 January 2025), section 3.8.1 and the revision table, and schema Schema_VFPR12_v1.2.3.xsd (documentation page); the Sistema di Interscambio list of checks, version 2.0 (31 January 2025), checks 00404 and 00471 to 00476. English glosses of the Italian code names are ours and are not the Agency's.