File name and transmission data
Every invoice sent to SDI has a file name, which follows the SDI naming convention, and a DatiTrasmissione block in its header, which includes the IdTrasmittente and ProgressivoInvio fields. Invoicetronic can handle them for you or leave them to you, depending on how you send the invoice.
Two modes
| File name assigned by Invoicetronic | File name provided by you | |
|---|---|---|
| When | POST /send/xml, POST /send/json, POST /send without file_name |
POST /send/file (the uploaded file's name is used), POST /send with file_name |
IdTrasmittente |
Filled in by us if empty (IT01180680397) |
Filled in by you |
ProgressivoInvio |
Filled in by us if empty | Filled in by you |
| Transmitted XML | Rebuilt from the invoice data | Transmitted as is |
Already signed files (.p7m) |
Not accepted | Accepted: the file name is required |
Unless you have specific needs, the first mode is the simplest: leave IdTrasmittente and ProgressivoInvio empty, don't specify a file name, and we take care of the rest.
File name assigned by Invoicetronic
When you don't specify a file name, Invoicetronic acts as the transmitter:
- it generates a unique file name, with the reserved prefix
IT01180680397; - it fills in
IdTrasmittenteandProgressivoInvioonly when they are empty: values already present in the XML are never overwritten; - it rebuilds the XML from the invoice data, so that the filled-in fields are included.
You can leave the two fields empty or omit them: validation (validate=true) runs after they are filled in, so it reports no errors. If you set them yourself, your values are kept: in that case it's better to also provide the file name, so that it is consistent with them.
The assigned name is returned in the file_name field of the response.
File name provided by you
You provide the file name when you upload a file with POST /send/file, when you use file_name with POST /send, and always when the file is already signed (.p7m). In this case the file is transmitted as is, and the transmission data is up to you:
- Fill in
IdTrasmittenteandProgressivoInvioaccording to the FatturaPA technical specifications. Withvalidate=true, an invoice with these fields empty is rejected with422 Unprocessable Entity. - The file name must follow the SDI convention: country code, tax identifier, underscore, progressive number,
.xmlor.xml.p7mextension, for exampleIT01234567890_00001.xml. A non-compliant name is rejected with400 Bad Request. - The
IT01180680397prefix is reserved for names assigned by Invoicetronic: a name starting with it is rejected with400 Bad Request. - The name must be unique for SDI, not just on Invoicetronic: SDI rejects with code
00002(duplicate file name) any name it has already received, through any channel. Invoicetronic immediately rejects names already used on the platform with409 Conflict, but it can't know about names transmitted through other providers. To avoid collisions, use your own tax identifier (the one inIdTrasmittente) as prefix and a progressive number that never repeats, including against past submissions made through other channels.
In the Sandbox, only Invoicetronic's check applies, and its archive is separate from the live one: the same name can be used in both environments.
If you ask Invoicetronic to sign the invoice, the .p7m extension is added to the file name.
Issuer and third-party intermediary
The issuer and third-party intermediary data (header blocks 1.5 and 1.6) describe the relationship between you and the supplier, and remain your responsibility. Invoicetronic should not appear in these blocks, neither because it transmits the invoice nor because it signs it. If you are migrating from another provider and your XML files list that provider as third-party intermediary, remove it.
For how to fill in these blocks in your case, for example if you issue invoices on behalf of your customers, ask your tax advisor.